A true up is the annual contract reconciliation process matching paid quantity to deployed quantity. On a Microsoft EA, true ups run on the contract anniversary date and capture net new deployment growth above baseline. The mechanic is asymmetric because deployment below baseline does not refund, so disciplined deployment governance matters.
True Up: An annual contract reconciliation process where the buyer reports actual deployed quantity against the baseline quantity contracted at signing. Net new deployment is paid at unit price at true up time; deployments below baseline are not refunded. Standard on Microsoft Enterprise Agreement, Adobe ETLA, Cisco Enterprise Agreement, and large multi year SaaS contracts with quantity baselines.
True ups exist because vendor sales teams want committed baseline revenue while buyers want flexibility to grow deployment without renegotiation. The mechanic resolves this by setting a baseline at signing, running deployment at any quantity during the year, and paying the difference at the anniversary date if deployment exceeds baseline. The buyer captures flexibility, the vendor captures growth revenue.
The asymmetry is the structural detail buyers most often miss. If deployment falls below baseline during a contract year, the buyer still pays for the baseline. There is no refund or credit for under deployment within term. The asymmetry makes baseline selection at signing a load bearing decision. Buyers who anchor baseline too high lock in spend they do not consume. Buyers who anchor baseline too low manage true up bills that compound across the term.
Our true up cost benchmark covers 218 Microsoft, Adobe, and Cisco EA true ups. Average annual true up bill, deployment governance failures, and the renewal renegotiation playbook.
Three mechanics drive true up outcomes. First, the deployment count is measured at a specific point in time, typically the contract anniversary date. Deployment spikes during the year that resolve before anniversary do not generate true up charges. Second, the unit price on net new deployment is locked at the original contract price, so true up additions get the same discount as baseline quantity rather than a renewal discount. Third, the true up resets the new baseline for the following year, compounding the commitment.
For applied true up management, see the true up cost benchmark, the Microsoft pricing and negotiation hub, and the Adobe pricing and negotiation hub. For the Microsoft EA specifically, the EA definition covers the full contract structure. The glossary hub carries the broader contract vocabulary.
For deployment governance, the software audit defense playbook covers the IT asset management discipline that prevents both true up surprises and audit findings. The software license compliance cost benchmark covers the cross vendor exposure data.
Three patterns drive overpayment at true up. First, shadow IT deployments outside the IT asset management system generate documented deployment counts at true up time without budget visibility. Second, M&A integrations add user populations during the year without renegotiating contract structure, triggering true up bills the acquiring entity did not forecast. Third, departmental deployment growth from product teams adopting SaaS through self serve buying creates true up exposure that procurement discovers only at anniversary.
The countermeasure is monthly deployment review, not annual true up scramble. Buyers who run quarterly deployment reviews against contract baselines typically reduce true up surprises by 60 to 80 percent compared to buyers who only reconcile at anniversary.
A true up is the annual reconciliation matching deployed software quantity against the baseline quantity in the contract. The buyer pays the unit price on net new deployment above baseline at the contract anniversary date. Deployments below baseline are not refunded.
True ups run on the contract anniversary date each year. For a 36 month Microsoft EA signed in March, the true up dates are the March anniversaries of years 1 and 2, with the year 3 reconciliation rolled into the renewal negotiation.
Microsoft Enterprise Agreement, Adobe ETLA, Cisco Enterprise Agreement, Autodesk multi year, and most large enterprise SaaS contracts with quantity baselines include true up language. The mechanic is most common on per user and per device licensing models.
True downs that refund or credit for deployment below baseline are rare. Microsoft EA does not offer true downs within term. Adobe ETLA offers limited true down at renewal. The general principle is that baseline commitment is firm, and over deployment is the only adjustment vector during the term.
Monthly deployment review against contract baselines, software asset management tooling with vendor reconciliation, M&A integration playbooks that update license counts during diligence, and procurement involvement in any product team SaaS purchase prevent the typical true up surprise. Quarterly governance is the minimum cadence; monthly is the standard for high spend accounts.
Send us the proposal or renewal. We return discount, term, and unit price intelligence in 48 hours.