© 2026 Procr
Every enterprise SaaS contract includes a mechanism for the vendor to charge you for growth. The true-up clause is that mechanism, and for mid-market teams that don't plan for it, it arrives as a line item on the renewal invoice that wasn't in any budget model.
A SaaS true-up clause is a contractual provision that reconciles the number of software licenses a customer actually used against the number they contracted and paid for, at a defined interval. If actual usage exceeded the contracted count, the customer owes the difference. If usage fell below the contracted count, most standard agreements do not issue a refund.
The reconciliation interval is typically annual, timed to the contract anniversary or renewal date. Some contracts run quarterly true-ups, which spread the billing more evenly but create more frequent reconciliation events. Either way, the process is the same: the vendor produces a usage report, compares it against your contracted baseline, and invoices for any gap.
The financial exposure depends on two variables: how far your usage diverged from the contracted baseline, and at what price the vendor bills overages. Most standard contracts bill overages at full list price, not the discounted rate you negotiated. In 2026, with SaaS vendors raising list prices at an average of 8.7% per year according to Vertice's SaaS Inflation Index, the gap between your contracted rate and the list price applied to overages is growing year over year.
True-up clauses protect vendors from under-licensing: the practice of contracting for fewer seats than are actually deployed. Without a true-up mechanism, a company could purchase 200 licenses, quietly provision 240 users over the year, and pay for only 200 at renewal. The clause ensures growth is captured and billed.
Vendors also benefit from the behavioral dynamic the clause creates. Because new users can be provisioned immediately and reconciliation does not happen until the end of the contract period, there is minimal friction to adding users. Growth happens organically, and the vendor collects at the next true-up date. By the time the bill arrives, the usage has already occurred, and reducing seat counts retroactively is not an option.
For buyers, this dynamic is worth understanding before signing. The clause is not unreasonable in principle, but the specific terms determine whether the exposure is manageable or unpredictable: how usage is counted, at what rate overages are billed, and whether you retain any right to reduce your contracted count at renewal.
Not all true-up clauses measure usage the same way. The counting methodology has a direct effect on cost, and it is negotiable at signing.
High-water mark: The vendor charges based on the single highest user count recorded at any point during the contract period. A temporary onboarding of 30 contractors for six weeks at mid-year can drive a full-year overage charge at that peak level. Oracle applies high-water mark counting for many of its SaaS products, logging peak monthly user counts throughout the term. Salesforce similarly measures the highest active user count reached during each billing period.
Period-end count: Usage is measured at a specific snapshot date, typically the contract anniversary or renewal. If you over-provisioned mid-year and right-sized your seat count before the measurement date, you may owe nothing.
Average usage: The vendor averages your user count across all measurement periods during the term. This is the most buyer-friendly methodology and the hardest to obtain in a standard contract, but it is achievable in negotiation when usage patterns are predictable and you can present historical data to support the request.
High-water mark is the most common and the most expensive for buyers who experience any headcount volatility. Negotiating the counting methodology at signing is one of the most underused cost controls in SaaS procurement.
The exposure varies by how far usage exceeded the contracted count and how overages are billed. A concrete example: a 300-person company contracts for 250 Salesforce Sales Cloud Professional licenses at a negotiated rate. Over the year, the sales team grows and active users peak at 280. The vendor's true-up report, using high-water mark counting, shows a 30-seat overage. At Salesforce's list price for Sales Cloud Professional ($100 per user per month), that overage is billed retroactively from the date it first occurred, producing an unbudgeted charge of $30,000 or more depending on when in the year the overage began.
Research from L.E.K. Consulting found that 40% of customers on horizontal SaaS platforms regularly exceed their contracted limits. Among those who do, overage fees average approximately 28% of the original contract value. For a mid-market team with a $75,000 annual contract, that is up to $21,000 in unplanned spend on a single platform.
The cost compounds when overages are billed at list price rather than your contracted rate. A buyer who negotiated a 20% discount on their base licenses pays 20% more per seat for every overage unit.
True-up terms are negotiable at signing. Most buyers treat them as fixed contract boilerplate, but vendors routinely adjust the terms for procurement teams that ask. The time to negotiate is before the contract is signed, not at renewal when you are already in an overage position and your leverage is limited.
If you are already mid-contract and facing a true-up invoice, pull your own usage data from your SSO logs before accepting the vendor's count. Vendor-reported figures frequently include provisioned but inactive accounts. The difference between your active-user count and theirs is your negotiating position for a credit or rate adjustment.
A true-up clause is the contract provision that allows a vendor to charge you for software users or usage you added above your original contracted count. The reconciliation happens at a set interval, typically annually, and the overage charge is calculated at whatever rate the contract specifies. That rate is often the full list price rather than the discounted rate you originally negotiated, which is why understanding the clause before signing matters.
The cost depends on how far your usage exceeded the contracted count and at what rate overages are billed. L.E.K. Consulting found that customers who exceed their contracted limits face overage fees averaging approximately 28% of their original contract value. For a mid-market company with a $50,000 annual contract on a platform, that is up to $14,000 in unplanned spend. The exposure is meaningfully higher when overages are billed at list price rather than your contracted rate, and when the vendor uses high-water mark counting rather than period-end.
Yes. The overage rate, counting methodology, whether true-down rights are included, and whether the vendor must notify you before overages accrue are all negotiable at signing. Most buyers don't ask, which is why standard vendor contracts are written to favor the vendor on all of these points. At renewal, your leverage weakens because you are already using the product and switching is costly. The time to negotiate true-up terms is before you sign the initial contract or at the start of a multi-year renewal.
A true-up adjusts your contract upward to cover usage above the contracted baseline, and you pay for it. A true-down allows you to reduce your contracted seat count, typically at renewal, without penalty. Standard SaaS contracts include true-up provisions automatically but do not include true-down rights unless you negotiate them. Securing a true-down right at signing protects you if headcount drops or if you over-provisioned during the initial rollout, which is common when companies deploy a new platform and estimate adoption conservatively.
No. True-up clauses apply to any billable metric defined in the contract: user seats, API call volumes, data storage, transaction counts, or compute hours. The reconciliation mechanism is the same, but the cost exposure varies by metric. Storage and API-volume contracts can produce higher variance than fixed seat counts, particularly in product-led environments where usage scales directly with customer growth. When reviewing any SaaS contract with a true-up clause, confirm which metric or metrics are subject to reconciliation.
Procr
See what Procr does with your real vendor portfolio.