SD / O2Cintermediate

SD Revenue Recognition Part 3: From Billing to Revenue Postings — Deferred Revenue and RAR

Key takeaway

Follow revenue from SD documents to FI in S/4HANA with Revenue Accounting and Reporting: revenue accounting contracts and performance obligations created from sales orders, allocation of transaction price, fulfilment events from deliveries or time, invoices as billing events, and the postings for deferred revenue and contract assets/liabilities.

Explanation

📌 KEY POINTS
✅ With RAR, SD sales orders create revenue accounting contracts and performance obligations (POBs).
✅ Transaction price is allocated using standalone selling prices (SSP).
✅ Fulfilment events (delivery/PGI, time, milestones) drive revenue; invoices drive billed amounts.
✅ Differences between fulfilment and billing create contract assets or contract liabilities (deferred revenue).
⚠️ RAR needs clean SSP data and POB design — otherwise allocation produces unexplainable results.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Parts 1–2 covered principles and legacy config. Now the S/4HANA flow.

━━━━━━━━━━━━━━━━━━━━
▶ 1. FROM SD TO RAR

Sales order items → revenue accounting items → contracts and POBs.
Delivery (PGI) and invoices → fulfilment and invoice items.

━━━━━━━━━━━━━━━━━━━━
▶ 2. PERFORMANCE OBLIGATIONS

POB types: point in time, over time (time-based, event-based).
Bundles: distinct POBs for goods and services.

━━━━━━━━━━━━━━━━━━━━
▶ 3. ALLOCATION

SSP per POB; allocation of discounts across POBs.

━━━━━━━━━━━━━━━━━━━━
▶ 4. POSTINGS

Revenue on fulfilment; invoice correction postings; contract asset/liability.
Period-end processing and reconciliation.

━━━━━━━━━━━━━━━━━━━━
▶ 5. OPERATIONS

Monitoring of revenue accounting items and errors.
Reconciliation SD ↔ RAR ↔ FI.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Define POB types and SSP with finance.
Configure SD integration.
Test bundle order: machine + service.
Check allocation and period-end postings.

✅ CHECKPOINT: revenue for the machine posts at delivery and service revenue monthly, with contract liability for billed-in-advance service.

Code example

ABAP Code

===== STEP 1: flow =====Sales order (machine + 12-month service) → revenue accounting contract with 2 POBsPGI machine → fulfilment → revenue | monthly time-based fulfilment → service revenueInvoice upfront → contract liability for unearned service part ===== STEP 2: allocation example =====Order total 11,000 (discount 1,000) | SSP machine 10,000, service 2,000 → allocation 9,167 / 1,833 ===== STEP 3: operations =====Monitor revenue accounting items | period-end run | reconcile SD billing ↔ RAR ↔ FI

Real project scenario

A company launched RAR with SSP values copied from list prices without finance review. Bundled discounts were allocated unevenly, and quarter-end revenue swung unexpectedly. Finance defined SSP by product family, POB types were simplified, and a reconciliation dashboard between SD, RAR and FI was introduced before the next quarter.

Common mistakes

SSP without finance governance.
Too many POB types.
No reconciliation between SD, RAR and FI.
Ignoring invoice vs fulfilment differences.
Late involvement of auditors.

Best practices

Govern SSP and POB design in finance.
Keep POB types simple.
Reconcile regularly.
Monitor RAR items and errors.
Involve auditors early.

Interview angle

Questions: "How does SD integrate with RAR?", "What is a performance obligation?", "What is a contract liability?"
Strong answer: SD orders to revenue accounting contracts and POBs, SSP allocation, fulfilment from delivery/time, invoice items, contract assets/liabilities, period-end and reconciliation.

Practice this lesson

Quick check

1. A bundle of machine and service is sold with a discount. How does RAR distribute the discount?

2. A common intermediate-level question is to explain the FI postings created by VF44 and why deferred revenue and unbilled receivables accounts are both needed. In the Revenue Recognition context, which answer shows the strongest practical judgment?

3. In RAR, what is a performance obligation?

Interview questions

1. After go-live, billing documents are posting correctly to FI-AR, but Revenue Recognition (or Revenue Accounting under IFRS 15/ASC 606) is showing deferred revenue balances that never clear even though services were fully delivered. What would you investigate?

Answer it in your own words first, then compare.

2. A client using S/4HANA wants billing documents to automatically feed revenue recognition postings for a subscription-based product line. What integration points and configuration decisions must be addressed?