software licensing

Software licensing compliance: entitlements, audits, true-ups and the contract terms that decide them

Tomas ArkwrightLegal technology writer10 min read

Written by Tomas Arkwright Software licensing compliance means using software only within the rights your licence agreements actually grant: the right number of users or devices, the right editions, the right environments and the right territories. It sounds administrative until a vendor audit letter arrives and the gap between what you bought and what you run turns into an invoice. This page explains how that gap opens, how the main license metrics work, what happens in a vendor audit and a true-up, which tools help, and which contract terms are worth negotiating before you sign, because software license compliance is decided as much by the agreement as by the IT estate. ## Entitlement against deployment: where compliance gaps come from Every compliance question comes down to two lists. The first is your entitlement: what your contracts, order forms and purchase records say you may use. The second is your deployment: what is actually installed, assigned or consumed across your laptops, servers, cloud tenants and SaaS accounts. When deployment exceeds entitlement, you are under-licensed and exposed. When entitlement exceeds deployment, you are over-licensed and wasting money. Both are compliance problems; only one of them gets you audited. Asset management tools call the comparison of the two lists your effective license position. Producing it is harder than it sounds, for three reasons. - Entitlement is scattered. Rights sit in master agreements, order forms, reseller quotes, renewal emails and product terms incorporated by reference. Product use rights such as downgrade rights, second-use rights for a laptop, or non-production use can change the position significantly, and they are written in the contract, not in the install data.

  • Deployment keeps moving. Virtual machines spin up, staff change roles, a team trials a premium feature and forgets to switch it off.
  • The metric decides the count. The same deployment can be compliant under one metric and badly short under another. ## License metrics and how each one goes wrong | Metric | What is counted | Where companies usually fall short | | --- | --- | --- | | Named user | Each individual allowed to use the software | Leavers never removed; shared logins; contractors not counted | | Concurrent user | Maximum users at the same time | No reliable record of peak use when the auditor asks | | Device | Each machine where the software is installed or accessed | Old installs left on reassigned laptops; virtual desktops | | Processor or core | Physical or virtual cores on the server running the software | Virtualisation: some terms count every core in the host cluster, not just the virtual machine | | Usage or consumption | Transactions, API calls, storage, compute hours | Growth without a cap; overage billed at a higher rate | | Enterprise or employee count | All employees, or all employees plus contractors | Headcount growth after an acquisition | | Feature or edition | Which edition or add-on is enabled | Premium features switched on by an administrator without an order | The contract defines the metric. A term like "User" may include anyone with access, not just anyone who logs in, and "Affiliate" may decide whether a newly acquired subsidiary is covered. Read the definitions before you count anything. ## What a vendor software audit looks like Most enterprise licence agreements contain an audit clause that lets the vendor, or an auditor it appoints, verify your usage. A typical audit runs in five stages. 1. The notice. A letter or email announcing a license review or audit, citing the clause. Check the notice period and scope the clause actually allows.
  1. The data request. Questionnaires, deployment reports, and sometimes vendor scripts to run on your servers. Agree in writing what data you will provide and in what format; running a vendor's script on your production estate is a decision, not an obligation, unless the contract says so.
  2. The analysis. The auditor compares your data with their record of your entitlement. Their record is often incomplete, so prepare your own entitlement file first.
  3. The findings. A report stating the shortfall, usually priced at list price plus back maintenance.
  4. The settlement. Most audits end in a negotiated purchase rather than a dispute. The strength of your position depends on the contract terms below and on how good your own records are. Treat every audit notice as a legal matter as well as an IT one. Someone should read the clause, confirm the scope, and control what leaves the building. ## True-ups and SaaS overages Not every compliance event is an audit. Many agreements build reconciliation into the contract. A true-up is a scheduled count where you report growth and pay for it. Microsoft's Enterprise Agreement guidance describes the true-up as an annual inventory of products, services, users and devices added during the year, priced at the terms agreed in the agreement, and says the true-up order must reach Microsoft between 60 and 30 days before the agreement anniversary. If nothing changed, an update statement is still due. A missed true-up is not a saving; it becomes a finding later. SaaS overages work differently. Usage beyond the subscribed quantity may be billed automatically, sometimes at a higher unit rate, or the vendor may move you to the next tier at renewal. The compliance work here is reading the order form for overage rates and caps and watching usage dashboards each month, not counting installs. ## Software license compliance management tools For a small estate, a well-kept spreadsheet of contracts and a quarterly user review can be enough. Beyond a few hundred staff or a meaningful server estate, most organisations use software asset management (SAM) tools. | Option | What it does | Fits | | --- | --- | --- | | Spreadsheet plus contract folder | Manual entitlement list and periodic user counts | Small companies with mostly SaaS and few servers | | Flexera One IT Asset Management | Its SAM page describes an entitlement library with product use rights, reconciliation to an effective license position for major vendors, and audit readiness reporting; a separate SaaS Management product covers SaaS | Large estates with major on-premise vendors | | ServiceNow Software Asset Management | Its product documentation describes reconciling discovered installations against entitlements to set a compliance status, and reclaiming unused rights | Organisations already running ServiceNow for IT service management | | Licensing advisers | Specialists who model your position and run audit defence | One-off audits, complex vendors, or no in-house SAM team | Every SAM tool depends on two inputs: good discovery data from your estate, and accurate entitlement data from your contracts. The second is where legal and procurement come in, because a tool cannot apply a product use right or a negotiated exception that nobody entered. ## Contract terms that decide your audit exposure The cheapest time to manage software license compliance is when the agreement is signed. These terms decide how painful a future audit will be. Our software license agreement negotiation playbook covers the wider deal; these are the audit-specific points. - Notice period. At least 30 days' written notice before any audit begins.
  • Frequency. No more than one audit in any twelve-month period.
  • Conduct. During business hours, without unreasonable disruption, limited to records relevant to the licensed products.
  • Who audits. An independent auditor bound by confidentiality, not a vendor sales team, and not paid on a contingency basis tied to findings.
  • Data and tools. You choose the method of providing data; no obligation to run vendor scripts unless agreed.
  • Cost-shifting. The vendor bears the audit cost unless the shortfall exceeds an agreed threshold, and the threshold is stated as a number in the contract.
  • Remediation price. Any shortfall is bought at your contracted discount, not list price, with no retrospective support fees beyond a stated period.
  • Cure period. Time to buy or remove licences after findings, before any breach or termination right arises.
  • Definitions. Clear meanings for User, Affiliate, production and non-production, and the rules for virtualised and cloud environments.
  • Acquisitions. A grace period to bring a newly acquired company's usage into compliance. For subscription software, the parallel points are overage rates, caps, the right to reduce quantities at renewal, and price increase limits; the SaaS contract negotiation playbook covers those. ## Events that quietly break a compliant position Many companies are compliant on the day they sign and drift out of it through ordinary business changes. Watch for these. Acquisitions and disposals. A newly bought company arrives with its own software, its own agreements and often its own gaps. Its licences may not transfer to you without vendor consent, and your licences may not cover its staff if the contract limits use to named entities. When you sell a business, the buyer may keep using software licensed to you under a transition arrangement, which also needs to be covered in writing. Moving to the cloud. Licences bought for on-premise servers do not automatically carry over to a public cloud. Some vendors allow it under specific programmes; others count cores differently once the software runs on shared hardware. Check the product terms before the migration, not after. Outsourcing. When a service provider runs software on your behalf, confirm whether your licence permits third-party use and whose licence covers the provider's staff. Restructuring and headcount growth. Enterprise-wide metrics based on employee numbers rise automatically as you hire. Contractors may or may not be counted, depending on the definition. Administrator changes. A new IT administrator enabling a premium feature for a pilot can move the whole tenant to a higher edition for billing purposes. Build a simple trigger: any of these events sends a short note to whoever owns the entitlement file, so the position is rechecked before the vendor notices. ## A 90-day software licensing compliance routine 1. Days 1 to 30: build the entitlement file. Gather every agreement, order form and amendment for your ten largest vendors by spend. Record metric, quantity, edition, product use rights and the audit clause terms for each.
  1. Days 31 to 60: count deployment. Pull user lists, install data and cloud consumption for the same vendors. Remove leavers and unused accounts first.
  2. Days 61 to 90: reconcile and act. Compare the two, buy or remove where you are short, reduce where you are over, and diarise each true-up and renewal date with an owner. Repeat each quarter for the top vendors and annually for the rest. ## Where Adira fits: reading the licence agreement itself Adira works on the contract side of this problem, not the estate side. Open a licence agreement or order form in Adira and its Document Intelligence Dashboard marks each position as favourable, neutral or unfavourable to your company, and lists red flags, obligations, key dates and monetary terms, which is how a reviewer quickly finds an audit clause with no frequency limit, remediation at list price, or a broad definition of User. Clause-Level Editing then lets you draft your counter-position in plain English, for example "limit audits to once in any twelve months with 30 days' notice", and returns a diff of the change. Adira does not discover installations, count users or calculate a license position, so you still need a SAM tool or a spreadsheet for deployment. The Practice plan is published at USD 89 per seat per month billed annually, minimum three seats, and there is a 7-day free trial at adiralaw.com.

