True-up

A true-up is a contractual reconciliation of additional licensed quantities over a defined period. Read it with the agreement’s permitted use, counting units, covered products, pricing, and reporting deadlines. FinOps Licensing & SaaS notes that some contracts permit increases without corresponding decreases. A true-down is a separate right whose timing and eligibility must be checked; neither direction follows from the word subscription alone.

Permitted use and payment are different questions

Some agreements permit eligible additions before a later reconciliation order. Others require an order or reservation before use. A later payment does not by itself authorize an uncovered product, deployment, or period. Microsoft’s Enterprise Agreement guidance describes annual reconciliation for eligible additions and usage, with an order or update statement before the enrollment anniversary. Its Enterprise Subscription Enrollment instead uses an Annual Order that can allow quantity reductions. These are examples of different terms, not rules for every supplier.

Keep the history the contract counts

Entitlements, deployed installations, assigned seats, active users, and concurrent users can produce different numbers. Retain the evidence the agreement requires across its measurement period. A quiet day at quarter-end does not establish that earlier use was covered. Reassignment rights, minimum quantities, eligible products, secondary meters, and renewal prices can affect what is payable.

Consider an invented one-year subscription: 100 seats cost 10 each per month, and the contract permits 20 additional seats from the start of month 7, priced for the remaining six months. The true-up adds 20 × 10 × 6 = 1,200 to the original 12,000, for 13,200. If only 80 people remain active from month 10 but the committed quantity cannot decrease until renewal, that decline does not refund the final three months. A simple year-end active-user count would miss the obligation. Different proration, counting, or reduction terms would require a different calculation.

Monitor use at a cadence suited to its variability and retain the necessary history. Separately calendar the contractual submission, renewal, and reduction deadlines. Quarterly management review is one option, not a universal compliance interval. Have IT asset management, procurement, legal, finance, and engineering resolve discrepancies before placing an order or claiming a saving.

In the fictional logistics case, an in-term seat floor prevents an immediate saving after staff numbers fall; a negotiated anniversary reduction changes future payments. The Supplier Changed Its Roadmap and Ours Changed With It places that choice among support, change, and exit terms. A commitment discount likewise requires comparing payment obligations with the same usage under an alternative, rather than reading a discount as a saving.

References:

• FinOps Foundation, Licensing & SaaS (CC BY 4.0)
• Microsoft, Enterprise Agreement Licensing Guidance