A true up is reported, but the terms around it are negotiable. Here is where the leverage sits and how a buyer side approach lowers what you actually pay.
Most teams treat a true up as a calculation. They count the growth, accept the number, and pay. The count is only part of the outcome. The price you pay, the products you commit to, and the terms that carry into the next year are all open, and the moment to shape them is before you submit, not after.
A true up is your own report of growth, which means the inputs are yours to get right and the commercial wrapper is yours to question. The number of users and devices is a matter of accuracy. The price applied, the product mix you commit to, and the way the true up sits against an upcoming renewal are matters of negotiation. The leverage is real because the true up lands inside an ongoing relationship that Microsoft wants to renew, and that relationship is the table you are negotiating at.
The count is accuracy. The price, the product mix, and the renewal alignment are negotiation. Decide all three before you submit, because once the report is in, the leverage is gone.
Negotiation built on a wrong count fails. Before any commercial conversation, reconcile your reported growth against primary records so that you are not paying for dormant accounts, double counted users, or assignments that no longer reflect real use. An accurate count does two things. It removes spend you should never have committed, and it gives you a clean position to negotiate from, because you can defend every number you bring. Knowing your data sources is what makes the count defensible rather than cautious.
The figures are indicative and show how the same growth produces different outcomes depending on preparation.
| Approach | What is counted | Effect on spend |
|---|---|---|
| Submit as drafted | Everything assigned, at list mix | Highest |
| Accuracy only | Real users, dormant accounts removed | Lower |
| Accuracy plus negotiation | Real users, right sized mix, renewal aligned | Lowest |
The distance between the first row and the last is the value of treating the true up as a negotiation rather than a calculation. The figures are indicative and show the shape of the outcome, not real client data.
Negotiating well and staying defensible are the same discipline. A true up that is accurate and well evidenced does not just cost less. It also removes the anomaly that draws verification. In 2026 Microsoft uses anomaly detection across licensing and telemetry to select audit targets, and an irregular or catching up true up is exactly the kind of signal that raises a risk score. Reporting a clean, defended number is both the cheaper outcome and the safer one. Treating the true up as an audit, by contrast, leads to overcounting, and overcounting is paying a penalty you were never owed.
A true up outcome is decided before submission, not after. The pillar on the Microsoft audit survival guide sets out how the verification tracks connect to your annual commitments, and the related articles below cover the difference between a true up and an audit and the specific levers that work. Book a strategy call and we will scope the negotiation with you before the deadline sets the terms for you.
If you want a second set of eyes first, we challenge inflated counts through our EA true up defense work.
Book a strategy call and we will scope the true up negotiation with you. Fixed Fee from $18,000 or Gainshare, both backed by our guarantee.
Book a Strategy CallWeekly intelligence on Microsoft and SPLA audit moves and the buyer side defenses that work.