Frequently asked questions

What is an effective license position?
It is the comparison of what you are entitled to use under your agreements with what you actually deploy or consume, product by product. A shortfall means you are under-licensed; a surplus means you are paying for rights you do not use.
Can a software vendor audit us at any time?
Only as far as the audit clause in your agreement allows. Many clauses set a notice period and a limit on frequency, and some set none. Read the clause before responding to any audit letter.
What is the difference between a true-up and an audit?
A true-up is a scheduled self-reported count built into the agreement, where you pay for growth at agreed prices. An audit is a verification the vendor starts, usually priced at list rates if a shortfall is found.
Do SaaS subscriptions need license compliance work?
Yes, though it looks different. Instead of counting installs, you watch user assignments and consumption against the subscribed quantity, and read the order form for overage rates, caps and the right to reduce at renewal.
Is Adira a software asset management tool?
No. Adira reviews licence agreements and order forms for audit terms, obligations, key dates and monetary terms, but it does not discover installations or count usage. Pair it with a SAM tool or a spreadsheet for the deployment side.
Was this useful?

See how Adira drafts in your voice and reads contracts from your side.

Explore the showroom

Working through a contract like this? Weave is Adira’s free tool to read, mark up, and connect any contract in your browser — no account needed.

Try Weave — free

Book a demo

See Adira on your own contracts

A 30-minute walkthrough with our team. Tell us a little about you, then pick a time that suits you.

Prefer email? [email protected]