Usage Rating with SAP Convergent Charging

Usage-based pricing is spreading across industries: software billed per transaction, equipment billed per operating hour, platforms billed per API call, and devices billed per procedure. To bill usage accurately, companies need to convert technical usage data into charges. In SAP Billing and Revenue Innovation Management (BRIM), this is the role of SAP Convergent Charging.

What Rating Means

Rating is the process of assigning a price to an event. A usage record – for example, "500 units consumed on 3 November" – becomes a charge, such as "USD 250", based on the customer's pricing plan.

Rating considers:

• the product and price plan,

• the customer's subscription and contract terms,

• tiers and volume discounts,

• included allowances or free units,

• time-based rules, such as peak and off-peak rates,

• minimum or maximum charges.

The Role of SAP Convergent Charging

SAP Convergent Charging is the rating and charging engine within BRIM. It runs as a separate application and is designed for high volumes. It handles:

• usage-based charges: pricing of consumption events,

• recurring charges: periodic subscription fees,

• one-time charges: activation, setup, or installation fees,

• allowances and counters: tracking of included volumes and thresholds.

Rated items are passed to SAP Convergent Invoicing, where they are aggregated and invoiced.

Where Usage Data Comes from

Usage data can originate from many technical sources: devices, platforms, network systems, or partner applications. Before rating, this data often needs to be:

• collected from different sources,

• validated and cleansed,

• transformed into a consistent format,

• enriched with customer and contract information.

This is typically handled by a mediation layer, such as SAP Convergent Mediation by DigitalRoute.

Key Design Decisions

Pricing Model Design

Business and IT should define the pricing model before configuration: what is charged, in which units, with which tiers and allowances. Complex pricing that is not clearly defined leads to complex and error-prone configuration.

Real-Time vs. Batch

Some businesses need real-time rating, for example to enforce credit limits or usage caps. Others can rate in batches. The choice affects architecture and performance.

Allowances and Counters

Included volumes, rollovers, and shared allowances across users or devices must be modeled carefully, as they directly affect charges.

Corrections and Re-Rating

Usage data is not always correct the first time. Late, duplicate, or incorrect records must be handled, and re-rating processes must be defined.

Link to Revenue Accounting

Rated usage is also relevant for revenue recognition. Companies must decide how usage information is passed to SAP Revenue Accounting and Reporting, and at what level of aggregation.

Common Challenges

• Data quality: Incomplete or inconsistent usage data leads to incorrect charges.

• Pricing complexity: Too many product and price variants make maintenance difficult.

• Performance: High volumes require careful sizing and design.

• Traceability: Customers and auditors need to understand how a charge was calculated.

• Change management: New products and price plans must be introduced quickly without disrupting existing customers.

Related Articles

• What Is SAP BRIM? The Components Explained

• SAP BRIM and RAR Integration: How Revenue Flows

• Subscription and Usage-Based Billing: Key Design Decisions

The Bottom Line

SAP Convergent Charging is the engine that turns usage into billable charges. Its success depends less on technical configuration and more on clear pricing models, reliable usage data, and well-defined correction processes – all connected to invoicing and revenue accounting.

Designing usage-based pricing in SAP BRIM? Talk to our experts.