Timing a software true-up to your contract anniversary rather than mid-term, and consolidating it into the renewal negotiation, can cut the unit price you pay for the added licenses by 20 to 40 percent compared with a reactive mid-term true-up declared in isolation. A true-up is not a fixed bill, it is a transaction, and like any transaction its price depends on when it happens and what else is on the table. Declared cold in the middle of a term, you pay close to list because you have no leverage and no event to attach it to. Declared at renewal, alongside a commitment the vendor wants, the same licenses become part of a negotiation you can win.
What a true-up is
A true-up is the periodic reconciliation of what you have deployed against what you have licensed, with payment for the difference. Many enterprise agreements, particularly volume and capacity-based ones, allow you to grow during the term and settle the additional usage at defined points rather than buying each license as you deploy it. The mechanism is convenient because it lets deployment move faster than procurement, but it carries a cost: the unit price at true-up is often the contract rate or list, without the discount you negotiated on the original volume, and the timing of the declaration is usually left to a contractual schedule that favors the vendor. The buyers who treat the true-up as an administrative settlement pay the most, because they surrender the timing and the pricing to a process the vendor designed.
Why timing changes the price
The price of a true-up turns on leverage, and leverage turns on timing. A mid-term true-up declared on its own gives you nothing to negotiate with: the usage exists, the contract requires settlement, and the vendor has no incentive to discount because there is no larger deal at stake. The same usage declared at renewal sits inside a negotiation where the vendor wants your continued commitment, which means the added licenses can be folded into the discount structure of the renewed agreement rather than priced at the cold mid-term rate. The difference is not a rounding error. Added volume that would settle near list mid-term can settle at the renewal discount band when stacked into the renewal, and on a large true-up that gap reaches well into six figures.
| Scenario | Leverage | Typical unit price outcome |
|---|---|---|
| Reactive mid-term true-up | None, usage already exists | Contract rate or near list |
| Planned anniversary true-up | Some, tied to renewal timing | Modest discount |
| True-up stacked into renewal | High, part of larger commitment | Renewal discount band, 20% to 40% lower |
Measure before you declare
The most expensive true-up mistake is declaring a number you have not verified, because the figure you report becomes the figure you pay, and it is frequently higher than your real deployment. Before any declaration, build an effective license position that reconciles actual deployed and used software against your entitlements, so you declare what you genuinely consume rather than what a vendor tool or an internal estimate suggests. Installed-but-unused software, decommissioned systems still counted, and double-counted instances all inflate a naive true-up. The same exercise often surfaces entitlements you forgot you held, which offset the additional usage. Measuring first turns the true-up from a number the vendor proposes into a number you control, and the gap between the two is regularly large enough to fund the effort many times over.
The reclaim before the true-up: Run a right-sizing pass before you declare. Unused and over-provisioned licenses you reclaim reduce the net true-up directly, because you are settling growth against a baseline that no longer carries dead entitlements. Buyers who declare growth without first reclaiming waste pay twice: once for the licenses they stopped using and again for the ones they added. The reclaim and the true-up belong in the same exercise, not in sequence.
Stacking the true-up into the renewal
The strongest play is to align the true-up with the renewal so the two become a single negotiation. When the additional licenses are part of the volume you are committing to for the next term, the vendor prices them inside the renewal discount rather than as a separate settlement, because the renewal is the deal they care about closing. This requires planning, because it means timing deployment and declaration so that the reconciliation point lands at or near the renewal rather than mid-term, and it means resisting the vendor's preference to settle the true-up early and separately. The vendor will often push for an isolated mid-term settlement precisely because it pays them more, so holding the true-up for the renewal, where the contract permits, is itself a negotiating decision. The mechanics of folding it in are the same ones our software contract negotiation guide applies to any added scope at renewal.
Guard against discount erosion on the new units
Even at renewal, the added licenses are a point where discount erosion creeps in, because vendors frequently price new units at a weaker discount than the existing base, betting that you will accept a blended rate that quietly raises your effective price. The defense is to negotiate the true-up volume at the same discount as the renewed base, in writing, rather than accepting a separate and worse band for the growth. This is the same dynamic our guide to discount erosion at renewal describes, applied to the incremental units, and it matters because the true-up volume often grows over successive cycles until the weaker rate applies to a large share of the estate. Locking the growth to the base discount at the moment of the true-up prevents the slow upward drift that funds much of the vendor's account growth.
The pitfalls that cost the most
Three errors account for most overpaid true-ups. The first is declaring reactively, after the vendor prompts, rather than on a planned timetable that aligns with the renewal. The second is declaring an unmeasured number that includes usage you do not actually have, which a proper effective license position would have excluded. The third is accepting a separate, weaker discount on the added units instead of the base rate. Each is avoidable with planning, and the combined effect of avoiding all three is the 20 to 40 percent unit-price reduction the lead figure describes. The same right-sizing discipline that controls the baseline, set out in our guide to right-sizing licenses, feeds directly into a cleaner true-up. A true-up is one of the few licensing events where the buyer chooses the timing, and that choice is the lever. Running it deliberately through our software licensing advisory service means you declare a measured number, at the moment of maximum leverage, at the renewal discount rather than the cold rate, which is the entire difference between a true-up that settles fairly and one that quietly funds the vendor's quarter.