How to Review a SaaS True-Up and True-Down Usage Audit

An ops lead at a 20-person UK SaaS is about to accept a Q4 usage-audit invoice because sales said you grew — standard true-up, same as everyone. He treats unused named seats at list as housekeeping. Knowing how to review a saas true-up and true-down usage audit means you lock the unit, write the measurement date and whose numbers, price the delta at the contracted unit not list, demand true-down at the same cadence, then cap, prorate, or walk.

In September 2026, Kade — Ops at a 20-person UK SaaS — has Finance’s yes on incident-response software the on-call rota uses. The order form is 22 named seats at £48 a month against an £80 list. Clause 5.2 invoices excess Named Users at then-current List Price and says fees do not decrease. Friday’s Q4 report says 28. His Entra export shows 20 humans with a 90-day login, plus leavers, service accounts, and an unused contractor. The invoice is six seats × £80 × three months = £1,440, and next year’s baseline resets to 28. AE Slack: “Standard true-up — you added users.” Go-live is Monday.

A true-up without a same-cadence true-down is a one-way ratchet, and then-current list on unused named seats is not a recon. ContractHQ (21 July 2026) prints the default: invoice the excess at then-current list — a 40–80% gap versus the committed unit. That is a costly miss if Kade pays list on leavers.

Disclaimer: Checkory provides AI support, not legal advice. Consult a qualified lawyer for binding decisions.

What does the vendor count — a seat, a login, an employee, or an API call?

Write the unit before you argue the 28. A provisioned named seat, a last-30-day login, an employee on the HR file, and an API call are four different bills. Unused named seats still count if the unit is provisioned. Silence favours the vendor.

Freeze the packet — the exact file set you will pay: the MSA — master services agreement sitting above the order form — plus the order form plus the usage-audit exhibit — an attached schedule. Circle Named User. Procr colour: provisioned versus logged in within 30 days versus a specified action — vague wording favours the vendor. For example, Kade’s three leavers still sit in a provisioned count. Do not start a named-versus-concurrent comparison. Do: write the unit and whether unused named seats count. Don’t: treat “Named Users” as humans with a login.

Which file owns the measurement date and the numbers?

Write the date and the method: peak, average, or end-of-term snapshot. Then write whose file wins — the vendor dashboard or your IdP. The vendor report is an opening position, not a fact. If the counts differ, demand a line-by-line recon.

ContractHQ splits peak, average, and snapshot. A single-date snapshot can bill a spike that is already gone. CloudEagle : the vendor dashboard may count inactive users and service accounts. StackIQ : pull a 90-day login list before the invoice. In practice, Kade’s 20 active humans versus their 28 is the fight. Do: write date + method + vendor versus IdP. Don’t: treat their Q4 export as the number.

How do you price list-price overage against the contracted unit?

Price the delta twice before you pay. Line A uses the order-form unit. Line B uses then-current list. Those words are not the same invoice. Kade’s six extra seats are £864 at £48 and £1,440 at £80.

ContractHQ’s default is then-current list, not the committed unit. CloudNuro : overage at full list is often 30–50% above the negotiated rate. Ask: overage at the order-form unit. If the fight is year-two CPI or a then-current uplift on the fee table, that is a different hunt — the annual price-uplift review. Do: price both lines. Don’t: assume overage inherits the £48 discount.

What does a missing same-cadence true-down do to the baseline?

A true-up that can fire every quarter with no matching true-down is a one-way ratchet. Silence means the baseline only climbs. A renewal-only cut after a year of unused seats is weaker than a Q4 down.

Kade’s paper: fees “do not decrease during the Term” = silent / up only. OpenText Audit Defense : concede the true-up without the true-down and the agreement only ever climbs. A 10–25% cut with 60–90 days’ notice is colour, not a statute for England and Wales. If unused commit pounds are the issue, one sentence then the volume-commit shortfall review. Do: mark true-down as same cadence, renewal-only, or silent. Don’t: assume unused seats drop the bill.

When to demand notice — before the invoice, not after?

If the invoice is the first you hear of 28 Named Users, write invoice first. Notice of 30–60 days is the ask so you can reclaim leavers before the snapshot. After that date, unused named seats are already in the bill.

Procr’s ask is 30–60 days’ notice before the charge. Write the notice days and whether silence equals deemed acceptance. Typical mistake: waiting for Finance to “sort it” after the PDF lands. Reclaim leavers before the date — after the snapshot, the hidden 28 is already locked. Do: write notice days or “invoice first.” Don’t: treat the invoice as the start of the argument.

How do you cap, prorate, or walk?

Cap the overage at the contracted unit or a stated premium. Prorate from the add date so a Q4 spike is not a 12-month bill. Walk if unused named seats bill at list, true-down is silent, notice is missing, and only the vendor owns the numbers.

ContractHQ colour: bill overage at 110% of the committed rate. OpenText colour: cap how far the baseline can rise in one recon. BizLeaseCheck : say whether extras are prorated, annualized, billed now, or piled onto renewal. If sales says “you have audit rights,” inspecting the vendor’s books is a different hunt — the customer audit-rights review. Spend counsel — a qualified lawyer, not the chatbot — on that risk: list-price unused seats, a silent true-down, or no notice.

Success bar before you pay: fill the one-page log — unit, unused seats, date, whose numbers, list or contracted, true-down, notice, cap / walk — and point to one sentence that would pause Monday. “Standard true-up” is not that sentence if unused named seats bill at list and the paper has no true-down. Optional: a Checkory first-pass — a first machine pass that extracts clauses before a human reads every page — at document analysis, then a human opens every High flag — a high-severity hit a human must verify — plus the list-price sentence. Do not mark the paper safe.