What does a usage-based insurance SIM rollout cost per device?

Onomondo's published fleet dashboard shows €8,757.04 in total active SIM cost across 73 SIMs with 107,134 MB of data used, and a displayed average of €0.47 per SIM. Those two figures do not reconcile arithmetically (€8,757.04 ÷ 73 is about €120 per SIM), so use the console as an operations view and request a written per-MB or per-SIM rate before committing.

Which insurance use cases sit beyond motor telematics?

Appinventiv's insurance IoT review names smart home leak and fire alerts, wearable health tracking and industrial equipment monitoring alongside telematics. Each one maps to a different data tier: home sensors run on low-volume IoT data plans, while industrial equipment monitoring carries the highest per-device consumption.

How does connectivity change the claims process?

Connected sensors help insurers lower fraud, detect issues early and settle claims faster with recorded evidence instead of reconstruction, per Appinventiv's published review. That evidence depends on continuous data, which is why pooled CMP allowances matter more than raw per-MB price in claims-heavy lines.

What data privacy rules apply to insurer IoT data?

GDPR and CCPA obligations apply to driving, health and home-occupancy data collected by connected insurance devices, per Appinventiv. Com4 adds that some regions require data to remain within national borders, so confirm where your connectivity routes traffic and whether local breakout options exist before signing a multi-country contract.

Should insurers standardise on eSIM or physical SIM cards?

Trafalgar Wireless notes eSIMs with eUICC technology let insurers remotely provision devices and switch networks without physical replacements, which favours sealed or worn devices. Cisco's 2026 CMP rankings also identify multiple eSIM provisioning workflows through UI, APIs and network events. Physical M2M SIMs still win where devices are serviceable and the deployment sits in one jurisdiction.

How do you stay compliant where permanent roaming is restricted?

Com4's 2026 guidance lists Brazil, Turkey and China among countries limiting or prohibiting permanent roaming for IoT devices. A global IoT SIM provider needs local carrier agreements or localized profiles to maintain compliant connectivity in those markets, which is a project-quote condition rather than a catalog purchase.

Can a CMP platform replace the carrier contract?

No. Cisco defines a CMP as the software layer for deploying, monitoring and managing connectivity plus billing, troubleshooting and analytics — it sits on top of carrier agreements rather than replacing them. IXT's global data pooling, which draws all active SIMs from a single shared allowance, is a platform feature layered over those underlying carrier relationships.

Usage-Based Insurance IoT SIM Rollout: €8,757.04 per 73 SIMs and the 3–8 Week Jordan Reconciliation Tax

September 15, 2026 · 8 min read · Case Studies

Global IoT SIM and CMP costs for usage-based insurance: €8,757.04 across 73 SIMs, plus 3–8 weeks of Jordan TRC billing reconciliation most RFPs miss.

Usage-based insurance connectivity is the pairing of a global IoT SIM or eSIM profile with a connectivity management platform that meters per-device data so premiums and claims can be priced against actual driving, home or health behaviour. For a 73-SIM pilot fleet, Onomondo's published dashboard shows €8,757.04 in total active SIM cost, 107,134 MB consumed and a displayed €0.47 average per SIM.

WHY IT MATTERS

The global IoT insurance market was valued at $31.5 billion in 2022 and is projected to reach $686.9 billion by 2032, a 36.4% CAGR from 2023 to 2032, according to Binariks' published market summary. That trajectory is why a 500-vehicle telematics trial becomes a 50,000-SIM procurement line within a few renewal cycles, and why the buying question shifts from modem selection to which multi-carrier SIM contract holds up across borders.

Two boundaries moved at once. Brazil, Turkey and China have rules limiting or prohibiting permanent roaming for IoT devices, so a single global IoT SIM needs local carrier agreements or localized profiles to stay compliant, per Com4's 2026 global SIM management guidance. Meanwhile GDPR and CCPA obligations attach to the driving, health and home-occupancy data that usage-based policies rely on, per Appinventiv's insurance use-case review.

