Your IT team has a spreadsheet showing 450 mobile devices. Your MDM platform reports 423 enrolled devices. Your carrier invoices include 468 active wireless lines.
Which number is correct?
The answer may be that all three are accurate within their own systems. The problem is that each system tracks a different part of your organization's mobile environment.
Carrier billing platforms track services and charges. MDM platforms track enrolled and managed devices. Procurement systems record purchased equipment, while HR systems track employees and their assignments.
When these systems are not regularly reconciled, organizations can lose visibility into which devices are in use, which wireless lines are being billed, and who is responsible for them.
This is more than an administrative inconvenience. Inaccurate records can lead to unnecessary wireless expenses, incorrect cost allocations, unmanaged devices, and delays when employees change roles or leave the organization.
Here's why these discrepancies happen and how to address them.
The first step toward understanding inventory discrepancies is recognizing that your systems do not necessarily measure the same thing.
Carrier records typically identify active wireless services, phone numbers, SIM or eSIM details, plan information, account ownership, and recurring charges.
They are essential for understanding what your organization is being billed for.
However, a carrier may not know whether a device is still physically in use, whether an employee has left the company, or whether a line is still needed.
Mobile Device Management platforms track devices enrolled in the organization's management environment.
Depending on the platform and configuration, they may provide information about:
But an MDM inventory is not necessarily a complete list of all devices or wireless services.
A device may be missing from MDM because it was never enrolled, was removed from management, or has not checked in recently. A wireless line can remain active even when its device is no longer visible in the platform.
Procurement records show which devices were ordered, purchased, received, or replaced.
They may include purchase dates, suppliers, device models, serial numbers, IMEIs, and purchase costs.
However, purchasing a device does not automatically mean it is currently assigned to an employee or connected to an active wireless service.
Devices may remain in storage, be returned, be transferred between departments, or be replaced without every system being updated.
HR records provide employee status, department, location, manager, and employment dates.
These records are important for determining who should be assigned a device and which department should be responsible for the associated costs.
But HR systems typically do not track carrier line status, SIM identifiers, or device enrollment.
The result is four different views of the same mobile environment, each with its own purpose and limitations.
Once you understand what each system tracks, the most common sources of discrepancies become easier to identify.
When an employee leaves, their HR status may be updated immediately, but their wireless line and device assignment may not be.
The reverse can also happen: a line is cancelled, but the internal inventory still shows it as active.
Internal transfers create similar problems. An employee may move to another department while their phone number, device assignment, and cost centre remain unchanged in other systems.
A replacement device may be recorded in procurement and MDM, while the old device remains in the internal inventory.
The associated wireless line may also remain active if the carrier cancellation or SIM transfer was not completed correctly.
This can result in two devices appearing in internal records while only one is being used, or two billed services appearing when the organization expects one.
A phone number, SIM card, eSIM profile, and physical device are related, but they are not interchangeable identifiers.
A SIM may be moved to another device, an eSIM may be activated during a replacement, or a phone number may be transferred between services.
If the inventory tracks only phone numbers or device models, it may not capture these changes accurately.
Not every corporate device is necessarily enrolled in the organization's MDM platform.
Some devices may be awaiting configuration, held in inventory, used for specific operational purposes, or excluded from management for a legitimate reason.
A missing MDM record should therefore trigger an investigation, not an automatic assumption that the device is unauthorized or missing.
In many organizations, updates happen manually.
IT updates the device spreadsheet, procurement records a replacement, HR changes an employee's department, and someone else contacts the carrier to modify the account.
If these processes are not connected, there may be a delay between the original change and its appearance in every system.
Over time, small delays create significant differences between records.
A useful reconciliation process goes beyond comparing total device counts.
It matches individual records using identifiers and then investigates exceptions.
| Data point | Carrier records | MDM | Procurement | HR |
|---|---|---|---|---|
| Phone number | Usually | May be available | Sometimes | Sometimes |
| IMEI / device identifier | May be available | Often | Often | Usually not |
| SIM / ICCID | Usually | May be available | Sometimes | Usually not |
| Device model | Sometimes | Usually | Usually | Usually not |
| Assigned employee | Sometimes | May be available | Sometimes | Yes |
| Department / cost centre | Sometimes | May be available | Sometimes | Yes |
| Service billing status | Yes | No | No | No |
| Device enrollment status | No | Yes | No | No |
| Purchase date and cost | No | No | Yes | No |
| Employment status | No | No | No | Yes |
The exact fields available depend on your carrier, MDM platform, procurement process, and HR system.
The important point is to identify which system is authoritative for each type of information.
For example, carrier records should generally be used to verify billed services, while HR should be used to verify employment status. MDM can help establish whether a device is enrolled and when it last checked in.
No single platform should automatically be treated as the complete source of truth for everything.
Before starting, collect current exports or reports from your carrier accounts, MDM platform, procurement system, and HR system.
Then check the following.
Carrier records
MDM records
Procurement records
HR records
Reconciliation results
Consider a fictional organization with the following records for one employee:
| System | Record |
|---|---|
| HR | Employee left the organization three weeks ago |
| Procurement | Device returned to IT |
| MDM | Device last checked in 24 days ago |
| Carrier | Wireless line still active and billed |
At first glance, the situation appears straightforward: the employee has left, the device has been returned, and the wireless line is still active.
But before requesting cancellation, the team should confirm whether the returned device is being held for reassignment, whether the number is required by another employee, and whether the line has any contractual or operational considerations.
A structured workflow would look like this:
Step 1: Flag the discrepancy. The HR departure record and device return record do not align with the active carrier line.
Step 2: Verify ownership. IT confirms that the device has been returned and checks whether it is intended for reassignment.
Step 3: Confirm business requirements. The department manager or mobility administrator confirms whether the phone number or service is still required.
Step 4: Take action. If the service is no longer needed, the authorized team requests cancellation or another appropriate carrier change.
Step 5: Verify the result. The team checks the carrier account and subsequent invoice to confirm that the service has been updated and recurring charges have stopped, where applicable.
Step 6: Update internal records. The device, line, and employee assignment records are updated to reflect the final status.
This process creates an audit trail and reduces the risk of the same discrepancy being discovered again during a future review.
Reconciling your mobile inventory once can reveal discrepancies, but it will not keep your records accurate indefinitely.
New devices are purchased, employees change roles, wireless lines are activated, and services are modified throughout the year.
A sustainable process should include:
For larger organizations, automation and integrations can reduce manual work. However, automated matching still requires clear rules and human review of exceptions.
When carrier billing, MDM, procurement, and HR records do not agree, it becomes difficult to know exactly what your organization is paying for and who is responsible for each device and service.
Valet Wireless helps organizations improve visibility into their wireless environments through telecom expense management and related mobility services.
A structured inventory reconciliation assessment can help identify discrepancies between carrier records and internal data, highlight areas that require investigation, and support better wireless expense management.
Get an Inventory Reconciliation Assessment
Find out where your mobile inventory and carrier records differ, and what your organization can do to improve accuracy and control.
Contact Valet Wireless to discuss an inventory reconciliation assessment.