Suspension of Service
Suspension of service is a vendor's right to switch off or limit your access for a while, without ending the contract, often for unpaid invoices, policy breaches or security risks.
What is suspension of service?
Suspension of service is the vendor's right to switch off or limit your access for a while without ending the contract. Your account, data and contract stay in place, but you or your users cannot use the product until the problem is fixed.
Suspension is a faster tool than termination. A vendor can use it the same day, while termination for cause usually needs notice and a cure period. That speed is why the triggers and the notice rules deserve a careful read.
Common triggers in SaaS terms are unpaid invoices, breaking the acceptable use policy (the vendor's list of banned uses), and activity that threatens security or other customers.
What it looks like in a vendor's terms
A typical clause reads like this:
Provider may suspend Customer's access if (a) any amount is more than 30 days overdue, after 10 days' notice, (b) Customer's use breaches the acceptable use policy, or (c) Customer's use poses a security risk to the service or others. Provider will restore access once the issue is resolved. Fees continue to accrue during any suspension.
- Overdue amount and notice: how late you must be, and how much warning you get, before payment suspension.
- Policy breach and security risk: triggers that often allow suspension with little or no notice.
- Restore access: the promise to switch you back on.
- Fees continue: you keep paying while switched off.
The real documents we read differ mainly on notice:
- Salesforce (section 5.4) may suspend once a charge is 30 or more days overdue, with "at least 10 days' prior notice that its account is overdue."
- Atlassian (section 10.4) requires at least 10 days' written notice before suspending for late payment.
- HubSpot (section 4.4) gives 10 days after a notice of non-payment, but allows suspension "without notice" for prohibited acts, such as unlawful use or email abuse.
- Zoom (section 12.7) can act "immediately and without prior notice" if payment is more than five calendar days late.
- AWS (section 4) lists security risk, breach, payment default and fraud, effective "immediately upon notice to you," and gives no service credits for the suspension period.
A real change we caught
Venpo flagged a change in which Google Cloud added new triggers for billing, suspension and termination. New triggers matter because each one is a new way to lose access. A softer version of the same idea is throttling: Box can now throttle you before you hit your limit.
Why it matters to you
A suspended tool stops your work, and maybe your customers' work, while the contract still runs. If the tool sits in your product, a suspension can become your outage. You may owe your own customers explanations or credits while still paying the vendor.
Suspension can also hit an innocent account. A single user who breaks a policy, a disputed invoice or a security alert can trigger it. HubSpot does not suspend for non-payment while you dispute charges in good faith, and Salesforce has a similar protection for good-faith disputes. Not every vendor says this.
Late payment is the trigger you control most. A card that expires, an invoice sent to a former employee, or a purchase order stuck in approval can all put you past the deadline. The notice period is your buffer, so a 10-day notice is much easier to live with than none. Zoom's five-day window with no notice leaves almost no buffer.
Finally, suspension can lead to data loss if it runs into termination and the deletion timer starts.
What to check
- List every suspension trigger, and watch for broad ones that leave the decision to the vendor's judgment.
- Note the notice you get for each trigger, especially for payment.
- Check that a good-faith billing dispute does not allow suspension.
- Ask that suspension be limited to the affected users or features, not the whole account.
- Check whether fees and SLA credits continue during suspension.
- Make sure billing contacts on the vendor's side reach someone who reads them.
How Venpo helps
Venpo monitors your vendors' terms, acceptable use policies and billing pages and emails you when a suspension trigger is added or a notice period gets shorter, with a plain-English note on what changed. The change history shows the wording you agreed to.
Frequently asked questions
Can a vendor suspend my account without warning?
For some triggers, yes, if the terms allow it. HubSpot, for example, can suspend without notice for prohibited acts such as unlawful use, while late payment comes with a 10-day notice.
Do I still pay while my account is suspended?
Often yes. AWS, for example, says you stay liable for fees during a suspension.
How do I get my account back after a suspension?
Fix the trigger first: pay the overdue amount, remove the content or user that broke the policy, or close the security issue. Then ask the vendor in writing to restore access, citing the clause that promises it.
What is the difference between suspension and termination?
Suspension pauses your access while the contract continues. Termination ends the contract itself, and often starts the clock on data deletion.
Related terms
Sources
Last reviewed