New Features and Enhancements in Revenue Management Winter 2024
The following new features have been introduced in the Winter 2024 release of Revenue Management.
If you are upgrading from a previous version, see Upgrading to Revenue Management Winter 2024. This provides a summary of the items that have been added for each feature and details of any required upgrade steps.
Applying Prospective Adjustment Following Source Record Changes
If you have recognized some revenue or cost on a source record, then you change the source record's total revenue or cost, or its start or end date, the next time you generate recognition schedules the source record's "Recognizable" schedule lines might need to be updated to correct the amount that is scheduled across the remaining periods. The way these updates are calculated for Equal Split recognition templates varies depending on the template's Calculation Adjustment Type:
- If the source record's recognition template has a Calculation Adjustment Type of "Retrospective", an additional catchup adjustment is applied to the first "Recognizable" schedule line to correct the amount that should have been recognized to date
- If the source record's recognition template has a Calculation Adjustment Type of "Prospective", the values of the remaining "Recognizable" schedule lines are adjusted according to the template's calculation type.
For example, you might have a source record with a total revenue of 12000 using an Equal Split - Months recognition template over one calendar year (12 periods). This gives a monthly revenue amount of 1000. After recognizing periods 1-3, the source record's total revenue increases to 24000. The next time recognition schedules are generated, the unrecognized recognition schedule lines are recalculated as shown in this table:
|
Period |
Revenue |
Recognized |
Recalculated Revenue using Retrospective Adjustment |
Recalculated Revenue using Prospective Adjustment |
|---|---|---|---|---|
| 2024/001 | 1000 | 1000 | 1000 | 1000 |
| 2024/002 | 1000 | 1000 | 1000 | 1000 |
| 2024/003 | 1000 | 1000 | 1000 | 1000 |
| 2024/004 | 1000 | 5000 | 2333.33 | |
| 2024/005 | 1000 | 2000 | 2333.34 | |
| 2024/006 | 1000 | 2000 | 2333.33 | |
| 2024/007 | 1000 | 2000 | 2333.33 | |
| 2024/008 | 1000 | 2000 | 2333.34 | |
| 2024/009 | 1000 | 2000 | 2333.33 | |
| 2024/010 | 1000 | 2000 | 2333.33 | |
| 2024/011 | 1000 | 2000 | 2333.34 | |
| 2024/012 | 1000 | 2000 | 2333.33 | |
| Total | 12000 | 3000 | 24000 | 24000 |
If the source record's recognition template has a Calculation Adjustment Type of "Retrospective", period 2024/004 includes an adjustment to correct the amount that should have been recognized to date. In this example, 6000 should have been recognized in the first three periods but only 3000 has been recognized. The new monthly revenue amount is 2000. Therefore the revenue amount for period 2024/004 is: 3000 + 2000 = 5000
If the source record's recognition template has a Calculation Adjustment Type of "Prospective", the remaining revenue is spread equally across the remaining "Recognizable" periods: 21000 / 9 = 2333.333333
For more examples, see Generating Recognition Schedules after Revenue or Cost Has Been Recognized. For an explanation of the rules Revenue Management follows when generating recognition schedules, see The Principles of Recognition Schedule Generation.
Organization-Wide Email Address
You can control the email address that Revenue Management uses when sending emails from background processes. The email address you intend to use must be a verified email address listed on Salesforce's Organization-Wide Email Addresses page.
Enter the email address in the Organization-Wide Email Address field in the FDN Background Processing Settings custom setting. Other Certinia applications might also use the email address in this field.
If you have previously created the custom field fferpcore__BatchSettings__c.FinancialForceOrgWideEmailAddress__c for this purpose, Revenue Management will check the custom field if this packaged field is not populated. If neither field is populated, emails are sent from the email address of the user who ran the process.
Using Revenue Management with SSM for Cost Recognition
The Enabling Cost Recognition for SSM feature in Feature Console allows you to set up Revenue Management to recognize costs against SSM purchase orders.
For information about how to set up this feature, see Enabling Cost Recognition for SSM.
Scheduling Automation Configurations
If you are using Revenue Management with recognition schedules, you can now schedule automation configurations to run at regular cadences. For example, you might want to generate and recognize your recognition schedules on a daily, weekly, or monthly basis. Previously you could only run automation configurations manually. Now, when you schedule an automation configuration, a process schedule record is created. If the process schedule is active, the Next Due field shows the date and time when it is next due to be run. When a process schedule runs, a log is created. The log contains information about the outcome of the scheduled process. For information on how to schedule automation configurations, see Scheduling Automation Configurations.
You must set up a scheduled job to run the process schedules. You can schedule the service via the Foundations Setup page or via the API. Depending on when you configure the scheduled job to run, there might be a delay before due process schedules run. For example, if your process schedules are configured to run daily at midnight, but the scheduled job is configured to run daily at 08:00, there is going to be an eight-hour delay before process schedules due at midnight are picked up by the scheduled job at 08:00 the following morning.
We recommend that you run the service regularly to avoid significant delays between process schedules being due to run and being picked up by the scheduled job. For information on configuring the scheduled job, see Scheduling a Job to Run Process Schedules.
Historic Recognizable Revenue Included during Recognition
When you run recognition from the Recognition Summary grid, unrecognized values in historic periods
Refers to all periods prior to the period being recognized in the Recognition Summary grid. are now included by default. Previously, values in historic periods were not included which could result in some values never being recognized.
If you want to continue excluding values in historic periods when running recognition from the Recognition Summary grid, select the Exclude Historic RSLs from Recognition field in the Revenue Management Settings custom setting. If this field is selected, when you run recognition from the Recognition Summary grid a warning is displayed if there are unrecognized values in historic periods. You must remember to recognize the historic periods, otherwise your reporting data might be inaccurate and some source records will never be fully recognized.
For more information, see the Exclude Historic RSLs from Recognition field description in Revenue Management Settings.
Release Content
We want to help you find all of the information and resources that you need to use our products effectively.
In-App Guidance
Certinia in-app guidance uses Salesforce user engagement features to deliver Certinia content, such as tutorials and walkthroughs, directly from our products.
In this release, we've updated our in-app guidance. For more information, see Revenue Management In-App Guidance.
Certinia Trailhead
If you want to learn more about the new features in this release, see the ERP Cloud - Winter 2024 Release Highlights Certinia Trailhead module. This module will guide you through the new features in ERP Cloud.
Certinia Help Is Now Available from help.certinia.com
You can now access the Certinia Help and Technical Reference from help.certinia.com.
We have updated all the Help links included in Revenue Management Winter 2024. For more information, see Certinia Help URL.
Fixes
Fixes are listed on the Known Issues page of the Certinia Community. You can access this page from the Community Support Hub. For a brief description of the issues that have been fixed in this version of Revenue Management, see the relevant section of the Known Issues page.