We went over our licensed user seats — what is our exposure?
The short answer
If your company has more active users or seats than your SaaS license covers, your agreement defines what happens next. Most SaaS agreements require the customer to stay within licensed seat counts, and a true-up clause typically requires the customer to purchase additional seats — often at list price, not the contracted discount rate — for any overage period. Whether the vendor has a right to conduct an audit, when the overage is assessed, and how the pricing is calculated are all governed by the agreement's specific provisions. The agreement defines what happens, not a general rule. Scan your contract to understand your true-up obligations and how overages are priced before a vendor inquiry arrives.
No account requiredFile deleted after analysisNot legal advice
What true-up and overage clauses typically say
Most SaaS agreements include either a true-up clause or an overage clause — sometimes both. A true-up clause typically requires the customer to report usage at defined intervals (quarterly or annually) and purchase additional seats for any overage discovered at the contracted or list price. An overage clause may automatically charge for seats above the licensed count on a prorated or full-period basis. The practical difference: a true-up is often a negotiated purchase at renewal; an automatic overage charge can trigger mid-term without warning if the vendor's platform tracks active users in real time.
The pricing consequences of an overage are often more significant than buyers expect. Overage seats are commonly priced at the vendor's then-current list price, not the discounted rate negotiated for the initial order. If your contracted rate was 30% below list, each overage seat costs materially more than your existing seats. Some agreements also include a retroactive billing provision, pricing the overage back to the date it began rather than only going forward.
How seat counts drift without anyone noticing
Overage situations most commonly arise from: new employee onboarding where licenses are added informally, integration tools or automated accounts that consume named-user licenses, test or development environments counted under the same license model, and AI agent or bot accounts in tools that have adopted per-user pricing that includes non-human accounts. IT teams report that the license model they purchased was designed for a specific usage pattern, and actual deployment diverged without a systematic check. The audit rights in the agreement are the mechanism by which the vendor can formally identify and address overages.
What to look for in your agreement
- How the agreement defines a 'user' or 'seat' — and whether automated accounts, API integrations, or read-only access consume a license.
- The true-up or overage clause: when is overage assessed, how is it calculated, and at what price?
- Whether overage pricing is at your contracted rate or at then-current list price.
- Any retroactive billing provision: does the overage price apply back to when the excess began, or only going forward?
- Audit rights: what process must the vendor follow before asserting an overage claim?
Questions to ask before signing
- Ask the vendor to confirm the license model and how specific user types (API integrations, admin accounts, read-only users) are counted.
- Ask the other party to clarify the overage price — specifically whether it is your contracted rate or list price.
- Confirm whether the agreement includes a grace period or notification requirement before overage charges are assessed.
- Consider having the seat definition and true-up provisions reviewed if the license model is complex or the platform will be used by a growing organization.
Why scan instead of guess
The general rule tells you the baseline. Your agreement tells you what you’re actually being asked to sign — and the wording is what binds. Dang reads the document and flags the clauses worth reviewing, in plain English.
The deterministic engine scores and decides what’s risky. The AI only enriches the plain-English wording — AI extracts, code decides, never the other way around.
Your original file is deleted promptly after processing — we keep only the report you can read. No account needed for a one-time scan. Free preview first; full report $6.99, one-time.
Common questions
Does going over my seat count mean the vendor can terminate the agreement?
Most agreements treat overages as a pricing and true-up matter rather than a termination trigger. The agreement defines what happens — typically a requirement to pay for overage seats and possibly an audit. Whether the vendor could characterize a persistent overage as a material breach depends on the specific breach and termination provisions of your agreement.
Can I negotiate overage pricing before it arises?
Yes — at signing, the overage rate is a negotiable term. Common asks include: overage pricing at the contracted rate rather than list price, a notification requirement before charges are assessed, and a cure period to bring usage into compliance. These are harder to negotiate after an overage has already occurred.
No account required · File deleted after analysis · Not legal advice. Dang reports contract findings in plain English — general information, not legal advice about your situation. For consequential decisions, consult a licensed attorney in your state.