SECTIONS
| If your source data is held in a Certinia standard object, this task is done by Certinia Customer Support as part of your onboarding. |
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 recognition settings records (see About Recognition Settings Records).
The data that Revenue Management requires varies depending on how your recognition templates are configured. The table below lists fields that typically need to be available on your source records (and mapped via a recognition settings record) to run recognition successfully. You might need to create additional custom fields on your source objects if appropriate fields are not already available.
The Recognition Settings Field column identifies which field on the recognition settings record each source object field must be mapped to.
|
Source Object Field |
Mandatory, Conditional, or Optional |
Notes |
Recognition Settings Field |
|---|---|---|---|
|
A numeric field that contains the source record's total revenue (or total cost for cost recognition). |
Mandatory |
For Revenue:
For Cost:
|
|
| 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. |
Active Field |
| Fields containing the GLA codes that values for the source record will be posted to on the Balance Sheet and Income Statement. | Mandatory |
For Revenue:
For Cost:
|
|
| Fields containing the source record's start and end dates. | Conditional | These fields are required when using the Equal Split template type. |
Start Date End Date/Deliverable Date |
| A field containing the source record's % complete. | Conditional | This field is required when using the % Complete template type. | % Complete |
| A field containing the date the source record is delivered. | Conditional | This field is required when using the Deliverable template type. | End Date/Deliverable Date |
| 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". |
Completed Field |
| A field that indicates the source record's currency (document currency). | Conditional | This field is required if your Salesforce org is multi-currency. | Document 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 cost, so that currency exchange gains and losses do not occur. See Using Historic Currency Exchange Rates for Recognition for more information. |
Home Currency and Document Rate Dual Currency and Dual Rate |
| 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. | SSP |
| A field containing the source record's company. |
Conditional See Note 1 |
This field is required for recognition schedules. The Recognize Schedules process creates separate recognition transactions for each combination of company, currency and recognition stream.
Otherwise this field is optional and might be useful for reporting purposes.
The value is held as text on recognition transaction lines. |
Company |
| A date or date/time field containing the source record's opening balance cutoff date. | Optional | This field is only used with recognition schedules. See Opening Balances for Recognition Schedules. | Opening Balance Cutoff Date |
| A boolean or formula field that indicates whether the source record is on hold. If using a formula field, the formula's return type must be Checkbox. | Optional | This field is only used with recognition schedules. | On Hold |
| A lookup, picklist, or text field containing a value that can be used to group source records when creating recognition transactions via Recognize All (and true-up). | Optional |
The Recognize All process creates separate recognition transactions for each combination of currency and recognition stream, and this additional field if used. The deferred revenue true-up process also applies these grouping rules. |
Grouped By |
| A numeric field to store the source record's Revenue Recognized to Date Value (or Cost Recognized to Date Value for cost recognition). | 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 recognition transaction lines are committed for the source record. This field is required if you intend running deferred revenue true-up. |
For Revenue:
For Cost:
|
| A boolean that can be set when the source record is fully recognized. | 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 and cost become fully recognized. The source record is then ignored by the retrieval process. | Recognition Complete |
| A numeric or currency field to store the total revenue recognized to date value or total cost recognized to date value for a primary level source record. | Optional |
This field can be useful for reporting in scenarios where the primary level and the lower level objects do not have a direct master-detail relationship. For example, you might want to define this field for PSA projects if you recognize revenue on milestones, timecards, expenses, or miscellaneous adjustments. When there is a master-detail relationship between the records, we recommend not using this approach. In this case, it is best practice that you create a roll-up summary field on the primary level object. For example, you would choose this approach for billing contracts in Billing Central. |
For Revenue:
For Cost:
|
|
Numeric fields to store the source record's Revenue Recognized to Date Value in home and dual currencies. When you enable the Deferred Revenue True-Up feature in Feature Console, the Revenue Recognized to Date (Home) and Revenue 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 recognition transaction lines with amounts in home and dual currencies are committed for the source record. |
Revenue Recognized to Date Value (Home) Revenue Recognized to Date Value (Dual)
|
| 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. |
Deferred Revenue to Date Deferred Revenue to Date (Home) Deferred Revenue to Date (Dual) |
|
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. |
Include in True-Up |
| 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 recognition transaction lines. | Account |
| 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 recognition transaction lines. | Product |
| 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 recognition transaction lines. If you are using 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. | Analysis Item 1-4 |
For more information about how to create mappings to these fields on your chosen source objects, see Creating Recognition Settings.