A software license entitlement is the record of what you are allowed to use: the product, the quantity, the metric it is counted by, and the dates and terms that apply to it. The license is the right the publisher grants; the entitlement is your proof that you hold it. In an audit, only the proof counts.
This guide explains how an entitlement differs from a license and from an entitlement certificate, what to record for each one, where to find the evidence, and the gaps we find most often when we build entitlement registers for clients. Entitlements are one half of every effective license position; the other half is what you have deployed.
In short
- An entitlement states what you may use: the product and edition, the metric, the quantity, the term and any restriction on how it is used.
- The evidence is the contract, the ordering document and the support renewal, not the invoice on its own.
- Entitlements change with every purchase, renewal, upgrade, merger and divestment, so the register has to change with them.
- The two gaps we meet most are licenses bought by an acquired company and licenses that dropped out of an old support contract.
Software license vs entitlement: what is the difference?
| Term | What it is | Where you find it |
|---|---|---|
| License | The legal right to use software, on the terms of the publisher’s agreement | The license agreement or master terms |
| Entitlement | What that right covers for you: product, metric, quantity, term and restrictions | Ordering documents, contracts, support renewals and the publisher’s own records |
| Entitlement certificate | A document from the publisher or reseller confirming an entitlement | Sent with the order or downloaded from the publisher’s portal |
| Deployment | What is installed and in use | Discovery tools, scripts and cloud consoles |
Put simply, the license sets the rules, the entitlement says how much you bought under them, and deployment shows how much you are using. Compliance is the comparison between the last two. An IT asset register records what is installed, while the entitlement record shows what you may use, and our guide to ITAM vs SAM explains why the two need different owners.
What is an entitlement certificate?
It is the publisher’s confirmation of what you bought, but each publisher keeps that record in its own way, and the certificate is rarely the whole story. For Oracle, each purchase is set out in an ordering document, and your licenses and support sit under a Customer Support Identifier (CSI). For IBM, your Passport Advantage agreement (IPAA or IPAEA) and each product’s License Information document set the terms.
Keep the certificate, the ordering document and the agreement together. The agreement and the order carry the terms that decide how a license may be used. An Oracle Application Specific Full Use license, for example, gives full use of the program, but only with the one application it was sold with. A certificate that shows only a product and a quantity does not tell you that.
What should an entitlement register record?
One line for each entitlement, recorded in the publisher’s own metric and never converted into another. These are the fields we keep for clients:
| Field | Example |
|---|---|
| Publisher, product and edition | Oracle Database Enterprise Edition |
| License metric | Processor or Named User Plus for Oracle; processor value units for IBM sub-capacity |
| Quantity | The number bought, as written in the order |
| License type and term | Perpetual, term or subscription, with start and end dates |
| Support status | Under support or not, with the renewal date and the support contract it sits under |
| Contract references | Agreement number, ordering document and CSI or customer number |
| Licensed company | The legal entity named on the contract |
| Restrictions | Restricted-use or application-specific rights, territory and virtualization terms |
| Evidence | Where the signed contract, order and renewal are stored |
How do you build an entitlement register?
- Collect every contract, ordering document, certificate and support renewal for the publisher, from every company in the group.
- Get the publisher’s own record of your purchases and support, and compare it with your documents. Differences are far easier to settle before an audit than during one.
- Record each entitlement with the fields above, in the publisher’s own metric.
- Link each entitlement to the support contract or subscription it renews under, so a lapse or a change in terms shows up.
- Update the register with every purchase, renewal, upgrade, merger and divestment, and reconcile it with what is deployed to produce your effective license position.
Collecting entitlements is the second step in the software asset management process, and keeping this register current is part of the work our SAM managed services do all year for clients, across Oracle, Microsoft, IBM, Broadcom/VMware, Red Hat and the other publishers that carry the most cost and risk. A software asset management policy is what keeps new purchases flowing into it.
Where entitlements go missing
Licenses bought by an acquired company
When companies merge, the licenses one of them bought are often still recorded under its old name, its old contracts and its old customer numbers, and nobody carries them into the group’s register. Entitlements and deployments need to be matched before the companies join, not after the first audit of the combined estate.
Licenses that dropped out of an old support contract
A perpetual license you stopped paying support on is still yours, but it no longer appears on the renewal quote, which is often the only document anyone reads each year. Unless the register keeps it, it disappears from view, and the company either buys it again or cannot prove it owns it. Before you drop support on anything, check the publisher’s terms: with Oracle, removing licenses from support can change what you pay for the rest, as our guide to shelfware explains.
Restricted licenses counted as full use
Application Specific Full Use and embedded licenses cover one application only. Counting them as general-purpose licenses makes the position look better than it is, until the publisher’s auditors count them correctly.
Only the invoice was kept
An invoice proves that you paid. It does not show the metric, the term or the restrictions, and those decide whether you are compliant.
Questions we are asked about software license entitlements
Is an invoice proof of entitlement?
Not on its own. An invoice shows a payment; the ordering document and the agreement show what was licensed, by which metric and on what terms. Keep the invoice, but rely on the order and the contract.
What if we cannot find our entitlement documents?
Ask the publisher, and the reseller you bought through, for their record of your purchases and support, and compare it with what you hold. Do this before an audit begins, because once it starts, every gap in your records becomes part of the findings.
Do SaaS subscriptions have entitlements?
Yes. The order form or subscription agreement states the service, the quantity and the term. Record them in the same register, and check the quantity against the users actually assigned.
How often should the register be updated?
Every time something changes: a purchase, renewal, true-up, upgrade, merger or divestment. Reconcile it with deployment at least once a quarter and before every renewal or audit.
Anil Nahata
Co-founder of Rythium Technologies and its designated partner since 2015. Anil co-leads Rythium’s practice, bringing deep software asset management and commercial negotiation experience across Oracle, Microsoft and the wider publisher landscape.
Before Rythium, Vice President heading the telecom towers infrastructure business at Reliance Communications, and its group Chief Procurement Officer. More than two decades across the telecom, software and financial industries.
See more of our analysis in Google: add Rythium as a preferred source