RAR Classic (Add-On) vs. RAR in SAP S/4HANA

RAR in SAP S/4HANA keeps the ASC 606 accounting logic of the classic add-on on SAP ERP, but adds a new architecture underneath: optimized contract management, optimized inbound processing, direct posting to the Universal Journal, and Fiori reporting. The key decision when moving is whether to stay classic or switch to optimized.

Many companies implemented SAP Revenue Accounting and Reporting (RAR) on SAP ERP when ASC 606 and IFRS 15 became effective. Now that they are moving to SAP S/4HANA, the question is what changes in revenue accounting. This article compares the add-on with RAR in S/4HANA. How to move existing contracts is covered separately in our SAP RAR series.

RAR as an Add-On on SAP ERP

On SAP ERP, RAR is delivered as an add-on, "SAP Revenue Accounting" (REVREC), with version 1.3 as the latest release. Further development came through support packages and feature packs, which added functionality such as:

• Intercompany and drop shipment processing

• Additional fulfillment types and fulfillment events

• Enhanced analysis and monitoring tools for rules and revenue accounting items

• Migration support and performance improvements for large contracts

The add-on architecture uses what is now called classic contract management and classic inbound processing. Revenue accounting items (RAIs) are processed in scheduled jobs or via the RAI monitor, and posting runs through the revenue accounting subledger to the general ledger.

RAR in SAP S/4HANA

From S/4HANA 1809, RAR is part of S/4HANA itself, delivered as software component REVREC. Initially, functionality was close to RAR 1.3. Since then, SAP has added several architectural changes:

• Optimized contract management (OCM) in more recent releases, depending on release and configuration, with performance improvements and day-based contract modifications.

• Optimized inbound processing (OIP), which processes operational documents in real time and uses a static table set instead of dynamically generated tables and APIs.

• Direct posting in more recent releases, which posts straight to the Universal Journal without persisting entries in the revenue accounting subledger. It requires OCM and is applied prospectively.

• Parallelization framework for selected programs, which changes where job logs are found.

• SAP Fiori reporting, with additional standard reports such as posted amounts by contract and by POB type, and a revenue accounting overview.

SAP recommends the optimized variants for new implementations. Contract-based revenue recognition in SAP S/4HANA Cloud Public Edition is built exclusively on the optimized architecture. The availability of individual features depends on the release; verify the details for your target release.

Side-By-Side

• Delivery – RAR add-on on SAP ERP: Add-on (REVREC) on SAP ERP; RAR in SAP S/4HANA: Part of S/4HANA

• Contract management – RAR add-on on SAP ERP: Classic; RAR in SAP S/4HANA: Classic or optimized

• Inbound processing – RAR add-on on SAP ERP: Classic, job- or monitor-driven; RAR in SAP S/4HANA: Classic or optimized, real-time

• Posting – RAR add-on on SAP ERP: Via revenue accounting subledger; RAR in SAP S/4HANA: Subledger or direct posting to the Universal Journal

• Reporting – RAR add-on on SAP ERP: Classic reports; RAR in SAP S/4HANA: Fiori apps and Universal Journal reporting

• Data model – RAR add-on on SAP ERP: ERP finance tables; RAR in SAP S/4HANA: Universal Journal (ACDOCA)

Classic or Optimized After the Move?

This is the most important design decision for RAR customers moving to S/4HANA. For customers coming from RAR on SAP ERP, keeping the classic functionality may be the stronger choice in some cases, because existing enhancements can be affected and may need to be reimplemented.

Considerations:

• Enhancements. Custom BAdI implementations and BRFplus extensions built for the classic architecture need to be assessed against OCM and OIP.

• Data model changes. SAP changed technical details of the data model in the optimized architecture, which can affect custom code.

• Volume and performance. Optimized processing targets performance and real-time processing. Assess the posting mode for your volumes before deciding on direct posting.

• Future direction. New functionality is focused on the optimized architecture. Staying classic may reduce effort now but may defer work to a later phase.

• Process changes. Real-time inbound processing changes how errors surface and who handles them. Period-end checklists, monitoring, and SOX control documentation need to be updated.

What Stays the Same

The accounting model does not change. Revenue contracts, performance obligations, SSP-based allocation, fulfillment types, deferral methods, and contract asset and liability calculation follow the same ASC 606 logic. BRFplus remains the rule engine for POB derivation, SSP, and account determination. Your accounting policies remain valid; what changes is how the system executes them. The same applies to lessor leasing in RAR under ASC 842 and IFRS 16, which runs without additional software in either architecture.

Pitfalls

• Treating RAR as a pure technical conversion. The move is the right time to review contract design, POB types, and BRFplus rules.

• Ignoring custom code. Enhancements are the most common source of surprises.

• Switching to direct posting without analysis. It changes reconciliation and period-end steps and is applied prospectively.

• Forgetting the auditors. A change in revenue system architecture is a change in ICFR. Involve them early.

The Bottom Line

The RAR add-on on SAP ERP and RAR in S/4HANA share the same ASC 606 logic, but S/4HANA adds optimized contract management, real-time inbound processing, direct posting, and Fiori reporting on the Universal Journal. The key decision is whether to stay classic or move to optimized, and it depends largely on your enhancements, volumes, and long-term roadmap. At Revident, we approach this decision with human-governed automation and a clear view of the controls your auditors will expect.

Related terms: Universal Journal · BRF+ · Revenue Accounting Item (RAI)

Related articles: Reconciling SAP RAR with the General Ledger

Moving RAR from SAP ERP to S/4HANA? Talk to our experts.