Most organizations can tell you what they spend on software. Far fewer can tell you what they are entitled to use, what they actually use, and where those two numbers disagree. Enterprise software license management lives in that gap. It is the discipline of knowing what rights you hold, how they are measured, and whether your estate stays inside them, at a cost that makes sense.
It sounds like bookkeeping until a vendor audit letter arrives, or until a renewal comes in 30% higher and nobody can say how many seats are really in use. This article explains what license management covers, how the common license models work, what the recent survey data says about audits and cost, and how to put a working process in place. It includes worked examples, and it does not recommend any specific tool.
What Enterprise Software License Management Covers
License management is the part of software asset management (SAM) that deals with rights and compliance. It answers four questions for every significant product.
- What did we buy, and under which terms?
- What are we using, and how does the vendor measure it?
- What is the gap between the two, and what does it cost to close?
- When is the next decision, such as a renewal, a true-up or an end of support date?
It overlaps with, but is not the same as, the wider software asset management program. SAM also covers inventory, procurement, usage and cloud spend. License management is the sharp end: the contract terms and the numbers that back them up. If you want the broader view, our article on why SAM programs stall in mid-size and large organizations covers it.
Why It Is Harder Than It Looks
A license is a legal document, not a quantity. Two products that look alike in an inventory can be measured in completely different ways, and the measure decides what you owe. A vendor may count named users, concurrent sessions, devices, processor cores, subscription seats or consumed units. The same vendor may use different metrics for different products, and those metrics can change at renewal.
Add to this the usual features of a large estate: virtual machines that move between hosts, cloud workloads that start and stop, subsidiaries acquired through mergers, contractors with accounts, and employees who change role. Each of these quietly changes the count.
A Worked Example
The figures below are illustrative, not drawn from a real client, but each one reflects a pattern we see repeatedly.
Product A is licensed per named user. The organization owns 1,000 seats. A review of sign-in activity shows 720 accounts used in the last ninety days. That leaves 280 seats that could be reclaimed or, at renewal, dropped. Reclaiming them is a saving. It is also a negotiation point.
Product B is licensed per processor core. The organization owns 128 cores. The product runs on a virtualized cluster of five hosts with 32 cores each, so the vendor’s rules count 160 cores. That is a shortfall of 32. At list price this may be a significant liability, and it often goes unnoticed because the cluster grew over time while the license stayed fixed.
Product C is a subscription with 500 seats. Only 410 have been assigned. That leaves 90 unused seats, but the subscription renews automatically, so the saving only exists if someone notices before the notice period ends.
The lesson is not that one product is worse than another. It is that surplus and shortfall exist side by side in the same estate, which is why a single total number, such as total spend, hides the real position. A good position report is built per product and per metric.
What the Survey Data Says
Two recent sources show how much audits and compliance now cost. The Flexera 2026 State of ITAM report, based on 512 respondents, found that 44% of organizations had spent more than $1 million on audits over three years, and that only 36% said they had complete visibility of their technology estate.
A second survey, run by Dimensional Research for the ITAM Forum and Azul in 2025, asked 500 IT and software asset management professionals at organizations using Oracle Java. It found that 73% had been audited in the previous three years, 54% were spending more than $100,000 a year on non-compliance, and 27% were spending more than $500,000. Around 81% ran licensing audits at least twice a year, and 74% did discovery and audits in-house. The sponsor of that survey sells an open source alternative, so the migration figures, with 79% moving or planning to move, should be read with that in mind. The audit and cost findings are still a useful picture of how heavy the load has become.
The same survey gives a feel for what makes the work hard. Respondents named accurate usage records, complex license terms and precise compliance metrics as their main struggles, at roughly a quarter each. Those are not tooling problems. They are problems of data, ownership and interpretation.
One example from that survey is worth knowing even if you do not use the product. In January 2023 the publisher moved its Java licensing to a per-employee basis. That is a change of metric, from something an IT team can count to something that depends on headcount. It shows how a contract can look unchanged while the cost basis moves under it. Changes of this kind are exactly why license rules need a named owner and a regular review.
The License Lifecycle
License management works when it is treated as a loop, not a project. Every product moves through the same stages, and every stage has a natural owner.
Most problems appear at a handoff. Procurement signs a contract with terms IT never saw. IT deploys the software in a way the contract does not allow. The business owner renews without checking usage. If each handoff has a record and a person, the loop closes. If not, the same mistakes come back each year.
Six Practices That Make the Difference
1. Keep a contract-based entitlement record
Invoices show what was paid. Contracts show what you may do. The entitlement record should capture the metric, the quantity, the term, the use rights, the support period and the renewal terms, for each product line, with a link to the source document.
2. Write the rules down once
For each major publisher, record how your organization interprets the metric: how virtual hosts are counted, whether disaster recovery copies need licenses, how contractors are treated. Have legal or procurement sign off. The result is a short rule book that prevents the same debate each time the numbers are rebuilt.
3. Match data sources to the metric
Named user licenses need identity and sign-in data. Core licenses need host and cluster data. Subscription products need admin console exports. Use the source that actually proves the metric, not just whatever is easiest to collect.
4. Produce a position by product, with confidence
Report the gap between entitlement and use for each significant product, and say how confident you are in each number. A number you can defend is more useful than a precise number you cannot.
5. Work to the renewal calendar
Renewals are where license management earns its keep. Work backward from the end of term, and start early enough that you still have options. Leverage fades as the date approaches.
6. Put a gate in front of new purchases
Many compliance gaps start with a purchase nobody in IT saw. A simple intake step that routes software requests through the license team, and checks for an existing license that can be reused, prevents duplicates and catches shadow purchases early.
Common Mistakes
The same errors appear across industries, and most of them are avoidable.
- Buying a discovery tool before deciding what the output must prove.
- Treating the first position report as final, rather than improving it every quarter.
- Reporting hard savings and soft savings together, which makes finance distrust both.
- Letting the person who built the spreadsheet be the only one who understands it.
- Waiting for an audit letter to learn the real position.
- Ignoring cloud and subscription products because they feel less formal than perpetual licenses.
That last point is growing in importance. Subscription and consumption pricing shift the risk from compliance to cost. You are less likely to be out of compliance, but far more likely to overspend quietly. The same rules apply: know what you hold, what you use and when the next decision falls. Our piece on AI and agents in software asset management looks at how this is changing.
Examples From the Field
Two patterns we see in regulated and manufacturing environments illustrate how this plays out.
In a financial services setting, the combination of strict audit rights in contracts and many virtualized platforms means a small configuration change can produce a large compliance gap. A structured preparation process, often called a true-up review, brings the position into line before the vendor asks. Our work in banking and financial services describes this approach.
In a global manufacturer with plants in many countries, local purchases and local contracts mean the same product is licensed several different ways. Consolidating entitlements, and agreeing one set of rules, removes duplicate spend and makes renewals predictable. Our note on global software license compliance in automotive covers the details.
Measures That Keep It Honest
- Entitlement coverage: the share of spend, by publisher, with a complete contract-based record.
- Position confidence: for each top publisher, the gap between use and entitlement, and how sure you are of it.
- Reclaim rate: licenses reclaimed per quarter, and the value that represents.
- Renewals reviewed early: the share reviewed at least ninety days ahead.
- Audit response time: days from notice to a complete, reviewed submission.
- Unmanaged purchases: software bought outside the intake process, per quarter.
Frequently Asked Questions
What is the difference between license management and software asset management?
License management is the contract and compliance part of SAM. SAM is the wider program, including inventory, procurement, usage, cost and lifecycle.
Do we need a tool?
Often yes, once the estate is large enough that spreadsheets stop scaling. But the tool should follow the decisions about data, ownership and rules, not lead them. Our software asset management tool assessment follows that order.
How often should we reconcile?
For major publishers, at least quarterly, plus ahead of every renewal. Products with fast-moving usage, such as cloud and subscription services, benefit from monthly checks.
What triggers a vendor audit?
Vendors audit for many reasons, including contract renewal, a change in ownership, a drop in purchases or a regular cycle. The survey figures above suggest audits are now routine for many organizations, so it is safer to assume one will come.
Where do we start if we have nothing in place?
Pick your top five publishers by spend. Build the entitlement record, write the rule book and produce a position for each. Ninety days is a realistic target where discovery data already exists.
Sources
- The Register, Oracle Java users audited (July 2025), reporting the Dimensional Research survey for the ITAM Forum and Azul
- Future CIO, Software license non-compliance spend
- Flexera, 2026 State of ITAM Report press release
- Flexera, State of ITAM 2026: audit findings
Where to Go From Here
If the examples above sound familiar, the next step is a baseline: where you stand on contracts, data, ownership and renewals, and which publishers carry the most exposure. Our approach is vendor-neutral and built around your own estate. You can read more on the software asset management page.
Start your software license management journey
Begin with the Desqcon online software asset management maturity assessment and see where your license program stands today. Or talk to one of our senior consultants about a deep-dive assessment plan and a strategy shaped around your estate.