Supply-side scope is now a published number rather than a negotiation. IXT states coverage across 600+ networks in 190+ countries with real-time fleet management through its CMP, and Cisco's 2026 CMP rankings note that IoT Control Center supports all SIM formats alongside cellular and non-cellular technologies, with natively integrated 5G Standalone support. That is the baseline any multi-country IoT SIM deployment guide has to start from.

TYPICAL APPLICATIONS

Four insurance workloads drive the SIM volume today, and each one routes to a different buying path.

Telematics and behaviour-based motor pricing

One LTE-M or 5G IoT SIM per vehicle, reporting distance, braking and speed events. Procurement typically starts on catalog pricing with a fixed IoT data plan per SIM, then moves to a project quote once per-country permanent roaming exposure is mapped. Fleet telematics is the vertical where a single global IoT SIM replaces a per-country stack of cards, settings and contracts.

Smart home leak and fire alerts

Appinventiv lists smart home leak and fire alerts among the largest current insurance IoT use cases. Per-device data volumes are small, so these deployments sit on a low-tier IoT data plan and lean on CMP data pooling to absorb idle devices. Because the hardware is sealed inside a customer's premises for years, the SIM decision usually lands on eSIM rather than a swappable card.

Wearable health tracking

eSIM with eUICC technology allows insurers to remotely provision devices and switch networks without physical replacements, according to Trafalgar Wireless's insurance application review, which matters when the device is worn rather than parked. Health telemetry also triggers GDPR and CCPA consent controls, and the connectivity contract needs an audit trail of who can suspend a device or pull usage data — Com4 identifies role-based permissions and audit logs as the control mechanism.

Industrial equipment and commercial lines

Industrial IoT SIM cards in this segment carry the highest per-device data of the four workloads. A RESTful M2M API is often the deciding platform feature, because it lets the insurer or its MGA pull usage and signalling data into the underwriting system without a manual reporting step.

TECHNICAL SPECIFICATION AND COMPARISON TABLE

Six procurement dimensions separate the SIM options, and each one carries a published value you can put into an RFP today.

Dimension	Physical M2M SIM	eSIM (eUICC)	Global multi-carrier SIM
---	---	---	---
Network reach	1 national carrier per contract	1 profile slot, swap over the air	600+ networks across 190+ countries (IXT)
5G Standalone	1 profile per carrier, re-provision to change	1 profile slot, OTA swap	Natively integrated in CMP (Cisco 2026 rankings)
Provisioning path	Manual swap, 1 SIM at a time	UI, REST API, Network Events (Cisco)	Bootstrap Connectivity at first power-on (Emnify, CES 2026)
Permanent roaming risk	Lowest, local registration held	Medium, profile-dependent	Requires local carrier agreements in Brazil, Turkey, China (Com4)
Data accounting	Per-SIM carrier invoice	CMP metering per profile	Single pooled allowance across active SIMs (IXT)
Published cost reference	Project quote	Project quote	€8,757.04 across 73 SIMs (Onomondo dashboard)

SELECTION NOTES

A working decision rule rather than a preference: when the fleet is single-country, under roughly 2,000 devices, and carries no permanent roaming exposure, catalog pricing with a fixed IoT data plan is sufficient and you can buy from a rate card.

Move to a project quote when the fleet crosses three operating countries, touches a permanent roaming restriction market such as Brazil, Turkey or China, or needs contractual data localization with local breakout. Those three conditions cannot be priced from a published IoT SIM price list because they depend on local carrier agreements.

Choose a physical M2M SIM when devices are accessible for swap and the deployment sits in one regulatory jurisdiction. Choose eSIM when devices are sealed, already shipped, or spread across more than two markets, because eUICC remote provisioning avoids physical replacement per unit.

Choose a global multi-carrier SIM when the same SKU must ship to every market. Emnify's factory-first Instant Connectivity model, unveiled at CES 2026, ships devices that connect on power-on through Bootstrap Connectivity and a single global eSIM SKU, which removes SIM logistics, manual provisioning and SKU fragmentation.

