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

IoT billing: the complete guide to monetizing devices

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

IoT billing: the complete guide to monetizing devices

OpencellNovember 21, 202616 min read

You sell a connected device once. You bill it for its whole life.

A smart meter, a container tracker, a charging station or an industrial sensor no longer earns money only on the day it is sold. It generates revenue every month, through the connectivity, platform, data and services that come with it. Provided you know how to bill them.

That is the challenge of IoT billing: turning millions of events, SIM cards, cascading contracts and multiple partners into accurate invoices, down to the individual device, without losing margin along the way.

The volume is already huge. IoT Analytics estimated the installed base at 21.1 billion connected IoT devices at the end of 2025 and forecasts 39 billion by 2030. In France alone, Arcep counted about 26 million machine-to-machine SIM cards at the end of September 2026.

This guide is for executives, finance, IT and marketing leaders at IoT operators and MVNOs, low-power network operators, device manufacturers and platform providers. It explains who bills what, the possible pricing models, the steps from device to cash, the traps that cost revenue and how to choose an IoT billing solution.

What is IoT billing?

IoT billing covers all the operations needed to bill connected devices and their services: connectivity, platform, data, applications and maintenance. It relies on the lifecycle of each device and the usage data it sends back to calculate prices, produce invoices, share revenue with partners and collect payment.

IoT stands for Internet of Things: equipment fitted with sensors and a connection (cellular, LoRaWAN, satellite, Wi-Fi) that exchanges data without human intervention. People also say M2M, for machine to machine.

IoT billing borrows from two worlds. From telecom billing, it takes volumes, usage measurement and SIM management. From subscriptions, it takes recurring contracts and bundled offers. But it has its own rules:

  • the billed unit is the device, often by the thousand or million, not the customer;
  • the customer is almost always a business, which sometimes resells the device or service to its own customers;
  • usage per device is small but total volume is enormous: a few kilobytes per device, billions of events overall;
  • lifetimes are long, often 5 to 10 years or more, with idle, inventory or suspension periods.
Criterion Consumer telecom billing SaaS subscription IoT billing
Billed unit The line, the customer The user, the account The device, the SIM, the event
Volume per customer 1 to a few lines A few dozen users Hundreds to millions of devices
Usage Voice, texts, data Users, features Kilobytes, messages, API calls, outcomes
Lifecycle Activation, cancellation Sign-up, renewal Inventory, test, active, sleep, suspended, end of life
Customer structure The end customer pays The company pays B2B2X cascade: operator, manufacturer, integrator, end customer
Partners Roaming Few Networks, manufacturers, resellers, marketplaces

To understand the consumption-based pricing behind most IoT offers, see our usage-based billing guide.

Who bills what? The IoT value chain

A single IoT offer involves several players: the connectivity operator, the low-power network operator, the device manufacturer, the platform vendor, the integrator and the end customer. Each bills its share, often in a cascade. This is the B2B2X model: a business sells to another business, which in turn serves an end customer.

Take a simple example: a heating equipment manufacturer sells connected boilers to installers, who fit them in people's homes. Connectivity is bought from an IoT operator, the monitoring platform comes from a software vendor, and the manufacturer offers a predictive maintenance contract.

Who bills whom?

  • the connectivity operator bills the manufacturer per SIM and per data volume;
  • the platform vendor bills the manufacturer per connected device or per API call;
  • the manufacturer bills the installer, or the homeowner directly, for the maintenance service;
  • the installer may rebill part of the service with its own margin.

This has three consequences for billing.

Deep account hierarchies

A large account can group subsidiaries, sites, fleets and thousands of devices. The invoice must be consolidated at the top, detailed at the bottom and split by cost center. An IoT billing platform must therefore manage parent and child accounts across several levels.

Partners to pay

Resellers, integrators and marketplaces expect their commission or revenue share, calculated on what was billed or collected. Partner calculation and settlement belong in billing, not in a spreadsheet on the side.

Margins to track device by device

Connectivity costs vary by country, network and actual usage. If the selling price does not follow, some devices cost more than they earn. Matching purchase cost and billed revenue, device by device, becomes essential.

These mechanics are close to those of telecom operators; our telecom billing and BSS guide details the systems behind them.

