What Is True-Up?

How Does a True-Up Work?

A contract sets an initial commitment, a measurement unit and a reconciliation date. The unit might be licensed users, deployed products, storage or API calls. The reconciliation compares the contractual allowance with the quantity that qualifies for billing.

An agreement may let a team add users before placing another order, then report those additions at an agreed checkpoint. Quarterly and annual reviews are possible contract designs, not a universal schedule. Read the order form before assuming when the invoice will arrive.

The measurement rule matters as much as the rate. Ask whether the vendor counts assigned licenses, active users, peak deployment or cumulative consumption, and whether additions are charged from their start date or another contractual date. Our guide to SaaS pricing models explains the broader charging choices.

Why It Matters to Software Buyers

A prepaid annual subscription is not necessarily a spending ceiling. Growth, forgotten accounts or a new integration can create additional billable quantities, so finance needs a forecast that separates the initial commitment from potential adjustments.

An adjustment can also affect the next renewal if the larger quantity becomes the new commitment. Ask the vendor to show the current reconciliation and next term’s proposed baseline separately. Compare both with the original annual contract value, rather than treating one invoice as the whole cost.

Use our Software Bloat Calculator to review the bills around an adjustment. Then check the underlying entitlement records, since a spreadsheet of payments cannot prove which users or events should have been counted.

How It Shows Up in Practice

Microsoft is the familiar enterprise example. Its Enterprise Agreement True-up Guide confirms that enrolled customers submit an annual reconciliation of changes in software usage. Check your own enrollment for the applicable products and reporting rules.

Adobe works the same way for enterprise customers. It publishes an ETLA report of additional deployments, showing prior deployment totals, additions and new totals. That form illustrates the reporting mechanism, not a promise that every Adobe subscription uses identical terms.

HubSpot uses a related but different mechanism. Its marketing contacts billing documentation explains automatic contact-tier upgrades when the allowance is exceeded. A tier upgrade changes the purchased capacity; it should not automatically be described as an annual enterprise true-up.

True-Up vs. True-Down

A true-up increases the amount owed when measured quantities exceed the commitment. A true-down is a contractual ability to reduce the committed quantity or spend. Having one does not establish a right to the other.

Removing a user today may stop future access without reversing a charge already earned under the agreement. It may also leave the minimum purchase unchanged until renewal. Ask for the effective date, notice period and any minimum quantity in writing.

For usage-based pricing, distinguish a retrospective reconciliation from ordinary monthly consumption billing. Both can increase spend, but the payment schedule, minimum commitment and ability to reduce future consumption may differ.

How Do You Negotiate a True-Up?

Negotiate the measurement process before negotiating a discount. A lower unit rate is difficult to evaluate if the counted population or reporting period is unclear. Request a worked example using your expected growth and a separate example for contraction.

• Define the billable unit, exclusions, reporting dates and evidence used to count additions.
• Ask for prorated additions, advance threshold alerts and a documented process for disputing the count.
• Request a matching reduction right, and identify any minimum commitment that limits it.
• Confirm whether adjusted quantities carry into renewal and whether renewal pricing is separately negotiated.

A proposed cap should say what happens when the cap is reached. It might limit charges, block further use or require another order, which are different commercial outcomes. Have procurement confirm the operational consequence with the team that depends on the tool.

How Do You Check a True-Up Invoice?

Keep the original order, amendments, license assignment history and vendor calculation together. Reconcile quantities first, then rates, dates and tax treatment. A clean audit trail is more useful than trying to reconstruct access changes after an invoice arrives.

• Compare the vendor’s counted population with the contract’s definition of a billable user or event.
• Check each addition’s effective date and the stated treatment of partial billing periods.
• Separate the current adjustment from any proposed renewal increase and submit questions within the contractual dispute window.

Do not remove accounts solely to change a snapshot unless that action matches the agreement and preserves required access. Ask IT to distinguish inactive accounts from service identities and legitimate occasional users. Assign one person to approve the final reconciliation.

When Is a True-Up the Right Choice?

A true-up can suit a growing team that needs to add capacity without repeated purchasing delays. Staying with the existing service can be sensible when the reporting burden is manageable and the extra capacity supports real work.

If reconciliation is hard to forecast, compare a smaller commitment or a different billing model at renewal. Include the transition work and switching costs, rather than choosing a replacement only because its headline rate looks lower. The next step is a side-by-side contract comparison, not an immediate migration.