In This Guide
A true-up clause is one of the most asymmetric provisions in enterprise SaaS contracts. When you use more than you licensed, the vendor charges you for the overage. When you use less, the vendor keeps your money. This asymmetry is by design — and it is negotiable in both directions, but only if you know to ask.
The scale of unexpected true-up exposure is significant. Organisations with 1,000+ seats across multiple SaaS platforms regularly carry six-figure true-up risk without knowing it. The risk is highest in platforms where user counts fluctuate rapidly (Salesforce, Workday), where measurement is opaque (ServiceNow's concurrent usage model), or where usage definitions are broad and vendor-controlled (Microsoft's EA true-up process).
How True-Up Clauses Work
A basic true-up clause operates as follows: you license a defined quantity (seats, users, consumption units) at a fixed price. At defined measurement intervals, the vendor compares your actual usage to your licensed quantity. If actual usage exceeds licensed quantity, you owe the difference at a defined rate — typically your contracted per-unit price, though standard contracts often allow the vendor to charge list price.
True-up clauses vary along four critical dimensions:
- Measurement frequency: Quarterly (worst for buyers — captures seasonal peaks) versus annual (smooths variation)
- Usage definition: Peak concurrent users (highest exposure) versus average active users (most representative) versus total provisioned accounts (often inflated)
- Overage pricing: Contracted per-unit rate (fair) versus current list price (potentially double your contracted rate)
- Grace threshold: Whether there is a buffer above your contracted quantity before true-up obligations trigger (most standard contracts have none)
The combination of quarterly measurement, peak usage definition, list price overage rate, and no grace threshold creates maximum financial exposure — and this combination appears in many standard SaaS contracts.
True-Up Practices by Vendor
| Vendor | Frequency | Measurement Method | Overage Rate | Risk Level |
|---|---|---|---|---|
| Salesforce | Quarterly (default) | Active users in period | List price (default) | High |
| ServiceNow | Annual | Peak concurrent capacity | Contracted rate | Medium-High |
| Workday | Annual | Active employee count | Contracted PEPM | Medium |
| Microsoft (EA) | Annual | Installed/provisioned users | Contracted rate | Medium (virtualisation risk) |
| Adobe (ETLA) | Annual | Active users by product | Contracted rate | Low-Medium |
| Zendesk | Quarterly | Active agents | List price (default) | High for support orgs |
| HubSpot | Monthly (auto-upgrade) | Contact/seat limits | Automated tier upgrade | Very High for contact-based tiers |
Salesforce's standard Order Form uses quarterly true-ups at list price for overages. This means if your negotiated per-user price is $150/month but current list is $250/month, a quarterly overage of 20 users costs you $15,000 (20 × $250 × 3 months) rather than $9,000 at your contracted rate. Negotiate the overage rate to your contracted price before signing any Salesforce agreement.
The Measurement Problem
Usage measurement is where true-up disputes most commonly occur — and where buyers most often lose. The problem has three dimensions:
Who Controls the Measurement Data?
In most SaaS contracts, the vendor's platform generates and retains the usage data used to calculate true-ups. Buyers typically receive reports from the vendor's admin portal, which may define "active user" differently in the contract versus the system. We have seen cases where the contract defines an active user as "any user who logged in during the measurement period" while the system counts provisioned accounts regardless of login activity — a definition that inflates usage by 20–40% in organisations with poor account hygiene.
Peak vs Average Usage
Quarterly peak usage measurement is particularly punishing for organisations with seasonal patterns. A retail organisation might have 600 active Salesforce users in Q4 and 400 in Q1–Q3. If they are licensed for 450, a quarterly true-up captures the Q4 spike and charges for 150 excess users — even though the average across the year is 425, within the licensed quantity. Annual measurement based on average active users eliminates this problem entirely.
Definition Creep
Vendors occasionally expand usage definitions through order form amendments, product updates, or support tickets without explicitly flagging the commercial impact. The most common example: a platform that previously counted "named users" shifts to counting "API-connected integrations" as licence consumption after a product update. Robust contracts specify the usage definition precisely and require buyer consent for any changes to measurement methodology.
True-Down Rights: The Other Side of the Equation
A true-down right is the commercial mirror of a true-up obligation — it allows you to reduce your contracted quantity (and therefore your subscription fees) at renewal if actual usage falls below your licensed amount. Standard SaaS contracts do not include true-down rights. The absence of a true-down right means that if your organisation has 500 Salesforce licences and only 380 active users, you pay for 500 at renewal without recourse.
True-down rights are negotiable, and the following structure is achievable in enterprise negotiations:
- Right to reduce licence count by up to 15% at annual renewal without penalty
- True-down measured against average active user count over the preceding 12 months
- True-down exercised by written notice no later than 90 days before renewal date
- Reduced quantity to be priced at current contracted per-unit rate (not re-priced at higher tiers)
Vendors most likely to accept true-down rights: Workday (particularly for organisations post-restructuring), Adobe, and ServiceNow for established enterprise accounts. Vendors most resistant: Salesforce (whose revenue model is built on ratcheting seat counts), HubSpot, and Zendesk.
8 Contract Protections That Prevent Surprise True-Ups
Grace Threshold Above Licensed Quantity
Negotiate a grace threshold of 5–10% above your contracted quantity before true-up obligations trigger. This buffer absorbs temporary spikes without creating immediate financial liability. On a 500-seat contract, a 5% grace means true-up obligations only begin when usage exceeds 525 seats — smoothing out temporary fluctuations from onboarding, seasonal peaks, or M&A activity. This single term eliminates the majority of minor true-up claims.
Annual (Not Quarterly) Measurement Frequency
Push every vendor to annual true-up measurement. Annual frequency smooths seasonal peaks, eliminates quarterly billing surprises, and gives you time to manage usage proactively before the measurement date. Frame the ask commercially: "We want to plan our licence requirements accurately — quarterly measurement creates volatility we can't budget for. We're willing to commit to annual measurement in exchange for a longer term commitment." Most enterprise vendors will accept this in exchange for a 2–3 year commitment.
Contracted Per-Unit Rate for Overages
Explicitly require that any true-up charges are calculated at your contracted per-unit rate, not current list price. This single term can halve the cost of a true-up event. The contract language to request: "Any incremental units purchased pursuant to a true-up shall be priced at the per-unit rate specified in the applicable Order Form, not at current list price." If the vendor insists on list price, counter with a specific cap: "no more than 110% of contracted per-unit rate."
Usage Notification Requirements
Require the vendor to notify you in writing when your usage reaches 80% and 90% of your contracted quantity. This early warning gives you time to either manage usage (deactivate inactive accounts, reassign licences) or negotiate a proactive licence expansion — on your timeline, not after a retroactive true-up demand. Without this provision, many organisations only discover they have a true-up liability when they receive the invoice.
Average Active Users (Not Peak) as the Measurement Basis
The contract should define the measurement basis as average active users over the measurement period — not peak concurrent users or total provisioned accounts. Define "active user" specifically: typically, a user who has logged in and performed at least one action in the platform within the 30-day period. Provisioned accounts that have never been used, deactivated accounts awaiting offboarding, and service accounts should be explicitly excluded from the count.
Dispute Resolution Process
Require a defined dispute resolution process for true-up claims: 30-day buyer review period before payment is due; right to audit vendor usage data; and escalation to a senior commercial contact (not just the billing team) if the dispute is unresolved within 15 business days. Without a contractual dispute process, the default is often payment-on-demand with limited recourse. The right to audit usage data is particularly valuable — it creates a structural check on vendor measurement practices.
True-Down Right at Annual Renewal
Negotiate the right to reduce licence count by up to 15% at each annual renewal based on documented underutilisation. This converts the contract from a ratchet (usage can only go up commercially) to a genuine subscription that reflects your actual needs. The negotiation frame: "We expect our deployment to grow, but we want the flexibility to right-size if our business needs change. We're happy to commit to a 3-year term in exchange for a 15% true-down right."
Fixed Measurement Methodology Language
Include explicit contract language that the measurement methodology may not be changed without written buyer consent. This prevents vendors from unilaterally expanding usage definitions through platform updates or order form amendments. The clause: "Any change to the usage measurement methodology defined in this Agreement requires written consent from the Customer and shall not take effect until the subsequent renewal period." This is particularly important for platforms that are rapidly adding AI and automation features that may consume licences in new ways.
Audit Your Current SaaS Contracts for True-Up Risk
We review your existing SaaS agreements and identify true-up exposure before it becomes a budget crisis. Most clients find six-figure risk they didn't know about.
Request a Contract ReviewNegotiating Better True-Up Terms
The best time to negotiate true-up protections is at the point of initial contract execution — not at renewal, when the vendor already has your money. When signing new SaaS agreements, treat the true-up provisions as a priority alongside price and term length.
At renewal, you can renegotiate true-up terms, but it requires leverage. The most effective approach: conduct a usage audit before the renewal conversation, identify specific instances where the current true-up structure worked against you, and frame the requested changes as a condition of renewal rather than a nice-to-have. "We experienced two true-up events last year that resulted in unbudgeted spend totalling $X. We need these terms addressed as part of the renewal." This framing is factual, non-threatening, and creates a commercial basis for the change.
Vendor-Specific Negotiation Notes
Salesforce: Push hard for annual measurement and contracted rate overages. Salesforce will often accept annual measurement in exchange for a 3-year commitment. The overage rate is harder — frame it as a budgeting requirement, not a commercial preference.
Workday: Workday's standard true-up is already annual and measured on active employee headcount, which is reasonably transparent. The negotiation priority is securing a true-down right, particularly for organisations with headcount variability. See our detailed guide on Workday contract negotiation for further context.
Microsoft: Microsoft's EA true-up is annual and well-documented, but the definition of "software licence entitlements" includes virtualisation scenarios that frequently generate unexpected claims. Ensure the measurement excludes test and development environments and specify the virtualisation treatment explicitly.
Ongoing True-Up Monitoring
Even with well-negotiated true-up terms, ongoing monitoring is essential. Implement the following practices:
- Monthly export of active user counts from each major SaaS platform's admin console
- Quarterly review of licences versus active users, flagged to IT procurement and finance
- Automated deprovisioning of accounts after 90 days of inactivity (particularly important for Salesforce and ServiceNow where provisioned accounts count as active users)
- Pre-notification to your SaaS vendor account teams 60 days before any large onboarding event (M&A, system rollout) that will temporarily spike usage
- An annual contract review comparing actual true-up charges against budgeted estimates, used to calibrate future planning
Organisations that monitor actively spend 15–20% less on SaaS true-ups annually than those that manage reactively — and they avoid the budget crisis that reactive true-up management invariably creates.
See also: SaaS Contract Negotiation Strategies | SaaS Vendor Lock-In: Exit Strategies | SaaS Contract Optimization Service