Revenue assurance: where telecom loses money quietly

Where the losses go

By industry benchmarking, revenue leakage at large telecoms runs at 0.5-3% of total revenue. For an operator with revenue of several trillion UZS, that is a meaningful annual sum. It does not “vanish” in a single big incident — it streams in small flows through several cracks.

Several typical places:

Between network usage and billing. Network ops registers that a customer used a service, but billing did not get the signal or got it late. Service delivered, not charged. If this happens to 0.1% of sessions, at scale it is significant daily.

Between billing and collection. Billing issued an invoice, but the collection process did not track it. Ninety days later the invoice goes to bad debt. If contained — fine. If not — leakage.

Between discount rules and billing. Marketing promises 20% off, billing applies 30% (or 0%). Both an overcharge to the customer and lost revenue for the operator.

Between partner settlement and actual usage. The partner reports usage of its services through the operator, but settlement does not match the operator’s own logs. Without reconciliation discipline — shortfall.

Between dealer commission and customer activity. The dealer gets commission for an activation, but the customer never activated. Commission paid, revenue not generated.

Between fraud detection and financial impact. Fraud is detected, losses are not recovered, attribution is incomplete.

Each is a separate leakage stream with its own remediation.

Timeline of a typical leakage incident

Sometimes it helps to walk through a typical case.

Start of month. Marketing launches a campaign with a “first three months 50% off roaming” rule. The campaign is live in marketing tooling.

Day 5. First customers activate roaming under the new rule. The billing engine applies its rating rules. But the specific “50% off first three months” rule is not configured in billing — only a generic “20% promotional discount” exists.

Day 30. First invoices with roaming. Customers receive bills with 20% off instead of 50%. Those who pay attention call the contact centre.

Day 45. The contact centre identifies the mismatch. A report goes to billing operations. Manual adjustments begin.

Days 60-90. Manual adjustments to complainers are done. But 80% of customers did not call — they either did not notice or accepted it. They got the correct discount; the operator got the correct revenue. The complainers got an adjustment with revenue loss for the operator.

Day 120. A grid of retro-adjustments via accounting. Finance reports — instead of the planned 50% promotional cost we got a mix. Net financial impact unclear.

End of campaign. Nobody comes back to understand what really happened.

That is leakage in its typical form. Not drama, not fraud — operational sloppiness that accumulates.

What changes in the operating model

Revenue assurance is not a quarterly report. It is an ongoing operating function with concrete responsibilities.

Reconciliation discipline. Between network and billing — usage reconciliation daily. Between billing and collection — receivables weekly. Between partner and usage — settlement monthly. Discrepancies investigated, root cause found, fixes implemented.

Discount rule audit. Each discount rule in billing is periodically audited. Is it applying correctly. If not — fix immediately, not next cycle.

Fraud loss measurement. Not “fraud detected” as a metric, but “fraud loss as percentage of revenue”. Including not just detected but unprevented losses.

Dealer commission validation. Commission paid only when the activation is validated as active for 90 days. Not upfront.

Cross-team coordination. Marketing, billing, operations, finance share a leakage dashboard. Monthly review. Owners assigned.

Audit trail for investigations. When an incident is found, root cause, action taken, prevention is documented. Above the trail — periodic pattern review.

What often goes wrong

Revenue assurance as a quarterly report. Too late — losses are already locked.

An RA team without authority. The team identifies issues but cannot push fixes. Issues sit in the queue.

Focus only on fraud. Fraud is high-salience but usually not the largest leakage stream. Operational leakage is often larger in total.

Manual reconciliation. Done manually in spreadsheets, frequency is low and errors are high. Automation is critical.

Politics around root cause. If leakage is attributed to a specific team (marketing, biller), the team defends. Without executive sponsorship, root cause work is blocked.

No measured prevention. RA reports identify problems but do not measure how effective prevention is. A year later the same problems.

A realistic upgrade roadmap

Months 1-3. Diagnostic. Mapping where leakage occurs. Initial sizing per stream. Identification of top-5 streams.

Months 4-9. Foundation. Reconciliation automation for top streams. A dashboard for visibility. RA team formalised with authority.

Months 10-15. Operating discipline. Monthly review with executive sponsorship. Issue lifecycle process. Root cause documentation.

Months 16-24. Maturity. RA as an ongoing function. Measurable reduction in leakage. Prevention proven.

By two years in the operator’s leakage rate should drop to what the industry calls well-controlled (around 0.3-0.5% of revenue). That is meaningful additional margin going straight to the bottom line.

When not to launch a large RA initiative

If the leakage rate is already under control (when measured) — do not over-invest. Diminishing returns.

If the organisation is in an acute phase of major billing transformation, RA on shifting underlying systems is mostly wasted.

If IT capacity is constrained, reconciliation automation will take longer than planned.

If cooperation between teams is insufficient, the RA team does not get the information it needs.

If the CFO is not committed to giving the RA function authority, the reform is politically blocked.

Discussion points for the committee

What is the current leakage rate estimate? If the answer is “not measured” — that is the problem.

Which 3 leakage streams are largest by estimate? Priority focus.

Who owns revenue assurance as a function? If distributed across teams — inefficient.

What is the RA team’s authority? Can they push fixes or only report?

What 18-24 month investment commit is needed and is it there?

How SamaraliSoft can help

Revenue Assurance Programme — initial leakage diagnostic across the main streams, sizing per stream, design of an RA operating model with authority and accountability, building reconciliation automation for critical streams, dashboard and monthly review establishment, and a phased rollout over 18-24 months with measurable leakage rate reduction.

Related reading

• /en/architecture/telecom-around-core-architecture/ — layer around the core
• /en/insights/telecom-data-contracts/ — data contracts
• /en/insights/telecom-event-driven/ — event-driven foundation
• /en/insights/telecom-dealer-quality-score/ — dealer network

Sources

• Ministry of Digital Technologies — telecom infrastructure UZ
• Digital Government Portal — digital infrastructure UZ
• UzDaily — telecom market
• MNP.UZ — number portability
• Central Bank of Uzbekistan — biometric verification for digital banking