SECTIONSNew Features and Enhancements in Revenue Management Spring 2024
The following new features have been introduced in the Spring 2024 release of Revenue Management.
If you are upgrading from a previous version, see Upgrading to Revenue Management Spring 2024. This provides a summary of the items that have been added for each feature and details of any required upgrade steps.
Additional Filtering Options for Revenue and Cost Recognition
You can now filter the Recognition Summary grid, automation processes, and the RevenueScheduleAutomationService by recognition method: % Complete, Deliverable, Equal Split. This means that you can, for example, process source records that use Deliverable and Equal Split templates whilst holding off processing source records that use % Complete templates until you have checked their latest % Complete values.
To enable filtering by recognition method, you must select the Group Transactions by Recognition Method field in the Revenue Management Settings custom setting. Recognition transactions will then be grouped by recognition method in addition to grouping by company, currency and recognition stream.
Analysis Item Fields Added to Recognition Schedule
The fields Analysis Item 1-4 have been added to the Recognition Schedule object so that they can be used when reporting on recognition schedules.
Lock the Value of Historic Schedules When Source Records Using Retrospective Adjustment Change
In Winter 24, the Prospective Adjustment calculation type was added for Equal Split templates. When using this calculation type and recognition schedules are regenerated after changes to source records, periods that end before the generate date are not changed regardless of their status. In Spring 24 this rule is applied to the Retrospective Adjustment 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. This gives a monthly revenue amount of 1000. You recognize the first period (Status=Complete). During period 4, you double the source record's value to 24000 and regenerate recognition schedules. Notice the difference between the old and new behavior when using the Retrospective Adjustment calculation type:
- Prior to Spring 24, the catchup adjustment was made in the earliest recognizable period (2024/002).
- From Spring 24, the catchup adjustment is made in the generate period (2024/004). Earlier periods are unchanged regardless of their status.
|
Period |
Scheduled Revenue |
Status | Prior to Spring 24 | From Spring 24 |
|---|---|---|---|---|
| 2024/001 | 1000 | Complete | 1000 | 1000 |
| 2024/002 | 1000 | Recognizable | 3000 | 1000 |
| 2024/003 | 1000 | Recognizable | 2000 | 1000 |
| 2024/004 | 1000 | Recognizable | 2000 | 5000 |
| 2024/005 | 1000 | Recognizable | 2000 | 2000 |
| 2024/006 | 1000 | Recognizable | 2000 | 2000 |
| 2024/007 | 1000 | Recognizable | 2000 | 2000 |
| 2024/008 | 1000 | Recognizable | 2000 | 2000 |
| 2024/009 | 1000 | Recognizable | 2000 | 2000 |
| 2024/010 | 1000 | Recognizable | 2000 | 2000 |
| 2024/011 | 1000 | Recognizable | 2000 | 2000 |
| 2024/012 | 1000 | Recognizable | 2000 | 2000 |
| Total | 12000 | 24000 | 24000 |
For more information about the rules followed when generating recognition schedules, see The Principles of Recognition Schedule Generation.
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.
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.