If you have signed a SaaS contract in the last five years, you have almost certainly agreed to a true-up clause. Most buyers do not notice it at the time. They notice it later, when a reconciliation invoice arrives that was not in the original budget.
True-up clauses are one of the most consistently misunderstood elements of enterprise software agreements. They sound technical and neutral. In practice, they are a mechanism that vendors use to capture additional revenue from customers whose usage grows beyond what was contracted, and in some structures, they are one of the most expensive surprises a finance team can encounter mid-year.
This guide explains what a true-up clause actually is, how different vendors use them, what the buyer-side risks are, and what you can negotiate to protect your budget.
A true-up clause is a provision in a software or SaaS contract that allows the vendor to reconcile actual usage against contracted usage at specified intervals, typically annually, and charge the customer for any excess.
The basic logic is straightforward. When you sign a SaaS contract, you commit to a certain level of usage: a number of seats, a volume of API calls, a quantity of data processed, or a number of transactions. You pay upfront for that committed level. If your actual usage exceeds the commitment during the contract period, the true-up clause triggers a reconciliation charge for the difference.
In plain terms: you agreed to pay for 100 users. You ended up with 125 users. At the true-up, you owe the vendor for those 25 additional users, typically at your contracted per-unit rate, sometimes at list price.
A 2024 Gartner study found that 65% of SaaS contracts now include true-up mechanisms, up from 45% five years prior. They are the rule, not the exception, across enterprise software.
The commercial rationale from the vendor's side is legitimate. When a customer commits to 100 seats at a fixed annual price, the vendor builds their revenue model around that commitment. If the customer grows to 130 seats during the year but only pays for 100, the vendor has delivered value for 30 additional seats without compensation.
True-up clauses protect vendors against this underpayment. They also create a mechanism for revenue expansion that is contractually embedded rather than dependent on the sales team identifying and closing an upsell.
For vendors with usage-based or seat-based pricing, a well-structured true-up is a reasonable commercial safeguard. The problem for buyers is that true-up clauses are often structured in ways that create asymmetric risk: they apply to growth but not to decline, they fire quarterly rather than annually, and they price overage at list rather than contracted rates.
Not all true-up clauses work the same way. Understanding the structure in your contract determines your actual financial exposure.
The most common type. If your active user count exceeds the contracted seat count during the measurement period, you owe the overage at a specified rate. Found in CRM, collaboration, security, and most SaaS tools with per-user pricing.
Key variables: What constitutes an active user? Is it any provisioned user, any user who logged in, any user who performed a meaningful action? Vendors define this differently, and vague definitions favour the vendor.
Common in cloud infrastructure, API platforms, and consumption-based SaaS. You commit to a volume of consumption (API calls, data processed, compute hours, envelopes sent) and owe for overages.
Key variables: The overage rate. Is it at your contracted per-unit price or at list price? For significant overages, the difference is material. Also: is the overage rate capped?
The frequency of reconciliation has a significant impact on your ability to manage costs. Annual true-ups give your team time to identify and address over-provisioning before the charge lands. Quarterly true-ups compress that window considerably, and mid-year invoices from a quarterly true-up are harder to forecast and budget for.
Many vendors are pushing toward quarterly or even monthly true-ups, particularly in cloud and infrastructure contracts. Negotiate for annual cycles wherever possible.
This is the structure most buyers fail to notice. A true-up clause allows the vendor to charge you for growth in usage. A true-down clause (far less common) allows you to receive a credit or reduction if your usage falls below the contracted level.
Most standard SaaS contracts allow true-ups without true-downs. This means the financial relationship is structurally asymmetric: you pay for exceeding your commitment, but you receive no benefit for falling below it. If your company reduces headcount mid-year, you continue paying for the contracted seat count until renewal. The vendor captures the upside of your growth but does not share the downside of your decline.
Salesforce: Salesforce conducts annual true-ups on seat counts. If your active user count during the year exceeds the contracted count, you owe the difference at your contracted per-user rate. The standard 9% price escalation added in December 2023 applies to the renewed contract, not the true-up charge, but the interaction between escalation and true-up in multi-year agreements compounds cost.
AWS Enterprise Discount Program: The EDP true-up is the most consequential version in enterprise software. If you commit to $3M in annual AWS spend and consume $2.4M, you owe $600,000 regardless. This is not a billing adjustment. It is a contractually enforceable payment for the shortfall. AWS calls this a shortfall payment, not a true-up, but the mechanism is identical.
Microsoft Enterprise Agreement: The Microsoft EA true-up is annual, occurring at the anniversary of the agreement. Customers must report all qualifying deployments of Microsoft software and cloud services made since the last anniversary and pay for any increases. The November 2025 elimination of volume discount tiers for online services means that EA true-ups are now priced at the negotiated EA unit rate regardless of total volume, removing the previous dynamic where a true-up could push a customer into a better discount tier.
DocuSign: Business Pro plans cap at 100 envelopes per user per year. If a team exceeds this limit, overages are billed at $1-$2 per envelope. These overages do not appear on the annual invoice but arrive on mid-year statements, making them easy to miss until they have accumulated significantly.
Atlassian Maximum Quantity Billing: Rolled out in 2025, this is a true-up variant that charges based on peak user count during a billing period, not end-of-month count. If you add 20 contractors for a three-week project and remove them before month-end, you still pay for those 20 users for the entire month. For teams with variable headcount, this creates systematic overpayment.
Budget-period misalignment: True-ups often fire at the contract anniversary, not at the company's fiscal year-end. A true-up invoice arriving in October for a calendar-year budget team can be difficult to absorb without disrupting other plans.
Overage rate risk: Some contracts price overage at list price rather than your contracted rate. If you negotiated a 20% discount on a $175/user/month product, your contracted rate is $140. An overage at list price costs $175. For a 30-seat overage over 6 months, the difference between contracted and list price is $9,450. Read the overage pricing clause explicitly.
Retroactive application: Some true-up clauses apply retroactively to the full contract period, not just the period of excess usage. If you exceeded your seat count in month 3 and the true-up fires at month 12, you may owe for 10 months of excess seats, not one.
Growth tax on multi-year deals: In a multi-year agreement with annual true-ups and price escalation, the interaction compounds. You pay escalated rates on the true-up volume, not original rates. A large true-up in year two of a three-year deal at a 9% escalator rate costs meaningfully more than the same overage would have in year one.
True-down rights: Push for symmetry. If the vendor can true up for growth, you should be able to true down for decline. Most enterprise buyers accept the default (true-up only) without asking. Many vendors will agree to annual true-down rights at renewal, even if they resist mid-term reductions.
Annual rather than quarterly cycles: Explicitly negotiate annual true-up cycles. Monthly or quarterly cycles compress your ability to manage usage before the charge fires.
Overage priced at contracted rate, not list: Specify in the contract that any true-up charges are calculated at the applicable contracted rate, not the vendor's then-current list price. This protects you from paying list price on overages after you have already negotiated a discount on the base contract.
Growth headroom: Rather than committing to exactly your current usage, negotiate headroom into the initial contract (an additional 10-20% of expected growth) in exchange for a slightly lower per-unit rate. This provides a buffer before the true-up fires, and the economics often work in your favour versus paying overage rates on even modest growth.
Measurement definition: Get explicit, written definition of what constitutes a billable unit. For seat-based true-ups: is a seat anyone provisioned, anyone who logged in within 30 days, or anyone who performed a specified action? Vague definitions resolve in the vendor's favour at audit time.
Notification before billing: Negotiate a requirement that the vendor notify you if your usage is approaching the contracted threshold, with sufficient time (30-60 days) to take action before a true-up charge is triggered. Some vendors do this voluntarily; many do not without it being in the contract.
For mid-market companies, the true-up/true-down asymmetry deserves specific attention.
Growth companies over-provision at contract signing, buying for projected headcount rather than current headcount. If growth slows, they carry excess seats to renewal. If growth accelerates past the contract, a true-up fires. In both scenarios, the vendor is protected. In neither scenario is the buyer.
The most valuable thing you can negotiate in a seat-based SaaS contract is not the per-seat rate. It is the right to reduce at renewal without penalty, combined with annual true-up (not quarterly) for growth. This structure acknowledges that your headcount will change in directions you cannot perfectly predict at signing, and distributes that uncertainty between vendor and buyer rather than putting it entirely on the buyer.
Before your contract anniversary, run a true-up audit:
For consumption-based contracts: pull your usage data from the vendor's billing console or your own cost management tools. Compare to your contracted commitment. Identify whether you are tracking above or below commitment, and what the trajectory suggests for the remainder of the term.
The true-up audit is also a negotiation input. Usage data showing that you have been significantly below your contracted commitment is leverage for negotiating a true-down at renewal, a lower commitment level, or a better per-unit rate.
True-up clauses are legitimate commercial mechanisms. They become costly when buyers sign them without understanding the measurement cycle, the overage rate, and the asymmetry between true-up and true-down rights.
The most important things to know:
And the question every finance lead should ask before signing any SaaS contract: what happens if we use more than we committed to? Then read the clause that answers it, rather than assuming the answer.
Procr
See what Procr does with your real vendor portfolio.