Question 1

What is SAP Revenue Accounting & Reporting?

Accepted Answer

SAP RAR is the revenue subledger that helps recognize revenue under ASC 606 / IFRS 15. It manages contracts and performance obligations, allocates transaction price (including SSP), processes order, fulfillment, and billing events as Revenue Accounting Items, and posts to the general ledger with contract assets and liabilities.

Question 2

When do companies typically need SAP RAR?

Accepted Answer

When commercial models outgrow simple invoice-based recognition: multi-element software deals, subscriptions, usage, milestones, or bundles where billing timing and recognition timing diverge. If finance is bridging the close in spreadsheets, RAR is usually on the table.

Question 3

Do you only implement SAP RAR, or do you stay after go-live?

Accepted Answer

Both. We run assessments and full implementations, and we offer AMS for period-end support, incident handling, and controlled changes when commercial offers evolve. Many clients keep a lighter retainer after hypercare rather than staffing a full-time specialist bench.

Question 4

What does RAR AMS cover?

Accepted Answer

Application management after go-live: incident triage, month-end support, configuration changes for new offers, performance and release impact review, and keeping inbound RAI processing healthy. The point is to run RAR as an operated system, not a finished project.

Question 5

We already have a systems integrator on SAP. Why add a RAR specialist?

Accepted Answer

Broad SI teams deliver ERP programs well; revenue accounting under ASC 606 / IFRS 15 still tends to need people who have configured POB structures, allocation, and RAI integration before. We work alongside your SI or internal team, owning the RAR workstream without displacing the rest of the program.

Question 6

Can you work with non-SAP billing or CRM upstream of RAR?

Accepted Answer

Yes. RAR needs clean order, fulfillment, and billing events. We integrate from SAP SD and BRIM where those are in place, and from non-SAP commercial systems via middleware or APIs when they are the system of record.

Question 7

How long does a RAR implementation take?

Accepted Answer

It depends on contract complexity, data quality, and how many source systems feed RAIs. A focused assessment often runs a few weeks; a full build can span several months. We sequence work from a written roadmap after discovery rather than quoting a one-size duration up front.

Question 8

What does a typical first conversation look like?

Accepted Answer

We ask how you sell and bill today, what close looks like, which systems create contract data, and whether you are pre-decision, mid-implementation, or live with pain. You leave with a plain recommendation on next step: assessment, remediation, or AMS, not a generic deck.

Revenue recognition that holds up in the subledger, and in the audit room.

A specialist firm for finance systems that sell more than one thing.

SAP RAR offerings from assessment to AMS.

RAR readiness assessment & roadmap

RAR implementation & cutover

SAP RAR Integrations

RAR application management & support

Operating principles, applied.

Standards before screens

Operate what you build

Integrate with intent

Specialist depth, clear ownership

Say the uncertain part out loud

What SAP RAR is, and what working with NYN INC looks like.

Ready to talk through your revenue landscape?