Challenging an Inflated True Up

Every year an Enterprise Agreement requires you to report and pay for the licenses you added above your baseline. That is the true up. The mistake organizations make is to treat the figure they are handed as a fixed obligation. A true up is a count, and a count can be wrong. When the demand looks inflated, the right response is not to pay and not to panic, but to verify. This top of funnel article explains why true ups come in high and how to challenge one with evidence.

A true up is not an audit, but the discipline is similar

A true up is a contractual reporting step inside your Enterprise Agreement, where you count the additional licenses deployed during the year and pay for them. It is not a formal audit and it does not run through a third party accounting firm. But the same principle applies: whoever counts carefully controls the number. If the count handed to you is built from assumptions rather than your real deployment, it will almost always favor the vendor.

Why the number tends to come in high

An inflated true up is rarely the result of bad faith. It is the predictable outcome of counting in the simplest, most conservative way. The usual causes are familiar.

• Peak counts instead of true positions, where a temporary spike during the year is treated as a permanent increase.
• Stale assignments included, so accounts for people who have left still register as deployed licenses.
• Tier assumptions, where users are counted at a higher edition than they actually consume.
• Benefits and rights ignored, including downgrade rights, secondary use, and entitlements you already hold that offset part of the count.
• Double counting across overlapping products, where the same user is charged twice through a suite and a standalone license.

What an inflated true up looks like in numbers

The gap between a demanded count and a verified one is often substantial. The figures below are indicative, but they show how each correction moves the total.

These numbers are indicative only, but the shape is real. A third of a true up line can disappear once leavers are removed and tiers are corrected to actual usage.

How to challenge the demand

Challenging a true up is a matter of replacing assumptions with evidence. The sequence is straightforward.

• Rebuild the count from your own deployment data, drawn from the same sources Microsoft can see, including cloud and Microsoft 365 telemetry.
• Strip out stale assignments and accounts that no longer represent real use.
• Right size every tier to actual consumption rather than the edition assigned.
• Apply every right and benefit you hold before agreeing any net figure.
• Present the corrected position with the evidence behind it, so the conversation is about facts rather than the opening demand.

Where a true up can turn into something more

An inflated true up is also a signal worth reading. A demand that is far above your own understanding of your estate can indicate that Microsoft's view of your deployment differs from yours, and that difference is exactly what draws audit attention. Correcting the true up with evidence does double duty: it lowers this year's bill and it closes the gap that could otherwise trigger a formal review later.

Take the playbook with you

Knowing why a true up inflates is the first step. Knowing how to rebuild the count and present it is the work. The Microsoft Audit Survival Guide sets out the full method our analysts use, including the true up corrections that most often move the number.

If you want a second set of eyes first, we challenge inflated counts through our EA true up defense work.