
Telecom billing and BSS: the complete guide for operators
The network carries the traffic. Billing turns it into revenue.
Telecom billing is one of the most demanding forms of billing there is: millions of subscribers, billions of usage events, bundles that combine mobile, fixed line, broadband and TV, prepaid and postpaid side by side, consumers next to enterprise accounts with thousands of lines.
It runs on a family of software that operators call the BSS. Two groups of systems keep an operator running. The OSS (Operations Support Systems) runs the technical network. The BSS (Business Support Systems) runs everything related to the customer and to revenue: offers, orders, consumption, billing and payment.
The telecom billing system sits at the heart of the BSS, which makes the BSS the commercial and financial core of an operator. Every plan sold, every gigabyte consumed and every add-on activated goes through it before it becomes revenue.
The stakes are high. France, a typical mature market, counts 84.9 million SIM cards and 27.1 million fiber subscriptions, yet operators' retail revenue is declining, according to the Arcep market observatory for Q4 2025. To grow, operators must launch richer offers, faster. And the BSS sets the pace.
This guide is written for CIOs, billing directors and marketing teams at telecom operators, cloud and IoT providers, and their system integrators. It explains what telecom billing is and what makes it different, what a BSS is and what it is made of, how it differs from the OSS, why and how to modernize it, and how to choose a solution.
Contents
- What is telecom billing?
- What makes telecom billing different
- Telecom billing and BSS: what is a BSS?
- The 7 building blocks of a telecom BSS
- OSS vs BSS: what is the difference?
- How an order flows through the BSS
- Why operators' BSS are under pressure
- Legacy vs modern BSS
- Modernizing your BSS: big bang or phased approach?
- TM Forum, ODA and open APIs: the standards to know
- How to choose a telecom billing system
- Customer story: Eir in Ireland
- Frequently asked questions about telecom billing
- The BSS does not run the network. It runs the revenue.
What is telecom billing?
Telecom billing is the set of operations through which an operator turns its customers' subscriptions and usage (calls, texts, data, add-ons) into invoices, then into cash. It covers usage collection, rating each event according to the customer's plan, invoice production, payment and collections.
For an operator, billing is not just another back-office function. It is where every commercial offer becomes revenue, or lost revenue.
A telecom billing system chains four main steps:
- usage collection, from the records produced by the network (CDRs, data sessions),
- rating, which applies to each event the price set by the customer's plan,
- invoicing, which brings together subscriptions, usage, add-ons, discounts and taxes,
- payment and collections, which turn the invoice into cash.
These steps rely on a broader set of software, the BSS, described below. Together they form what every industry calls the quote-to-cash cycle.
What makes telecom billing different
Telecom billing stands out in five ways: prepaid and postpaid coexist, offers are bundled and convergent, usage abroad follows specific rules, enterprise customers have hundreds or thousands of lines, and event volumes are among the highest of any industry.
Prepaid and postpaid
In postpaid, the customer consumes first and receives an invoice later. In prepaid, the customer pays in advance and the balance is decremented in real time: each call or data session must be rated and authorized instantly, before it even happens. The billing system has to handle both, often for the same customer.
Bundled and convergent offers
Mobile plans, home broadband, TV, content, add-ons, multi-line discounts: operators sell offers that combine several services on a single invoice. Each combination adds pricing, discount and eligibility rules. Billing them on one invoice is called convergent billing.
Usage abroad
Usage outside the home country follows its own rules, such as the "roam like at home" regulation inside the European Union. Roaming records often arrive late, through partner operators, and must still be matched to the right subscriber and rated correctly.
Enterprise customers
A single company can have hundreds or thousands of lines, spread across subsidiaries, sites and cost centers. It expects a readable invoice, internal chargebacks, negotiated discounts and sometimes billing on behalf of third parties. This is the territory of B2B and B2B2X account hierarchies.
Extreme volumes
Every call, text and data session produces at least one record. Multiplied by millions of subscribers, these events reach volumes few other industries know. Any data loss translates directly into lost revenue.
On top of this, e-invoicing mandates are spreading across Europe, including France from September 2026, and they also apply to the invoices operators send to their business customers.
Telecom billing and BSS: what is a BSS?
A telecom BSS (Business Support System) is the set of software that runs telecom billing and, more broadly, customer and revenue management: product catalog, order capture, subscription management, usage mediation and rating, invoicing, payment, customer care and reporting. It complements the OSS, which runs the network.
The term comes from the telecom world, where it is framed by the standards of the industry body TM Forum, such as the eTOM process framework. People often say "OSS/BSS" to refer to an operator's entire IT landscape.
A BSS is not a single piece of software. It is a set of building blocks, sometimes supplied by one vendor, more often by several, connected to each other.
The term now reaches beyond mobile and fixed-line operators. Cloud providers, IoT operators and even energy suppliers use comparable systems, because they share the same challenge: billing subscription and usage-based services at scale.
The 7 building blocks of a telecom BSS
A telecom BSS is made of seven building blocks: customer relationship management (CRM), the product catalog, order management, usage mediation and rating, billing, payment and collections, and financial reporting. Each one produces data that the next one depends on.
| Building block | Role | What to watch |
|---|---|---|
| CRM | Know the customer, sell, handle requests | A single customer view, including B2B account hierarchies |
| Product catalog | Define products, plans, add-ons, prices and eligibility rules | Launch an offer without IT development |
| Order management | Process subscriptions, changes and cancellations; trigger network activation | A reliable link with the OSS for activation |
| Mediation and rating | Collect usage (CDRs, data sessions), clean it, price it | Massive volumes, real time, missing feeds |
| Billing | Produce invoices: subscriptions, usage, discounts, taxes | Bundles, convergent billing, readable invoices |
| Payment and collections | Collect, reconcile, chase, suspend unpaid accounts | Multiple payment methods, dunning rules |
| Reporting and finance | Recognize revenue, feed accounting, track KPIs | Fast close, KPIs such as ARPU and churn |
Two building blocks deserve special attention.
Mediation turns the raw records produced by the network, the CDRs (Call Detail Records) and data sessions, into billable events: deduplicated, normalized and linked to the right subscriber. We cover it in depth in our guide to billing mediation.
Rating applies to each event the price defined by the customer's plan: included allowance, tier reached, roaming rate, active add-on. When rating happens in real time, especially for prepaid offers, it is called online charging.
OSS vs BSS: what is the difference?
The OSS (Operations Support Systems) runs the network: equipment inventory, service activation, monitoring and fault management. The BSS (Business Support Systems) runs the customer and revenue side: offers, orders, billing and payment. The OSS answers "does the service work?", the BSS answers "is it sold and billed correctly?".
| Criterion | OSS | BSS |
|---|---|---|
| Scope | The network and technical services | The customer and revenue |
| Functions | Inventory, activation, monitoring, fault management | Catalog, orders, mediation, billing, payment |
| Users | Network and operations teams | Marketing, sales, customer care, billing, finance |
| KPIs | Availability, quality of service, incidents | ARPU, churn, time to market, invoice accuracy |
| Key question | "Does the service work?" | "Is it sold and billed correctly?" |
The two worlds are tightly linked. When a customer subscribes, the order flows from the BSS to the OSS to activate the line. When the customer uses the service, usage flows back from the network to the BSS to be billed.
Many errors are born at these borders: a line activated but never billed, an add-on cancelled but still active on the network, usage lost between collection and rating.
How an order flows through the BSS
An order goes through the BSS in seven steps: the customer picks an offer from the catalog, the order is captured, the OSS activates the service, mediation collects the usage, rating prices it according to the plan, the invoice is produced, then paid. This journey is the operator version of quote-to-cash.
Take a simple example: a business customer subscribes to a mobile plan with an international add-on for twenty lines.
- The offer: the sales rep configures the plan and add-on from the catalog, with the negotiated discount.
- The order: the BSS creates twenty subscriptions linked to the company account.
- Activation: the order goes to the OSS, which activates the twenty lines on the network.
- Usage: every call and data session produces a record collected by mediation.
- Rating: each event gets its price, based on the plan, the add-on and the discount.
- The invoice: the BSS produces one invoice per line or one consolidated invoice, depending on the contract.
- Payment: the payment is reconciled; if it is late, a reminder goes out, then possibly a suspension.
This journey is quote-to-cash, the process that runs from quote to cash collection. We detail it in our quote-to-cash guide.
Why operators' BSS are under pressure
Operators' BSS are under pressure for four reasons: declining retail revenue that forces them to launch new offers faster, the growing complexity of convergent offers and 5G, the explosion of connected devices, and the need to cut the operating costs of often aging systems.
Revenue under strain
According to Arcep, French operators' retail revenue stood at €9.6 billion excluding tax in Q4 2025, down since the start of the year. In this context, every new revenue stream matters, and every euro billed wrongly or forgotten hurts.
Richer offers
Fixed, mobile, fiber, TV, content, add-ons, multi-line: convergent offers multiply the combinations. A rigid BSS turns every new offer into an IT project that takes months.
5G and new use cases
The same observatory counts 32.9 million 5G SIM cards in France, 39% of the base. 5G opens up services that are billed differently: guaranteed quality of service, private networks for enterprises, on-demand services. The BSS still has to know how to price them.
IoT and B2B2X
Connected devices, offers resold by partners, services billed on behalf of third parties: operators increasingly bill for others and with others. The BSS must handle account hierarchies, revenue sharing and very high volumes of small transactions. Our IoT billing guide covers these models.
Legacy vs modern BSS
A legacy BSS is often monolithic, built or heavily customized years ago, costly to change and dependent on one vendor or scarce experts. A modern BSS is modular, configurable without development, open through APIs, deployable in the cloud and designed to scale.
| Criterion | Legacy BSS | Modern BSS |
|---|---|---|
| Architecture | Monolithic, heavily customized | Modular, independent components |
| Launching an offer | An IT project of several months | Catalog configuration, in days or weeks |
| Integration | Custom interfaces, file transfers | Open, documented APIs |
| Deployment | On premise, dedicated hardware | Cloud, containers or on premise |
| Scalability | Limited by the architecture | Horizontal scaling |
| Dependency | Single vendor, rare skills | Open standards, reversibility |
| Running cost | High and rising | Controlled, shared |
Many operators live with several billing systems inherited from mergers, successive launches or subsidiaries. Each one has its own rules, teams and costs. Consolidation then becomes a matter of efficiency as much as agility.
Modernizing your BSS: big bang or phased approach?
A BSS can be modernized in a big bang, replacing the whole system at once, or in phases, migrating offer by offer, segment by segment or block by block. A phased approach reduces risk and delivers value sooner; a big bang avoids running two systems in parallel but concentrates the risk.
Big bang
The whole system is replaced on a given date. The upside: no coexistence period. The risk: everything depends on a single cutover, often covering millions of customers.
Phased approach
The new BSS first serves a limited scope: a new offer, a customer segment (enterprise, a brand, a country) or a building block (rating, billing). Existing customers then migrate in waves.
Three phased patterns come up often:
- new offers first: launch new services on the new BSS and let the old one fade out with its legacy plans,
- by segment: migrate a homogeneous population first, such as business customers or a secondary brand,
- by building block: replace the most critical or most expensive block first and keep the rest.
Whatever the approach, four workstreams make or break the project: catalog rationalization, data migration of customers and contracts, parallel billing runs to check results during the transition, and change management for billing and customer care teams.
TM Forum, ODA and open APIs: the standards to know
TM Forum is the industry body that sets telecom standards. Its Open Digital Architecture (ODA) defines a modular, cloud-native architecture built on interoperable components and open APIs to modernize OSS and BSS. Choosing a solution aligned with these standards eases integration and reduces lock-in.
According to TM Forum, ODA aims for modular, interoperable, cloud-native systems built around open APIs. It covers business architecture, information systems architecture, deployment and transformation management.
For an operator, these standards bring three concrete benefits:
- a shared language between the operator, its vendors and its integrators,
- standardized interfaces that reduce custom development,
- the ability to replace one block without rebuilding everything.
On the network side, 3GPP standards define how usage is measured and passed to the charging and billing system, including for 5G.
How to choose a telecom billing system
To choose a telecom billing system or BSS, assess seven criteria: functional coverage (from catalog to cash), catalog and pricing flexibility, the ability to process usage volumes, openness through APIs, the deployment model, B2B and partner management, and references in your industry.
| Criterion | Questions to ask |
|---|---|
| Coverage | Does it go from catalog to cash? Can you use only part of it? |
| Catalog and pricing | Can you launch a convergent offer with add-ons and discounts without development? |
| Volumes and real time | How many events per day? Real-time rating? How are missing feeds handled? |
| Openness | Documented APIs, CRM and ERP connectors, alignment with industry standards? |
| Deployment | SaaS, private or public cloud, on premise? Hosting in Europe? |
| B2B and partners | Account hierarchies, billing on behalf of third parties, revenue sharing? |
| References | Operators of comparable volume and complexity? Time to go live? |
Ask for a demo on your own offers: a real convergent bundle, a mid-month plan change, a discount across several lines, an enterprise customer with its subsidiaries.
These are the criteria we built the Opencell platform around: a mediation, rating and billing engine designed for high volumes, B2B2X account hierarchies, more than 200 APIs, deployment as sovereign SaaS, in the cloud or on premise, and go-live in three months.
Customer story: Eir in Ireland
Eir, a leading Irish telecom operator with more than 2 million customers, replaced fragmented rating and billing systems with the Opencell platform, which became the core of its new IT landscape, from order capture to payment.
Eir provides mobile, broadband, TV and fixed-line services, and is investing heavily in fiber and 5G.
The challenge: consolidate several rating and billing systems and modernize a legacy estate processing millions of transactions a day.
The solution: Opencell became the core of the new IT landscape, from order capture to rating, billing and payment.
What the project demonstrated:
- handling high volumes of orders with complex lifecycles,
- bundles with up to 40 distinct parameters,
- transferring financial transactions and invoice amounts between customer accounts.
According to Brian Chapman, Eir's CIO, the Opencell solution reduces billing costs, increases operational efficiency and simplifies the IT architecture. Read the full Eir customer story.
Opencell also works with other telecom players such as Orange Business, Salt, Telus and Truphone.
Frequently asked questions about telecom billing
What is telecom billing?
It is the set of operations through which an operator turns subscriptions and usage (calls, texts, data, add-ons) into invoices, then cash: usage collection, rating according to the plan, invoice production, payment and collections.
What is a telecom billing system?
It is the software that collects usage, rates it, produces invoices and manages payments for an operator. It is the central part of the BSS, alongside the CRM, the product catalog and order management.
What does BSS stand for in telecom?
BSS stands for Business Support Systems. It is the software an operator uses to manage its customers and revenue: product catalog, orders, usage mediation and rating, billing, payment and customer care.
What is the difference between OSS and BSS?
The OSS runs the network: inventory, service activation, monitoring and faults. The BSS runs the customer and revenue side: offers, orders, billing and payment. They exchange data constantly: orders go from BSS to OSS, usage goes from OSS to BSS.
Is billing part of the OSS or the BSS?
Billing is part of the BSS. Usage measurement starts in the network, but collecting it, rating it, producing invoices, and collecting payment all belong to the BSS.
What is mediation in a BSS?
Mediation collects the usage records produced by the network, such as CDRs and data sessions, then cleans, deduplicates, normalizes and links them to the right subscriber before the billing engine rates them.
How long does a BSS modernization take?
It depends on scope, number of offers, volumes and strategy. A phased approach can put a first scope into production within a few months, then migrate customers in waves. A full big bang replacement usually takes longer.
Does BSS apply to industries other than telecoms?
Yes. Cloud providers, IoT operators, energy suppliers and mobility services use comparable systems, because they also bill subscription and usage-based services at scale.
The BSS does not run the network. It runs the revenue.
Telecom billing is among the most complex of any industry, and the BSS is its engine. It is the link between what the operator sells and what it collects. When it is rigid, every offer takes months. When it is flexible, the operator can innovate at market speed.
Key takeaways:
- telecom billing combines prepaid, postpaid, bundles, roaming and enterprise accounts,
- the BSS runs the customer and revenue, the OSS runs the network,
- seven building blocks make up a BSS, from catalog to reporting,
- revenue pressure, convergence, 5G and IoT are pushing operators to modernize,
- a phased approach reduces the risk of modernization,
- open standards and APIs make integration and reversibility easier.
A modern network with an old BSS is a highway with a single toll booth.
Go further with Opencell
Opencell is an agile, open source monetization platform that automates quote-to-cash, from quote to cash collection, for subscription and usage-based services. Born in telecoms in 2007, it now manages €14 billion in revenue for around fifty customers, including operators such as Eir, Orange Business, Salt and Telus.
Planning to modernize your BSS or launch new offers faster?



