SAP BRIM · high-volume billing
Subscription and usage-based billing in SAP BRIM (Billing and Revenue Innovation Management) turns millions of usage records into invoices every cycle. Testing it needs subscriptions, contract accounts and usage that line up, at volumes production can't lend to test. Synthesized masks subscriber data and generates usage at the scale a billing run needs.
On SAP, we measure results on your own data in a 10-day validation.
The billing chain
| Stage | Where it lives | What the test data needs |
|---|---|---|
| Subscriber | Business partner and contract account: BUT000, FKKVKP | Masked identity, address and bank details, with the right account settings |
| Subscription | Provider contract | Active, changed and ending contracts, linked to the contract account |
| Usage | Consumption items, rated by charging | Usage records at the volume and pattern of a real cycle |
| Billing and invoicing | Billable items in Convergent Invoicing | Items that bill and invoice, plus the exceptions |
| Contract accounting | FI-CA documents: DFKKKO, DFKKOP | Open items, payments and dunning levels that follow from the invoices |
BRIM landscapes differ. The scope is mapped to your components and release in the first workshop.
Why it breaks
01
02
0304How it works
A subset by region, product or contract account, with every provider contract and open item that belongs to them.
Names, addresses, contacts and bank details are masked, the same way in every connected system.
Consumption items for the cycle, at the volume and pattern you set, including the edge cases a run must handle.
Run billing, invoicing and dunning, compare the results, and rebuild the same data set for the next cycle.
Who uses it
Usage-basedTelecommunicationsCalls, data sessions and roaming, with plan changes and bundles mid-cycle.SubscriptionMedia and subscriptionsRecurring plans, trials, upgrades and cancellations at scale.
Event-basedTransport and tollingTrips and tolls rated per event, with high daily volumes.We've got you covered
SAP Billing and Revenue Innovation Management: SAP's set of components for subscription and usage-based billing, including charging, Convergent Invoicing and contract accounting (FI-CA). It was marketed as SAP Hybris Billing for a time.
The data in S/4HANA: business partners, contract accounts, provider contracts, consumption and billable items, and FI-CA documents. We map the scope to your components in the first workshop.
Often, yes. Once usage is linked to a subscriber, it can show where and when that person was. Generated usage has no real person behind it.
Yes. Generate usage at the volume of a real cycle, or of the peak you expect, and measure the run. See performance testing.
Yes. Both use contract accounting, so business partners and contract accounts are masked the same way for both.
Next step
Tell us the products and the cycle. In a 10-day validation, we build masked subscribers and generated usage for one billing run.
SAP, S/4HANA, SAP HANA, SuccessFactors, Ariba, Concur and other SAP products and services mentioned herein, as well as their respective logos, are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.