IoT billing models

The main IoT billing models are a flat fee per device, usage-based billing, pooled data, tiered pricing, prepaid, hybrid, and outcome-based pricing. The right choice depends on how predictable usage is, the size of the fleet and what the customer actually values.

No model fits every case. Most IoT offers combine several mechanisms and change model over the product's life.

Model Principle When to use it Watch out for
Flat fee per device A fixed monthly price per device, all included Stable, predictable usage; customer wants a simple budget Heavy-usage devices destroy margin
Usage-based Price per kilobyte, message, API call or hour Variable usage, cloud offers Less predictable invoices for the customer
Pooling A data allowance shared by every device in a fleet Large fleets with uneven consumption Overage calculated at fleet level, not device level
Tiers Unit price decreasing with device count or volume Encouraging fleet growth Tier changes during the period
Prepaid (wallet) The customer buys credit consumed over time Seasonal devices, small customers, international Real-time balance tracking and top-up reminders
Hybrid Base subscription plus a variable part above a threshold The most common: predictability and alignment with usage Invoice readability
Outcome-based Price tied to a result: miles tracked, failure avoided, energy saved High-value services, customer buying a result Measuring the outcome and a precise contract

Bill the device, the service or the outcome?

The underlying trend is the shift from selling hardware to selling a service: device-as-a-service. The manufacturer no longer just sells equipment; it sells its use, its availability or its outcome. This changes everything in billing: long contracts, recurring revenue, revenue recognized over time and the need to measure precisely what is delivered.

The special case of pooling

Pooling is very common in IoT connectivity. Instead of a plan per SIM, the customer buys a global allowance (for example a monthly data volume) shared by the whole fleet. Low-usage devices offset heavier ones. For billing, the calculation is no longer done device by device but at group level, with rules for overage and for devices joining or leaving mid-month.

From device to cash: the 7 steps of IoT billing

IoT billing follows seven steps: define the offer in the catalog, manage the device lifecycle, collect and prepare usage data, rate it, produce the invoice, pay partners, then collect and account for revenue. Every step done badly creates lost revenue or a dispute.

1. Define the offer in the catalog

Everything starts with the catalog: offer components (connectivity, platform, service), prices, discounts, commitments, eligibility rules. A flexible catalog lets you launch a new offer in days, without IT development.

2. Manage the device lifecycle

A connected device goes through several states: in stock, in test, active, sleeping, suspended, terminated. Each state has its billing rule. A device in test should not be billed; a suspended device may be billed at a reduced rate. The link between the system that manages SIMs or devices and billing must be automatic.

3. Collect and prepare usage data

This is mediation: retrieving usage data from networks, platforms and devices, checking it, removing duplicates, enriching it (which customer, contract and offer does this device belong to?) and formatting it. In IoT, volumes make this step critical. Our billing mediation guide covers it in detail.

4. Rate the usage

Rating applies pricing rules to usage data: flat fees, tiers, pooled allowances, overages, geographic zones. The calculation must be accurate, traceable and fast enough to keep up with volumes.

5. Produce the invoice

The invoice brings together subscriptions, usage, discounts and taxes, at the right level of the customer hierarchy, with the detail needed: per site, per fleet, per device. For a large account, it must stay readable despite thousands of lines.

6. Pay partners

Reseller commissions, payments to network operators, revenue sharing with a marketplace: these amounts are calculated from what was billed or collected, and must be settled and justified.

7. Collect and account

Direct debits, transfers, card payments, multiple currencies, dunning, cash matching, then accounting entries and revenue recognition. The cycle ends when the money is collected and correctly booked, not when the invoice goes out. That is the whole point of quote-to-cash.

7 traps that leak IoT revenue

In IoT, revenue losses rarely come from one big mistake. They come from small gaps multiplied by thousands of devices: active devices not billed, late usage data, roaming costs not passed on, rigid offers. Spotting them requires continuously reconciling the network, the device base and billing.

1. Dormant or forgotten devices

SIMs activated but never billed, or idle devices billed at full price that end up in disputes. Regularly reconciling the active device base with billed contracts is the first protection.

2. Late or incomplete usage data

When a network's data arrives after the period closes, usage is billed late, or never. Check data completeness before every billing run and know how to handle late arrivals.

