SAP RAR Interview Cheat Sheet (Fast Revision)

1. What is SAP RAR?

SAP Revenue Accounting & Reporting (RAR) is used to comply with IFRS-15 / ASC-606 by handling:
✔ 5-Step Revenue Recognition
✔ Complex contracts
✔ Bundles & multi-element arrangements
✔ Revenue schedules, deferrals, reallocations
✔ Event-based revenue posting
✔ Integration with SD, FI, CRM, Hybris Billing

2. The 5 Steps in IFRS-15 (Mandatory)

  1. Identify the contract
  2. Identify performance obligations (POBs)
  3. Determine transaction price
  4. Allocate transaction price to POBs
  5. Recognize revenue as POBs are satisfied

RAR fully automates these steps.

3. SAP RAR Key Objects

📌 Revenue Accounting Contract (RAC)

Equivalent to the “contract” in IFRS-15.

📌 Performance Obligations (POB)

Items representing obligations in the contract — product, service, subscription.

📌 Revenue Accounting Item (RAI)

Input to RAR received from SD/FI/Subledger.

Types:

  • RAI Type 11 – Order
  • RAI Type 21 – Delivery
  • RAI Type 31 – Invoice
  • RAI Type 41 – Event (Fulfillment)

📌 Revenue Recognition Methods

  • Over time
  • At point in time
  • Percentage of completion
  • Straight-line, time-based

4. RAR Integration Points

  • SD (Sales Orders, Deliveries, Billing Docs)
  • FI-AR (Billing, Payments)
  • CRM (Services, subscriptions)
  • Hybris Billing / BRIM (Convergent Invoicing)
  • S/4HANA Universal Journal

RAR sits between source systems → RAR Engine → FI-GL.

5. RAR Process Flow (Simple Steps)

  1. RAI Extraction
  2. RAI Processing → Contract creation
  3. POB determination
  4. Stand-alone selling price (SSP) allocation
  5. Revenue schedule generation
  6. Event-based fulfillment
  7. Revenue posting to FI
  8. Reconciliation & disclosures

6. Key Configuration Areas

  • Account determination
  • RAI type mapping
  • POB templates
  • Allocation rules
  • SSP (Standalone Selling Price) setup
  • Fulfillment types & events
  • Posting rules
  • Contract modification settings

7. Frequent Interview Questions (One-liners)

  1. What does RAI do?
    It serves as the input object that triggers contract creation and revenue processing.
  2. What is SSP?
    Standalone Selling Price — used for allocation of transaction price to POBs.
  3. What is a POB template?
    Pre-defined rules for how POBs are identified and processed.
  4. Difference between Time-Based vs Event-Based recognition?
    Time-based spreads revenue over a period; event-based recognizes when triggered (delivery/service).
  5. What is contract modification in RAR?
    Updates to Revenue Contracts when order changes — amendment, cancellation, upsize/downsize.
  6. What are revenue postings made in RAR?
    Deferred revenue, unbilled revenue, revenue recognized, contract assets, liabilities.
  7. Can you reprocess RAIs?
    Yes, via RAI Worklist → Fix data → Reprocess.
  8. What is Delta vs Full RAI extraction?
    Delta extracts only updated items; full loads complete history.
  9. How does RAR handle bundled products?
    Using allocation functionality & SSP-based splitting.
  10. What are leading vs non-leading POBs?
    Leading POB triggers or controls additional POB behavior.

8. Common Issues & Troubleshooting

  • RAI stuck in error → Check mapping, missing fields, wrong RAI Type.
  • Incorrect POBs created → Review template and rules.
  • Revenue not posted → Check fulfillment events & posting logs.
  • Contract not created → RAI config or grouping wrong.
  • Wrong allocation → Verify SSP setup, allocation flags.

9. RAR Key Transactions / Apps

ECC / S4 T-Codes

  • FARR_RAI_MON – RAI Monitor
  • FARR_RAI_PROC – RAI Processing
  • FARR_CONTRACTS – Display Contracts
  • FARR_D_WL – Worklist
  • FARR_D_LIABILITY – Contract Liability Reporting
  • FARR_D_POSTING_LOG – Posting Logs

Fiori Apps

  • Manage Revenue Contracts
  • Display Revenue Postings
  • Process RAIs
  • Run Revenue Allocation
  • Revenue Analytics Dashboard

10. Contract Grouping & Merge Logic

  • Same key fields (Customer, Contract ID, Product, etc.)
  • Same RA type
  • Same contract profile
    If grouping fields differ → multiple contracts created.

11. Allocation Concepts

  • Based on SSP
  • Relative standalone selling price method
  • Requires:
    ✔ POBs
    ✔ Total transaction price
    ✔ SSP lookup table
    Allocation adjusts revenue schedule for each obligation.

12. Migration Questions (S/4HANA)

  • RAR replaces SD Revenue Recognition
  • Integrated with Universal Journal (ACDOCA)
  • Parallel accounting supported
  • Multiple GAAPs handled through multiple ledgers

13. Scenario-Based Questions

  1. How do you handle subscription + hardware bundle revenue?
  2. What happens if invoice amount changes after revenue allocation?
  3. How does RAR treat contract cancellation?
  4. How do you test time-based revenue schedules?
  5. Customer pays upfront for a 12-month service — how posted?
  6. Delivery created but no revenue posted — what to check?
  7. How do you handle credit memos in RAR?
  8. What happens when a POB is partially fulfilled?

14. Memory Quick Sheet (15 Seconds)

TopicOne-Line Memory
RAIInput to RAR
POBRevenue obligation
SSPPrice allocation basis
AllocationSplits TP across POBs
FulfillmentTriggers revenue
Time-basedEven spread
Event-basedOn delivery/event
RAR OutputFI postings
ModificationContract changes
RAR EngineIFRS-15 automation

I share content relevant to Tech/Interview/Corporate/ & Anything Stuff !!

Do follow for more useful content : https://www.linkedin.com/in/vartika-gupta24/