RT to Journal Integrations Overview

There are two RT to Journal Integrations between Revenue Management and Certinia Accounting. There are dependencies between them so if you enable one you must also enable the other. The two integrations are:

  • The RT to Journal Integration allows you to create Accounting journals for revenue amounts on committed recognition transactions.
  • The RT to Journal Integration for Cost allows you to create Accounting journals for cost amounts on committed recognition transactions.
Note:

When using these integrations, journal lines are created from recognition transaction lines not from recognition transaction summaries.

To set up these integrations you must enable Feature Console features for Certinia Accounting and Revenue Management. For more information, see Setting up the RT to Journal Integrations.

After completing the setup, you can create revenue and cost journals from a recognition transaction's detail page and from the list view. You can only create journals for recognition transactions with the status "Committed". The journals are created with the status "In Progress" and have a type of either “Revenue Recognition“ or ”Cost Amortization”. Separate journals are created for revenue and cost amounts. If a recognition transaction has lines with both revenue and cost amounts, separate revenue and cost journals are created from it.

When journals are created from recognition transactions, information is passed between Revenue Management and Accounting via Foundations. For information about which details are passed between these applications, view the publications and subscriptions for the Journal.Create message type on the Message Types tab of the Foundations Administration application. If you have custom fields on your recognition transaction lines and you want to map their values to journal lines, add them to the CreateJournalFromRRT publication for revenue journals, and to the CreateJournalFromCostRRT publication for cost journals.

Each recognition transaction and its resulting journals are linked at header and line level by lookup fields. The recognition transaction has lookups to the revenue and cost journals that have been created, and each recognition transaction line has lookups to the corresponding revenue and cost journal line items. Similarly, the journal and journal line items have lookups to their corresponding recognition transaction and transaction lines. The Journal Status and Journal Date are also recorded on the recognition transaction.

Recognition Transactions Must Be Grouped by Company

In the FFA subscription to the Journal.Create message type, the mappings for Journal Currency and Period are resolved in relation to Company. Therefore it is imperative that recognition transactions are grouped by a field that identifies a source record's company.

  • If you intend creating recognition transactions using the Recognize Schedules process, the recognition settings records for your source objects must have Company mapped to a field that identifies a source record's company.
  • If you intend creating recognition transactions using Recognize All, the recognition settings records for your primary source objects must have Grouped By mapped to a field that identifies a source record's company.
  • If you intend creating recognition transactions from the Recognize Revenue page, the RM Grouped Transactions feature in Feature Console must be enabled, and you must group your source data on the Recognize Revenue page by a field that identifies a source record's company.

The process to create journals will fail if the correct company cannot be identified on recognition transactions.