By clicking “Accept”, you agree that cookies may be stored on your device in order to improve site navigation, analyze site usage, and help us with our marketing efforts. Check out our for more information.

Guides

Convergent billing: the complete guide for every industry

#QUOTE-TO-CASH Insights
Opencell #QUOTE-TO-CASH Insights cover: Convergent billing, the guide

Convergent billing: the complete guide for every industry

OpencellNovember 21, 202613 min read

One customer, one account, one invoice. Behind it, dozens of rules that must converge.

Convergent billing means billing services of different kinds from a single system, and often on a single invoice: subscriptions, usage, one-off sales, prepaid and postpaid, several products or several lines. Instead of one billing system per product, the company gets a single view of the customer, a single catalog and a single rating engine.

The term was born in telecoms, when operators wanted to bring fixed line, mobile, broadband and TV onto one bill. It now goes far beyond that industry. A software vendor selling a subscription, usage credits and professional services, an energy supplier adding EV charging, an IoT provider billing connectivity and devices: all face the same convergence challenge.

Most search results on the topic come from telecom specialists and analyst firms. This guide takes a wider view: what converges, why, in which industries, with which technical requirements, and how to choose a convergent billing system.

For the operator-specific case, see our guide to telecom billing and BSS.

What is convergent billing?

Convergent billing is the ability to bill, from one platform, every way a company sells and gets paid: several pricing models in one offer, several services for one customer with cross-discounts, prepaid and postpaid in one account, and a single invoice or a chosen split, all produced from the same data.

In practice, a convergent billing system can:

  • combine several pricing models in one offer: flat fee, usage, tiers, overage, one-off sale;
  • manage several services for one customer, with cross-service discounts;
  • handle prepaid and postpaid in the same account, or even the same offer;
  • produce a single invoice, or several invoices if the customer needs them, from the same data.
Siloed billing Convergent billing
Systems One per product, payment mode or business One platform for all
Customer view Several unrelated accounts One account with all its services
Bundles Discounts calculated by hand, or impossible Cross-discounts configured in the catalog
Invoices One per system One invoice, or a chosen split
Launching an offer Repeated in every system Configured once
Costs Several systems to maintain One platform to evolve

Two related terms are often confused. Convergent charging refers, in telecoms, to real-time rating of usage, whether prepaid or postpaid. The 3GPP specification TS 32.290, which describes the charging function of the 5G core, includes offline, online and converged charging scenarios. Convergent billing is broader: it also covers subscriptions, invoicing, payment and the customer relationship.

Why converge?

Companies converge their billing for four reasons: to sell bundles with cross-discounts, to simplify the customer relationship with one account and one invoice, to launch combined offers faster from one catalog, and to cut the cost and revenue leakage of running several systems.

To sell bundles

Customers increasingly buy packages: a subscription with add-ons, a main service with related services, equipment with a contract. Cross-discounts such as "20% off the second service" are impossible to manage cleanly when each service lives in a different system.

To simplify the customer relationship

One invoice, one customer portal, one point of contact: convergence reduces calls to customer care, reconciliation errors and misunderstandings. It also gives sales teams a complete view of the customer, useful for offering the right service at the right time.

To launch offers faster

With a single catalog, a new offer combining several services is configured once, without development in several systems. That is a decisive advantage for companies that regularly test new pricing models.

To cut costs and leakage

Every extra system has a cost: licenses, maintenance, teams, interfaces. Every interface between two systems is also a place where revenue gets lost, as our guide to revenue leakage explains. Convergence reduces both.

What converges: the four dimensions

Convergence plays out across four dimensions that combine: services (several products for one customer), pricing models (subscription, usage, tiers, credits, one-off sales), payment modes (prepaid, postpaid, mixed) and accounts (lines, sites, users, subsidiaries).

Services

Several services for one customer: in telecoms, fixed, mobile, broadband and TV; in software, several products or modules; in energy, electricity, gas, efficiency services and EV charging.

Pricing models

Flat subscription, per-unit usage, tiers, minimum commitments, prepaid credits, one-off sales of equipment or services. One offer can mix several of these, as our guides to recurring billing and usage-based billing describe.

Payment modes

Prepaid, where the customer pays before consuming and the balance must be checked in real time, and postpaid, where the customer is billed afterwards. One customer can have both: a prepaid mobile line and a postpaid home broadband plan, or a postpaid subscription plus prepaid credits for extra usage.

Accounts

One customer can have several lines, sites or users. Business customers add subsidiaries and cost centers. The account hierarchy brings them together, allocates costs and decides who receives the invoice.

