| If your source data is held in a FinancialForce standard object, this task is done by FinancialForce Customer Support as part of your on-boarding. |
Revenue Management requires certain data from your source records to perform the recognition and forecasting calculations. For example, if your source records are projects Revenue Management typically needs to know a project's start date, end date, and total revenue. To make this data available to Revenue Management, an administrator creates mappings to the relevant fields on the source objects. These mappings are defined in settings records (see About Settings Records).
The data that Revenue Management requires varies depending on how your templates are configured. The table below lists fields that typically need to be available on your source records (and mapped via a settings record) to run revenue recognition successfully. You might need to create additional custom fields on your source objects if appropriate fields are not already available.
|
Source Object Field |
Mandatory, Conditional, or Optional |
Notes |
|---|---|---|
|
A numeric field that contains the source record's total revenue (or total cost for cost amortization). |
Mandatory | |
| A field whose value indicates whether or not the source record is active and will therefore be included in the recognition process. | Mandatory |
For example, this might be a boolean and whether it is True or False determines whether the source record is included in the recognition process. |
| Fields containing the GLA codes that values for the source record will be posted to on the Balance Sheet and Income Statement. | Mandatory | |
| Fields containing the source record's start and end dates. | Conditional | These fields are required when using the Equal Split template type. |
| A field containing the source record's % complete. | Conditional | This field is required when using the % Complete template type. |
| A field containing the date the source record is delivered. | Conditional | This field is required when using the Deliverable template type. |
| A field whose value indicates whether or not the source record is completed and will therefore be included in the recognition process. | Conditional |
This field is required when using the Deliverable template type. For example, this might be a picklist with the values "Not Started", "In Progress", and "Finished" but a source record is only included in the recognition process when its value is "Finished". |
| A field that indicates the source record's currency (document currency). | Conditional | This field is required if your Salesforce org is multi-currency. |
| Fields containing up to two reporting currencies (home and dual) and associated exchange rates. | Conditional | These fields are required if you want to use historic exchange rates when recognizing revenue and amortizing cost, so that currency exchange gains and losses do not occur. See Using Historic Currency Exchange Rates when Recognizing Revenue for more information. |
| A numeric field containing the source record's standalone selling price. | Conditional | This field is required if you intend using revenue contracts and performance obligations. |
| A numeric field to store the source record's Recognized to Date Value (or Amortized to Date Value for cost amortization). | Conditional |
It is best practice to include this field on your source objects because it is useful for reporting. The value is updated each time revenue recognition transaction lines are committed for the source record. This field is required if you intend running deferred revenue true-up. |
|
Numeric fields to store the source record's Recognized to Date Value in home and dual currencies. When you enable the Deferred Revenue True-Up feature in Feature Console, the Recognized to Date (Home) and Recognized to Date (Dual) fields are added to your selected source objects for this purpose. |
Conditional | These fields are required if you intend running deferred revenue true-up. The values are updated each time revenue recognition transaction lines with amounts in home and dual currencies are committed for the source record. |
| Number fields containing the source record's deferred revenue to date in document, home, and dual currencies. | Conditional | These fields are required if you intend running deferred revenue true-up. |
|
A checkbox to indicate if the source record should be included in deferred revenue true-up calculations. When you enable the Deferred Revenue True-Up feature in Feature Console, the Include in True-Up checkbox is added to your selected source objects for this purpose. |
Conditional |
This field is required if you intend running deferred revenue true-up. |
| A boolean that can be set when the source record is fully recognized (and fully amortized). | Optional | It is best practice to include this field because it improves record retrieval performance. It is set to True when the source record's revenue becomes fully recognized (and cost becomes fully amortized). The source record is then ignored by the retrieval process. |
| A lookup, picklist, or text field for grouping source records when using the Recognize All process. | Optional | The Recognize All process creates separate revenue recognition transactions for each combination of currency and revenue stream, and this additional field if used. See About Recognize All for more information. |
| A lookup field containing the Salesforce account on the source record. |
Optional See Note 1 |
Useful for reporting purposes. Allows you to look up to the Salesforce account from revenue recognition transaction lines. |
| A lookup field containing the product on the source record. |
Optional See Note 1 |
Useful for reporting purposes. Allows you to look up to the product from revenue recognition transaction lines. |
| A field containing the source record's company. |
Optional See Note 1 |
Useful for reporting purposes. The value is held as text on revenue recognition transaction lines. |
| Up to four fields contain reporting values on the source record. |
Optional See Note 1 |
Useful for reporting purposes. The values in these fields are held as text in the Analysis Item 1-4 fields on your revenue recognition transaction lines. If you are using FinancialForce Accounting with Revenue Management, you might want to use the Analysis Item 1-4 fields to populate the Dimension 1-4 fields on journal line items. |
For more information about how to create mappings to these fields on your chosen source objects, see Creating Settings Records.