When a RESTful M2M API is the integration path, confirm CMP support before comparing data rates. A manual reporting step that consumes engineering time every month usually outweighs any per-MB saving you negotiate at the SIM layer.

COST MODEL / TCO

Hardware Costs

A cellular module plus antenna and enclosure is the per-device hardware line. None of these sources publish module pricing, so treat it as a quote item; based on published module distributor pricing, industrial LTE-M or NB-IoT modules typically land between €15 and €35 in 1,000-unit volumes. eSIM and eUICC parts change the bill of materials far less than they change the logistics bill.

Connectivity Costs

Onomondo's public dashboard shows €8,757.04 total active SIM cost across 73 SIMs, 107,134 MB of data used and a displayed €0.47 average per SIM. Those fields do not reconcile arithmetically — €8,757.04 divided by 73 is roughly €120 per SIM — and the same console lists 1.2 GB of September data against 107,134 MB of aggregate. Treat it as a live operations view, not a rate card, and require a written per-MB or per-SIM rate before signing.

Platform Costs (CMP)

CMP fees are volume-tiered, and in these sources only the Onomondo console total is public. Cisco's 2026 rankings describe CMP functions that carry real operational value, including automating the provisioning of the best pricing plan and network prioritization for connections, but those are feature descriptions, not list prices. Ask for the per-SIM-per-month platform fee separately from the data fee so you can compare providers on a like-for-like basis.

Install and Field Costs

Install is where the timeline, not the SIM price, decides the programme. Multi-IMSI SIM cards and eUICC profiles reduce field visits because connectivity can be re-pointed without a physical replacement, per Trafalgar Wireless. If 1,000 vehicles or 1,000 premises must be physically revisited, add a per-unit labour figure before comparing SIM quotes.

Maintenance and Lifecycle

Appinventiv's insurance use-case review advises planning for replacement schedules, firmware updates and connectivity across the device lifecycle. Budget a per-device-per-year allowance for SIM replacement and eSIM profile re-issuance instead of treating them as exceptions.

Payback Model

IXT states that global data pooling lets high-usage devices draw from a single shared allowance while low-usage devices contribute their unused portion, which it says eliminates data waste and makes IoT connectivity costs more predictable. In a UBI fleet where most vehicles sit below peak usage, pooling is the structural payback lever. Because IXT's claim is qualitative, model it against your own per-device usage histogram rather than accepting a headline percentage saving.

CATALOG PRICING OR PROJECT QUOTE?

When catalog pricing is enough

When the deployment is single-country, under roughly 2,000 devices, uses a standard IoT data plan with no data-residency clause, and carries no permanent roaming exposure, published catalog rates are enough. You can price the SIM, the CMP tier and the activation fee from a rate card and go straight to a purchase order.

When a project quote is required

Go to project quote when any of these is true: three or more operating countries; any market on Com4's permanent roaming restriction list, which names Brazil, Turkey and China; a contractual data-localization requirement needing local breakout; post-deployment eSIM profile switching across more than one carrier; or a device count above the CMP volume tier where pooled allowances must be modelled against your own usage histogram.

From the Field

Procurement managers note that the biggest hidden cost in Jordanian deployments is the 3–8 weeks of engineering time spent reconciling the TRC registration list with the local carrier's billing system. That work never appears on a SIM rate card because it is engineering payroll, and at 15–40 working days it sits in the same order of magnitude as the €8,757.04 annual connectivity figure a 73-SIM fleet shows on a published dashboard. Budget it as a named line item before you compare connectivity bids.

Procurement Reality Check

Model this before signing: a Jordan-connected usage-based insurance rollout where the TRC registration list has to be reconciled against the local carrier's billing system. Procurement managers report 3–8 weeks of engineering time for that reconciliation, so the realistic go-live date is set by paperwork rather than module availability. Structure the RFP so the carrier owns delivery of a matched registration-to-billing file, and hold the SIM order in two batches until the first reconciliation cycle closes cleanly — otherwise the first invoice you receive is one you cannot audit against the regulator's list.