Subscription and Usage-Based Billing: Key Design Decisions

Recurring revenue models have moved far beyond software. Equipment manufacturers sell machines as a service, medical technology companies charge per procedure, and industrial companies bill based on usage data from connected devices. These models change how companies invoice – and how they recognize revenue.

Traditional order-to-cash processes were built for one-time sales. Subscription and usage-based models require a different design.

Decision 1: What Exactly Is Being Sold?

Before any system design, the commercial model must be clear:

• Fixed subscription: a recurring fee for access or availability.

• Pure usage: charges based on actual consumption (per unit, per hour, per transaction).

• Hybrid: a base fee plus usage, often with included volumes, tiers, or minimum commitments.

• Prepaid models: credits or tokens purchased upfront and consumed over time.

Each model has different implications for pricing, billing frequency, and revenue recognition.

Decision 2: Where Is the Contract Managed?

Subscriptions change constantly: upgrades, downgrades, renewals, cancellations, price changes. A clear master for subscription contracts is essential. In SAP landscapes, options include SAP Subscription Billing, the subscription order management of SAP BRIM, or contract and service management in S/4HANA – depending on the volume and complexity of the business.

Decision 3: How Is Usage Captured and Rated?

Usage-based billing depends on reliable consumption data:

• Where does usage data come from (devices, platforms, partner systems)?

• How is it validated, aggregated, and corrected?

• How is it priced (rating), including tiers, allowances, and minimums?

In high-volume scenarios, this is typically handled by dedicated components such as SAP Convergent Charging and Convergent Invoicing within SAP BRIM.

Decision 4: How Is Revenue Recognized?

Billing and revenue diverge more often in recurring models:

• Upfront payments for annual subscriptions create contract liabilities.

• Minimum commitments may need to be recognized differently from actual usage.

• Usage-based fees can often be recognized as consumed – under certain conditions through the variable consideration allocation exception or the "right to invoice" practical expedient.

• Bundles of equipment, service and usage require allocation based on standalone selling prices.

• Contract modifications are frequent and must be classified correctly.

SAP Revenue Accounting and Reporting integrates with SAP BRIM and SD to apply ASC 606 and IFRS 15 to these scenarios.

Decision 5: How Are Receivables Managed?

High invoice volumes with small amounts need a different receivables approach than traditional B2B sales. SAP Contract Accounting (FI-CA) is designed for high-volume postings, payment processing, and dunning, and is a core part of SAP BRIM.

Decision 6: How Is Everything Reconciled?

With several systems involved – contract management, usage, rating, invoicing, receivables, revenue accounting and the general ledger – reconciliation must be designed from the start. Every step should be traceable: from usage record to invoice line to revenue posting.

Common Mistakes

• Designing billing first and thinking about revenue recognition later.

• Underestimating the frequency of contract changes.

• No clear process for usage data corrections.

• Using a one-time-sale process for recurring business "just for now".

• Missing reconciliation between billing and revenue.

Related Articles

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

• What Is SAP Subscription Billing?

• Usage Rating with SAP Convergent Charging

The Bottom Line

Subscription and usage-based models are not just a pricing decision. They require a consistent design across contract management, rating, invoicing, receivables, and revenue accounting. Companies that make these decisions deliberately – and early – avoid costly redesigns once volumes grow.

Building recurring revenue processes in SAP? Talk to our experts.