A wholesale billing review is rarely glamorous work, but it is where an MVNO discovers whether its commercial model works in practice or only in a spreadsheet. A tariff can look attractive at launch, subscriber growth can be encouraging, and the brand can be acquiring customers efficiently. None of that protects margin if the usage records, wholesale rates, retail charges and settlement invoices do not reconcile.
For a light MVNO in particular, billing is not a back-office utility. It is the commercial control plane between the host MNO, the MVNE, payment providers and the customer. Weak controls create leakage in both directions: the MVNO pays for usage it cannot recover, or it charges customers inaccurately and damages retention. The first issue is a margin problem. The second becomes a brand problem very quickly.
Why wholesale billing deserves executive attention
Wholesale billing sits at the point where contractual terms meet network events. The host network records voice, SMS and data activity. An MVNE may mediate, enrich or rate those records. The MVNO applies its retail proposition, allowances, out-of-bundle rules, discounts, taxes and customer policies. Each layer can be individually reasonable while the combined result is commercially wrong.
The most damaging errors are often small. A fractional difference in data rounding, an omitted roaming destination, or a tariff table loaded a month late may not be visible in a high-level P&L. Across a growing base, however, these exceptions compound. They also distort product decisions. An apparently profitable unlimited plan may be loss-making for a cohort with particular roaming, tethering or international calling behaviour.
A proper review should therefore answer more than, “Does the invoice add up?” It should establish whether the MVNO can explain usage, price it correctly, recover costs, and challenge a supplier with evidence when the numbers do not match.
The wholesale billing review framework
The strongest reviews follow the usage journey rather than starting with the supplier invoice. Begin with a representative event on the network and follow it through every commercial system until it reaches both the customer bill and the wholesale settlement.
Start with the commercial source of truth
Before testing data, identify which documents and systems define the truth. This usually includes the wholesale agreement and rate cards, product catalogue, allowance policy, roaming terms, MVNE service schedule, tax treatment, and approved change requests. In many MVNOs, these sources are fragmented. Commercial teams hold the signed rate card, operations holds a revised spreadsheet, and billing has a configuration that reflects neither perfectly.
The review should produce a controlled tariff inventory. For every active product, record the retail charge, included units, fair-use terms, out-of-bundle rate, applicable zones, effective dates and wholesale cost basis. Where the MVNO sells through multiple channels or brand partners, include promotional pricing and dealer-funded discounts. A rate is not operational merely because it appears in a contract. It must be loaded, versioned and demonstrably active in the rating environment.
Reconcile network usage to rated usage
The next task is to compare source usage records with the events received and rated by the MVNO or its billing partner. Depending on the architecture, this may involve CDRs, data usage records from the P-GW, roaming files, mediation outputs and customer-facing consumption records.
The objective is not necessarily to match every record one-for-one. Aggregation, latency and privacy controls can make that impractical. The objective is to explain material variances by service, destination, time period and subscriber segment. Data deserves particular attention because rounding rules, session boundaries and delayed usage can create meaningful differences.
Test normal domestic usage, but do not stop there. The exceptions expose the real operating quality: port-in and port-out dates, SIM swaps, suspended accounts, shared data plans, roaming, premium destinations, short-duration calls, spend caps, and accounts that move between tariff versions. These are the conditions under which a nominally integrated billing stack tends to reveal manual workarounds.
Test rating logic, not only invoice totals
Invoice-level reconciliation can conceal rating defects. A wholesale invoice may appear consistent with its own rate card while the retail bill is wrong, or the MVNO may be giving away usage because its allowance logic is too generous.
Use a controlled sample of subscriber journeys and calculate the expected outcome independently. Test the first byte or first minute of out-of-bundle usage, allowance exhaustion, a mid-cycle plan change, a recurring discount, and the final bill after cancellation. For roaming, test both the customer price and the underlying wholesale cost. For enterprise and IoT propositions, test pooled usage, private APN traffic and the treatment of inactive SIMs.
This is where commercial teams should be involved. Billing specialists can confirm configuration, but they cannot decide whether the configuration still supports the proposition. If a plan promises a fixed monthly price yet data overage is triggered by a rounding convention customers cannot reasonably understand, the issue is product design as much as billing.
Challenge supplier settlement with evidence
Once usage and rating have been tested, compare the supplier invoice with independently calculated expected charges. Segment variances into categories: volume differences, rate differences, timing differences, tax differences and unexplained items. A variance log should name an owner, the financial exposure, the evidence required and the deadline for resolution.
Do not treat every variance as a dispute. Some are legitimate timing effects, particularly around roaming records and late-arriving usage. Others result from a contract that leaves a tariff interpretation open. The practical question is whether the variance is predictable, bounded and reflected in the MVNO’s margin model. If not, it needs commercial or operational correction.
A mature wholesale relationship should support transparent dispute handling. That means agreed file formats, clear invoice detail, defined credit-note procedures and a realistic escalation route. If the MVNO cannot reconstruct an invoice line without supplier intervention, it does not have sufficient control of its cost base.
Where margin leakage usually hides
Most leakage is not caused by one spectacular billing failure. It emerges from gaps between teams, platforms and contract versions. Four areas deserve regular scrutiny:
- Data rounding and allowance treatment: Wholesale data may be rounded per session while retail rating rounds differently. Unlimited or large-bundle plans can mask the impact until heavy users scale.
- Roaming and international services: Zone changes, delayed TAP files, destination classifications and international SMS are frequent sources of unexpected cost and customer complaints.
- Tariff change governance: Product launches, promotional offers and rate-card updates often reach sales before they reach the billing configuration and finance controls.
- Inactive and exception states: Suspended SIMs, failed activations, disconnected accounts and IoT devices can continue to attract platform, numbering or connectivity charges.
The response should not be to build a large manual reconciliation team. Manual work may be necessary while an MVNO is small or resolving a legacy issue, but it does not scale and it weakens accountability. The better approach is to automate the repeatable controls, set materiality thresholds, and reserve expert review for the exceptions that can change margin or customer outcomes.
Turn review findings into operating discipline
A billing review has little value if it becomes a quarterly forensic exercise. The output should be a short control agenda with named owners across commercial, finance, operations and the MVNE relationship.
At minimum, establish a monthly wholesale-to-retail margin bridge by product and usage type. Track billed usage completeness, rating exceptions, disputed invoice value, credit-note ageing and revenue leakage estimates. These measures should be visible before month-end close, not discovered after finance has locked the period.
Change management matters just as much. Every product or pricing change needs a documented effective date, configuration confirmation, test evidence and post-launch validation. For high-risk changes such as roaming bundles or unlimited plans, require a defined cost guardrail. This is not bureaucracy for its own sake. It is how an MVNO protects the simplicity of its customer proposition while retaining commercial control.
The strategic value of getting billing right
An MVNO does not win because its billing platform has more features than a competitor’s. It wins when the platform supports a proposition that customers understand and the business can profitably deliver. A wholesale billing review makes that distinction visible.
For founders and operators, the useful closing question is simple: if a supplier invoice increased by 8 per cent next month, could the team identify the affected products, subscribers and usage types within days? If the answer is no, the next priority is not another tariff launch. It is building the billing evidence needed to run the business with confidence.
