HomeMicrosoft HubEA True Up
Microsoft  |  EA True Up Buyer Guide 2026

Clean reconciliation cut the true up invoice 10 to 25 percent

The true up bill is a count, and in most estates nobody audits the count until Microsoft states it. Charges run from first use rather than the order date, the base can never go down at a true up, and the 10 to 25 percent that reconciliation recovers is simply the difference between Microsoft's count and a clean one.

Prepared by Redress Compliance · August 15, 2026 · Microsoft advisory. EA true up and renewal engagements, 2024 to 2026.

Executive summary

Clean reconciliation typically trims the true up invoice by 10 to 25 percent. Double counted users, departed employees still assigned seats, test accounts, and misclassified licenses inflate the raw count, and every one of them is correctable before the anniversary.

Charges run from first use, not from the true up order. A license activated in month two carries most of a year of charges at the anniversary, which makes deployment discipline during the year part of the bill.

The base never goes down at a true up. The annual event only adds licenses above the baseline, so a seat that slips into the count is not a one year cost, it is a permanent addition until the renewal resets it.

Per user security add ons are the fastest growing line on recent true ups, assigned broadly during the year without the usage review that would justify each seat, then settled at the anniversary as if the assignment were the need.

Count early. A reconciliation run a quarter before the anniversary corrects the count while it is still deployment hygiene; the same corrections after Microsoft states the count are a negotiation conducted uphill.

10 to 25%
What clean reconciliation typically trims from the true up invoice.
First use
When charges start: activation, not the true up order date.
1 way
The true up ratchet: additions only, reductions wait for the renewal.
1 quarter
The head start the reconciliation needs before the anniversary.
1.

How the count is built

ElementHow it worksBuyer note
The annual true upSettles every license added during the year at the anniversaryAdditions only; the base cannot go down
The first use dateCharges run from activation, not the orderA month two seat carries most of a year at settlement
The count sourceDeployment and assignment during the yearAssignment is the meter, whether or not anyone uses the seat
Security add onsPer user lines settled like any otherThe fastest growing true up line; audit assignment against alerts
The shelfware floorAssigned but unused seats bill and then renewEvery uncorrected seat becomes renewal baseline
The renewalThe only moment the base resets downwardTrue up discipline is renewal preparation

The count Microsoft states is assembled from your own systems, on Microsoft's reading. Departed employees still assigned, contractors double counted across tenants, test and service accounts holding full seats, and users placed in heavier SKUs than their role requires all survive into the raw count, because no one is paid to remove them. The 10 to 25 percent is not a discount; it is the error rate of an unaudited count.

Watch the briefing · 7:05Microsoft EA Negotiation: Five ThingsThe five levers that move an Enterprise Agreement: the baseline, the SKU mix, the true up treatment, the term timing, and the price protection that survives the next price list.Open the full page, with the transcript →
2.

The reconciliation that cuts the bill

Free download

The Microsoft EA renewal playbook

Microsoft renewal moves, the EA framework, the M365 SKU framework, the Copilot framework, and the buyer side moves across the estate.

Get the playbook →
3.

A meter read once a year

Most consumption billing reads its meter continuously, and buyers respond continuously: cloud spend gets dashboards, alerts, and weekly reviews. The EA true up is stranger. It is a consumption meter read once a year, and the reading is taken by the party being paid.

That design produces a predictable behavior. For eleven months, license assignment is an operational act with no visible price: a manager requests, IT provisions, the ticket closes. At the anniversary, all of it converts into invoice at once, backdated to first use, and the organization discovers what its own helpdesk decided the estate should cost.

The one way ratchet turns that discovery into permanence. Because a true up only adds, every seat that slips into the count joins the baseline, bills forward, and arrives at the renewal as Microsoft's opening position. Multiply the pattern by the per user security add ons, the fastest growing line on recent true ups, and the year's unexamined assignments compound into the next agreement's floor.

Seen this way, the 10 to 25 percent that reconciliation recovers is not clever negotiation. It is the measured error of a count nobody audited: leavers still assigned, contractors duplicated, test accounts holding seats, roles over-SKUed. Microsoft did not invent those seats; your systems did, and Microsoft merely counted what it found.

The discipline that follows is unglamorous and decisive. Read your own meter quarterly, correct assignment while it is still hygiene, check the first use dates, and file your count before the anniversary. An estate that does this converts the true up from an annual surprise into a confirmation, and arrives at the renewal, the one day the base can actually go down, holding the accurate count that renewal leverage is built from.

The renewal side of the ratchet sits in the EA renewals guide, the agreement mechanics in the Microsoft EA pillar, and the wider position in the Microsoft practice.

