Request a quote
Emergency SectorsCareers About us Blog Get in touch
Desk by a window with a laptop, an open notebook and two cups of coffee

Software license management: what you pay for and never use

Software license management sounds like admin, and it is. The difference is that this admin produces an invoice every month for licences nobody uses: for people who have left, for products that do the same job and for subscriptions that renewed without anyone noticing. This is the order in which we get licences under control, and what you need to be able to show when a software vendor asks for an audit.

7 min read Written by the ITproposal team
Short answer

A licence list built from invoices tells you what you bought. Only next to what is assigned and what is actually used do you see where the money goes.

Most unused licences come from leavers, shared mailboxes and products that overlap. That is why licences belong in the joiner, mover and leaver process.

Appoint one licence manager with the authority to act, and track the notice period on every contract. In an audit you supply proof of purchase and the technical count; the legal side belongs with a lawyer.

Software license management starts with an inventory

A licence overview built only from invoices tells you what you bought. It does not tell you what is running or who uses it, and that gap is where the money sits. Put three sources side by side:

  • What you bought: contracts, invoices and order confirmations, including those from the supplier who once arranged it for you. For each product, record the quantity, the licence metric (per user, per device, per processor core or per site) and the term.
  • What is assigned: the admin consoles of your cloud services. They show who each licence is assigned to and, for most products, when that person last signed in.
  • What is installed: the software on laptops, servers and virtual machines, taken from your device management or an inventory agent. This is where you find installations with no purchase behind them.

Then ask finance what is being paid by company card and expense claim. A team that signs up for its own design, survey or planning tool appears in no admin console, but it does appear on the statement.

The result is one line per product with three numbers: bought, assigned, used. How to combine that with your hardware is covered in our article on the IT asset register.

Where the unused and duplicate licences are

Once the three numbers sit next to each other, the same kinds of gap almost always show up:

  • Leavers. The account is blocked, but the licence is still attached. Or the account is still active because someone “just needed to check the mailbox”.
  • Shared mailboxes with a licence. In Microsoft 365 a shared mailbox usually does not need a licence of its own, unless it needs more storage or an archive, for example. Many still have one because they were created as ordinary users.
  • Overlap between products. Two video meeting tools, two places to store files, a separate security product alongside a suite that already includes the same function. Each was a reasonable choice on its own; together you pay twice.
  • A bigger licence than needed. Everyone on the most comprehensive plan because that was easy at the start, while some people only use email and a browser.
  • Trial and project licences. Bought for a pilot and never cancelled after it.
  • Installations nobody uses. Software in the standard image, so it is on every laptop, while a handful of people ever open it.

Do not remove everything in one go. Send the list to department heads first, ask what can go and give them a deadline. Whatever nobody claims is removed.

Licences follow people: tie them to joiners, movers and leavers

A one-off clean-up does not last a year if licences are assigned by hand. What lasts is a licence that moves with the process that brings someone into, through and out of the organisation.

  • Joiners: the role decides which plan someone gets. Work with a few fixed profiles instead of choosing per person, and assign licences through groups where you can.
  • Movers: the old licence goes back. This is the step most often forgotten, because nobody is leaving.
  • Leavers: HR tells IT the date in advance. On that date the account is closed. You then decide what happens to the mailbox and the files (hand them to a colleague, convert to a shared mailbox, or retain them under your retention policy), and the licence is released.

Agree who makes the decision about the data. It is personal data, so this is a UK GDPR question as well as a licensing one, and it belongs with the line manager or whoever is responsible for data protection, not with the administrator closing the account.

Renewal dates, notice periods and auto-renewal

Most software renews automatically. That is convenient while you want to keep the product, and expensive the moment you no longer do and the notice period has just passed. For each contract you want to know four things:

  • The renewal date and the notice period, not just the end date. If you give notice on the end date, a notice period of a few months means you are too late.
  • Whether you can reduce quantities during the term. Some annual subscriptions let you add licences mid-term but only reduce them at renewal, even if you pay monthly.
  • Whether there is an annual true-up for what you used beyond what you bought. It arrives after the fact, and without your own count you cannot check it.
  • Who signed the contract, and in whose name. A subscription tied to the email address of someone who has left is hard to cancel.

