SAP Subscription Billing automates subscription lifecycle management natively and prices usage-based fees natively, but it does not handle dunning at all. This SAP Subscription Billing features overview traces where the rest lives: dunning, collections and dispute management sit in SAP S/4HANA Cloud for contract accounting and invoicing, and high-volume usage mediation runs through SAP Convergent Mediation by DigitalRoute. Answering all three needs three products.

Key Takeaways

• SAP Subscription Billing natively handles mix-and-match pricing across one-time, recurring and usage-based fees, plus contract changes and auto-renewals.

• Dunning, collections and dispute management are documented under SAP S/4HANA Cloud for contract accounting and invoicing, not under Subscription Billing.

• High-volume usage mediation runs through SAP Convergent Mediation by DigitalRoute, an OEM product, which handles enrichment, aggregation, correlation and splitting.

• Customer entitlements need SAP Entitlement Management, a third product, so feature gating isn't part of the billing engine either.

• SAP publishes no price for Subscription Billing. The pricing section on its product page is a demo request form.

What does SAP Subscription Billing actually automate?

Lifecycle management is the part SAP Subscription Billing owns end to end. Subscriptions carry mixed pricing and change mid-term without leaving the product.

• Mix-and-match pricing combines one-time, recurring and usage-based fees on a single subscription.

• Contract changes, updates and automatic renewals run through the subscription record.

• Invoice-level discounting applies by amount, by percentage or by rule.

• Customer-specific offers and promotions generate automatically from customer attributes.

• Revenue recognition posts through native integration with SAP S/4HANA Cloud.

Does SAP support usage-based rating and mediation?

Rating yes, mediation separately. SAP Subscription Billing prices usage-based fees, but the layer that collects and cleans high-volume usage before rating is a different product.

• SAP Convergent Mediation by DigitalRoute collects data from multiple systems, then automates enrichment, aggregation, correlation and splitting.

• Error-detection rules validate data quality before the events reach billing.

• That mediation layer is what an SAP deployment uses at telco-scale event volume, and it carries its own licence, its own implementation and its own consultants.

The practical consequence is scope. A question that sounds like one product decision turns into a stack: Subscription Billing for the contract, Convergent Mediation for the events, Entitlement Management for feature access, and S/4HANA contract accounting for receivables.

Where do dunning and collections actually live?

Outside SAP Subscription Billing. SAP documents dunning, collections and dispute management under high-volume receivables management in SAP S/4HANA Cloud for contract accounting and invoicing.

• That product manages contract-based subledger accounting, complex account hierarchies and group postings at account level.

• It's the right tool for an enterprise with millions of invoices, and it's also a full S/4HANA implementation.

• A subscription business that wanted automated retries and dunning campaigns from its billing tool has to buy and implement the receivables product to get them.