So what is true up? True up is the annual reconciliation on a Microsoft Enterprise Agreement where a company counts the licenses and users it added during the year and pays for them. The Enterprise Agreement is built to let you deploy software first and settle up once a year, which is convenient for fast moving organizations. The catch for a buyer is that true up only ever counts growth. It adds the new seats but never removes the ones that fell out of use, so left unmanaged it quietly inflates Microsoft 365 spend year after year.
For a finance or IT leader, true up is one of the clearest examples of how a contract mechanic, not a bad decision, drives overspend. Understanding it is the first step to controlling it.
What is true up and how does it work?
At the start of an Enterprise Agreement, the company sets a baseline count of qualified users, devices, and licenses. Through the year, as people join and as teams add products, the deployed count grows above that baseline. At the annual true up date, the company reports that increase and Microsoft invoices for it, usually at the pricing agreed in the agreement.
The mechanic is one directional by design. You can add during the year and pay at true up, but you cannot hand seats back mid term. The order count only moves up until the agreement reaches renewal. That single rule is why true up matters so much to spend control, and it sits inside the wider mechanics of the Microsoft Enterprise Agreement.
True up versus true forward
Buyers often meet a second term, true forward, and confuse the two. True up reconciles added licenses each year and bills for them under the current agreement. True forward, used on newer agreement structures, defers payment for added subscription licenses until the next renewal rather than billing every year. Both exist to settle growth that happened mid term, but the timing differs: true up pays annually, true forward pays at renewal.
Source: Microsoft Enterprise Agreement and Microsoft Customer Agreement program terms, as of June 2026. Program mechanics change, so confirm the current terms in your own agreement.
Why true up inflates Microsoft 365 spend
The problem is the asymmetry. True up captures every seat you added but ignores every seat that became dead weight. Someone leaves, their license is never reclaimed, and you keep paying for it. A team gets moved to a premium tier for a project that ends, and the tier stays. None of that is corrected at true up, because true up only adds. The result is that the count you carry grows faster than the headcount that justifies it, a pattern explored further in Microsoft 365 cost optimization.
How to control true up costs
Controlling true up is a discipline of two timings. Through the year, track active users against assigned licenses and reclaim seats as people leave, so the growth you report at true up is genuine and not padded with seats nobody uses. Then save the deeper work for renewal, when reductions are actually allowed. That is the only point where you can drop the unused seats and over specified tiers that true up will never remove, which is why disciplined SaaS license right sizing before renewal is where the real savings land.
The order is what makes the difference. Right size first so the renewal baseline is lean, then let true up only ever report real growth on top of an honest starting point. Done well, true up becomes a fair reflection of how the company actually grew, rather than a ratchet that only turns one way.