Choose telecom billing software by testing how it charges in real time, how fast your team can launch a new offer in its catalogue, and how it handles the traffic you exchange with other operators. Delivery model and migration path come next, because they decide what the system costs you after go-live, not just at signature.
Feature lists from billing vendors look alike. Almost every one says convergent, real-time, cloud-ready and open. The differences show up only when you ask the system to do something specific in front of you, which is what this guide is for: the criteria that separate systems, a table of demo tests, and a checklist to paste into an RFP.
What telecom billing software has to do
Telecom billing software turns network usage into money. It rates calls, messages and data sessions against price plans, keeps prepaid balances and postpaid accounts, produces invoices, collects payments and settles with partners. In a modern BSS (business support system) that work is split across several modules that have to behave as one:
- Online charging (OCS) authorises and charges usage in real time, so a prepaid customer cannot go below zero and a data bundle stops when it is used up.
- Product catalogue holds offers, bundles, prices and eligibility rules in one place.
- Convergent billing produces one account and one invoice across prepaid, postpaid and every service line.
- Mediation collects and cleans usage records from the network before they are rated.
- Interconnect and wholesale billing settles with other operators, the host network and, for an MVNE, its tenants.
A vendor that sells “billing” may cover two of these or all five. Ask early which ones are in scope, because the gaps become separate projects.
Eight criteria that separate billing systems
These are the criteria where systems actually differ. Each one comes with the question to ask.
- Real-time convergent charging. Prepaid, postpaid and hybrid customers should be charged by one engine with one balance model. Ask: can a customer move from prepaid to a monthly plan without being re-created in another system?
- Catalogue and time to market. Marketing should be able to build and test an offer without a code release. Ask: how long does it take to launch a new bundle, from idea to first subscriber, and who has to be involved?
- Rating flexibility. Tiered prices, shared balances, family plans, zero-rated apps and promotions with end dates all need to be configuration, not development. Ask: show me a shared data pool across four lines with one line on a different allowance.
- Interconnect and roaming. If you settle with other operators, the system needs dated partner tariffs, re-rating of closed periods and reconciliation. Interconnect billing is often the module bought last and regretted first.
- Mediation. Usage records come from different switches, gateways and partners in different formats. Ask: how is a new network element added, and what happens to duplicates and malformed records?
- Multi-tenancy for an MVNE. An enabler running several MVNOs needs separate catalogues, balances and invoices per tenant on one platform, plus wholesale settlement between them. Ask: can tenant A change a price plan without a release that touches tenant B?
- Open APIs. CRM, self-care apps, payment gateways and partner portals all need to reach billing. TM Forum’s Open APIs (product catalogue, ordering, usage and customer bill, among others) are the common reference. Ask which ones the vendor exposes and which are custom.
- Delivery model and migration. On-premises, private cloud, public cloud or a managed service change who runs upgrades, where subscriber data lives and how the cost is booked. Ask how existing subscribers, balances and open invoices move from the old system, and how long the parallel run lasts.
Key point. Criteria 1, 4 and 8 are the expensive ones to get wrong. A missing report can be built later; a charging engine that cannot do hybrid plans, or a migration that loses balances, cannot.
Demo tests: requirement and how to check it
A demo run on the vendor’s own script shows what the vendor wants you to see. Send your scenarios a week before and ask for them to be run live.
| Requirement | How to check it on a demo |
|---|---|
| Real-time prepaid control | Start a data session on a prepaid account with a small balance and watch it stop at zero |
| Prepaid to postpaid move | Convert one customer, keep their number and balance, and show the next invoice |
| New offer without code | Have a product manager build a bundle with a promotion and an end date during the call |
| Shared and multi-balance | Show one data pool across four lines with a separate allowance on one line |
| Re-rating | Change a tariff with a past start date and re-rate last month for one account |
| Interconnect reconciliation | Load a partner statement and show the discrepancies against your own rated traffic |
| Multi-currency | Invoice one customer or partner in a second currency with the exchange rate on the invoice date |
| Tenant isolation (MVNE) | Change a price in tenant A and show that tenant B is untouched |
| API access | Create an order and read the resulting bill through the API, not the GUI |
Nine live tests, run on your own scenarios, say more than a long RFP response.
RFP checklist for telecom billing software
Paste these into the requirements section of an RFP, and ask for “yes, configured”, “yes, with development” or “no” against each:
- Prepaid, postpaid and hybrid charging in one engine, with one balance model
- Real-time charging over Diameter (and CAMEL if you still run 2G/3G)
- Product catalogue managed by business users, with eligibility, compatibility and offer priority
- Shared balances, accumulators, bonuses and promotions with validity dates
- Bundles across mobile, fixed and digital services on one invoice
- Multi-currency and multi-balance accounts
- Re-rating of closed periods with dated tariffs
- Mediation with filtering, de-duplication and aggregation
- Interconnect billing with reconciliation, netting and partner balances
- Multi-tenant operation with per-tenant catalogue and invoicing (MVNE only)
- Documented APIs, with the TM Forum Open APIs covered named explicitly
- Exports to ERP, CRM and reporting tools
- Deployment options: on-premises, private cloud, managed service
- A migration plan for subscribers, balances, open invoices and history, with a parallel run
- References from operators of a similar size and model
Choosing billing software for an MVNO
For an MVNO (mobile virtual network operator), the right billing scope follows the operating model. A Light MVNO that resells the host’s service often uses the host’s or an enabler’s billing and needs mainly a catalogue, CRM and invoicing it controls. A Medium MVNO runs its own charging and billing on top of the host network, so criteria 1 to 3 decide the choice. A Full MVNO adds its own core and interconnect agreements, which brings criteria 4 and 5 into scope from day one. The operating models page compares them line by line.
The common mistake is buying for launch day only. A bank or retailer that starts with prepaid SIMs will usually want monthly plans, family bundles or a second country soon after launch. If the billing system cannot do those without a migration, the cheap launch becomes an expensive second project. Our review of MVNE and MVNO BSS platforms lists vendors by the models they fit.
Where Avante fits
Avante builds BSS for telecom operators, MVNOs and the MVNEs and MVNAs that serve them. The billing scope described above maps onto its modules:
- Avante OCS charges prepaid and postpaid in real time over Diameter and CAMEL, with multi-balance at service and contract level and horizontal scaling without service interruption.
- Avante Billing is a convergent billing system with multi-currency, multi-balance accounts, bonuses and accumulators, and reporting exports to ERP and CRM.
- Avante PC, the product catalogue, lets marketing build convergent prepaid and postpaid offers step by step, with availability rules and offer priority.
- Avante Mediation and Avante IBS handle usage collection and interconnect settlement.
For MVNOs and MVNEs the modules come together as the MVNO platform, behind one API and deployed on-premises, in a private cloud or as a managed service. Avante is a TM Forum member and won the Best Moonshot Catalyst award at DTW Ignite 2025 for its ODA-in-a-Box modernisation engine.
FAQ
What is the most important feature of telecom billing software?
Real-time convergent charging. If one engine handles prepaid, postpaid and hybrid customers with one balance model, you can change plans, bundle services and move customers between payment types without migrations. Most other gaps, such as a missing report or an extra invoice format, can be closed after go-live; a split charging architecture cannot.
How is MVNO billing software different from operator billing software?
The functions are the same, but the scope depends on the MVNO’s operating model. A Light MVNO may need only catalogue, CRM and invoicing, while a Full MVNO also needs interconnect billing and mediation. An MVNE needs multi-tenancy on top, so several MVNOs can run separate catalogues and invoices on one platform.
How long does it take to replace a telecom billing system?
It depends on the number of subscribers, products and integrations, and on how clean the data is. Plan for configuration of the catalogue, integration with CRM, network and finance, data migration with a parallel run, and a staged cut-over. Ask each vendor for a dated plan built on your own volumes, not a generic range.
Should telecom billing software be cloud or on-premises?
Either can work; the choice turns on data residency, regulation and who you want to run the system. Regulated sectors such as banking or government often keep subscriber data on-premises or in an approved data centre. A managed service moves upgrades and operations to the vendor and spreads the cost over the contract.
Shortlisting billing vendors?
Send us your scenarios and we will run them live on Avante OCS and Billing.
Request a Demo