Reconciliation Reports for Technical Users

Technical users, such as a system administrator, can use reports to identify technical issues that cause data inconsistency between different components of Revenue Accounting.

Report A

Item	Details
Report name	Revenue Postings and General Ledger
Intended users	Technical users
Selection criteria	Company code (required): You can select only one company code. Fiscal year and period (required): You can run reconciliation for only one period at a time. Accounting principle (required): You can select only one company code. Revenue reconciliation key: You can run reconciliation against data that is associated with specific revenue reconciliation keys. Revenue reconciliation keys are part of the technical implementation of the Revenue Accounting system. For more information, see the Revenue Reconciliation Keys section. Run in background: This search option is not part of the selection criteria. Instead, this is a report switch that controls whether the report runs in the background. When this option is enabled, the report creates a background job and redirects you to the job details page. This option is for jobs that involve a large volume of data and take a long time to complete. In this case, you can start a background job and check its status at a later time.
Comparison for reconciliation	This report compares the Posting table and the FI documents posted to the general ledger. The report matches records from both sides, by account assignment fields, G/L account, and amount. If records have the same account assignment fields and G/L account but have different amounts, they are identified as a difference. Or, if a record from one side does not have a match from the other side, it is also identified as a difference.
Indication of differences	The report displays a line for each difference, indicated with a red traffic light. Only differences are displayed in the report. For each difference, items from the two sides are paired together. For the Posting table side, performance obligations are listed. For the general ledger side, the corresponding line item in the FI document is displayed. A difference line is displayed that indicates the difference amount.
Reconciliation action	This type of difference may occur because of technical issues. However, it can also occur because of inconsistent account assignment data. In this case, you can perform a reversal posting job against the previous posting job, correct the account assignment, trigger a reprocessing of the account assignment, and then perform a revenue posting job again. Alternatively, you can make manual postings to fix the differences.

Revenue Reconciliation Keys

Revenue reconciliation keys are part of the technical implementation of the Revenue Accounting system. Each reconciliation key is identified by a 10-character string. The reconciliation key tracks transactions relating to contract creation, fulfillment, and posting for a certain accounting period, for a certain company code, and under a certain accounting principle.

Posting Table

Before posting FI documents to the general ledger for revenue-related transactions, the system tracks these transactions and prepares revenue posting data in a table, known as the Posting table. The Posting table represents the revenue accounting perspective of the posting data. Each record includes information extracted from revenue accounting data, such as a posting category that indicates why this posting is needed, the G/L account used for the posting, and account assignment data.

Report B

Item	Details
Report name	Logistics and Revenue Accounting
Intended users	Accountants
Selection criteria	Company code: You can perform reconciliation for specific company codes. Accounting principle: You can perform reconciliation against a specific accounting principle. Start date of reconciliation: This reconciliation report checks data of a time range starting from the specified date up to the present time. If the report finds no difference for the time range, it marks the end time as a “last good time” to indicate all data up to that time is correct. By default, the report starts from the point that was verified as correct the last time. You can specify a time earlier than the last checked time.
Comparison for reconciliation	Revenue Accounting tracks revenue-related transactions by using its own objects. Certain technical issues may cause this data to be inconsistent with the data in the operational system. This reconciliation report performs the following checks: Compares the quantities and amounts of revenue accounting contracts and performance obligations with the quantities and amounts of corresponding operational documents (such as sales orders) Compares the invoiced amounts tracked by Revenue Accounting with the actually invoiced amounts passed from the operational system Compares the fulfillment tracked by Revenue Accounting with the fulfillment events passed from the operational system, in terms of quantities
Indication of differences	The report displays results in several sections, each for a check item. The amounts and quantities that involve differences are highlighted in red.
Reconciliation action	If this report finds any inconsistencies, you may have to manually fix this issue. For example, you can reprocess certain revenue accounting items, manually edit corresponding performance obligations, or start another revenue posting run for the checked period.

Note Note

This reconciliation report is typically scheduled for the end of the period, when the operational system stops processing more events for that period. While this report is running, make sure that no more revenue-related events are passed from the operational system.
This reconciliation report runs as a background job. You can view the job details to see the report results.

End of the note.