Put every renewal date, with its notice period before it, in a shared calendar or your ticketing system, with an owner per line. Well before the notice period is the moment to look at the three numbers from the inventory again, so you decide how many to renew from data rather than from last year’s figure.

A software vendor audit: what you need to be able to show

Many licence terms give the vendor the right to check whether your use matches what you bought, either directly or through an external auditor. The request usually arrives by letter or email, with a deadline. There is no need to panic, but there is a need to move: with an inventory in place you answer in days, without one in months.

What you need to be able to show:

  • Proof of purchase for each licence: contract, invoice or licence certificate, including licences that came through a previous supplier or an acquisition.
  • The licence terms that applied when you bought. Terms change, and the earlier version may be more favourable to you.
  • Where the software runs: on which servers, on how many processor cores, in which virtual environment. For software licensed per core or per server, virtualisation is the difference between a correct count and one that is far too low.
  • Who has access to it, and whether that is only people or also integrations and service accounts.

Read exactly what the request covers first, and supply no more than is asked. Agree the format and the channel for sharing data, and bring in a lawyer before you sign anything or accept a finding. Exports containing user names are personal data, and that belongs in the same agreement.

Who holds the licence manager role

Licence management rarely fails for lack of knowledge and almost always for lack of ownership. IT sees the installations, procurement the contracts, finance the invoices and HR the joiners and leavers, and each assumes someone else has the overview.

Appoint one person as licence manager, with a deputy. It need not be a full-time job; in an SME it is a task alongside another role. It includes:

  • keeping the inventory and comparing the three numbers per product every quarter;
  • watching the renewal calendar and asking for a decision well before each notice period;
  • seeing new purchases before they happen, so a third meeting tool does not appear;
  • being the point of contact when an audit request arrives.

Give that person authority as well. Someone who can see unused licences but cannot cancel them without three signatures writes a report and changes nothing. Agree which decisions the licence manager takes alone and which go to the budget holder.

Where our work stops

What we do. As part of our workplace management and our management of Microsoft 365 and other cloud services, we track which licences exist, who they are assigned to and whether they are used. We tie assignment and release to joiners and leavers, keep the renewal dates in a calendar, flag unused and duplicate licences, and in an audit we supply the technical data: installations, servers and users. Which licences you cancel or keep is your decision.

What we do not do. We are not lawyers and not licence auditors. We do not give legal interpretations of licence terms, we do not declare your organisation compliant, and we do not negotiate with a software vendor on your behalf about an audit finding or a settlement. For that you need a lawyer or a specialist licensing adviser; we supply the figures they need.

Frequently asked

Questions we get about this

The five that come up most often.

What is software license management?

It is keeping track of which software your organisation has bought, how much of it is assigned and installed, and who actually uses it. It includes releasing licences when people leave, watching renewal dates and notice periods, and being able to demonstrate your licence position in an audit. It is also called software asset management.

What should you do with a leaver’s licence?

Close the account on the last working day, decide what happens to the mailbox and files, then release the licence. A mailbox can often be converted to a shared mailbox or handed to a colleague. Have HR give the leaving date in advance, otherwise the licence keeps running for months.

Does a shared mailbox in Microsoft 365 need a licence?

Usually not. A shared mailbox can exist without a licence of its own, unless it needs more storage or an archive, for example. Shared mailboxes created as ordinary users often still have one, and they are among the first things to check in a clean-up.

What do you need to show in a software licence audit?

For each product, proof of purchase, the licence terms that applied when you bought, where the software runs (servers, processor cores, virtual environments) and who has access to it. Read exactly what the audit request covers first and supply no more than is asked. Involve a lawyer before you accept a finding or sign anything.

Can you represent us in a software vendor audit?

No. We are not lawyers or licence auditors, and we do not negotiate on a client’s behalf about an audit finding or a settlement. What we do is supply the technical data: which software runs where and who uses it. The legal reading of the terms and the conversation with the vendor belong with a lawyer or a specialist licensing adviser.

Shall we put your licences next to actual use?

Send us the list of products and renewal dates you have now. We compare it with what is assigned and used in your environment and show you where the gap is; which licences you cancel is your call.

Practical IT knowledge in your inbox

New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.

We use your address for the newsletter only. See our privacy policy.

Request a quote Call