Skip to main content
SearchEnquiry basket
OfficesIndia · UAE

Licensing practice

Preparing for a software licence audit before anyone asks

An audit is a documentation exercise. Organisations that fail one usually had the licences and could not prove it.

· 7 min read

Software audits arrive from three directions: a publisher exercising an audit clause, a customer's supplier assurance process, or a tender asking for compliance evidence. All three ask the same question, and it is not "are you licensed". It is "show me".

The organisations that struggle are rarely pirating anything. They have bought what they needed, over several years, through several people, and cannot now assemble the evidence.

What an audit actually asks for

What is installed, where. A list of installations by machine or by user, for the products in scope.

What you are entitled to. Proof of licence for each: the invoice in your organisation's name, the agreement or enrolment number for volume licences, and portal access.

How the two reconcile. Installations matched against entitlements, with the gaps explained.

That the licence type matches the use. A named-user licence used by two people, an academic licence used commercially, or an OEM licence moved to a different machine are all non-compliant despite the licence being genuine.

The four-step preparation

Step one: inventory what is installed. Discovery tooling does this properly. Done by hand it is a survey, and surveys miss the machine in the corner that runs the plotter.

Step two: assemble entitlements. This is the slow part and the reason to start before anybody asks. For each product: who bought it, when, under what agreement, and where is the paperwork. Expect gaps where a purchase predates the current finance system or the person who made it.

Step three: reconcile. Installations against entitlements, per product, per licence type. Two kinds of gap appear and both matter:

  • Under-licensed — installations with no entitlement. This is the exposure.
  • Over-licensed — entitlements with no installation. This is money already spent on nothing, and it is usually the larger number.

Step four: close the gaps. Buying a shortfall prospectively, before an audit finds it, costs the licence price. Found during an audit it can cost considerably more, and publishers are entitled to back-date.

The specific things that trip people

Named-user licences treated as floating. Most current design and productivity software is per person. An estate administered as though licences were per machine will reconcile badly.

Server CALs. Rarely tracked, frequently short. See Windows Server 2025 licensing explained.

Virtual machines and test environments. A development or test instance usually needs licensing. "It is only a test box" is not an entitlement.

Software on machines that left. A licence assigned to a laptop that was disposed of, or to somebody who left two years ago, is an entitlement you are paying for and not using.

Eligibility that lapsed. An academic or non-profit licence remains compliant only while the eligibility holds.

Keys without paperwork. The commonest finding. The software is genuine, the organisation paid for it, and there is no document that says so. See how to buy genuine Microsoft licences in India.

What to keep, permanently

A single place holding, per product:

  • Invoices, in the organisation's name
  • Agreement and enrolment numbers, with portal credentials recorded against a role rather than a person
  • Licence terms, quantities and renewal dates
  • The assignment record — who or what each licence covers
  • Deployment and disposal records

This is not an audit artefact. It is what makes renewals rational, and the reconciliation that produces it typically finds enough over-licensing to pay for itself.

How often

Annually, and before any renewal of consequence. An estate reconciled two years ago is wrong now, because people joined, left and changed roles.

Common questions

Can we refuse an audit? Volume licensing agreements generally contain an audit clause you have already agreed to. Read yours.

Does the publisher's own portal show our entitlements? For subscriptions bought through current channels, largely yes. For older perpetual purchases, often not, which is why the paperwork matters.

What if we find a real shortfall? Close it prospectively and keep the record of having done so. A gap found and fixed is a different conversation from a gap found by an auditor.

Who should own this? Someone named. Shared ownership of a licence register means no ownership, which is how registers go stale.

Where to go next

Software asset management is the service that builds and maintains the register, and licence management keeps the renewal calendar against it. See also the hidden cost of unused licences, which is the half of this exercise that saves rather than costs money. To start with a reconciliation, send us your licence list.

More articles