Most Canadian enterprises that have started deploying eSIM-capable devices or IoT SIMs are managing them with the same processes they use for physical SIM cards—and those processes are silently failing. Enterprises manage eSIMs at scale by treating SIM lifecycle management as a distinct telecom expense and inventory discipline, with automated provisioning, profile management tied to device lifecycle events, and continuous invoice reconciliation against an authoritative device inventory. Not by extending the spreadsheet they use for physical SIMs. The gap between how most organisations think about SIM management and what eSIM actually demands is where cost leakage and security exposure begin.
The SIM card was simple—eSIM and IoT SIM changed the rules
A logistics company deploys 800 new Zebra handheld devices with eSIM capability. IT provisions them through the carrier portal, one profile at a time. Six months later, 60 of those devices have been swapped out through the break/fix process, but the original eSIM profiles were never deactivated. The replacement devices got new profiles. The company is now paying for 860 lines of connectivity on 800 devices—and nobody noticed because there is no physical SIM to collect and cancel.
This is not a hypothetical. It is the operational reality we see in Canadian fleets that have transitioned to eSIM without updating their lifecycle workflows.
The scale of the shift makes this more than an edge case. Juniper Research projects that eSIM connections will reach 9.1 billion globally by 2028, up from 3.4 billion in 2024. This is not a niche technology. eSIM is becoming the default connectivity method for enterprise devices, and the management gap is widening with every deployment cycle.
The IoT dimension compounds the challenge. IoT Analytics estimates that connected IoT devices exceeded 16 billion globally in 2023 and will surpass 27 billion by 2027. Even a modest Canadian enterprise fleet now includes dozens or hundreds of IoT endpoints—sensors, trackers, telematics units—each with a SIM that needs lifecycle management.
Here is what changed: with physical SIMs, decommissioning a device meant pulling the SIM card out. That physical act was the control mechanism—it forced someone to touch the SIM, which triggered a process. With eSIM, there is no physical act. The profile lives in software. If your decommissioning workflow does not explicitly include an eSIM deprovisioning step, those profiles persist—and so do the monthly charges.
| Dimension | Physical SIM management | eSIM and IoT SIM management |
|---|---|---|
| Provisioning | Insert card, activate via carrier | Software profile push via carrier portal or API |
| Deprovisioning | Physical removal forces cancellation | Must explicitly deprovision—no physical trigger |
| Invoice visibility | Line items tied to removable cards | Profiles often aggregated or buried in pooled plans |
| Inventory tracking | Card can be scanned, counted, matched | Profile exists only in carrier system and device software |
Where eSIM and IoT SIM costs hide on Canadian carrier invoices
Canadian carrier invoices were designed for voice and data plans assigned to people. They were not designed to make IoT SIM charges or eSIM profile costs easy to audit.
The result is that eSIM and IoT connectivity charges are often buried in pooled data plans, listed under generic account codes, or aggregated in ways that make it impossible to match a line item to a specific device or sensor without a reconciliation tool.
Most IT leaders know they are overspending somewhere in their telecom budget. Aberdeen Strategy & Research has found that enterprises typically overspend on telecom by 15–25% due to billing errors, unused lines, and rate plan mismatches. That 15–25% figure was established in the era of physical SIMs. eSIM and IoT SIM add new categories of invisible waste—orphaned profiles, duplicate provisioning, IoT lines on plans designed for smartphones—that push the real number higher for fleets in transition.
Here is a detail only someone who has parsed thousands of Canadian carrier invoices would know: IoT SIMs frequently end up on standard enterprise data pools because the carrier account rep provisioned them under the master account rather than a dedicated IoT rate plan. It is faster. It closes the ticket. But the per-unit cost difference between an IoT-specific plan and a standard enterprise data plan can be 3–5x.
Multiply that across 500 sensors and the annual overspend is significant—but it does not show up as a billing “error.” It shows up as normal usage against a plan that was never right for the device type.
The inventory blind spot—devices you cannot see, lines you cannot cancel
Every IT director has a device inventory—a spreadsheet, an asset management database, or a lifecycle management portal. But ask them how many active eSIM profiles exist across their fleet, or how many IoT SIMs are currently transmitting data, and most cannot answer with confidence.
The inventory gap is not about carelessness. It is about the fact that eSIM profiles and IoT SIMs are provisioned through carrier portals that do not sync with internal asset databases.
eSIM profiles outlive the devices they were provisioned on
Devices get swapped, redeployed, or decommissioned, but eSIM profiles are not tied to a physical object that moves through the same workflow. A device goes through break/fix, gets replaced with a unit from the spare pool, and ships back to the user. The old device sits in a drawer waiting for repair. Its eSIM profile is still active. The new device has a new profile. Nobody cancelled the first one.
Without explicit deprovisioning processes, profiles accumulate.
IoT SIMs in the field are nobody’s responsibility
IoT SIMs on sensors, trackers, and environmental monitors are often provisioned by the operations team or a third-party integrator—not IT. When the sensor is replaced or the project ends, nobody tells IT to cancel the SIM. The line stays active indefinitely.
The ownership gap is structural. IT manages devices. Operations manages the use cases. The carrier sends IT the invoice for both.
This is where the concept of “zombie lines” becomes operationally meaningful. As we have noted elsewhere on telecom inventory management: “The gap between those two numbers is where Canadian enterprises lose money every month. Not through dramatic errors—through the slow accumulation of zombie lines, rate plan drift, and relationship mismatches that no quarterly count can catch.”
In a physical SIM environment, a quarterly inventory count—walking the floor, scanning devices, matching SIMs to asset tags—catches most discrepancies. In an eSIM and IoT SIM environment, there is nothing to scan. The only way to detect orphaned profiles is to reconcile carrier invoice line items against an authoritative device database, line by line, every billing cycle.
Most organisations do not have the tooling or the staff hours to do this—which is why the problem compounds month over month until someone asks why the wireless bill keeps climbing while headcount stays flat.
Why traditional telecom expense management falls short for eSIM fleets
An IT director at a Canadian retail chain runs their wireless expense management through a combination of carrier portal exports and a shared Excel workbook. It works tolerably for 400 smartphones on standard rate plans. Then the company deploys 1,200 IoT sensors across 80 stores for inventory tracking, each with its own SIM.
The Excel workbook cannot accommodate a 4x increase in line items. The carrier portal does not distinguish between smartphone lines and IoT lines in its reporting. The IT director’s monthly reconciliation process—which already took two days—now takes a week.
Something has to give.
Carrier portals were not built for multi-SIM-type fleets
Bell, Rogers, and TELUS each provide account management portals, but these portals are optimised for managing voice and data plans, not for providing fleet-level visibility across a mix of eSIM profiles, physical SIMs, and IoT SIMs under a single pane of glass.
An enterprise with lines across all three carriers—common in Canadian fleets—cannot get unified visibility from any single portal. Each carrier presents eSIM and IoT charges in different invoice formats, with different line-item structures.
Spreadsheet-based TEM breaks at IoT scale
The manual reconciliation approach that works for a few hundred lines becomes operationally unsustainable when IoT SIMs push the line count into the thousands. The error rate compounds with volume. A 2% reconciliation error on 400 lines is 8 mismatches. On 1,600 lines, it is 32—and those are the ones you catch.
The volume problem is accelerating. GSMA Intelligence reports that eSIM-capable device shipments are growing at over 30% year-over-year across enterprise segments. The devices entering Canadian enterprise fleets over the next two to three refresh cycles will increasingly be eSIM-capable by default. Any TEM approach that cannot handle eSIM profile data alongside traditional SIM data will become obsolete within one to two refresh cycles.
Here is an operational detail that illustrates the challenge: when an enterprise has both physical SIMs and eSIM profiles active on the same carrier account, the carrier invoice often does not differentiate between the two connectivity types at the line-item level. The only way to distinguish them is to cross-reference the ICCID—the SIM identifier—against a provisioning record. That requires either a purpose-built tool or a very patient analyst with access to both the carrier portal and the internal asset database.
The organisations that are getting ahead of this are not working harder at manual reconciliation. They are changing the approach entirely—
What enterprises are doing to get ahead of eSIM and IoT SIM sprawl
The organisations that are managing eSIM and IoT SIM fleets effectively share three characteristics: they treat SIM lifecycle as a distinct operational workflow—not an afterthought of device management—they reconcile connectivity costs against device inventory at least monthly, and they have automated the detection of orphaned profiles and zero-use lines.
That last point is the differentiator. Manual detection does not scale. Automated detection does.
Gartner reports that fewer than 25% of enterprises have a formalised process for managing IoT device connectivity lifecycle. The reader is not behind—most organisations have not solved this yet. But the cost of inaction compounds with every billing cycle, and the organisations that formalise this process first gain an advantage that widens month over month.
Building internal SIM lifecycle workflows
Organisations with mature internal IT operations are creating explicit provisioning and deprovisioning checklists for eSIM, assigning IoT SIM ownership to specific cost centres, and integrating SIM status into their ITSM platforms. ServiceNow workflows that trigger eSIM deprovisioning when a device enters the break/fix queue. Automated alerts when a new IoT SIM is provisioned without a matching cost centre assignment.
This works—if you have the staff, the platform maturity, and the institutional discipline to maintain it.
Using TEM platforms that parse eSIM and IoT line items
An emerging category of telecom expense management tools can ingest Canadian carrier invoices, distinguish between SIM types at the line-item level, and flag anomalies automatically. Some use AI to parse invoice data that would take an analyst days to reconcile manually. The category is new enough that most organisations have not evaluated these tools yet—but the capability exists.
Outsourcing SIM lifecycle to a managed mobility partner
Some organisations hand off the entire SIM lifecycle—provisioning, plan optimisation, deprovisioning, invoice reconciliation—to a managed mobility services provider. This approach makes sense for organisations that lack the internal staff or tooling to build and maintain these workflows themselves, or that want to focus IT resources on higher-value work than parsing carrier invoices.
A managed partner can integrate SIM lifecycle management into broader lifecycle management and secure decommissioning processes—ensuring that when a device reaches end-of-life, its eSIM profile is cancelled as part of the same workflow that handles data erasure and asset disposition.
One pattern seen repeatedly in Canadian enterprise fleets: the IT team builds a solid provisioning process for eSIM on new device deployments, but nobody builds the corresponding deprovisioning process. Provisioning is exciting—it is part of a rollout, it has a project manager, it has a deadline. Deprovisioning is invisible—it happens when a device breaks or a project ends, and there is no project manager ensuring the eSIM profile gets cancelled.
The organisations that avoid sprawl are the ones that build deprovisioning into the break/fix workflow from day one.
How ClearSight TEMs AI surfaces eSIM and IoT SIM cost leakage
For organisations that want to start with visibility before committing to a fully managed approach, a purpose-built TEM platform that can parse eSIM and IoT SIM line items from Canadian carrier invoices is the lowest-friction entry point.
Before you can fix the problem, you need to see the problem.
Canadian carrier invoice parsing built for multi-SIM-type fleets
ClearSight TEMs AI ingests invoices from Bell, Rogers, TELUS, and regional carriers, and its AI agents parse 100% of line-item data—including the IoT and eSIM charges that manual audits miss. The platform distinguishes between connectivity types that carrier invoices aggregate, cross-references ICCIDs against usage patterns, and surfaces discrepancies that would take an analyst days to find manually.
Bilingual output—English and French—addresses the procurement requirements for federal contracts and Quebec operations. Secure Canadian hosting means telecom inventory data stays within Canadian jurisdiction, eliminating the PIPEDA exposure that comes with US-hosted TEM platforms.
Detecting orphaned eSIM profiles and zero-use IoT lines
ClearSight automatically flags zero-use lines, billing anomalies, and cost allocation mismatches—the exact categories of waste that eSIM and IoT SIM sprawl creates. At $99/month per billing account, it provides immediate visibility without requiring a full managed mobility engagement.
Most organisations that upload their first carrier invoice to ClearSight discover anomalies within minutes—zero-use lines they did not know existed, IoT SIMs on rate plans designed for smartphones, and eSIM profiles that outlived their devices. The diagnostic step is often more revealing than expected.
Frequently asked questions
How do enterprises manage eSIMs at scale?
Enterprises manage eSIMs at scale by treating SIM lifecycle as a distinct operational discipline—with automated provisioning, profile management tied to device lifecycle events, and continuous invoice reconciliation against an authoritative device inventory. Fewer than 25% of enterprises have formalised this process, but those that do gain compounding cost advantages.
What is the difference between managing physical SIMs and eSIMs in an enterprise fleet?
Physical SIMs have a self-correcting decommissioning mechanism—the card must be physically removed. eSIM profiles persist in software and must be explicitly deprovisioned. Without updated workflows, profiles remain active when devices are swapped or retired, creating orphaned lines and ongoing charges.
How do I know if my organisation has orphaned eSIM profiles or unused IoT SIMs?
The most reliable indicator is a discrepancy between active lines on carrier invoices and active devices in your asset inventory. If line count exceeds device count, orphaned profiles or unused SIMs are likely present. Aberdeen research indicates 15–25% telecom overspend is typical—eSIM and IoT add new categories of invisible waste.
What does eSIM and IoT SIM sprawl actually cost a Canadian enterprise?
Cost leakage occurs across three categories: orphaned eSIM profiles paying for connectivity on decommissioned devices, IoT SIMs on mismatched rate plans with 3–5x cost differentials, and undetected billing anomalies that compound monthly. The total depends on fleet size and transition maturity.
Can Canadian carrier portals manage eSIM and IoT SIM fleets effectively?
Bell, Rogers, and TELUS each provide account management portals, but these show data only for their own network. Enterprises with multi-carrier fleets—common in Canada—cannot get unified visibility. IoT and eSIM line items are often not broken out in ways that support fleet-level reconciliation.
Does PIPEDA affect how Canadian enterprises manage eSIM and IoT SIM data?
Yes. Telecom inventory records—ICCIDs, IMEIs, device-to-user assignments, usage data—constitute personal information under PIPEDA. Where a TEM platform stores and processes this data determines cross-border transfer obligations and breach notification requirements. US-hosted platforms create jurisdictional exposure that Canadian-hosted alternatives avoid.
What is IoT SIM management and how is it different from standard wireless expense management?
IoT SIMs connect sensors, trackers, and embedded devices—not people. They generate data-only usage at lower volumes than smartphones, require different rate plans, and are often provisioned by operations teams rather than IT. Standard wireless expense management tools do not account for these differences.