MVNO Billing Platform: Features, Pricing & Setup | VoiceBuy

Quick answer: An MVNO billing platform rates subscriber usage, applies plan rules, generates CDR-based charges and connects to IMS/HSS and the wholesale supplier. It needs real-time balance control, dunning, tax handling and reseller support. The right pricing model depends on traffic forecast, margin target and network risk.

What an MVNO billing platform actually does

An MVNO does not own the radio network, but it does own the customer relationship. That means it must decide, in real time, whether a subscriber is allowed to make a call, how much that call costs, and what appears on the invoice. The billing platform is the system that turns raw network events into a customer-visible product. It sits between the core network (IMS/HSS or HLR), the wholesale supplier and the subscriber-facing apps.

This page focuses on the MVNO billing layer. For the wider platform, see wholesale MVNO solutions, infrastructure and pricing; for the launch sequence, see how to build a cloud MVNO.

Core features checklist

Capability Why it matters What to verify
Real-time rating Stops revenue leakage and runaway usage Per-second or per-minute rating, rating before or after connect
Plan and bundle engine Defines what subscribers buy Included minutes, data buckets, rollover, add-ons, family plans
Balance and credit control Prevents post-paid losses Online charging integration, threshold alerts, automatic top-up
CDR ingestion Source of truth for usage Formats, deduplication, late CDR handling, dispute flags
IMS/HSS integration Links identity and service profile to billing state Diameter/Radius interfaces, subscriber status synchronisation
Wholesale reconciliation Protects margin Supplier rate tables, route-level margin reports, invoice matching
Tax and invoicing Required for regulated markets Jurisdiction rules, VAT/sales tax, digital invoices
Dunning and collections Recovers unpaid balances Retry schedule, payment channels, suspension rules
Reseller and partner support Enables channel growth Multi-tenant accounts, commission, white-label invoices
Self-care and APIs Reduces support cost Customer portal, mobile app APIs, usage visibility

IMS, HLR/HSS and billing integration

Subscriber identity lives in HSS (or HLR in legacy networks). Service control lives in IMS. Money lives in the billing platform. If these three disagree, subscribers see incorrect balances or calls fail unexpectedly. A practical integration checks three states: the subscriber is provisioned in HSS, the service profile allows the call in IMS, and the charging system authorises it. Changes to credit status must propagate in both directions; a suspended account should be reflected in the network, not only in an invoice.

For the network side, our cloud IMS platform explains how the service layer is built, and IMS architecture in 2026 covers the call flow in detail.

Pricing models the platform must support

The billing engine should be able to represent the commercial model you agreed with the host network, not force you into one template. The six common models are retail minus, cost plus, revenue share, capacity commitment, tiered volume and hybrid. Each changes who carries volume risk and who sees margin first. The MVNO wholesale pricing models guide compares them side by side.

  • Retail minus: you pay the host network a percentage of retail revenue; simple, but margin moves with discounting.
  • Cost plus: wholesale cost plus a fixed margin; predictable, but you carry volume risk.
  • Revenue share: aligns incentives, but requires transparent reporting from both sides.
  • Capacity commitment: lower unit cost in exchange for a minimum spend; risky if demand is uncertain.
  • Tiered volume: unit price falls as traffic grows; needs accurate forecasting.
  • Hybrid: a combination, common in real contracts; the billing system must model more than one rate simultaneously.

Setup timeline (illustrative, not a guarantee)

The following sequence is a planning illustration. Actual timing depends on the host network, number porting, regulatory approval and how much of the stack already exists.

  1. Commercial design (week 1): choose the wholesale model, define plans, target margin and tax jurisdictions.
  2. Integration design (weeks 1-2): map HSS/IMS interfaces, CDR formats and charging flows.
  3. Platform configuration (weeks 2-4): load rate tables, plan catalogue, dunning rules and reseller hierarchy.
  4. Lab testing (weeks 3-5): test call setup, rating edge cases, roaming and suspension/reactivation.
  5. Pilot with a limited subscriber group: validate invoices and dispute handling before a full launch.
  6. Go live and monitor: track rating accuracy, failed charges and margin by service.

Common mistakes

  • Rating only after the call: gives no control over high-risk subscribers or fraud.
  • Ignoring late CDRs: produces under-billing and reconciliation disputes.
  • No route-level margin view: overall averages hide unprofitable destinations.
  • Treating tax as a post-launch task: retrofitting invoices is expensive and risky.
  • Building for one pricing model: contract renegotiation then requires a platform rewrite.

How to evaluate a platform

Ask vendors to demonstrate a real call: provision a subscriber, change the credit limit, make a rated call and generate an invoice. Ask how a late CDR is handled, how a reseller is billed, and how a tariff change is versioned. Require a written list of supported HSS/IMS interfaces and a sample margin report by destination. Avoid any claim of guaranteed launch time or revenue.

Frequently asked questions

Do I need a separate billing platform if my IMS vendor offers billing?

It depends on the commercial complexity. Basic post-paid rating may be enough for a small pilot. A multi-plan, multi-reseller MVNO usually needs a dedicated billing system with stronger reconciliation, tax and dunning capabilities. Test the actual workflows rather than relying on a feature list.

What is the difference between online and offline charging?

Online charging authorises usage before or during the call using a real-time balance. Offline charging rates CDRs after the call. Pre-paid services normally need online charging; post-paid can use offline charging with credit limits. Many MVNOs run both.

Which wholesale model is easiest to bill?

Retail minus and cost plus are usually the simplest to represent in a rating engine. Revenue share and hybrid contracts need more detailed reporting and reconciliation. The best model is the one matching your risk tolerance, not the one that is easiest to configure.

Can billing prevent wholesale margin loss?

Only if it reports margin by route and destination, not just total revenue. Rating errors, unprofitable routes and late CDRs all erode margin silently. Route-level reporting is the control that matters.

Request a platform demo

Want to see how billing, IMS and wholesale rates fit together for your MVNO? Request a VoiceBuy platform demo and bring your planned price points and traffic forecast.

Ready to Get Started?

Contact our team today and get a fast response.

Contact Us

Last edit: November 19, 2026 - 20:05

ENG. Hisham Mohamed

Written by

ENG. Hisham Mohamed

Eng. Hisham Mohamed is a telecommunications specialist with over 8 years in VoIP, SIP termination, IMS and MVNO infrastructure. He writes VoiceBuy's guides.

Chat with
our team