Summary

  • Google Cloud Marketplace says cancellation of a SaaS subscription with a specified term takes effect at the end of that term. In its one-year example, a buyer who cancels after the second month's bill is charged for the remaining ten months, then renewal stops.
  • The buyer may also need to revoke a service account granted access to the app and remove resources created for it. The order status, payment schedule and access grants require separate checks.

The cancellation menu is easy to find. The exit is dated in the contract.

Google Cloud Marketplace lets a buyer open Your Orders under a Cloud Billing account, choose a SaaS product and select Cancel purchase, Cancel subscription or Cancel auto-renewal. A procurement team can complete that action and still watch the invoice arrive. Google's billing guide states that, for a subscription with a specified period, cancellation takes effect at the end of that period and the customer is billed for the whole term.

The company's example is unusually plain. Buy a one-year subscription. Cancel after being billed for month two. The remaining ten months continue to be billed. At the end of the year, the subscription does not renew. The example is a rule illustration, not a named customer's invoice. It gives finance an exact way to read the button: the action changes the future renewal state while the existing payment commitment keeps running.

This is a market distinction that often gets flattened into one status word. A buyer may have stopped using the software, decided to leave the vendor and clicked the relevant menu item. None of those events rewrites the agreed subscription period. The useful record is the term start and end date, the monthly or upfront payment schedule, the cancellation effective date and the renewal setting. Those dates show which payments are already committed and which future extension has been stopped.

Access has its own trail. Google says that if the buyer granted a service account access to the app, that access must be revoked manually through IAM; resources created for the service account must also be removed. The subscription action is therefore an incomplete exit checklist for an organization that provisioned technical access. The person who can see the order may not be the person who owns IAM grants, and the person who disables access may not control the billing commitment.

Google's documentation identifies the roles at those boundaries. Viewing purchases in Your Orders requires Billing Account Viewer. Choosing a billing plan requires Billing Account Administrator. Service-account cleanup happens in IAM. A cancellation request should move through those owners with one shared record of contract, cost and access state. Otherwise, each team can truthfully report its own task done while the organization still pays or retains an app credential it meant to remove.

Private offers add another date to the buyer's calendar. Google says they commonly run for a set period, such as 12 months, at a custom price. For some pricing models, continued use after that period may move to list price unless a renewal or new offer is arranged. This is a separate question from the remaining payments on an active fixed-term SaaS subscription, but it makes the term end an active commercial decision rather than an archive date.

To determine a specific buyer's exposure, one would need its accepted order, term dates, payment schedule, IAM grants and final billing lines. Google's published one-year example is enough to establish the mechanism. The purchase ends when the contract says it ends; the renewal ends when the cancellation takes effect; technical access ends when somebody revokes it.

Official sources