The Empty Desk Still Has a Licence: A Quarterly Reconciliation of Named Software Seats

Named-user software licences rarely announce themselves when they go wrong. A person changes team, hands over a project or leaves on a Friday; the account is disabled, the laptop is wiped, and everyone assumes the seat has gone with them. In practice, the licence often remains assigned in a vendor portal, attached to an add-on, or counted in a renewal quote that nobody has challenged. For UK SMEs, the result is a quiet recurring cost and a weaker compliance position than the finance team believes.

The problem is not usually negligence. It is a timing mismatch. HR records change when a person moves. Software administration changes when someone remembers to log in and update the vendor portal. Between those two events, a named seat can sit against a role that no longer exists. With many UK firms approaching end-of-year renewals in late 2026, a quarterly reconciliation is a practical control rather than an academic exercise.

Why the seat moves with the person

Named-user licensing is built around identity. The vendor issues a seat to a named individual, often tied to an email address, a user principal name or an employee record. When that person changes department, the old licence may remain assigned because the new role needs a different product tier. When the person leaves, the account may be disabled in Microsoft 365 or Google Workspace while the vendor portal still shows an active subscription.

The audit is not a witch hunt. It is a reconciliation between three sources of truth that rarely update at the same moment: the HR system, the identity platform and the vendor admin portal. The aim is to prove that every paid seat maps to a current person, a documented service account or a deliberate retention decision.

Start with HR, not the vendor portal

Begin with a starter, mover and leaver report for the quarter. Ask HR or payroll for effective dates, department, line manager, employment type and, where relevant, contract end date. The mover record is the one most often missed. A leaver is visible because someone leaves. A mover is quieter: the person is still on payroll, still has an email address, but may no longer need the old product or may now need a different one.

Use a consistent identifier. Employee ID is preferable where available; otherwise use the primary work email address and record aliases separately. Do not rely on a distribution list or a memory of who sits in which team. The audit needs evidence that can be repeated next quarter by someone else.

Separate named seats from concurrent seats

Named-user and concurrent licensing answer different questions. Named licensing asks who is entitled to use the software. Concurrent licensing asks how many people may use it at the same time. An SME can have fifty staff and ten concurrent seats if peak simultaneous use is genuinely ten. It cannot have fifty named seats and only thirty current assignments without explaining the gap.

For named seats, every active assignment should map to a person, a documented shared account or an integration account with an owner. For concurrent seats, do not use headcount as the measure. Use peak concurrency evidence from the vendor portal or from a short sampling exercise. If the vendor cannot provide usage data, treat the renewal conversation as a negotiation rather than an assumption.

Reconcile the vendor portals

List every vendor that issues named licences, including the less obvious ones: design tools, telephony add-ons, backup agents, accounting plug-ins and specialist line-of-business applications. For each, record the admin portal, the contract owner, the renewal date and the licence type. Then export the active user list and compare it with the HR data.

Flag four categories: active staff with no licence, licensed users who are not in HR, licensed users whose role no longer requires the product, and add-ons attached to users or tenants without a clear base licence. Check last sign-in date where the portal provides it, but do not treat a lack of sign-in as proof of non-use. Seasonal staff and project users may be legitimate. The decision should be recorded, not guessed.

Treat exceptions by rule, not by memory

A short decision table prevents the audit from becoming a series of one-off arguments. A leaver should have licences removed after any documented data retention or handover period. A mover should have the old seat reclaimed and the new seat assigned through the same change request. A contractor should have an end date recorded in the licence register. A shared mailbox should not carry a named-user licence unless the vendor terms explicitly allow it.

For long-term absence, record the retention reason and review it at the next quarter. For integration accounts, record the business owner and the system they serve. The point is not to remove every seat aggressively; it is to ensure that every seat has a defensible reason to exist.

The orphaned add-on problem

Add-ons are where licence hygiene often breaks down. A telephony add-on may remain assigned after the base licence is removed. A backup or analytics module may be billed at tenant level while the user-level licence has gone. A security add-on may be attached to a leaver because the offboarding checklist only covered the main product.

Review add-ons separately from base licences. Ask the vendor whether the add-on requires a qualifying base licence and what happens to billing if the base licence is removed. Record the answer. This is also a useful question at renewal, because vendors sometimes bundle add-ons into a quote without showing the underlying seat count.

Build evidence for renewal and compliance

Keep a simple audit workbook with columns for quarter, vendor, contract type, licensed quantity, active assignments, exceptions, decision, owner and date. Store it with the contract and the renewal notice. This is not bureaucracy for its own sake. It gives the finance team a defensible number, gives the IT manager a repeatable process and gives the business a cleaner position if a vendor or auditor asks how named seats are controlled.

A vendor quote is a claim. The reconciliation is evidence. When the renewal notice arrives, compare the quoted quantity with the active assignment count and the documented exceptions. If the gap is material, ask for a true-down or a revised quote before the auto-renewal date. In late 2026, with software budgets under scrutiny, that conversation is easier with a workbook than with an anecdote.

A single-afternoon timetable

A quarterly audit does not need a project board. Allow roughly half a day. Spend thirty minutes confirming scope and pulling the vendor list. Spend forty-five minutes obtaining and cleaning the HR starter, mover and leaver data. Spend ninety minutes working through the admin portals and recording exceptions. Spend thirty minutes applying the decision rules with the relevant budget owner. Spend the final fifteen minutes updating the workbook and setting the next quarter date.

The first run will take longer because the vendor list and portal access need to be established. Later runs become a routine reconciliation. The important discipline is to run it before renewal, not after.

Make it quarterly

Named licences are not static assets. They follow people, and people move. A quarterly reconciliation keeps the paid estate close to the real organisation, catches orphaned add-ons before they accumulate and gives UK SMEs a plain-spoken answer to a simple question: who is actually using what we pay for?