Subscription Renewal Date vs the Cancel-By Date

A renewal date of 14 October 2026. A contract asking for thirty days' notice. A calendar entry for 14 September 2026, which is a Monday, and which is wrong by four days.

The reason it is wrong sits in a different section of the same agreement from the one that gave you the thirty days. Renewal clauses say how much notice. Notices clauses say when a notice counts as given. Those are two separate questions, and vendors answer them in two separate places: in the agreement quoted below, three pages apart, under headings that do not cross-reference each other.

Five dates, and the renewal date is the least useful of them

The date everyone writes down is the term end. It is the one date on this list that you cannot act on, because by the time it arrives every decision has already been made for you.

Four of those five are earlier than the renewal date. On a self-serve monthly plan they can collapse into a single day. On a signed annual agreement bought through a reseller they can spread across six weeks, which is why "we have until October" is an answer that needs a follow-up question.

Thirty days before what, and does sending count as giving?

Salesforce publishes its Main Services Agreement openly, and the version reviewed here is stamped SFDC-MSA, June 1, 2026. Section 11.2, "Term of Purchased Subscriptions", reads:

Except as otherwise specified in an Order Form, subscriptions will automatically renew for additional one year terms, unless either party gives the other written notice (email acceptable) at least 30 days before the end of the relevant subscription term.

Clear enough on its own. Thirty days, written, email accepted. Now section 12.10, "Manner of Giving Notice", three pages later in the same document, on page 11 of 17:

Except as otherwise specified in this Agreement, all notices related to this Agreement will be in writing and will be effective upon (a) personal delivery, (b) the second business day after mailing, or (c), except for notices of termination or an indemnifiable claim ("Legal Notices"), which shall clearly be identifiable as Legal Notices, the day of sending by email.

Read the carve-out in (c) slowly. The day-of-sending rule for email is written with termination notices taken out of it. Section 11.2 says email is an acceptable form; 12.10 sets out when a notice becomes effective and puts termination notices on the delivery-based routes rather than the send-based one. Whether a non-renewal notice under 11.2 is a "notice of termination" for the purposes of 12.10 is a question for whoever signs agreements where you work, holding both clause numbers. This page does not interpret contracts, and neither should the person doing the migration.

What is not ambiguous is the arithmetic if the delivery route applies. Take the 14 October 2026 renewal, and take it as the term-end date on the Order Form rather than the day a charge appears. Thirty days earlier is Monday 14 September. If the notice has to be delivered rather than merely sent, and mailing is effective on the second business day after posting, then the last day that letter can go into the post is Thursday 10 September 2026 — Friday counts as one business day, Monday as the second. Post it on Friday 11 September and it becomes effective on Tuesday 15 September, one day past the window, for a renewal five weeks away.

The failure mode here is not carelessness. It is reading the renewal clause, finding an explicit allowance for email, and reasonably concluding that the job is finished the moment the message leaves your outbox. The allowance is about form. The deadline is about effect. Send the email and put the same text in the post on the same day, well before the deadline, and the question stops mattering.

The reminder arrives on the day the window shuts

Google Workspace's page on renewing an Annual/Fixed-Term contract states the default plainly: "If you don't do anything, your subscription automatically renews on a one year term." It also promises warning: "You'll get a notification 30 days and 3 days before your renewal date."

Hold that against a contract shaped like Salesforce's. Thirty days before renewal is not advance warning under a thirty-day notice period. It is the deadline itself, arriving as an email, on the last day it could possibly be useful, and only if somebody is reading the billing contact's inbox that afternoon. The three-day reminder is a receipt, not a warning.

There is also a widespread assumption that some law guarantees a reminder and an easy cancel button. For a business subscription in the United States, mostly not. California's automatic renewal law is written around a "consumer", which Business and Professions Code section 17601 defines as "any individual who seeks or acquires, by purchase or lease, any goods, services, money, or credit for personal, family, or household purposes". A company buying project management software is not inside that definition.

At federal level the position is unsettled rather than protective. The FTC's amended Negative Option Rule, the one reported everywhere as "click to cancel", was vacated by the Eighth Circuit in 2025, before its compliance date, in Custom Commc'ns, Inc. v. FTC, 142 F.4th 1060. The Commission's own rule page now lists a Federal Register notice from 12 February 2026 headed in part "Revision of the Negative Option Rule ... To Conform These Rules to Federal Court Decisions", and an Advance Notice of Proposed Rulemaking dated 13 March 2026 (both checked 28 August 2026). That February notice put the older, narrower prenotification rule back into the Code of Federal Regulations; the March one asks for comment on whether to amend it. The rule everybody read about is gone, in other words, and what replaces it is at the question-asking stage. Treat any reminder you receive as a courtesy setting the vendor chose, revocable, and never as the thing your deadline depends on.

Three buttons that are not the same button

The word "cancel" does not map to one mechanic, and on some vendors it is not even the word on the control.

Atlassian's help article for ending a cloud subscription is titled Deactivate a subscription, and the menu path it gives is more actions > Deactivate. The consequence is not immediate and not term-aligned either: "When you deactivate a subscription, it's deactivated 15 days after the end of your current subscription period." Two extra weeks of access after the period ends, which is useful if you are still pulling exports and misleading if you are counting the days until the account is gone.