3. Roaming and connectivity costs

A device that travels, such as a container tracker, consumes on foreign networks with different costs. If the offer sold ignores these zones, the margin disappears without anyone noticing.

4. Event volumes

Hundreds of thousands of devices reporting several times an hour produce hundreds of millions of events a month. A system that cannot keep up forces simplifications, overly broad flat fees or manual work.

5. 2G and 3G network shutdowns

Legacy networks are being switched off in many countries. In France, Arcep reports that the number of 2G IoT SIM cards fell by 21.5% in the first quarter of 2026 alone, as the 2G and 3G shutdown progresses. Every device migration is a billing event: replacement, plan change, possibly absorbing the cost. Without clear rules, migration costs more than it should.

6. Multi-country VAT and taxes

A manufacturer selling in several countries must apply the right VAT, sales tax and local levies based on the customer's country and the nature of the service. A mistake repeats on every affected invoice.

7. Invisible margin per device

When connectivity, billing and operations live in separate systems, nobody sees margin device by device. Poorly calibrated offers stay in place for months.

IoT marketplaces and billing-as-a-service: the Actility case

Some IoT companies do not just bill their own services: they run a marketplace for devices and services, and offer billing to their partners. Actility, a major LoRaWAN player, relies on Opencell to automate billing and settlement for its marketplace.

Actility is a leader in LoRaWAN, an open radio standard that connects sensors and devices over long distances with long battery life. The company runs its ThingPark network with customers and partners worldwide, and a marketplace selling sensors and devices certified for that network.

The need, as described in our Actility customer story: automate the complex billing and settlement flows of the marketplace, integrate them with ThingPark, and be able to deploy the same solution for partners' own needs.

The solution covers:

  • bundled product and service offers;
  • custom mediation for usage data;
  • automated marketplace billing;
  • multi-country VAT and local taxes;
  • automated payment collection and cash matching.

Results: fast go-live, end-to-end automated billing and a "billing-as-a-service" capability, the ability to offer billing as a service to partners.

This case illustrates a trend: in IoT, billing itself becomes a product. A network or platform operator that can bill on behalf of its partners strengthens its ecosystem and creates an extra revenue stream.

Opencell also works with other IoT and M2M players such as Objenious, Matooma and Worldline, as well as telecom operators in Europe and Canada.

Must-have features of an IoT billing solution

An IoT billing solution must at least handle a flexible offer catalog, the device lifecycle, high-volume mediation, every pricing model (flat, usage, pool, tiers, prepaid), B2B2X account hierarchies, partner revenue sharing, multi-country tax and payment collection.

Area Expected features
Catalog and offers Bundles of device, connectivity and service; launch without development; offer versions; discounts
Lifecycle Device states (inventory, test, active, sleep, suspended, terminated); bulk activations; link with the SIM management platform
Mediation Multi-source collection (networks, platforms, APIs), checks, deduplication, enrichment, rejection handling
Rating Flat fees, usage, tiers, pooled allowances, overages, zones, prepaid, real time where needed
Accounts and invoices Multi-level hierarchies, consolidated and detailed invoices, rebilling, e-invoices
Partners Commissions, revenue sharing, marketplaces, partner portal
Tax Multi-country VAT and local taxes, multiple currencies
Payment and finance Payments, dunning, cash matching, accounting export, revenue recognition
Steering Margin per device, offer and customer; dashboards; gap detection
Openness Documented APIs, connectors to CRM, ERP and IoT platforms; scalability

Mediation and rating are often underestimated. Yet they decide whether the solution will handle tomorrow's volumes. The Opencell platform includes a mediation module and a rating engine built for high-volume usage, inherited from the solution's telecom roots.

How to choose an IoT billing solution

To choose an IoT billing solution, check that it can handle the volumes, manage every pricing model and the B2B2X cascade, launch an offer without development, integrate with your IT systems and pay partners. Total cost over five years matters more than the license price.