Watch the briefing · 4:02The Microsoft EA Preparation Playbook: The Work That Wins the RenewalFive workstreams in order: the license position, the usage file, the demand forecast, the benchmark and alternatives files, and the ask list drafted first.
Try Vera AI · free 30 day trial
Vera reconciles your assignment data against the identity system, flags the first use date exposure, and models the true up before Microsoft states it.
  • Percentile standing for your exact deal size and industry, from real closed transactions
  • Scenario simulation before the call: test alternative terms and see the financial impact of each
  • A negotiation playbook, talking points, and a two page executive brief on day one
Start the free Vera AI trial →30 days free · no credit card · cancel anytime
4.

What the true up engagements showed, 2024 to 2026

Across the EA true up and renewal engagements we advised, the corrections clustered in the same places every year:

10 to 25%
Trimmed by reconciliation

The share of the true up invoice removed by cleaning the count before the anniversary: leavers, duplicates, test accounts, misclassified seats.

Add ons
The fastest growing line

Per user security add ons assigned broadly during the year and settled at the anniversary as if assignment were need.

Three patterns recurred. Counts accepted as stated because the anniversary arrived before anyone reconciled. First use dates unexamined, so early activations carried close to a full year of charges. And add on lines growing unwatched because assignment had no price until settlement day.

The buyer side move is to read your own meter first. The wider library sits in the Microsoft practice.

5.

Your first five moves

  1. Set the reconciliation date one quarter before the anniversary and make it a standing calendar event, not a scramble.
  2. Pull assignment against the identity system: leavers, duplicates, service and test accounts, corrected in deployment before they become invoice lines.
  3. Verify first use dates on the year's additions, because the charge runs from activation and misdated seats add silent months.
  4. Audit the security add on assignment against usage, the fastest growing line on recent true ups and the least reviewed.
  5. File your count first and keep the workpapers, since the same reconciliation becomes your renewal baseline. The Microsoft practice runs the count with you.
6.

Frequently asked questions

What is a Microsoft EA true up and when does it happen?

The annual reconciliation at each Enterprise Agreement anniversary that settles every license added during the year. It only adds licenses above the baseline; quantities can never go down at a true up, which is why reductions wait for the renewal.

How does Microsoft count licenses for the true up?

From deployment and assignment during the year, and charges run from when a license was first used, not from when you place the true up order. That first use date is the trap: a seat activated in month two carries most of a year of charges at the anniversary.

Can you reduce licenses at a Microsoft true up?

No. A true up only adds licenses above the baseline, and the base cannot go down until the renewal. That one way ratchet is why the count you allow to form during the year, and the reconciliation you run before the anniversary, decide the bill.

How much can reconciliation cut a true up invoice?

Clean reconciliation typically trims the true up invoice by 10 to 25 percent, by removing double counted users, departed employees still assigned licenses, test accounts, and misclassified seats before Microsoft states the count.

What are the most expensive Microsoft true up traps?

The first use date trap, where charges run from activation rather than the order; the shelfware floor, where seats assigned but unused still bill and then renew; and per user security add ons, the fastest growing line on recent true ups, often assigned broadly without an alert or usage review.

When should true up preparation start?

Count early: run your own reconciliation at least a quarter before the anniversary, so gaps can be cleaned while they are still deployment hygiene rather than invoice lines. A count corrected after Microsoft states it is a negotiation; a count corrected before is just accuracy.

How does the true up relate to the EA renewal?

The true up ratchets the base upward each year, and the renewal is the only moment the base can reset downward. Whatever count survives your last true up becomes Microsoft's opening position at renewal, which is why true up discipline is renewal preparation.

Watch the briefingResearch briefing · 4:02

The Microsoft EA Preparation Playbook: The Work That Wins the Renewal

Five workstreams in order: the license position, the usage file, the demand forecast, the benchmark and alternatives files, and the ask list drafted before Microsoft drafts theirs, with the executives aligned before the first meeting.

© 2026 Redress Compliance · Independent, buyer sideredresscompliance.com
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent
Microsoft Renewal

The full Microsoft EA renewal playbook from the advisory practice.

Microsoft renewal moves, the EA framework, the M365 SKU framework, the Copilot framework, and the buyer side moves across the estate.

Gated with a work email on the download page. No sales follow up you did not ask for.

Get the White Paper →
Independent, buyer side. We never share your details with vendors.
Put your own numbers on this with the Microsoft licence optimisation calculator.
Open the Calculator → Microsoft Practice →
Editorial boardroom interior

The advisor your vendors do not want.

500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.

Stay ahead of Microsoft pricing and contract moves.

One buyer side briefing a week. Renewal signals, discount bands, and the levers that work. No vendor spin.