Dimension Examples Requirement for the system
Services Fixed, mobile, broadband; software modules; energy and charging Shared catalog and cross-discounts
Pricing models Subscription, usage, tiers, credits, one-off sales A rating engine that can combine them
Payment modes Prepaid, postpaid, mixed Real-time balances and periodic invoicing
Accounts Lines, sites, users, subsidiaries Multi-level account hierarchy

Industries that need convergent billing

Convergent billing started with telecom and cable operators, but it now matters for software and digital services, energy and mobility, IoT, and any company that combines a subscription, usage and one-off sales: banks, insurers, media and transport operators.

Telecom and cable operators

The birthplace of convergent billing. Bundles of fixed, mobile, broadband and TV, family multi-line plans and loyalty discounts forced operators to unify their systems. Operators now add partner content, cloud services and connected devices.

Software and digital services

A vendor sells a per-user subscription, usage (API calls, storage, compute), prepaid credits and professional services. With the rise of AI, usage takes a growing share of revenue, as our guide to AI billing shows.

Energy and mobility

Energy suppliers combine supply, efficiency services, EV charging and sometimes self-consumption. Each business has its own pricing and metering rules, yet the customer expects a single relationship. See our guide to EV charging billing.

Internet of Things

An IoT provider bills connectivity, the platform, the devices themselves and usage-based services, often to companies deploying thousands of devices. Our IoT billing guide details these models.

Financial services, media, transport

More broadly, any company combining a subscription, usage and one-off sales needs convergence: banks and insurers selling packaged services, media combining subscriptions with pay-per-view, transport and shared mobility operators.

One customer, one catalog, one invoice

Convergence rests on three foundations: a single view of the customer with all services, contracts, balances and payments; a single catalog shared by sales channels, CPQ and billing; and an invoice that can be unified or split as the customer prefers, from the same data.

A single customer

The foundation of convergence is a single customer view: services, contracts, usage, balances, invoices and payments. Without it, you cannot apply a cross-discount or simply answer a question about the bill.

A single catalog

The catalog describes every offer, its components, prices and compatibility rules. It lets you create bundles with their discounts without duplicating products. It is shared by sales channels, CRM, CPQ and billing, which guarantees that what is sold is what is billed.

One invoice, or nearly

The convergent invoice groups all the customer's services. It must stay readable: a summary on page one, detail per service, an explanation of cross-discounts. Some customers, especially businesses, prefer several invoices, by site or cost center. Convergence does not mean forcing a single invoice; it means being able to choose the split from the same data.

Real time, prepaid and postpaid

Prepaid requires knowing the customer's balance at every moment to authorize or refuse usage. Postpaid also needs real time to cap usage, alert customers before an overage or apply a fair use policy. A convergent system rates every event as it arrives and feeds both prepaid balances and postpaid counters.

Why real time

Prepaid means knowing the customer's balance at all times, to authorize or deny consumption. Postpaid can need real time too: to cap usage, warn a customer before an overage or apply a fair use policy.

Continuous rating

In a convergent system, each usage event (call, data session, API call, charging session, kilowatt-hour) is collected, checked and rated as it happens, according to the contract. That is the job of billing mediation, then the rating engine. Prepaid balances are decremented, postpaid counters are updated, and the invoice at the end of the period is simply the sum of what has already been rated.

Mixed cases

Hybrid offers are increasingly common: a postpaid plan with an included allowance, then prepaid top-ups beyond it; a software subscription with a wallet of usage credits shared between users. A convergent system treats each of these as one offer, on one account, not as two products managed separately.

Convergent billing in B2B

Business customers add their own requirements to convergence: multi-level account hierarchies, tailored contracts with group-wide commitments, invoices consolidated at group level or split by entity, and high volumes of lines, devices or users to rate every day.

  • Account hierarchies: parent company, subsidiaries, sites, cost centers and users, with terms negotiated at group level and applied everywhere.
  • Tailored contracts: specific prices, volume commitments across all services, year-end rebates.
  • Fitting invoices: consolidated at group level or split by entity, with detail usable for internal chargebacks.
  • High volumes: thousands of lines, devices or users, with usage to rate every day.

When the supplier is itself a group, convergence meets multi-entity billing: one customer may be served by several entities, in several countries and currencies.

Architecture and project

A convergent platform brings together the catalog, customer accounts, orders and subscriptions, mediation, rating, invoicing, payment and integrations. Companies either replace their systems in waves or first add a convergent layer on top of them. Either way, success starts with catalog rationalization and parallel billing runs.

