Negotiating down a SaaS true up begins with a mindset: the true up figure the vendor sends is an opening position, not a settled invoice. A true up reconciles the licences you actually consumed against the licences you committed to, and on agreements like a Microsoft Enterprise Agreement it is a defined mechanic that runs on a schedule. The bill counts the seats you added during the term. What it almost never does is account for the seats that have since gone inactive, the roles that changed, or the duplication you could remove. That difference is the room to negotiate.
As an independent, buyer side advisor with no vendor relationship and no commission, we approach a true up as a number to be tested rather than paid. This guide feeds the wider SaaS renewal negotiation work and the broader digital workplace cost optimization effort, because a true up is a moment where overspend is easy to lock in.
What is a SaaS true up?
A true up is the reconciliation between what you committed to buy and what you actually used. If you added users or upgraded plans during the term, the true up captures that growth and bills for it. On a Microsoft Enterprise Agreement, the true up is an annual process for counting additional licences consumed since the last count (source: microsoft.com licensing documentation, as of June 2026). The mechanic itself is reasonable. The problem is that it is usually run in the vendor's favour, capturing every addition while ignoring every reduction you are entitled to make.
Microsoft Enterprise Agreement true up mechanics are from microsoft.com licensing documentation, as of June 2026. Licensing programs and terms change, and your specific agreement governs, so confirm against your contract and a current quote.
Why is the true up bill often overstated?
It counts additions but not removals
The headline reason. A true up is built to capture growth. Seats that became inactive, people who left, and licences assigned to wound down projects are not netted off unless you raise them. Left unchallenged, you true up on a peak that no longer reflects reality.
It rolls plan tiers forward
Upgrades made mid term are captured, but the question of whether those richer tiers are still needed is not asked. Some users trued up to a premium plan could sit on a lower one, which is the same logic behind right sizing Microsoft 365 plans.
It ignores overlap you could retire
If some of the licences being trued up duplicate capability you already own elsewhere, the true up is paying to grow a tool you should be shrinking.
Negotiating down a SaaS true up: the levers
Bring your own count. Pull current usage and active user data and compare it to the seats the true up bills for. Identify inactive seats, departed users, and over provisioned tiers. Net the genuine reductions against the additions so the number reflects what you actually consume now, not the high water mark. Then time the conversation: a true up handled alongside a renewal gives you more leverage than one settled in isolation, which is why reading a SaaS renewal quote carefully matters here too.
Where does the evidence come from?
From your own systems. Admin console reports, active user data, and a current licence inventory give you the counter number. The work of building that inventory once pays back every true up and every renewal after, and it underpins the SaaS renewal business case for finance. Without it you are negotiating against the vendor's figures with nothing of your own.
Where to start
Start by refusing to treat the true up as a settled bill, then build the counter case. Pull active usage, find the inactive and over provisioned seats, and present a number grounded in current consumption. The vendor counts additions because that is its job. Counting the reductions is yours, and it is where the saving comes from.