Google Cloud added new triggers for billing, suspension and termination

The change

On September 2, 2026, Google published an updated version of its Google Cloud Terms of Service, replacing the version dated June 1, 2026. This is the agreement that governs Google Cloud Platform, Google Workspace and Cloud Identity accounts on Google's standard online terms.

Four changes are substantive, and all four sit in the sections on billing, suspension and termination. The rest of the diff is renumbering, plus one new definition that supports the suspension change.

What changed

1. Fee avoidance joins the list of billing triggers (Section 2.1(a)).

The billing section already allowed Google, if it reasonably determined that a customer posed a risk of non-payment, bad-faith dealing or dishonesty, to invoice more frequently or to require the customer to buy credits before using certain services. The updated version adds a fourth trigger: accessing or using the Services "in a manner intended to avoid incurring Fees" or to circumvent service-specific usage limits or quotas. The consequences did not change. The list of behaviors that can set them off did.

2. A full month at peak account count for Workspace and Cloud Identity (Section 2.1(b)).

This is an entirely new paragraph. It applies to the Flexible Plan and the Annual/Fixed-Term Plan for Google Workspace and Cloud Identity, and it introduces the defined term "Customer Malfeasance" for bad-faith dealing, dishonesty or fee avoidance by the customer or any of its end users. When Google reasonably determines that such conduct occurred:

"Google may bill Customer for the Fees for the entire month during which the Customer Malfeasance occurs, for the total number of End User Accounts used at any time in that month, regardless of whether Customer has disabled any End User Accounts."

In plain terms, the bill for that month is calculated at the highest number of accounts active at any point in it, and disabling accounts during the month does not bring it down.

3. Suspension for bank-transfer payers before a payment is late (Section 2.4).

The old clause had one condition: in the event of any late payment, Google may Suspend the Services. The new clause keeps that condition and adds a second one:

"or if Customer is using a Delayed Authorization Form of Payment and Google reasonably determines that Customer poses a risk of non-payment, Google may Suspend all or part of Customer's use of the Services."

A new definition explains the term. A Delayed Authorization Form of Payment is "a form of payment where the transaction authorization does not happen at the time the payment is initiated, such as bank account transfers." Google's billing documentation lists bank accounts as a supported payment method in many countries and describes invoiced accounts as paid by check or bank transfer. Those are the customers the new condition covers.

4. Termination without a cure period (Section 8.3(b)).

Termination for breach used to follow one path: the other party fails to cure a material breach within 30 days of written notice. That path is still there as item (i). Item (ii) is new:

"in the case of a material breach by Customer, Google reasonably determines that the breach is incapable of being cured."

The 30-day window is no longer guaranteed. If Google concludes that a breach cannot be fixed, the agreement can end without it.

One document, three products

The Google Cloud Terms of Service is a single agreement covering Google Cloud Platform, Google Workspace and Cloud Identity, so a change to it lands on all three at once. The same fee-avoidance wording also appears in the Google Workspace Terms of Service, which means a company that never touches Google Cloud Platform but runs its email and documents on Workspace is under the same billing language.

The peak-account rule is the one with a direct line to the invoice, and it is specific to the Workspace and Cloud Identity plans. A seat-based bill that used to reflect the accounts a company kept enabled can, after a finding of Customer Malfeasance, reflect the highest count reached at any moment in the month.

Why this matters

Three of the four changes move a decision point earlier. Suspension no longer waits for a missed payment when the customer pays by bank transfer. Termination no longer waits 30 days when Google decides a breach cannot be cured. Full-month billing no longer depends on which accounts were disabled. In each case the trigger is a determination by Google, which the text describes as reasonable, rather than an event the customer can see on a calendar.

None of this required a new signature or a renewal conversation. It arrived as a revision to a page most customers accepted once, at signup. That is the pattern we described when DigitalOcean made spend commitments non-cancelable: single sentences inside a long document, each with a direct effect on what a customer pays or when. It is also why vendor legal changes are a hidden risk for companies that read terms during procurement and not afterwards.

Potential impact

Companies on Google Workspace, Google Cloud Platform or Cloud Identity under the online terms may want to review whether:

• their Google billing account pays by bank transfer or invoice, since that is the payment path the new suspension condition names

• anyone adds and removes Workspace accounts mid-month in a way that could be read as fee avoidance under the new billing trigger

• their incident and continuity plans assume a 30-day cure window with Google that the text no longer guarantees

• a negotiated agreement, where one exists, overrides these online terms or incorporates them

Answering those questions across a full vendor stack, and keeping the answers current as documents change, is the work of vendor contract monitoring. Our guide on how to monitor vendor terms of service covers a repeatable workflow for exactly this document type.

How Venpo detected it

Venpo monitors the Google Cloud Terms of Service at the URLs where Google serves it and picked up the September 2 revision within a day. The diff isolated the four substantive edits from the surrounding renumbering, and every quote in this article was checked against the inserted and deleted text in the redline and against the live document. The full redline is on the Google Cloud change page, and the monitored documents are listed on the Google Cloud vendor profile.

The change also registered twice, once under each Google URL Venpo tracks for this document, with identical insertions in both copies. Two matching captures at two URLs rule out a crawl artifact, the same check we applied when LinkedIn redrew the line between Recruiter and Sales Navigator.

Business outcome

Teams that caught this change early were able to:

• check which payment method sits on their Google billing account, since bank transfers are now a named suspension condition

• brief finance and IT admins that mid-month account changes on Workspace can be billed at peak count after a malfeasance finding

• update continuity plans that relied on a 30-day cure period

• confirm whether a signed Google agreement takes precedence over the online terms

The alternative is finding out about a new trigger at the moment it fires: a suspended project, a bill at peak seat count, or a termination notice with no cure window.

Key takeaway

Four edits to one page changed when Google can charge more, suspend earlier and terminate faster, and the page covers Google Cloud Platform, Google Workspace and Cloud Identity at once. The wording is precise and the triggers are Google's determinations, which is the kind of clause that reads as unchanged until it is used. As with Perplexity's rewrite and Akamai's recording section, what the document says is what a customer can be held to, and the only reliable way to know when it changes is to be reading it when it does. That is the case for automated monitoring over scheduled manual review.