SAP Subscription Billing

What You'll Find Here

The articles in this category explain what SAP Subscription Billing does, how subscription revenue gets recognized, and how the solution relates to SAP BRIM. Further articles cover usage-based charges, upgrades, downgrades, and cancellations mid-term, the bridge between ARR and MRR metrics and GAAP revenue, hardware plus subscription bundles, and annual upfront billing and prepayments.

How This Connects to SAP RAR

Each subscription is replicated to a provider contract in SAP S/4HANA, and the billing forecast becomes a billing plan. Which revenue engine applies depends on the integration path and the edition:

• Convergent Invoicing, private cloud: SAP Revenue Accounting and Reporting (RAR).

• Convergent Invoicing, public cloud: contract-based revenue recognition, the public cloud counterpart to RAR.

• Sales billing, public cloud: event-based revenue recognition for provider contracts.

Because the integration path determines the revenue engine, we evaluate billing and revenue design together rather than in sequence.

Key Questions We Cover

• Sales billing or Convergent Invoicing: which path fits your volume and receivables needs?

• How do products and rate plans shape the performance obligations in the revenue contract?

• Where do standalone selling prices come from, and who maintains them?

• Which controls keep billing, receivables, and recognized revenue reconciled for SOX?

Our Agentic Finance approach applies human-governed automation across this chain: agents monitor transfers and compare billed and recognized amounts, and finance owners review and approve. The same RAR foundation supports lessor leasing under ASC 842 and IFRS 16 without additional software.

Start Here

• What Is SAP Subscription Billing?

• SAP Subscription Billing and RAR: How Subscription Revenue Gets Recognized

• SAP Subscription Billing vs. SAP BRIM: Which Fits Your Model?