Carrier portals, MDM, Active Directory and ERP: why telecom data needs to be integrated

A simple question: who uses the line ending in 555 01 23, which device is it in, which cost centre does it belong to, and how much did it cost this month?

In most companies, answering it means opening four different systems. The carrier portal says what it cost. The MDM says which device it is in. Active Directory says who the person is and which department they belong to. The ERP says which cost centre it is charged to. Each system holds part of the truth and none of them holds all of it.

Four sources, four partial views

Carrier portals and invoices

They are the source of cost: lines, plans, usage and charges. But every carrier has its own portal, its own invoice format and its own way of naming things. And they know nothing about your organisation: to a carrier, a line is a number, not a person or a department.

MDM (Intune, Samsung Knox, Workspace ONE…)

It is the source of the device: model, serial number, IMEI, operating system, who it is assigned to. But the MDM does not know what the line inside it costs or which contract covers it.

Active Directory

It is the source of people: who works at the company, in which department, at which site, who their manager is and, above all, who is no longer active. But it knows nothing about lines or invoices.

ERP (SAP, Microsoft Dynamics…)

It is the accounting source: cost centres, projects, accounts, budgets. It is where spend has to end up correctly allocated. But the ERP receives the invoice as a single total, not line by line.

What happens when they are not connected

When these sources live apart, problems do not show up in any one system: they show up in the gaps between them.

• Orphan lines. The carrier bills a line that is not assigned to anyone in the MDM and does not match any active person in Active Directory.
• Leavers that never reach the carrier. Someone leaves, Active Directory disables them, but nobody tells the carrier and the line keeps billing. We cover this in Unused mobile lines.
• Devices out of control. The MDM has devices with no line, or active lines in devices nobody can locate.
• Manual cost allocation. Someone in Finance splits the invoice across cost centres every month in a spreadsheet, using rules nobody else knows.
• Inventories that never match. IT has one line count, Procurement another and Finance a third. And all three are right according to their own source.

None of these problems is serious on its own. The problem is that they pile up, repeat every month, and nobody has the full picture to spot them.

Why manual integration does not work

The usual fix is a master spreadsheet that someone updates by cross-referencing exports from each system. It works for a while, but it has three weaknesses:

1. It goes stale quickly. New starters, leavers and device changes happen daily; the spreadsheet gets updated when someone has time.
2. It depends on one person. If that person changes role or leaves, the knowledge leaves with them.
3. It leaves no trail. Nobody knows who changed which data or when, which complicates any carrier dispute or internal audit.

What changes when the data is integrated

Integration is not just putting data in one place. It means each source automatically feeds the others and the discrepancies surface on their own:

• A single record per line, with its cost (carrier), its device (MDM), its user (Active Directory) and its cost centre (ERP).
• Alerts on inconsistencies: lines without a user, inactive users with lines, devices without a line, or lines billing without usage.
• Automatic allocation of spend to the right cost centre, ready for the ERP.
• An inventory that maintains itself, because every change in the MDM or Active Directory is reflected without manual work.
• A full audit trail of every change: what was modified, from which source and when.

Example

At Acme Services, ana.ejemplo leaves the company. Active Directory marks her account as inactive. With integrated sources, her line immediately shows up as "assigned to inactive user", together with the device registered in the MDM and the cost centre it is charged to. The manager decides whether to cancel or reassign it, and the decision is recorded. Without integration, the line would most likely keep billing until someone reviewed the invoice in detail.

How EPItoolbox does it

EPItoolbox connects to the sources you already have:

• Carrier invoices and data, from every carrier you use.
• MDM: Microsoft Intune, Samsung Knox and Workspace ONE.
• Active Directory, to know who each user is and whether they are still active.
• ERP: SAP and Microsoft Dynamics, to allocate spend by cost centre.

Inventory, invoice audit, optimisation and cost allocation are all built on that integrated data. You can see every integration on the platform page.