What SAP RAR Support Covers: Scope of an AMS Engagement

Once SAP Revenue Accounting and Reporting (RAR) is live, the project team moves on – but revenue keeps flowing through the system every day. Orders, fulfillments, and invoices become revenue accounting items, contracts are updated, and the revenue posting run feeds the general ledger. Someone has to keep that chain healthy.

Application management services (AMS) for RAR are often contracted with a scope copied from a generic SAP support agreement. That rarely fits. RAR sits between operational systems and the financial statements, so its support has to combine system knowledge with ASC 606 (and, for lessors, ASC 842) judgment. This article outlines what a sound RAR support scope includes.

Four Ticket Types, Four Different Processes

Most support models follow ITIL terminology, and it helps to keep the categories clean:

• Incident: an unplanned interruption to a service or a reduction in its quality – for example, revenue accounting items stuck in error, or a posting run that fails.

• Service request: a standard request for information, advice, access, or a pre-approved routine task, such as reprocessing a defined set of items or running a report on request.

• Problem: the cause, or potential cause, of one or more incidents. Problem management asks why the same error keeps returning.

• Change: any addition, modification, or removal that could affect the service – from a new BRFplus rule to an adjusted account determination.

In RAR, the distinction matters because the fix for an incident (correct one contract) is often not the fix for the problem (correct the configuration or source data that keeps creating faulty contracts). An AMS scope that only covers incidents keeps the team busy without making the system better.

What Daily Operations Should Cover

Monitoring the inbound flow. Revenue accounting items must reach processable status before RAR can process them. Items that fail checks – unknown company code or currency, a missing order item for an invoice, an undeterminable profitability segment – stay in raw status. Support should monitor these queues continuously, not only at month end.

Contract errors and review items. RAR validates contracts and performance obligations when they are created or changed and provides an error worklist. Revenue posting can be suspended for affected performance obligations, and contracts can be reprocessed once the underlying configuration is corrected. Working these lists is a core support task.

Consistency checks. RAR includes a consistency monitor that flags contracts with data inconsistencies, such as differences after allocation. Resolving its findings before close belongs in scope.

Interfaces. Items may come from SD, billing systems, or non-SAP sources. The scope should state who owns each interface on each side.

Period-End Support

The close is where RAR support earns its keep. Typical activities include monitoring the transfer and processing jobs, the revenue posting run, and the calculation of contract assets and liabilities; resolving posting errors; and supporting the opening and closing of revenue accounting periods. Some steps depend on others – opening a new period can be blocked, for example, while reconciliation keys for the posting period are still open.

The detailed close sequence belongs in a checklist of its own; for AMS scope, the key point is availability. Support capacity should be planned around the close calendar, with defined response times on close days and clear escalation paths to the controller who signs off revenue.

Change Requests and Enhancements

New products, new contract types, pricing changes, and organizational changes all reach RAR eventually. The AMS scope should cover:

• Configuration changes: performance obligation types, BRFplus rules, account determination, and reconciliation settings.

• Enhancements of custom programs: many landscapes rely on custom upload programs, lifecycle programs, or audit reports around RAR. These need an owner who understands both the code and the accounting.

• Regression testing: every change to revenue logic should be tested against representative contracts before it reaches production.

For US public companies, change handling is also a control topic. Program change management is one of the IT general control areas that auditors test under SOX, so tickets, approvals, test evidence, and transports need to be documented in a way that holds up in an audit.

Accounting Judgment Within Support

A RAR ticket often starts as a technical question and ends as an accounting one: Is this allocation correct? Should this modification be prospective? Support should be able to explain system results in ASC 606 or ASC 842 terms, while decisions on accounting policy remain with the company's accounting team. A clear rule helps: support explains and proposes, the controller decides.

Lessor Leasing in RAR

Where RAR also handles lessor accounting – operating, sales-type, and direct financing leases under ASC 842, and operating and finance leases under IFRS 16 – the support scope must cover lease-specific scenarios: modifications, early terminations, and the integration with asset accounting. In our experience, these scenarios need support staff who know both the lease standards and how they are modeled in RAR without additional software.

How Automation Fits

Classifying errors, collecting context, and drafting root-cause notes are repetitive tasks that Agentic Finance approaches can take over. In a human-governed model, AI prepares the analysis and the proposed fix, and an accountable person approves any change to revenue data or configuration.

What to Define in the Contract

• Ticket categories, priorities, and response times – with stricter levels during close.

• Responsibilities between AMS, internal IT, business users, and interface owners.

• Problem management: who analyzes recurring errors, and how often.

• Change process and documentation standards aligned with SOX requirements.

• Knowledge management: runbooks, known errors, and documented workarounds.

The Bottom Line

RAR support is more than fixing failed items. A complete AMS scope covers monitoring, incidents, problems, changes, and period-end support – and connects system behavior with ASC 606 and ASC 842 judgment. Define the scope along these lines, and support becomes a source of stability rather than a recurring close risk.

Related terms: SAP RAR · Revenue Accounting Item · Human-Governed Automation

Related articles: Period-End Close in SAP RAR: A Practical Checklist · SOX Controls for Revenue Processes in S/4HANA

Setting up support for a live RAR landscape? Talk to our experts.