BLOG

Billing & Order-to-Cash

Order-to-cash (O2C) is the end-to-end process from a customer order to delivery, invoicing, and the collection of payment. Billing is the part of that process that tells the customer what they owe. Under ASC 606 and IFRS 15, it no longer tells the company what it has earned: revenue follows the transfer of control, not the invoice. The gap shows up on the balance sheet. A receivable is an unconditional right to consideration, a contract asset is a conditional right for goods or services already transferred, and a contract liability is an obligation to perform for which the customer has already paid or payment is due. For US finance and SAP teams, getting billing right – and reconciling it with revenue – is what keeps cash, revenue, and audits on track.

Review Your Billing Setup

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

Under ASC 606 and IFRS 15, billing and revenue recognition follow different rules. Why they diverge, what contract assets and liabilities are, and how SAP handles it.

Read article →

Billing & Order-to-Cash

Subscription and Usage-Based Billing: Key Design Decisions

Recurring and consumption-based business models need billing and revenue processes built for volume and change. The key design decisions for SAP landscapes.

Read article →

Billing & Order-to-Cash

Order-to-Cash Exceptions: Where Revenue Leaks

Missing invoices, pricing errors, blocked documents and unreconciled revenue – the most common order-to-cash exceptions and how to detect them systematically.

Read article →

What You'll Find Here

Our billing and O2C articles look at the commercial and operational side of revenue. They explain why invoices and revenue diverge, which design decisions matter for subscription and usage-based models, and where order-to-cash exceptions cause revenue leakage. Further articles cover billing plans in SAP SD, credit memos and returns, unbilled receivables and contract assets, retroactive price changes and rebilling, channel and reseller billing, consolidated and split invoicing, and sales tax presentation on invoices.

Key Questions We Cover

• Why do billed amounts and recognized revenue differ – in timing, in amount, or both?

• Where is a subscription contract managed, and how is usage captured and rated?

• Which exceptions – unbilled deliveries, blocked documents, unlinked credit memos – leak revenue, and how can they be detected early?

• How are billing, revenue accounting, and the general ledger reconciled?

How This Connects to SAP

In SAP landscapes, billing can run in SAP SD, SAP Subscription Billing, or SAP BRIM, with high-volume receivables in FI-CA. Revenue is then determined in SAP Revenue Accounting and Reporting (RAR), which receives order, fulfillment, and invoice information and posts revenue and contract balances. Each flow has to be designed so that every amount can be traced from order to invoice to revenue posting.

Revident's approach follows Discover. Engineer. Validate. Operate. With human-governed automation, AI agents can monitor exceptions and prepare root-cause analysis, while finance teams decide on corrections to invoices and revenue.

Start Here

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

• Subscription and Usage-Based Billing: Key Design Decisions

• Order-to-Cash Exceptions: Where Revenue Leaks

Aligning billing and revenue in your SAP order-to-cash process? Talk to our experts.

Ready to Make Your SAP Finance Landscape Agentic?

Whether you are implementing SAP RAR, modernizing revenue processes, or exploring agentic finance operations, Revident helps you move from strategy to execution.

Talk to Our Experts