The building blocks of a convergent platform

Building block Role
Offer and price catalog Describe every offer, its components and rules
Customers and accounts Hierarchies, contracts, payment methods
Orders and subscriptions Activate, change, suspend and cancel services
Mediation Collect and check usage events
Rating Price each usage event, in real time when needed
Invoicing Produce invoices, credit notes and revenue recognition data
Payment and dunning Direct debits, payments, cash matching, reminders
Integrations CRM, ERP, technical systems, e-invoicing platforms

Replace or unify

There are two approaches. The first replaces existing systems with a convergent platform in waves, one product or customer segment at a time. The second places a convergent layer above existing systems, for the invoice and customer relationship, before replacing them gradually. The choice depends on the age of the systems, volumes and commercial urgency.

Key steps

  1. Map existing offers, systems and flows.
  2. Rationalize the catalog before migrating it.
  3. Define the target invoice with sales and customer care teams.
  4. Migrate in waves, with a period of parallel billing to compare results.
  5. Decommission old systems once every gap is explained.

How to choose a convergent billing system

To choose a convergent billing system, test it on your own offers: a real bundle mixing subscription, usage and one-off sale, a prepaid and a postpaid component, a mid-month change and a business customer with several sites. Then check real-time rating, volumes, hierarchies, invoice options, multi-entity support, APIs, deployment and project method.

Criterion Question to ask
Catalog Can you create an offer combining subscription, usage and one-off sale, with cross-discounts, without development?
Payment modes Are prepaid and postpaid handled in the same account and offer?
Real time Can usage be rated and balances checked in real time?
Volumes How many events per day, with what measured performance?
Hierarchies How many account levels, with what rules for inheriting terms?
Invoice Can you choose between one invoice and a split by site or cost center?
Multi-entity Are several entities, countries and currencies handled natively?
Integration Which APIs to CRM, ERP, network and e-invoicing platforms?
Deployment SaaS, private cloud, on premise: which options, and where is data hosted?
Project Which migration method, what timeline, which comparable references?

Ask for a demo on your own offers: a real bundle with a prepaid and a postpaid part, a mid-month plan change and a business customer with several sites. Our billing guide offers a broader comparison grid.

Frequently asked questions about convergent billing

What is convergent billing?

It is billing, from one platform and often on a single invoice, services of different kinds: subscriptions, usage, one-off sales, prepaid and postpaid, several products or several lines for the same customer.

What is a convergent billing system?

It is a billing platform that combines a single catalog, a single customer account and a single rating engine, so it can price every service and payment mode a company sells and produce one invoice or a chosen split.

What is the difference between convergent billing and convergent charging?

Convergent charging refers to real-time rating of usage, prepaid or postpaid, mostly in telecoms. Convergent billing is broader: it also covers subscriptions, invoicing, payment and the customer relationship.

Is convergent billing only for telecoms?

No. It started with operators, but it matters for any company combining subscriptions, usage and one-off sales: software vendors, energy suppliers, IoT providers, media and financial services.

Do you always need a single invoice?

No. A single invoice simplifies the relationship with consumers, but many business customers prefer a split by site or cost center. A convergent system lets you choose the split from the same data.

How do you handle prepaid and postpaid together?

With a real-time rating engine that decrements prepaid balances and updates postpaid counters, and a single customer account that holds both. Hybrid offers then become one offer.

How long does a convergent billing project take?

It depends on the number of systems to unify, volumes and the quality of the existing catalog. Migrating in waves, product by product or segment by segment, limits risk and lets you measure gains along the way.

Convergence starts with the catalog

Convergent billing is not one more feature in a billing system. It is a way of organizing all monetization around the customer: one catalog, one account, one rating engine and an invoice that simply tells the customer what they bought.

Key takeaways:

  • convergent billing brings together services, pricing models, payment modes and accounts,
  • born in telecoms, it now applies to every subscription and usage-based service,
  • it enables bundles, simplifies the customer relationship and reduces leakage,
  • real time is essential as soon as there is prepaid or usage caps,
  • in B2B, it relies on account hierarchies and fitting invoices,
  • a successful project starts with catalog rationalization and migrates in waves.

The more offers converge, the simpler the invoice must stay.

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 brings together on a single platform the product and price catalog, subscriptions, usage mediation and rating, billing, payment and collections.

Want to bring all your offers onto a single invoice?

Optimize your recurring revenues with Opencell

Get a demo