Billing vs. Revenue: Why Invoices Don't Equal Revenue

For decades, many companies recognized revenue when they issued an invoice. In SAP, that was the natural setup: the billing document in SD posted revenue directly to the general ledger. Under ASC 606 and IFRS 15, this link no longer holds. Billing follows commercial agreements. Revenue follows the transfer of control. The two often differ – in timing, in amount, or both.

Why Billing and Revenue Diverge

Timing differences

A customer pays an annual subscription upfront, but the service is delivered monthly. The invoice is issued once; revenue is recognized over twelve months.

Allocation differences

A bundle of equipment and a service contract is sold at a discount. The invoice shows the contractual prices, but revenue is allocated based on standalone selling prices. The equipment may carry more or less revenue than its invoiced amount.

Unbilled performance

A project is completed in stages, but billing follows milestones. Revenue for work performed may need to be recognized before the next milestone invoice.

Non-invoiced obligations

A service-type warranty included free of charge or a material right never appears on an invoice, but it receives a share of the transaction price and is recognized separately.

Variable consideration

Expected rebates, returns, or bonuses can reduce or increase revenue before any credit memo or invoice is issued.

Contract Assets and Contract Liabilities

The gap between billing and revenue appears on the balance sheet:

• A contract liability arises when the customer has paid or been invoiced before the company has performed – deferred revenue.

• A contract asset arises when the company has performed before its right to consideration is unconditional – for example, when revenue is allocated to a delivered item, but payment depends on delivering further items.

• A receivable is recognized when the right to consideration is unconditional, typically when an invoice is issued.

These balances must be presented and disclosed, and auditors expect them to be reconciled with billing and the general ledger.

What This Means for SAP

In a traditional SD setup, billing documents post revenue directly. With SAP Revenue Accounting and Reporting (RAR), the logic changes:

• Billing documents post receivables and, depending on configuration, to clearing or deferral accounts instead of final revenue accounts.

• RAR determines revenue based on performance obligations, allocation and fulfillment, and posts revenue and contract asset or liability balances.

• Both flows must reconcile: what was invoiced, what was recognized, and what remains as a contract balance.

This separation is the reason RAR can apply ASC 606 and IFRS 15 correctly. It is also the reason why integration and reconciliation between SD, RAR and finance must be designed carefully.

Common Pitfalls

• Billing still posting final revenue in some processes, leading to double counting.

• Missing fulfillment events, so revenue is recognized too late.

• Unclear account determination for clearing and deferral accounts.

• No regular reconciliation between billed amounts, recognized revenue and contract balances.

• Treating contract assets as receivables in reporting.

Related Articles

• Subscription and Usage-Based Billing: Key Design Decisions

• Order-to-Cash Exceptions: Where Revenue Leaks

• FI-CA and SAP RAR: How Invoices and Revenue Stay in Sync

The Bottom Line

Billing tells you what the customer owes. Revenue recognition tells you what the company has earned. Under ASC 606 and IFRS 15, both are needed – and both must be connected through a reliable system design and reconciliation process.

Separating billing and revenue in SAP? Talk to our experts.