Every software license position rests on one question: what are we allowed to use? The answer is your entitlements. Get them wrong and every report built on top of them is wrong too. You will either pay for licenses you already own or, worse, believe you are covered when you are not.
This article explains what an entitlement is, what an entitlement record should contain, where entitlements hide in a typical organization's paperwork, and how to keep them accurate over time.
What an entitlement is
A software entitlement is the set of rights a contract grants you to use a product. It is not the same as an installation, an assignment or an invoice:
- An installation or assignment is what you have deployed.
- An invoice is what you paid.
- An entitlement is what you are allowed to use, under which conditions.
The three should line up. When they do not, you have either waste (more entitlements than use) or exposure (more use than entitlements). Comparing them product by product is how you build an effective license position.
The eight fields every entitlement record needs
A useful entitlement record answers eight questions. If any of them is missing, decisions made on top of it are guesses.
| Field | Question it answers | Example |
|---|---|---|
| Product and edition | Exactly what was licensed? | Microsoft 365 E3 |
| Quantity | How many units? | 2,500 |
| License metric | What does one unit cover? | Per user |
| Term | From when to when? | Jan 2026 – Dec 2028 |
| Price and currency | What does each unit cost? | $36 per user per month |
| Renewal and notice | When does it renew, and by when must we act? | Auto-renews; 90-day notice |
| Usage rights and restrictions | What is allowed, and where? | Commercial use; no hosting for third parties |
| Proof of entitlement | Which document proves it? | Order form #4471, amendment 2 |
The license metric deserves special attention. Two contracts for "500 licenses" can mean very different things if one counts users and the other counts devices or processor cores. Our guide to software license types explains the common metrics.
Where entitlements hide
In most organizations, the full picture of an entitlement is spread across several documents, systems and people. Rebuilding it means collecting from all of them.
Common places entitlements go missing:
Licenses added mid-term, never filed with the original agreement.
Show current subscriptions, but not the contractual terms behind them.
The order is with a partner, and the vendor's own records may differ.
Change over time and can alter what a license allows.
Click-through terms and no central record at all.
Contracts that came with an acquisition and were never transferred or recorded.
When you rebuild entitlements for the first time, expect the record to thin out at each step. The gap between "contracts in scope" and "reconciled to invoices" is the work.
Proof of entitlement
Proof of entitlement is the evidence that you own what you claim to own. In an audit, licenses you cannot prove are often treated as licenses you do not have. Good proof usually means the signed order or agreement together with evidence of payment, and for some publishers, records from their licensing portal.
Keep proof linked to each entitlement record, not in a separate folder that only one person knows about. When a contract owner leaves, the proof should not leave with them.
Keeping entitlements accurate
Entitlements change constantly: renewals, true-ups, upgrades, mergers and cancellations all alter what you own. Four habits keep the records right:
Four habits that keep entitlements accurate
How MI One helps
Frequently asked questions
Is a license key proof of entitlement?
Usually not on its own. A key shows that software was activated, not what the contract allows. Keep the order and payment records.
What happens to entitlements when we renew?
The renewal may change quantities, editions, prices or terms. Update the record and keep the history, so you can show what you owned at any point in time.
Who should own entitlement records?
A SAM manager or the IT asset team, with procurement responsible for sending every new contract and amendment into the process.
Sources
- ISO/IEC 19770 family of IT asset management standards; Part 3 defines an entitlement schema and common entitlement terms. https://en.wikipedia.org/wiki/ISO/IEC_19770