A software true-up reconciles the licenses you deployed against the licenses you own, and an unmanaged true-up bills every excess unit at full list price, commonly adding 15 to 40 percent to the annual contract value. The true-up is not a penalty clause. It is the routine mechanism by which subscription and volume agreements settle growth. The cost problem is not that true-ups exist; it is that buyers arrive at the reconciliation with the vendor's deployment count, no discount on the excess, and no credit for entitlement they paid for and never used. This guide explains what triggers a true-up, why the excess almost always prices badly, and the three contract terms that keep the annual settlement controlled.
What a true-up actually settles
A true-up is the periodic reconciliation between contracted quantity and actual consumption. Under a Microsoft Enterprise Agreement it runs once a year on the anniversary, capturing every license added during the prior twelve months. Under most SaaS agreements it runs at renewal, when the platform reports the peak or current active count and bills the difference against the contracted minimum. The common thread is that the vendor measures, the buyer pays for the gap, and the gap is priced at terms the buyer rarely set in advance.
The reconciliation is structurally tilted toward the vendor for a simple reason: the vendor controls the measurement and the buyer controls almost nothing about how the count is produced. Deployment data comes from the vendor's tooling, the timing favors the vendor's fiscal calendar, and the price applied to the excess is whatever the contract left unspecified. Where the contract is silent, the excess defaults to list. Building an effective license position before the vendor measures is the single most reliable way to change that balance.
What triggers a true-up
True-ups trigger on a schedule, on an event, or on both. Anniversary true-ups are calendar driven and predictable. Renewal true-ups settle accumulated growth at the same moment the renewal price is set, which is why they are the most expensive: the buyer is negotiating quantity and price in the same conversation, from the weakest possible position. Event-driven true-ups follow acquisitions, new module activations, or a crossing of a tiered threshold that resets the unit price.
| Vendor model | True-up cadence | What is counted | Default price on excess |
|---|---|---|---|
| Microsoft Enterprise Agreement | Annual, on anniversary | Net new licenses added in the year | Contract price for that SKU, prorated |
| Salesforce | At renewal (added seats billed immediately) | Activated subscriptions above contract | List, unless ramped pricing was negotiated |
| Adobe VIP / ETLA | Anniversary and renewal | Deployed licenses against pool | Tier price at time of true-up |
| Oracle (ULA certification) | End of ULA term | Certified deployed processors or users | Locks perpetual quantity, no refund for under-use |
| SAP (annual measurement) | Annual system measurement | Named users and engine metrics | List, plus back maintenance on the gap |
The pattern across every model is the same: the excess prices at or near list, and there is no symmetrical mechanism to recover entitlement the buyer paid for and did not use. A true-up moves the bill up. It almost never moves it down unless the buyer negotiated a true-down right in advance, which is the central point of this guide.
Why the excess prices badly
Three things make true-up units more expensive than the units in the original deal. First, the original purchase carried a volume discount that the incremental true-up units frequently do not inherit, so a buyer who negotiated 45 percent off the base contract can find the true-up billed at 10 percent off or at flat list. Second, the timing strips bargaining power: the licenses are already deployed and in production, so the buyer cannot credibly threaten to walk away from units already running the business. Third, the count itself is often inflated by inactive accounts, duplicate identities, and test users that were never cleaned up, a problem covered in reclaiming inactive licenses.
Negotiate the true-up price before you need it: The time to fix the price of incremental units is at the original signature, when the vendor wants the deal, not at the true-up, when the units are already in production. Lock the per-unit price for added quantity at the same discount as the base contract, for the full term, and the annual reconciliation stops being a repricing event.
Build the baseline before the vendor counts
The buyer who arrives at a true-up with an independent count negotiates from evidence. The buyer who arrives with nothing accepts the vendor's number. Building the baseline means reconciling three data sets: contracted entitlement from the order forms, actual deployment from your own discovery tooling, and active usage from the application's own login and activity records. The gap between deployment and active usage is the reclamation opportunity; the gap between entitlement and deployment is the true-up exposure.
In practice the deployed count and the billable count diverge sharply once inactive identities are removed. Terminated employees whose accounts were never deactivated, service accounts double counted as users, and seats provisioned for a project that ended all inflate the vendor's measurement. A disciplined baseline run before the measurement window routinely removes a double-digit percentage of the proposed charge. The discipline is the same one described in our license metric disputes guide: define the unit precisely, then hold the vendor to that definition.
The three terms that control true-up cost
True-up management is mostly won in the contract, not in the reconciliation. Three terms carry most of the protection. A price-hold on incremental units fixes the per-unit cost of true-up quantity at the base discount for the full term, removing the repricing risk. A true-down right lets the buyer reduce the contracted minimum at renewal to match real consumption, converting the reconciliation from a one-way ratchet into a two-way adjustment. A measurement-method clause defines exactly how the count is produced, what tooling is authoritative, and how disputed records are resolved.
| Term | Vendor default | Buyer target | Effect |
|---|---|---|---|
| Incremental unit price | List or reduced discount | Base-contract discount, fixed for term | Removes repricing on growth |
| True-down right | None (one-way ratchet) | Reduce minimum at renewal to actual use | Recovers unused entitlement |
| Measurement method | Vendor tooling, vendor discretion | Named tooling, active-user basis, dispute process | Limits inflated counts |
| True-up timing | Vendor fiscal year-end | Decoupled from renewal pricing | Separates quantity from price talks |
The true-down right is the term vendors resist most and the one that returns the most over a multiyear contract. Without it, a buyer that over-bought in year one carries that excess for the full term and trues up further on top of it. With it, the contract tracks the business. The complete framework for these master terms sits in our software contract negotiation guide, and the renewal-side discipline is covered in price uplift caps.
Run a true-up calendar, not a true-up scramble
The buyers who manage true-ups well treat the reconciliation as a scheduled event with a runway, not a surprise. A working calendar starts the internal baseline ninety days before the measurement window, completes account cleanup and reclamation sixty days out, and reconciles the internal count against the vendor's preliminary measurement thirty days out, leaving time to dispute records before the invoice is cut. The same eighteen-month renewal runway described in our reclamation work applies to true-ups: the earlier the count is clean, the smaller the settlement.
For SaaS estates where true-ups settle at renewal, the calendar and the renewal strategy are the same project. Separating the quantity reconciliation from the price negotiation, where the contract allows it, keeps the vendor from using deployed growth as price leverage. Where they cannot be separated, the baseline becomes the buyer's only counterweight, which is why it is built first and built independently. Engagement support is available through our software licensing advisory practice.
A worked true-up example
The cost of an unmanaged true-up is easiest to see in numbers. Take a buyer with a 4,000-seat SaaS subscription bought at a 40 percent discount off a 1,200 dollar list price, so 720 dollars per seat per year. During the year the business grows and the platform reports 4,700 active seats at the measurement date. The 700 excess seats are the true-up. If the contract fixed incremental pricing at the base discount, the true-up bills at 720 dollars per seat, or 504,000 dollars. If the contract was silent and the excess prices at list, the same 700 seats bill at 1,200 dollars, or 840,000 dollars. The single contract term that fixed the incremental price saved 336,000 dollars on one reconciliation.
Now add the count problem. Of the 4,700 seats the platform reports as active, a clean baseline finds that 350 belong to terminated employees whose accounts were never deactivated and 120 are duplicate or service accounts. The true billable excess is not 700 but 230. A buyer who reconciled the count before the measurement pays for 230 seats; a buyer who accepted the vendor number pays for 700. The combination of a fixed incremental price and a clean count is the difference between a 165,600 dollar settlement and an 840,000 dollar one on the same growth, which is why both the contract term and the baseline are non-negotiable parts of true-up management.
| Approach | Billable excess | Per-seat price | True-up cost |
|---|---|---|---|
| Unmanaged (vendor count, list price) | 700 seats | $1,200 | $840,000 |
| Price fixed, count not cleaned | 700 seats | $720 | $504,000 |
| Count cleaned, price at list | 230 seats | $1,200 | $276,000 |
| Managed (clean count, fixed price) | 230 seats | $720 | $165,600 |
The four true-up mistakes that cost the most
Most true-up overspend comes from a small set of repeated mistakes. The first is treating the vendor's measurement as authoritative rather than as an opening position to be reconciled against an independent count. The second is allowing the true-up to settle in the same conversation as the renewal price, which lets the vendor use deployed growth as price leverage at the exact moment the buyer is weakest. The third is failing to clean inactive and duplicate accounts before the measurement window, leaving the count inflated by records that generate no value. The fourth is signing the original contract without a fixed incremental price or a true-down right, which removes the buyer's protection before the first true-up ever runs.
Each of these is preventable, and each is prevented at a different point in the contract life. The incremental price and true-down are won at signature; the clean count is produced in the ninety days before measurement; the separation of quantity from price is a renewal-planning decision. A buyer who treats the true-up as a recurring, scheduled commercial event rather than an annual surprise addresses all four. The broader discipline of tracking entitlement against deployment across every vendor is the subject of our software license management guide, and the renewal-timing discipline is set out in our software contract negotiation guide.
True-up management across a portfolio
A single true-up is a project; managing true-ups across a portfolio of vendors is a function. Large estates carry true-ups on different cadences across Microsoft, Salesforce, Adobe, Oracle, and others, and without a central calendar each one arrives as its own surprise. The organizations that manage this well maintain a master schedule of every measurement and reconciliation date, run a standard baseline process ahead of each, and apply the same contract-term checklist to every renewal so that no agreement is signed without a fixed incremental price and a true-down right. That portfolio view is one of the core jobs of a vendor management office, and the savings from running it well compound across the whole supplier base rather than landing on one deal.