Revenue leakage rarely looks like a major financial loss when it starts. It looks like one active SIM that never reached billing, one disconnected line still appearing on a carrier invoice, one expired promotion that was never removed, or one wholesale rate that no longer matches the contract.
For an MVNO or telecom reseller, those exceptions can quietly compound across hundreds or thousands of services. You buy connectivity from an upstream carrier, resell it to customers, and depend on multiple systems to keep the two sides aligned. When they do not match, the difference comes out of your margin.
Start with one simple question:
For every active line, SIM, number, circuit, or device you sell, can you prove who ordered it, when it activated, what the carrier charged you, what you billed the customer, and whether the cash actually arrived?
Most connectivity businesses can answer that for a sample. Far fewer can answer it for every service, every billing cycle.
That is the problem this guide addresses.
This article is written specifically for MVNOs, telecom resellers, MSPs, IoT connectivity providers, MVNEs, and other businesses that buy connectivity wholesale and sell it downstream. It is not written for Tier-1 network operators.
That distinction matters because your business carries risk on both sides of the ledger. You must validate what your upstream carriers charge you while also making sure every billable service reaches the right customer invoice. Traditional telecom revenue assurance focuses heavily on the downstream path from network usage to customer billing. A reseller also has to control the upstream cost side.
That creates three distinct forms of leakage:
- Revenue leakage: a service is delivered but never billed correctly.
- Cost leakage: a carrier charges you for a service, rate, or usage that should not have been charged.
- Margin leakage: both sides are recorded, but pricing, discounts, commissions, taxes, pooling, proration, or other billing rules reduce the expected spread.
The result is more than a billing problem. It is a margin problem.
A single missed invoice line may look insignificant. A disconnected service billed by a carrier for several months, hundreds of expired discounts, or a recurring wholesale rate mismatch can become a material drag on gross margin.
The good news is that leakage is measurable.
You do not need to begin with a large revenue assurance team or an enterprise-grade platform. Start by reconciling four things:
What is active → what the carrier charged → what the customer was billed → what was collected.
This guide identifies the 12 most common leakage sources for MVNOs and telecom resellers, shows the data signal that can expose each one, explains the control that can prevent it, and assigns an accountable owner.
The goal is not to chase an industry-wide leakage percentage that may not apply to your business. The goal is to identify where your own money is disappearing, quantify the exposure, and put controls around it before the same exception repeats next month.
What Is Telecom Revenue Leakage for an MVNO or Telecom Reseller?
Telecom revenue leakage is the gap between the value of connectivity you deliver and the revenue, cost, and margin you actually capture. In practice, it occurs when services, usage, rates, discounts, or payments do not move correctly through the order-to-cash process.
For MVNOs and telecom resellers, the problem is more complex because there are two sides to reconcile. You are buying connectivity from an upstream carrier while simultaneously selling that connectivity to downstream customers. A mismatch on either side can reduce profitability.
Revenue leakage generally falls into three categories:
- Revenue leakage: A service or usage is delivered but is never billed, is underbilled, or is billed incorrectly.
- Cost leakage: Your carrier charges you for a service, usage, or rate that should not have been charged.
- Margin leakage: The customer is billed and the carrier is paid, but pricing, discounts, commissions, taxes, pooling, or proration reduce the expected margin.
For a reseller, this means revenue assurance cannot stop at checking whether customer invoices were generated. You also need to verify that the wholesale cost behind every service is correct.
The Four Records You Need to Reconcile
A practical MVNO revenue assurance process connects four records:
Active service → Carrier charge → Customer invoice → Payment
For every service, you should be able to answer:
- Is the service actually active?
- Is the carrier charging you for it?
- Is the customer being billed for it?
- Was the expected amount collected?
If those four records cannot be reconciled, you have an exception worth investigating.
This approach follows the broader revenue-assurance principle of comparing what was contracted and delivered with what was rated, billed, and ultimately collected.
Why This Matters More for Resellers
A network operator primarily needs to ensure that network activity becomes accurate customer billing. An MVNO or reseller has an additional responsibility: the wholesale cost must also match the commercial agreement with the carrier.
That creates leakage opportunities at both ends.
A customer may have an active SIM that never appears on an invoice. At the same time, another SIM may have been disconnected in your system while the carrier continues charging you. Neither issue necessarily appears in your standard financial reports.
The result is a business that can show healthy subscriber growth while its gross margin quietly deteriorates.
That is why telecom revenue leakage should be treated as a cross-functional control problem, not simply a billing problem. Billing, finance, operations, carrier management, provisioning, sales operations, and product teams can all own part of the leakage chain.
The rest of this guide breaks that chain into 12 specific sources of leakage, with the signal to look for, the control that can prevent it, and the person responsible for fixing it.
The 12 Sources of Telecom Revenue Leakage, at a Glance
For MVNOs and telecom resellers, leakage rarely comes from one large failure. It usually comes from small gaps between provisioning, billing, carrier reconciliation, pricing, and collections.
The fastest way to find those gaps is to start with the signal in your data.
The table below organizes the 12 most common sources into three categories: revenue leakage, cost leakage, and margin leakage. Each category represents a different way value can disappear from the wholesale-to-retail business model.
| # | Leakage Source | Type | First Signal to Investigate |
|---|---|---|---|
| 1 | Active lines that never entered billing | Revenue | Active or provisioned count exceeds billed count |
| 2 | CDR and usage mediation gaps | Revenue | Mediated usage trails carrier-reported usage |
| 3 | Plan and order changes that never reach billing | Revenue | CRM or order changes have no matching invoice line |
| 4 | Test, demo, and temporary lines left live | Revenue | Billing-exempt lines remain active past their intended purpose |
| 5 | Disconnected lines the carrier keeps billing | Cost | Carrier-billed lines are inactive in your system |
| 6 | Expired promotions and discounts still applied | Cost | Promotional rate remains active after its end date |
| 7 | Carrier rate-card drift | Cost | Invoiced rate does not match contracted rate |
| 8 | Roaming, interconnect, and IoT charges outside contracted terms | Cost | Usage is billed at a default rate instead of the agreed rate |
| 9 | Pooled and shared-plan allocation errors | Margin | Independent pool calculation differs from billed allocation |
| 10 | Proration errors on mid-cycle changes | Margin | Expected proration differs from invoiced proration |
| 11 | Commission calculation errors | Margin | Recomputed commission differs from amount paid |
| 12 | Tax, surcharge, and regulatory fee miscalculation | Margin | Applied rate differs from the current applicable rate |
Revenue Leakage
1. Active Lines That Never Entered Billing
What happens: A SIM, number, circuit, or eSIM is activated but never becomes a billable subscription.
Why it happens: Provisioning, subscriber management, CRM, and billing systems do not always stay synchronized. A failed integration, delayed batch job, or missed manual step can leave an active service outside the billing population.
Signal in your data: Active or provisioned services exceed billed services for the same period.
Control: Reconcile the active-service roster against customer billing every cycle. Automate the activation-to-billing handoff and flag unmatched services.
Accountable owner: Billing operations, with provisioning or subscriber operations.
Example: Forty new business lines are activated, but a failed billing sync leaves them unbilled for an entire cycle.
2. CDR and Usage-Mediation Gaps
What happens: Voice, data, SMS, or IoT usage is generated but does not reach the rating and billing process correctly.
Why it happens: Carrier files can arrive late, change format, contain incomplete records, or fail during transfer. Without reconciliation, missing usage can remain invisible.
Signal in your data: Carrier-reported usage or CDR counts do not match the usage received by your mediation or rating system.
Control: Reconcile carrier usage totals with mediated usage and create an exception whenever the difference exceeds an agreed threshold.
Accountable owner: Billing or mediation operations, with technical teams supporting investigation.
Example: A carrier changes a CDR format and several days of usage fail to process, leaving customer invoices understated.
3. Plan and Order Changes That Never Reach Billing
What happens: A customer upgrades a plan, adds a service, changes a line, or increases capacity, but billing continues using the old configuration.
Why it happens: Sales, CRM, support, provisioning, and billing may each maintain different versions of the customer’s service state.
Signal in your data: A completed order or plan-change event has no corresponding billing change.
Control: Connect order and service-change workflows directly to billing. Do not allow an operational change to close without a corresponding billing event.
Accountable owner: Operations and billing.
Example: A customer moves to a higher data plan after a support request, but the billing system continues charging the old lower rate for several months.
4. Test, Demo, and Temporary Lines Left Live
What happens: A test, trial, demo, or internal line remains active and continues consuming carrier resources without generating customer revenue.
Why it happens: Billing exemptions are often created manually and have no enforced expiry date.
Signal in your data: Test, demo, trial, or complimentary accounts remain active beyond their approved end date.
Control: Give every exemption an owner and automatic expiry date. Review the exemption list regularly and require approval for extensions.
Accountable owner: Billing operations, with sales or partnerships approving extensions.
Example: A demo SIM created for a prospect remains active for a year after the opportunity has been closed.
Cost Leakage
5. Disconnected Lines the Carrier Keeps Billing
What happens: You deactivate a customer service, but the upstream carrier continues charging you for it.
Why it happens: Deactivation often requires an action in both your system and the carrier’s system. A failed API call, missed portal update, or missing confirmation can leave the wholesale service active.
Signal in your data: Carrier-billed services are marked inactive in your own service inventory.
Control: Reconcile your active-service roster against every carrier invoice. Require confirmation that carrier-side deactivation has completed.
Accountable owner: Carrier or vendor management, with finance validating the invoice.
Example: A customer ports out, but the carrier continues charging the reseller for the number for three additional billing cycles.
6. Expired Promotions and Discounts Still Applied
What happens: A promotional rate or discount continues after its agreed end date.
Why it happens: Promotions are frequently maintained through manual configuration, spreadsheets, or reminders rather than enforced expiration rules.
Signal in your data: Promotional rates remain attached to accounts after their effective end date.
Control: Store start and end dates with every promotion and make expiry automatic. Review upcoming expirations before each billing cycle.
Accountable owner: Billing operations and commercial or pricing teams.
Example: A six-month customer promotion remains active for 14 months because nobody removed the discount code.
7. Carrier Rate-Card Drift
What happens: The rate charged by a carrier no longer matches the rate agreed in the contract.
Why it happens: Wholesale contracts change, but rate tables and expected-cost models may not be updated at the same time.
Signal in your data: Actual carrier invoice rates differ from the current contracted rates.
Control: Maintain a single source of truth for wholesale rates, including effective dates. Compare every invoice against expected costs before approval.
Accountable owner: Finance or carrier management.
Example: A negotiated volume rate becomes effective in January, but the reseller’s cost model continues using the previous rate until June.
8. Roaming, Interconnect, and IoT Charges Outside Contracted Terms
What happens: Roaming, cross-border, interconnect, or IoT usage is charged using a default rate instead of the negotiated commercial rate.
Why it happens: These usage categories may follow different rating and settlement paths from standard domestic services.
Signal in your data: Specific usage categories show unexpected rates, destinations, or surcharges on carrier invoices.
Control: Validate roaming, interconnect, and IoT charges against the specific contract terms for each service, destination, and usage type.
Accountable owner: Carrier management, with product or IoT operations where applicable.
Example: IoT devices operating across a border are charged standard roaming rates even though the contract specifies a dedicated IoT tariff.
Margin Leakage
9. Pooled and Shared-Plan Allocation Errors
What happens: Usage, overage, or charges are allocated incorrectly across parent and child accounts or shared data pools.
Why it happens: A line may be assigned to the wrong pool, allocation rules may be misconfigured, or usage may not be distributed according to the intended commercial rules.
Signal in your data: An independent calculation of pool usage or overage does not match the billing allocation.
Control: Periodically recalculate pool allocations independently and compare the result with the billing engine.
Accountable owner: Billing operations and product or pricing teams.
Example: A new line is added to a shared pool but is assigned to the wrong billing group, distorting the charges across the entire account.
10. Proration Errors on Mid-Cycle Changes
What happens: A customer upgrades, downgrades, or changes services during a billing period, but the prorated charge or credit is incorrect.
Why it happens: Multiple plan changes, partial billing periods, different product rules, and edge cases can produce unexpected results.
Signal in your data: Independently calculated proration differs from the amount shown on the customer invoice.
Control: Test common mid-cycle scenarios and automatically validate proration whenever billing configuration or product rules change.
Accountable owner: Billing operations.
Example: A customer upgrades halfway through the month but receives the new plan for the remaining period without the correct partial-period adjustment.
11. Commission Calculation Errors
What happens: Sales representatives, agents, or channel partners receive commissions that do not match the agreed commercial terms.
Why it happens: Commission calculations often depend on separate spreadsheets, rate tables, or manually maintained rules.
Signal in your data: An independent commission calculation does not match the amount actually paid.
Control: Calculate commissions from current billing data and approved contract terms. Review changes to commission structures whenever pricing or promotions change.
Accountable owner: Finance, with sales operations responsible for commission rules.
Example: A partner moves into a higher volume tier, but the commission spreadsheet is not updated and continues calculating payouts using the old rate.
12. Tax, Surcharge, and Regulatory Fee Errors
What happens: The wrong tax, surcharge, or regulatory fee is applied to a customer invoice, reducing collected revenue or creating future credits and adjustments.
Why it happens: Tax and regulatory rules vary by location and can change independently of billing-system releases.
Signal in your data: The rate configured in the billing system does not match the applicable current rate.
Control: Maintain dated tax and surcharge rules and review them regularly. For complex jurisdictions, consider using a dedicated tax engine or validated external rate source.
Accountable owner: Finance, with billing operations handling configuration.
Example: A regulatory fee changes in one state, but the old rate remains configured for several billing cycles and the reseller must later absorb the difference.
5 Revenue Assurance KPIs Every MVNO and Telecom Reseller Should Track
Finding leakage is only the first step. To prevent the same problems from recurring, you need a small set of metrics that shows where value is disappearing and whether your controls are actually working.
You do not need dozens of KPIs to get started. For most MVNOs and telecom resellers, five metrics provide a practical baseline across billing, carrier costs, reconciliation, commissions, and exception resolution.
| KPI | What It Measures | How to Calculate It |
|---|---|---|
| Active-but-unbilled rate | Potential revenue leakage from active services not appearing on customer invoices | (Active services not billed ÷ Total active services) × 100 |
| Carrier invoice variance | Difference between actual wholesale charges and expected contracted cost | (Actual carrier cost − Expected cost) ÷ Expected cost × 100 |
| Reconciliation coverage | Percentage of services checked against carrier and customer billing records | Reconciled services ÷ Total active services × 100 |
| Commission accuracy rate | Accuracy of partner and sales commission calculations | Correct commission calculations ÷ Sampled commission calculations × 100 |
| Days to detect vs. days to recover | How quickly leakage is identified and resolved | Median days from leakage occurrence to detection, and from detection to resolution |
Stop Revenue Leakage Before It Hits Your Margin
For MVNOs and telecom resellers, revenue leakage is not just a billing issue. It can come from unbilled services, carrier invoice errors, outdated rates, expired discounts, proration, commissions, and other gaps between what you deliver, pay, bill, and collect.
The first step is simple: reconcile your active services, carrier charges, customer invoices, and payments. Then track the exceptions, assign ownership, and fix the controls that allow them to repeat.
You do not need a perfect industry benchmark to know whether you are leaking margin. Your own data can show where the gaps are and how much they are costing your business.
Ready to find yours? Start a 30-day connectivity revenue audit with your active-service data, carrier invoices, customer billing records, and wholesale contracts.
FAQs
Find where your connectivity margin is leaking. Start a 30-day revenue audit with Spenza today.
