Revenue Leakage in Telecoms: The Numbers Nobody Wants to Talk About

[alicejames]

Revenue leakage is one of those topics that tends to be discussed in hushed tones internally but rarely gets aired publicly. Yet industry estimates consistently put undetected telecom revenue leakage at 1–3% of gross revenue. For a carrier doing £5M annually, that's up to £150,000 quietly disappearing.

What Revenue Leakage Actually Means​

Revenue leakage in telecom is the difference between the revenue that should have been billed and the revenue that was actually invoiced and collected. It can be caused by CDR processing errors, rate misapplication, unbilled usage, fraud, or reconciliation failures.

The Sources of Leakage​

The most common sources are: CDRs that are generated but never reach the billing system (network-to-billing integration failures),CDRs that reach the system but are rated incorrectly (wrong rate table, expired rate, misconfigured destination),and usage that is billed but never collected (invoiced but unpaid, with no automated dunning).

Why It's Hard to Detect​

Revenue leakage is hard to detect precisely because it tends to be the absence of something rather than the presence of an error. If a CDR never arrives in the billing system, there's no visible error — just a gap. Identifying gaps requires comparing what your network reported with what your billing system received.

The Business Case for Plugging Leakage​

Revenue recovery has an unusually good return on investment. Unlike growth initiatives, which require new customers, plugging leakage recovers money from activity that has already occurred. Even recovering half the industry-average leakage rate adds significant margin without additional sales effort.

Closing / Discussion Prompt​

Has anyone done a formal revenue leakage audit? Curious what the most common sources are when people actually dig into the data.

 

[AI Helper]

Revenue leakage: it’s rarely “one big hole”, it’s death by a thousand cuts

The 1–3% figure rings true because most leakage sits between systems and teams: network ops, billing, finance, credit control, and product all owning a slice but nobody owning the end-to-end “cash for usage” chain. On a £5m turnover carrier, even 1% is a material headcount or capex line, so it’s worth treating as a board-level control topic, not just an engineering tidy-up.

When operators run a formal audit, the usual “found money” tends to come from a few predictable places:

• CDR mediation gaps (dropped files, partial loads, timezone/sequence issues, retries not monitored)
• Rating and tariff hygiene (expired promos, wrong destination mapping, rounding rules, VAT treatment)
• Provisioning mismatches (service active on network but not on billing, ceased services still billed or vice versa)
• Credit control process failures (no consistent dunning, disputes parked, write-offs not challenged)
• Partner/interconnect reconciliation (disputed minutes, delayed statements, settlement errors)

A practical way to structure an audit is to reconcile “network events → mediation → rating → invoice → cash” with a small set of control totals at each hop. Even a weekly control pack catches drift early: record counts, usage volumes, rated value, billed value, collected value, plus exception queues with clear owners and ageing.

If anyone’s considering doing this in the UK, it’s worth involving finance early so recoveries are handled cleanly (credit notes, VAT, revenue recognition) and so the fixes become ongoing controls rather than a one-off project. Curious: are people seeing more leakage from mediation/rating, or from collections and dispute handling?