Period-End Close in SAP RAR: A Practical Checklist

Period-end close is where every weakness in a revenue accounting process becomes visible. Missing fulfillment events, unprocessed items, or unexplained differences all surface when finance tries to close the books. With SAP Revenue Accounting and Reporting (RAR), a structured close process makes the difference between a predictable close and a last-minute search for errors.

This checklist covers the key steps. The exact sequence and programs depend on the release and configuration, but the logic applies to most implementations.

Before Period End: Preparation

1. Review open revenue accounting items

Check the RAI monitor for items that are not yet processed or are in error. Resolve errors before period-end processing starts.

2. Confirm completeness of source data

Ensure that all relevant orders, deliveries, service confirmations and invoices for the period have been transferred from source systems – including non-SAP sources.

3. Check fulfillment events

Verify that deliveries, goods issues, and service completions have been recorded. Missing fulfillment means revenue is not recognized.

4. Review contract changes

Identify modifications, terminations, or price changes during the period and confirm they are reflected correctly.

5. Update SSP data if required

If standalone selling prices are reviewed periodically, ensure updated values are in place before processing.

During Close: Processing

6. Process remaining RAIs

Run final RAI processing so that all contracts and performance obligations are up to date.

7. Run fulfillment and time-based processing

Ensure time-based performance obligations are updated for the period and progress-based obligations reflect the current status.

8. Transfer revenue

Run the revenue transfer for the period so that revenue to be recognized is determined for each performance obligation.

9. Calculate contract assets and liabilities

Run the calculation of contract balances at contract level.

10. Post to the general ledger

Run the posting process to transfer revenue, contract asset and liability postings, and reclassifications to the general ledger.

11. Check posting results

Review posting logs for errors and ensure all postings were transferred successfully.

After Processing: Reconciliation and Review

12. Reconcile with source systems

Compare billed amounts in source systems with invoice information in RAR.

13. Reconcile with the general ledger

Compare RAR balances – revenue, contract assets, contract liabilities, and clearing accounts – with general ledger balances.

14. Analyze clearing accounts

Billing clearing accounts should reflect expected timing differences only. Unexpected balances point to process or configuration issues.

15. Review significant contracts

Review large or complex contracts, as well as contracts with modifications during the period.

16. Analyze changes

Compare revenue and contract balances with the prior period and with expectations. Investigate unusual movements.

17. Prepare disclosure data

Extract information for disclosures, such as disaggregation of revenue, contract balances, and remaining performance obligations.

18. Close the period in RAR

Once all steps are complete, close the revenue accounting period so that no further changes can affect it.

Typical Issues and How to Prevent Them

• RAI errors found at period end – Daily monitoring and clear ownership

• Missing fulfillment events – Process checks in source systems

• Unexplained clearing balances – Regular reconciliation during the month

• Late contract changes – Cut-off rules and communication with sales

• Manual corrections – Root cause analysis after each close

Making the Close Faster

• Move work into the month. Monitoring and reconciliation should not wait for period end.

• Automate checks. Standard reconciliations and plausibility checks can run automatically.

• Use exception-based review. Focus attention on deviations rather than reviewing everything.

• Document and improve. Every close is an opportunity to remove a recurring issue.

Related Articles

• Revenue Accounting Items: Processing and Error Handling

• SAP RAR Architecture: From Source Documents to Postings

• SOX Controls for Revenue Processes in S/4HANA

The Bottom Line

A reliable period-end close in SAP RAR is the result of a clear sequence, continuous monitoring during the month, and systematic reconciliation. Companies that treat revenue accounting as a daily process rather than a period-end task close faster and with fewer surprises.

Want to make your SAP RAR close faster and more reliable? Talk to our experts.