Revenue Assurance
Leakage detection across the billing chain, CDR reconciliation, margin analysis, and why RA needs cross-system visibility.
What Revenue Assurance Actually Does
Revenue Assurance (RA) is the discipline of detecting and preventing revenue leakage across the billing chain. Revenue leakage occurs when a telco delivers a chargeable service but fails to bill for it, bills incorrectly, or fails to collect payment. RA is not a single system — it is an analytical function that sits across mediation, rating, billing, and collections, comparing what should have been charged with what was charged.
Where Revenue Leaks
Revenue leakage can occur at every stage of the billing chain. RA teams must monitor each handoff point.
Leakage Points in the Billing Chain
| Stage | Leakage Type | Cause | Detection Method |
|---|---|---|---|
| Network → Mediation | Lost CDRs | Collection failure, file corruption, network element not feeding mediation | CDR volume trending — compare expected vs actual record counts per switch/node |
| Mediation → Rating | Unrated events | Records rejected by rating due to format errors, unknown tariff codes, or missing subscriber mapping | Reject queue monitoring — track rejection rates and categorise reasons |
| Rating → Billing | Incorrect charges | Wrong tariff applied, discount miscalculated, proration error | Sample audits — re-rate a statistical sample and compare with actual charges |
| SLM → Billing | Subscription leakage | Active service not reflected in SLM, or SLM shows wrong plan/pricing | Inventory-billing reconciliation — compare active services in SLM vs billing charges |
| Billing → Collections | Uncollected revenue | Failed payments not escalated, dunning process gaps, write-offs too aggressive | Aging analysis — track payment success rates and dunning effectiveness |
CDR Reconciliation and Margin Analysis
The two core RA techniques are CDR reconciliation and margin analysis. CDR reconciliation compares record counts and values at each handoff point in the billing chain: switch → mediation → rating → billing → invoice. Any drop in volume or value indicates leakage. Margin analysis compares expected revenue (based on subscriber base, plan mix, and average usage) with actual billed revenue — systematic deviations signal structural leakage.
- Switch-to-bill reconciliation — Compare CDR count at the network switch with the count that reaches billing. Any gap represents lost revenue events.
- Revenue-per-subscriber trending — Track ARPU by segment over time. Unexpected drops may indicate rating errors or catalog misconfigurations affecting an entire product.
- Interconnect reconciliation — Compare outbound interconnect CDRs with partner settlement statements. Discrepancies indicate either leakage or overpayment.
- Activation-to-billing lag — Measure the time between service activation (SOM/ROM completion) and first billing event. Extended lags mean the customer is using the service without being charged.
Key Takeaways
- Revenue Assurance detects and prevents leakage across the entire billing chain — from network event to cash collection
- Leakage occurs at every handoff: network→mediation, mediation→rating, rating→billing, SLM→billing, and billing→collections
- Core techniques are CDR reconciliation (comparing record counts at each stage) and margin analysis (expected vs actual revenue)
- Effective RA requires cross-system visibility and organisational authority — it cannot function with billing data alone