Most organizations can’t give an accurate count of their mobile devices, and the first time anyone notices is when someone senior asks for one. The device management console says one number, the carrier bill says another, and finance has a third.
If you’ve just been asked for that count and realized nobody knows the answer, you’re not alone. Device inventories drift for predictable reasons, and they can be brought back into line with a structured cleanup.
This post covers why the numbers don’t match, how to reconcile them, what a proper device record should include, and how to keep it accurate once it’s fixed.
Why nobody can give you an accurate device count
Inventories drift because devices change state far more often than records do. Every swap, repair, loss, and departure is a chance for the record to fall behind.
Devices get bought outside IT for a project or a new site. Replacements go out, but the broken devices they replaced never get marked as retired.
Spares sit in drawers and cradles, uncounted. Devices drop out of device management after a reset and nobody re-enrols them.
Then there are the bigger events. Acquisitions bring in fleets nobody documented, staff leave with devices that are never recovered, and old hardware sits in storage rooms years after it was replaced.
Each one is small. Together they make the count a guess.
Why your MDM count, carrier bill, and purchase records never match
The three main sources don’t disagree because one of them is wrong. They disagree because each one counts something different.
| Source | What it counts | What it misses |
|---|---|---|
| Mobile device management (MDM) | Devices currently enrolled and checking in | Spares, devices that were reset or never enrolled, devices in storage, Wi-Fi-only devices outside management |
| Carrier bills | Active lines and SIMs | Devices without a line, and which device (if any) each line is actually in |
| Purchase records | Everything ever bought | What’s been lost, broken, retired, or bought outside the normal process |
Lines are a separate inventory problem with their own clean-up, covered in the piece on telecom inventory management. This post stays on the devices themselves.
How to reconcile the records
Reconciliation means matching every device across every source using a unique identifier, then deciding what to do with everything that doesn’t match. It’s tedious once and much easier after that.
- Export each source. Pull the device list from your management console, the line list from each carrier, and purchase records for the last several years.
- Match on serial number or IMEI (International Mobile Equipment Identity). These are the only identifiers that follow the device, so use them rather than user names or phone numbers.
- Sort the mismatches. Devices bought but not managed, managed but not bought, lines with no device, and devices with no line each point to a different cause.
- Check physically at the sites. Ask each location to scan or list what it actually holds, including spares and devices in storage.
- Decide on each exception. Re-enrol it, reassign it, retire it, or write it off as lost, and record the decision.
Missing devices deserve particular care. If a lost device held personal information, you remain accountable for it under PIPEDA, so lock or wipe it remotely if you can and record what happened.
Where the missing devices usually turn up
When the reconciliation shows devices you paid for but can’t find, most of them aren’t really lost. They’re sitting somewhere nobody thought to check.
The usual places are predictable. Spare cradles and drawers at each site, storage rooms holding the previous generation, repair vendors who still have devices from months ago, and managers who kept a few aside “just in case”. Devices handed back by departing staff often sit in an office until someone has time to deal with them.
Ask each site to look in those places specifically, not just to count what’s in use. The devices that truly can’t be found should be locked remotely and written off on purpose, with a record of what was on them.
What a device asset record should include
A good asset record answers every question someone is likely to ask about a device without a search through three systems. Here’s what it should hold.
- Serial number and IMEI, plus an asset tag if you use one
- Model, operating system version, and purchase date
- Assigned site, role, and worker (or “shared” or “spare”)
- Carrier and line, if it has one
- Device management enrolment status
- Warranty or support end date
- Repair and replacement history
- Lifecycle status (in service, in repair, spare, retired) and, for retired devices, the data destruction record
The asset tagging FAQ for device fleets covers how physical tags tie each device to its record.
Keeping the inventory accurate after the cleanup
A one-time cleanup only lasts if every change to a device updates its record at the moment it happens. Inventories drift again within months when updates are left for later.
Build the update into each event. Issuing a device, swapping it, sending it for repair, receiving it back, and retiring it should each change the record as part of the task, not as an extra step. Then reconcile the sources on a regular schedule, quarterly for most fleets, so drift is caught while it’s small.
Give the inventory an owner. When everyone is responsible for keeping records current, nobody is, and the drift starts again. One named person, with time set aside for the quarterly check, keeps the cleanup from being wasted.
Locating devices matters as much as counting them. If staff regularly lose track of where devices are on site, the post on finding misplaced devices covers practical ways to keep tabs on them.
Where outside help fits
If your fleet is small and stable, a spreadsheet and a quarterly check can keep it accurate. The trouble starts when devices move constantly between sites, repairs, and spares, and the people who should update the record are the same people fixing the devices.
That’s where a managed approach helps. Through lifecycle management, every swap, repair, and retirement we handle updates the device record in our AIM portal, so the inventory stays current because the work and the record happen together.
Just know that it’s most useful when device changes are frequent and spread across many locations. A single-site fleet with little turnover rarely needs it.
Questions we hear about device inventory
Why doesn’t our MDM device count match our carrier bill?
Because they count different things. Your device management console counts devices that are enrolled and checking in, while your carrier bill counts active lines and SIMs. Devices without lines, lines without devices, spares, and devices that dropped out of management all create gaps between the two numbers.
How often should we reconcile our mobile device inventory?
Quarterly works for most fleets, with a full reconciliation after major events like an acquisition, a large rollout, or a fleet refresh. The more important habit is updating the record every time a device is issued, swapped, repaired, or retired, so the quarterly check finds small gaps instead of large ones.
Which identifier should we use to track mobile devices?
Use the serial number, and the IMEI for devices with cellular capability. Both stay with the device for its whole life, unlike user names, phone numbers, or SIM cards, which change. An asset tag can add a quick visual reference, but it should map back to the serial number in your records.
Where to start
Export your device management list, your carrier line list, and the last few years of purchase records, and match them on serial number. The mismatches will tell you where the drift comes from. Fix the record, then fix the process that let it drift, so you’re not doing this again next year.