Billing Overview
Where billing sits in Lead-to-Cash, its key interfaces with SLM, mediation, catalogs, and ERP, and why billing is the hardest BSS system to replace.
Where Billing Sits in Lead-to-Cash
Billing & Revenue Management is the Order-to-Cash (O2C) domain within Lead-to-Cash. It sits downstream of fulfilment: once COM captures the order, SOM/ROM activate the service, and SLM records the active subscription, billing takes over. Its job is to turn service usage and subscription commitments into invoices, collect payment, and reconcile revenue. Without billing, there is no revenue.
Billing is not a single system — it is a domain comprising multiple capabilities: rating & charging (calculating what to charge), mediation (collecting and normalising usage records), invoice generation, payment processing, dunning (chasing overdue payments), and revenue assurance (detecting leakage). In large telcos, these may be separate systems from different vendors. In modern BSS suites, they are increasingly converged.
Click any capability to see its description, inputs, and outputs
Key Interfaces
Billing does not operate in isolation. It depends on accurate data from upstream systems and feeds critical financial data downstream. Understanding these interfaces is essential to understanding why billing breaks.
Billing Interfaces
| Interface | Direction | What Flows | If Broken |
|---|---|---|---|
| SLM / Product Inventory | Inbound | Active subscriptions, product structure, pricing tier, contract terms | Billing charges for products the customer no longer has, or fails to charge for new ones |
| Product Catalog | Inbound | Pricing rules, charge types (recurring, one-time, usage-based), discount structures | Rating engine cannot calculate charges; prices default or error |
| Mediation | Inbound | Rated or raw usage records (CDRs, event records) | Usage charges are missing or delayed; revenue leakage |
| COM / Order Management | Inbound | Order completion events, activation dates, contract start | Billing start date misaligned with service activation; customer billed before service is live |
| Payment Gateway | Outbound | Payment requests, direct debit instructions | Payments not collected; cash flow impact |
| ERP / General Ledger | Outbound | Revenue recognition, accounts receivable, tax records | Financial reporting inaccurate; audit risk |
Billing in the BSS Context
Billing is often the oldest and most deeply embedded BSS system in a telco. Many operators run billing platforms that are 15-25 years old, with decades of accumulated business rules, custom rating logic, and regulatory patches. This creates a specific transformation challenge: billing is simultaneously the system with the highest replacement risk and the system most in need of modernisation.
Key Takeaways
- Billing is the O2C (Order-to-Cash) domain — it turns service delivery into revenue
- It depends on accurate data from SLM, product catalog, mediation, and order management
- Billing is typically the oldest, most embedded BSS system — and the hardest to replace
- Understanding billing interfaces is critical: most billing errors originate in upstream systems, not in billing itself