Microsoft True-Up: How to Avoid Overpaying

How the EA True-Up Works

The Microsoft Enterprise Agreement requires enterprises to report and pay for any product deployments that exceed the quantities committed at the start of the EA term. This annual reconciliation — the "true-up" — takes place on each anniversary of the EA start date and requires the enterprise to submit a deployment report covering all licensed products.

The true-up is structured as a one-way ratchet under standard EA terms: overages (deployments above committed quantities) require immediate payment; underages (committed quantities above actual deployment) do not result in refunds. This asymmetry means that enterprises that commit to more licences than they deploy are permanently over-committed until the EA renewal.

This article is part of our Microsoft Enterprise Agreement Negotiation: Definitive Guide. For the full EA commercial framework, start there.

Where True-Up Overpayment Occurs

True-up overpayment typically arises from four sources:

1. Inaccurate Deployment Reporting

True-up reports are typically prepared by IT teams under time pressure, using inadequate tooling. Inconsistent definitions of "licensed users" — particularly around guest accounts, service accounts, shared mailboxes, and external contractors — consistently produce deployment counts above the contractually required count. A pre-true-up deployment audit with clear definitions of licensable users typically reduces reported true-up quantities by 8–15%.

2. Overage Pricing at List Rate

Under standard EA terms, true-up overages are priced at the EA commitment rate — which should reflect the negotiated EA discount. However, Microsoft's true-up invoicing process sometimes applies list pricing to overages rather than the discounted EA rate, particularly for products that were not included in the original EA scope. Verifying that true-up overage pricing reflects your negotiated EA discount is a required step in any true-up review.

3. Failure to Apply Licence Reductions

When employees leave the organisation, get reassigned to roles that require a different licence tier, or when systems are decommissioned, the corresponding licence reduction should be reflected in the true-up. In practice, many enterprises accumulate unused licences for months before the true-up period, resulting in payment for licences that should have been removed. A monthly licence reconciliation process — rather than a once-annual review — eliminates this source of overpayment.

4. NCE Subscription Restrictions

Since the introduction of the New Commerce Experience (NCE), enterprise subscriptions for Microsoft 365 and other cloud products are locked for the subscription term — typically annual. This means that seat reductions that would previously have been reflected in the true-up may now be blocked until the NCE subscription anniversary. Understanding the interaction between NCE subscription terms and EA true-up obligations is critical for cost management. See our guide on Microsoft NCE Impact on Costs for the full analysis.

Negotiating True-Up Terms

True-up terms are negotiable at EA signature — most enterprises accept Microsoft's standard terms without challenge. The negotiable elements include:

• Overage pricing rate: Standard EA terms price overages at the EA commitment rate. Negotiate explicit language that confirms the discounted EA rate applies to all overages across all product families included in the EA — not just the core M365 products.
• True-up reporting grace period: Standard EA terms require true-up reports within 30 days of the annual anniversary date. A grace period of 60–90 days is negotiable and provides additional time for accurate deployment counting.
• Definition of licensable users: The EA's definition of which users require an M365 licence is not always explicit. Negotiating clear exclusions for service accounts, shared mailboxes (with usage limits), external contractors below a usage threshold, and temporary staff provides a commercially significant reduction in the reportable user count.
• True-down mechanism: Standard EA terms do not allow seat count reductions below the committed base during the EA term. For organisations with volatile headcount — due to M&A, divestitures, or seasonal workforce changes — negotiating a true-down mechanism (allowing seat reductions under defined circumstances) prevents permanent over-commitment.
• New product addition pricing: When new Microsoft products are added to the EA scope mid-term (outside the original commitment), the pricing applied to those additions is negotiable. Establishing pre-agreed pricing for anticipated additions at EA signature prevents Microsoft from pricing mid-term additions at list rate.

True-Up Management Process

A robust true-up management process eliminates most sources of overpayment before the annual reconciliation. The key steps are:

1. Monthly licence reconciliation: Run automated licence reports monthly to identify unused licences (assigned but inactive for 30+ days), departed employee accounts, and service accounts. Remove or reassign licences promptly rather than accumulating them to the annual true-up.
2. Pre-true-up audit (60 days before anniversary): Conduct a full deployment audit 60 days before the true-up anniversary. Compare actual deployment counts against committed quantities. Identify overages that can be addressed through deprovisioning before the reporting date.
3. User definition review: Apply the contractually defined user exclusions before finalising the report. Shared mailboxes, service accounts, external contractors, and temporary staff should be reviewed against the contractual definition before being included in the reportable count.
4. Price verification: Before approving the true-up invoice, verify that overage quantities are priced at the EA committed rate — not list price — and that any new product additions reflect pre-agreed pricing where applicable.
5. True-up as renewal input: The true-up report provides the most accurate picture of actual Microsoft deployment in the enterprise. Use this data as the foundation for the EA renewal conversation — particularly for identifying over-provisioned product families where the committed base can be reduced at renewal.

True-Up and EA Renewal

The annual true-up is the single most valuable data source for EA renewal preparation. A three-year history of true-up reports reveals patterns in over-provisioning, product family utilisation, and growth rates that Microsoft's account team has and uses in renewal negotiations. Enterprise buyers should analyse this data equally rigorously before entering the renewal conversation.

Products where true-up quantities have consistently been below committed levels for two or more years are candidates for committed base reduction at renewal. Products where true-ups have consistently generated overages indicate growth areas where committed quantity increases — at negotiated rates — may be appropriate. See our full EA renewal guide at Microsoft EA Renewal: 15 Tactics That Work.

Further Reading

• Microsoft Enterprise Agreement Negotiation: Definitive Guide — full EA framework
• Microsoft EA Renewal: 15 Tactics That Work — EA renewal negotiation playbook
• Right-Size Your Microsoft Licence Estate — licence census methodology
• Microsoft NCE Impact on Costs — NCE and true-up interaction
• Microsoft Advisory Service — IT Negotiations' Microsoft engagement capability
• Microsoft EA Negotiation Guide (Free PDF)