The annual true-up is where a well-negotiated agreement quietly leaks money. Software license true-up best practices exist because the true-up is the one moment each year when the vendor, not the customer, sets the count — and an unprepared customer pays for every licence the reseller decides was deployed, at whatever price the contract permits. The discipline is not complicated, but it is rarely run well: customers who controlled their own deployment count paid 15–30% less at true-up than those who let the reseller run the numbers. This guide sets out the process that captures that difference, building on our contract negotiation strategy master guide.
What a True-Up Actually Is
A true-up reconciles the licences you have deployed during the year against the baseline you committed to, and charges you for the difference. In a Microsoft Enterprise Agreement it is an annual obligation; equivalent mechanisms exist across most enterprise agreements under different names. The structural problem is that the true-up counts up but rarely down: you pay for additions, but most agreements give no automatic credit for licences you stopped using. That asymmetry is deliberate, and it is why a passive true-up almost always overstates what you owe — a pattern we catalogue among the contract red flags worth challenging before signature.
Run a Continuous Count, Not an Annual Scramble
The single most effective practice is to treat every quarter as a mini true-up rather than waiting for the annual deadline. Reconcile entitlement against actual deployment monthly or quarterly, so discrepancies surface while they are small and correctable. Pair this with disciplined reclamation: when an employee leaves or a project ends, free the licence immediately into a redeployment pool rather than leaving it active and billable. Organisations that run this rhythm walk into the true-up with their own defensible number already in hand — the same continuous discipline that underpins a software licence compliance program.
Without your own data, you are at the mercy of the vendor's interpretation of your usage. The true-up is not won in the month it is due — it is won by the quarterly reconciliation that gives you a number to defend.
Documentation Is the Leverage
The ability to challenge a true-up depends entirely on the records you can produce. Maintain accurate documentation of entitlements, activations and reassignments throughout the year, because the moment you cannot evidence your own position, the vendor's count becomes the default. Failing to document reassignments is the most common and most expensive omission: a licence reassigned from a departed user to a new one looks, in the absence of records, like a net addition you must pay for. The remedy is a single source of truth maintained continuously, the same artefact that anchors an accurate total cost of ownership model.
| True-up practice | Effect |
|---|---|
| Quarterly reconciliation | Discrepancies caught small; defensible count ready |
| Immediate licence reclamation | Removes phantom additions before they are billed |
| Documented reassignments | Prevents reassignments being counted as new licences |
| Pre-negotiated add price | Caps mid-term additions at the original discounted rate |
| Customer-run deployment count | 15–30% lower true-up cost than reseller-run counts |
Negotiate the True-Up Terms in Advance
The most powerful true-up practice happens at signature, not at reconciliation. Negotiate, into the original agreement, that any licences added via true-up will be priced at the same discounted rate as your initial purchase — not at a higher mid-term rate — and put a ceiling on how much mid-term additions can cost. Without this, vendors are free to price additions above your negotiated baseline, eroding the discount you worked for. These protections turn the true-up from an open-ended liability into a capped, predictable line, and they are exactly the kind of forward terms set out in our work on vendor negotiation leverage. For the Microsoft-specific mechanics, the Microsoft vendor hub and our guide to the Microsoft EA true-up go deeper on EA timing and SKU traps.
True-Up vs True-Down: Reclaim the Asymmetry
Because most agreements count additions but not reductions, the only way to recover value from licences you no longer use is to engineer a true-down opportunity — and that has to be planned, not hoped for. In a Microsoft EA the practical lever is the anniversary and renewal point, where the committed baseline can be reset downward if you have the utilisation data to justify it. The asymmetry means a reduction realised six months too late is simply lost, so the reclamation pool and the renewal calendar have to work together: identify the licences to shed, document the drop in usage, and time the reduction to the contractual point where it actually counts. Treated this way, true-down planning routinely recovers 10–20% of an inflated baseline that would otherwise renew at full commitment.
Run the True-Up as a Project
When the true-up does fall due, treat it as a project with a timeline, not a form to file. Begin formal data gathering and reconciliation at least one to two months before the report is due, validate the vendor's deployment data against your own, and challenge any line you cannot independently confirm. The deadline is the vendor's pressure point, not yours — a report assembled under time pressure is a report that overstates. Benchmark the resulting additions against market rates, the discipline in our guide to enterprise software price benchmarking, so you are confirming both the count and the price. To prepare for an upcoming true-up or contest one already in progress, request a confidential briefing, and structure the annual cycle using our CIO Contract Governance framework.