An East Coast bank opened its annual Microsoft true up to a bill far above forecast. A reconciliation before submission turned a surprise charge into a controlled, defensible count.
An East Coast bank opened its annual Microsoft true up to a bill far larger than expected. The number was real, but it was not right. A reconciliation before submission turned a surprise charge into a controlled, defensible count.
This client was a regional bank on the East Coast with a single large Enterprise Agreement. Growth had been steady, and the licensing baseline had not kept pace.
The annual true up arrived as a routine task. The invoice forecast did not match the number the team had in mind, and the gap was large enough to escalate.
The true up counts net new usage above the baseline. Nobody had been tracking what changed during the year, so every added seat was in scope.
The mechanics are well documented. The annual reconciliation reports usage added above the committed baseline, as described in the Microsoft Enterprise Agreement structure.
The true up was nobody's job until the invoice landed. Without a named owner, the user count was never reconciled against reality before submission.
The team treated the true up as a reconciliation, not a payment. They had a short window before the deadline and used it to clean the count.
Each license was checked against an active, entitled user. Microsoft sets out how seats are assigned and reassigned in the Microsoft Product Terms, and the team used those rules to reclaim what was idle.
What the reconciliation removed from the count
| Category | Status before | Action taken |
|---|---|---|
| Leaver accounts | Still licensed | Deprovisioned and removed |
| Duplicate identities | Counted twice | Merged to one seat |
| Idle project seats | Provisioned | Reclaimed and reassigned |
| Genuine net new | Unverified | Confirmed and reported |
A clean leaver list and a verified active user count let the bank report a number it could stand behind, aligned to the assignment rules in the Microsoft licensing guidance. The true up stopped being a guess.
The common advice is to treat the true up as an administrative submission and simply pay what the count shows. We disagree. In the true ups we reviewed, the reported count was inflated by stale and leaver seats more often than not, so paying the shown number meant overpaying by 8 to 18 percent. The buyer side move is to reconcile before you submit. Reclaim idle and leaver licenses, correct the user count, and resolve duplicates first. The true up is not a deadline to meet with any number. It is a measurement you control.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
A true up is not a tax you pay on growth. It is a count you report, and the number you can defend is almost always lower than the number you are handed.
The reported true up came in materially below the first forecast. The reduction was the difference between the inflated count and the verified one.
Microsoft sets out reporting expectations across its Microsoft 365 enterprise documentation, and the bank built its routine to meet them with verified data.
A Microsoft EA true up is the annual reconciliation where you report and pay for the licenses added above your baseline during the year. It is a count of net new usage, billed once a year against the agreement.
Headcount and device growth had outrun the reported baseline, and nobody had tracked leavers or reassigned seats. The true up swept up every added license, including ones that belonged to staff who had already left.
Yes. Reclaiming idle and leaver seats, reassigning licenses, and correcting the user count before submission all lower the reported number. The reconciliation, done early, is where the saving sits, not in the paperwork.
It is very common. Counts get padded by stale accounts, duplicate identities, and seats left active after departures. Without a clean reconciliation, the easy path is to report a number that is higher than real usage.
Start at least 60 to 90 days before the true up date. That window gives time to reclaim seats, fix the user count, and resolve disputes over what counts, rather than rushing a number to meet the deadline.
It can. A true up that quietly ratchets the baseline upward raises the floor for your next renewal. Controlling the reported count protects both the immediate bill and the starting point of the renewal that follows.
Active user counts, device assignments, and a clean leaver list matter most. The ability to show who is genuinely entitled, and who is not, is what lets you defend a lower number with confidence.
A named owner across IT asset management and procurement should own it. When the true up is nobody's job until the invoice arrives, the count is never reconciled and the bill is always higher than it needs to be.
Microsoft renewal moves, the EA framework, the M365 SKU framework, the Copilot framework, and the buyer side moves across the full Microsoft estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
