End-to-End Automation of Recognition Schedule Processes

If you are using Revenue Management with recognition schedules, an automation service can handle the end-to-end process from generating and recognizing the recognition schedules through to creating Accounting journals.

The processes that can be run via the automation are:

Sequential Order

Process
1 Delete Schedules Where Source Unavailable
2 Generate Schedules
3 Recognize Schedules
4 Summarize Transactions
5 Create Journals

The processes always run in the sequential order shown in the table above, but you can choose which process to start from and which process to finish at. For example, if your org uses a customization to post recognition transactions to a third party accounting system you might want to automate processes 1-3 only.

You can start the automation from the Revenue Recognition page, or via the API:

  • For information about starting it from the Revenue Recognition page, see Launching the Automation Process.
  • For information about starting it from the API, see Running the Automation via the API. When running it from the API, you can specify additional configuration parameters including filters to run the processes for specific companies and currencies.
Warning:

Before you start using this automation Revenue Management must be set up to generate recognition schedules, and to recognize revenue and cost against recognition schedules. For setup information, see Setting up Revenue Management, Additional Setup for Generating Recognition Schedules, and Recognize against Recognition Schedules.

If you intend creating Certinia Accounting journals from the recognition transactions, the RT To Journal Integrations must also be enabled and working. For more information, see RT to Journal Integrations Overview and Summarized RT to Journal Integration Overview.

Processes Available for Automation

This section provides more information about the processes that can be run by the automation.

The automation runs each process asynchronously.

Delete Schedules Where Source Unavailable

The Delete Schedules Where Source Unavailable process ensures that obsolete recognition schedules do not accumulate and affect your data.

A source record might be unavailable for any of the following reasons:

  • The source record has been deleted.
  • The source record is no longer marked as active for recognition.
  • The source record has had its recognition template removed.

For more information about what happens when you run this process, see Deleting Obsolete Recognition Schedules.

Generate Schedules

The Generate Recognition Schedules process creates or updates recognition schedules for all valid source records in the org.

The process generates a recognition schedule per source record, with separate recognition schedule lines for each period that the source record covers. If a recognition schedule already exists for a source record, the process updates it to reflect the latest source record details.

Recognize Schedules

The Recognize Schedules process recognizes revenue and cost on all valid recognition schedule lines up to the current period. For example, if the process runs in February, revenue and cost scheduled up to and including January is recognized. The recognition period in this example is set to January. The recognition date is set to the date the process runs.

Note:

The Recognize Schedules process creates recognition transactions and commits them. There is no opportunity to review the "In Progress" transactions before they are committed.

Summarize Transactions

If summarization is enabled, the Summarize Transactions process summarizes a recognition transaction if it meets all the following criteria:

  • The transaction was created by the Recognize Schedules process.
  • The transaction's Recognized Date is within the last 30 days.
  • The transaction's status is "Committed".
  • The transaction is not already summarized.

The batch size is controlled by the Schedules Transaction Summary Batch Size field in the Revenue Management Batch Settings custom setting.

For information about how transaction lines are grouped for summarization, see Recognition Transaction Summaries.

Note:

The Summarized RT to Journal Integration must be enabled and working if you intend creating journals from recognition transaction summaries rather than from recognition transaction lines.

Create Journals

The Create Journals process creates Accounting journals from a recognition transaction if it meets all the following criteria:

  • The transaction's status is "Committed".
  • The transaction has a valid Grouped By value.
  • The transaction is not already linked to a journal.

Separate journals are created for revenue and cost amounts. The journals are created with the status "In Progress".

The batch size is controlled by the Schedules Create Journals Batch Size field in the Revenue Management Batch Settings custom setting.

Note:

Journals are created from recognition transaction summaries or from recognition transaction lines depending on how the automation is configured. The relevant RT to Journal Integrations must be enabled and working for journals to be created successfully.