Criterion Question to ask
Volumes How many events per day does it process in production, and for whom?
Pricing models Can one offer combine flat fee, usage, pool, tiers and prepaid?
Agility How long to launch a new offer, and does it need a developer?
Lifecycle Are device states managed natively, with bulk activations?
B2B2X How many hierarchy levels, and is rebilling native?
Partners Are commissions, revenue sharing and marketplaces built in?
International Multi-country tax, multiple currencies and languages?
Openness Which APIs, which connectors, what documentation?
Deployment European cloud, on premise, private cloud? Where is data hosted?
Total cost License, implementation, operations, changes: what cost over five years?

Build or buy?

Many IoT companies start with an in-house tool or a spreadsheet. That is reasonable for a few hundred devices. Beyond that, limits appear fast: new offers impossible to launch, calculations that cannot be traced, time spent fixing errors. In-house development rarely costs less than a market solution once maintenance, regulatory changes and dependence on a few people are added.

Mistakes to avoid

  • Choosing on the demo rather than a real case: ask the vendor to model one of your offers, with your volumes.
  • Forgetting partners: reseller and integrator compensation is often discovered at the end of the project.
  • Underestimating mediation: the quality of usage data determines the accuracy of every invoice.
  • Ignoring openness: a closed solution quickly becomes a brake on innovation.

Running the project without risk

A successful IoT billing project moves in stages: scope offers and volumes, model the catalog, connect data sources, migrate existing data, run billing in parallel with the old system, then switch over. A phased approach, offer by offer or customer by customer, greatly limits risk.

  1. Scope: current and future offers, volumes, partners, country and tax constraints.
  2. Model the catalog: translate each offer into the new solution and check that no rule is missing.
  3. Connect sources: networks, device management platforms, CRM, ERP.
  4. Migrate: customers, contracts, device fleets, useful history.
  5. Run in parallel: compare invoices from the old and new systems over one or two periods.
  6. Switch in waves: by offer, segment or country, starting with a new offer if possible.

With a preconfigured platform, a first go-live can happen within a few months. Opencell targets go-live in three months, with more than 200 APIs and connectors to integrate with existing systems.

Frequently asked questions about IoT billing

How do you bill a connected device?

You rarely bill the device alone: you bill the connectivity, platform, data and services around it. The model can be a flat fee per device, usage-based billing, a pooled allowance, prepaid or a hybrid, depending on usage and what the customer values.

What is the difference between IoT billing and telecom billing?

IoT billing reuses usage measurement and SIM management from telecoms, but the billed unit is the device, by the thousand or million, for mostly business customers, with long lifecycles, idle periods and a cascade of partners to pay.

What is data pooling in IoT?

Pooling means sharing a data allowance across every device in a fleet rather than giving each one its own plan. Low-usage devices offset heavier ones. Billing then calculates usage and overage at group level.

How do you bill IoT services on usage?

Collect usage data (kilobytes, messages, API calls, operating hours), check it and link it to the right contract, then apply pricing rules. A hybrid offer, with a base subscription and a variable part, often reassures customers about their budget.

How do 2G and 3G shutdowns affect IoT billing?

Every device to migrate becomes a billing event: hardware or SIM replacement, plan change, possibly absorbing costs. A billing solution must handle these migrations in bulk, with clear, traceable rules.

What is the best IoT billing software?

The right one handles your volumes, supports every pricing model and B2B2X hierarchies, pays partners and integrates with your systems through APIs. The best test is to have the vendor model one of your real offers, with your volumes.

In IoT, margin is won device by device

A connected device earns money throughout its life, provided every month, every kilobyte and every partner is billed correctly. Billing is no longer an administrative function: it is what makes an IoT model profitable.

Key takeaways:

  • IoT billing bills devices, by the thousand or million, and the services that come with them,
  • the B2B2X value chain requires account hierarchies and partner revenue sharing,
  • flat fee, usage, pooling, prepaid and outcome-based pricing combine: the solution must handle them all,
  • revenue losses come from small gaps multiplied by volume: reconcile the device base and invoices continuously,
  • mediation and rating decide whether the solution will handle tomorrow's volumes.

In IoT, billing is not the end of the sales cycle. It is what keeps it going.

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 manages €14 billion in revenue for around fifty customers, including IoT players such as Actility, Objenious and Matooma.

Launching an IoT offer or modernizing how you bill connected devices?

Optimize your recurring revenues with Opencell

Get a demo