The Invoice Is Not the Inventory: Reconciling Comms Services Before They Become a Liability

Most UK SMEs treat the monthly comms invoice as a payment instruction. It arrives, it is compared with last month, and it is approved. The trouble is that an invoice records what a supplier believes it should charge, not what the business actually uses. Over time, those two things drift apart. A line left behind after a move, a SIP channel bought for a project, a SIM kept in a drawer, a software licence attached to a leaver: none of these announce themselves. They simply become part of the bill.

That drift matters beyond cost. A service register that cannot be defended is a procurement risk. It makes renewals harder to negotiate, exits harder to execute and continuity planning less reliable. The ghost circuit is not only a line that should have been cancelled. It is a line whose owner, purpose and notice period are unknown.

A bill audit is an exit-readiness check

Cost saving is the obvious reason to reconcile comms invoices. It is rarely the most important one. The more serious question is whether the business can state, with evidence, which services it buys, at which sites, on what terms and for what purpose. If that cannot be answered, a supplier holds the advantage at renewal and the business holds the liability at exit.

Termination charges, auto-renewal clauses and minimum contract terms tend to attach to services that have been forgotten rather than services that have been actively chosen. A dormant analogue line may carry a small monthly rental and a disproportionate early termination charge. An unused SIP channel may sit inside a bundle that cannot be reduced without renegotiating the whole arrangement. A duplicate mobile SIM may be cheap per month but expensive in data protection terms if it is still active and unmanaged.

For procurement teams, reconciliation is therefore a form of due diligence. It turns a supplier-led account into a business-owned record.

Where ghost services tend to hide

Ghost services rarely appear as obvious anomalies. They hide in the ordinary language of telecoms billing. Dormant analogue lines may still support a lift, an alarm, a fax or a payment terminal, even if the main office has moved to cloud telephony. Unused SIP channels may have been ordered for a peak that never arrived. Duplicate mobile SIMs may sit with former employees, temporary sites or shared devices. Forgotten circuits may include legacy broadband, point-to-point links or backup connections that were superseded but never ceased. Licence creep is subtler still: per-seat telephony, call recording, contact centre seats, security add-ons and management portals can all expand quietly as staff join, move or leave.

Bundles make the problem harder. A single invoice line may combine line rental, calls, broadband, mobile and support. The total can look stable while the components change. That is why a bill audit should not begin with the total. It should begin with the components and the evidence behind them.

Start with evidence, not the invoice

The first step is to gather source documents rather than rely on memory. A practical evidence set includes twelve months of invoices, current contracts and order forms, supplier welcome letters, accounts payable records, site lists, network diagrams, mobile SIM inventories and any previous service schedules. Where available, customer relationship management records and internal approval emails can help identify who ordered what and why.

From those documents, build a service record for each item. At minimum, record the service type, supplier, billing reference, site or user group, monthly cost, contract start and end date, notice period, business owner, stated purpose, technical dependency and a link to the supporting evidence. A register without evidence is just another list. A register with evidence becomes a defensible inventory.

Reconcile in layers

Reconciliation works best in three layers. The first is documentary: compare invoices against contracts and order confirmations. The second is technical: check active ports, call logs, SIM management platforms, router interfaces and telephony administration screens. The third is business-led: ask service owners to confirm whether each item is still needed. Each layer catches a different kind of error.

The discrepancies should be classified rather than immediately cancelled. Some services are active and needed. Some are active but no longer needed. Some are billed but not active. Some are active but not billed, which is a risk in itself. A billed-but-inactive service is a savings opportunity. An active-but-unbilled service is a commercial and continuity risk. An active-but-unneeded service is a decision, not an automatic termination.

Resolve with dependencies in mind

Once a discrepancy is confirmed, the response should be one of four options: retain, reduce, migrate or terminate. Termination is rarely the first safe move. A dormant line may support a safety or security service. A legacy circuit may carry a building management system. A SIM may be attached to a lone worker or a telemetry device. The cheapest-looking line can be the most expensive to remove if it carries an essential dependency.

Notice periods also need checking before any cancellation instruction is issued. A service that appears monthly may sit inside an annual minimum term. A bundle may reprice if one component is removed. The register should record those constraints so that procurement decisions are made with the full picture rather than the invoice alone.

Make the register defensible

A defensible register has a version, a date, an owner and an approval trail. It should be reviewed at least quarterly and again before any major renewal. It should link to the business continuity plan and to the IT exit file, so that service dependencies are visible when a supplier changes or a site closes. When a supplier asks who owns a service, the answer should be a record rather than a name.

Reconciliation is not a one-off spring clean. It is a habit. In 2026, with analogue services being retired and cloud telephony renewals continuing to reshape comms estates, the businesses that manage this well will be those that can separate the invoice from the inventory. Start with one site or one supplier, gather the evidence and build the register from there. The aim is not simply to pay less. It is to know what is being paid for, why it exists and how it can be exited.