Google Workspace splits the same idea by plan. Not renewing an Annual/Fixed-Term contract leads to suspension rather than closure — "If you chose the option not to renew your contract, your service will be suspended" — and the page describes restoring it by turning auto-renewal back on. Cancelling mid-term is a different act with a different bill attached: on the Annual/Fixed-Term Plan "you'll be charged for the remaining balance of your contract", and the cancellation page carries the blunt warning that after cancellation "your users' Google Workspace data will be deleted and can't be restored."

So there are at least three distinct outcomes hiding behind similar labels: the term runs out and nothing renews, the account is switched off some days after the term, or the service stops now and the money is still owed. Write down which one your click produces before you click it. The order in which that click has to happen relative to your exports is the whole subject of the pre-cancel checklist.

The same deadline governs staying, if you want to stay smaller

The renewal window is not only the exit. It is usually the only moment the quantity can move downward, which makes it a decision deadline rather than a cancellation deadline.

The Salesforce agreement puts the restriction in the fees section, not the term section, where almost nobody looks for it. Section 5.1 states that except as otherwise specified, "quantities purchased cannot be decreased during the relevant subscription term". Google Workspace files its version in a table cell rather than in prose: on the plan comparison page, the Annual/Fixed-Term column allows users to be removed only at contract renewal, and the row underneath answers leaving early with "Must pay full commitment (even if you cancel early)."

Then there is the sting in the tail of that Salesforce renewal clause, one sentence after the thirty days:

Notwithstanding anything to the contrary, any renewal in which subscription volume or subscription length for any Services has decreased from the prior term will result in re-pricing at renewal without regard to the prior term's per-unit pricing.

Shrinking is allowed, at renewal, and it can cost you the rate you were on. Forty seats at last year's price and thirty seats at this year's list price are not obviously the cheaper and the more expensive option in that order. Whether that trade is worth making is the arithmetic in why your bill is higher than the pricing page says, and it needs doing before the notice deadline rather than after, because both choices run through the same date.

Where the authoritative date actually lives

Section 11.2 defers the term to somewhere else entirely: "The term of each subscription shall be as specified in the applicable Order Form." Not the billing screen. Not the invoice. A signed document that lives in somebody's email or a shared drive, and that has to be found before any of the arithmetic above can start.

Three specific mismatches are worth checking for, because each produces a confident wrong answer:

• Next payment date is not term end. An annual commitment billed in monthly instalments shows a payment date every month. None of them is the renewal date.
• Co-termination moves things quietly. Products added mid-term are commonly aligned to the master term end, so the renewal date on the newest line item is inherited, not its own.
• Bought through a reseller means the deadline is theirs. Your notice goes to the partner who holds the agreement, on their timetable, and the vendor's self-serve screens may not reflect it at all. Find out who the counterparty actually is before drafting anything.

Locating the clause numbers in your own agreement is a fifteen-minute job with a search box, covered step by step in reading a SaaS agreement for exit terms. Every later decision is scheduled backwards from what that search turns up, which is why the 30-day switch runbook spends its first day on the date and nothing else.

What the notice says, and what a real confirmation looks like

Keep it short and make it unmistakably a notice rather than an enquiry. Name the agreement and the Order Form or subscription ID. State that you are giving notice of non-renewal, effective at the end of the current subscription term. Give the term-end date you believe applies, in full, with the year.

Then ask for one thing back: written confirmation of the effective end date and of the last day data can be exported from the account.

That reply is the point of the exercise. A response that says "your request has been received" is not a confirmation of anything. A response containing a date is. If the date the vendor sends back is not the date you sent them, you have found the disagreement while there is still time left to argue about it, which is a considerably better week to find it than the one after the card is charged.

---

Verified against Salesforce, Atlassian and Google documentation, and against California and FTC sources, on 28 August 2026. The renewal, notice-delivery and quantity clauses are quoted from the Salesforce Main Services Agreement, version stamped SFDC-MSA, June 1, 2026, sections 5.1, 11.2 and 12.10. The 15-day figure comes from Atlassian's Deactivate a subscription article. The automatic-renewal default, the reminder schedule and the suspension behaviour come from Google Workspace's Renew your Annual/Fixed-Term Plan contract page, with the cancellation consequences from Cancel Google Workspace and the licence-reduction rule from the plan comparison page. The definition of "consumer" is California Business and Professions Code section 17601, and the current status of the federal rulemaking is taken from the FTC's own Negative Option Rule page together with the Federal Register notice it lists, Revision of the Negative Option Rule ... (12 February 2026), which carries the Eighth Circuit citation.

Section numbers move when an agreement is re-versioned, and a support article can be rewritten overnight with nothing to mark the change, so read every clause number and day count above as a description of those documents on the date in bold rather than as a description of your contract. Yours is the one that governs. Three vendors appear here because they publish these particular terms in the open, where a reader can check a sentence against its source in the minute they read it — that is a property of the documents, not a ranking of the companies. Nothing above is legal advice, and the notice-delivery question in particular belongs with whoever signs agreements where you work. Where a quotation has drifted from its source, the contact form reaches me and the page goes back up with a new verification date.