How to Review Suspension of Services for Non-Payment

Luce, Ops at an 18-person UK SaaS, is about to treat “they can suspend if we are late — standard” as harmless boiler. Finance said yes. Knowing how to review suspension of services for non-payment is a 25-minute kill-switch hunt: write the trigger, demand written notice and a named cure, bar suspend during a bona-fide invoice dispute, then lock restore, data, and credits — or walk Friday.

The packet — the exact files that will be signed — is the vendor CRM MSA (master services agreement, the frame vendors hang order forms on) plus Order Form 1, annual seats prepaid, and Order Form 2, a £4,200 analytics add-on true-up they did not add. English law; exclusive courts of England and Wales. September 2026. Signature is Friday.

Clause 9.1: if any invoice remains unpaid after its due date, Vendor may immediately suspend all Services until Customer has paid all outstanding amounts in full, including late fees. No notice, no cure, no “undisputed,” no dispute bar. Clause 9.2: fees keep running; no service credits while dark. Clause 9.3: restore in Vendor’s discretion after payment in full. AE Slack: “We never actually cut people off.” Billing already opened a query on the true-up.

Market-standard SaaS paper will not suspend you during a reasonable good-faith dispute — and a declined card is a shorter fuse than an unpaid invoice. Salesforce Global MSA 5.4 (checked 21 September 2026): 30 days overdue, 10 days if they charge a card, at least 10 days’ prior notice except a declined card, then they may accelerate and suspend. 5.5: no suspend during a reasonable good-faith dispute with diligent cooperation. Luce’s 9.1 has none of that.

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

Can they cut the prepaid CRM for any overdue invoice?

Circle “any invoice” and “all Services.” The trigger you want is undisputed overdue cash — not a disputed add-on line, and not a credit-card glitch as the whole clause. Log undisputed overdue, any invoice, or declined card. On Friday’s paper the answer is any invoice, immediately, the whole suite.

Do: rewrite the trigger to undisputed amounts on the unpaid SKU. Don’t: treat “they can suspend if we are late” as 2026 form colour. For example, Datawiza MSA (29 July 2026): suspend affected Services if an undisputed amount remains unpaid ten (10) days after written notice. AWS §4.1 (live 21 September 2026) may suspend any portion or all immediately upon notice for a payment breach. Split cash from security. Limit scope to the unpaid SKU.

What does written notice and a real cure window require?

Circle the silence: no days, no named billing inbox, no “billing notice.” Slack is not a clause. Demand written notice to a named billing contact and a named number of days to cure after notice. “We never actually cut people off” is not a cure period.

Do: write days and an inbox. Don’t: invent a statutory notice-day number for England and Wales SaaS paper — there isn’t one on this hunt. Salesforce colour is at least 10 days’ prior notice except a declined card. Datawiza colour is ten (10) days after written notice. Vaquill sample: [10] days’ written notice after an undisputed amount is overdue. BLG: most SaaS forms give a reasonable opportunity to cure an inadvertent admin error.

Can they suspend while a bona-fide invoice dispute is running?

A query on the whole file is not a bona-fide line-item dispute. Silent paper lets them dark production while Finance fights the £4,200 true-up. Salesforce 5.5 and Tyk colour: no suspend while Customer disputes reasonably and in good faith. Luce’s 9.1 has no 5.5.

Do: bar suspension for amounts disputed in good faith if the undisputed rest is paid. Don’t: tell Friday that opening a query already froze the kill-switch. Sprintlaw UK (30 July 2026): it depends on the contract. If the fight is the dispute window itself — written dispute, pay the undisputed slice, resolution clock — that is a different hunt: invoice dispute withhold undisputed. Stay here for whether they can dark you during that fight.

How do you lock restore hours, data access, and SLA credits?

Circle “restore in its discretion after payment in full including late fees.” Discretion is not a clock. Demand named hours after payment in full and cleared funds, export while dark, and no SLA-credit wipe.

Do: write hours, a usable export, and credit a wrongful suspend. Don’t: assume they will “just turn it back on.” Tyk: restore promptly after payment in full and cleared funds; fees remain payable during suspension. In practice, a BACS sent is not cleared funds. AWS §4.2 still bills fees during the dark and wipes service credits for the suspend. Strike the wipe. Keep export while dark.

Is this the Net 30, default-interest, or AUP hunt?

This is the kill-switch after cash is overdue. It is not when Net 30 starts, not the percentage on the overdue sum, and not an AUP abuse rider. Construction pages sit on the same SERP. Stay on access.

If the fight is when Net 30 starts, withhold, or pause, that is a different hunt: payment terms Net 30 review. If the fight is the % on the overdue sum versus the 1998 Act floor, that is a different hunt: default interest statutory late payment. Fees while dark is colour here, not a rate review. If the fight is AUP / suspend-on-suspicion, that is a different hunt: vendor acceptable use policy mid-term. Split cash-suspend from security-suspend. HGCRA 1996 s.112 is a SERP false friend: a contractor’s statutory suspend. Luce is not a builder stopping work.

When to add notice, bar dispute-suspend, or walk?

Keep only if the log shows undisputed overdue, written notice plus named cure days, no suspend during a bona-fide line-item dispute, unpaid SKU only, restore in X hours after cleared funds, export while dark, and no SLA hostage wipe. Otherwise redline 9.1–9.3 or walk.

Walk if that package remains. Success bar: a one-page log plus one Friday pause sentence. “We never actually cut people off” is not that sentence. Workflow: undisputed overdue trigger → written notice + cure → no suspend during bona-fide dispute → restore clock / data / no SLA wipe → not Net 30 / default interest / AUP → add notice / bar dispute-suspend / walk. Optional: upload the same PDF to document analysis for a first-pass (first machine pass extracting clauses). A human still opens clause 9. Verify every High flag (high-severity item). Escalate to counsel — a qualified lawyer, not the chatbot.