Slack Credits an Idle Seat, Atlassian Bills It Anyway: What Each Vendor Lets You Cut Mid-Contract

You usually can't. We read the billing pages and terms of 11 vendors (the table has 13 rows because Google and Microsoft are split by plan or account type), and only two say a removed seat is credited mid-term: Slack on self-serve plans and Google Workspace on its Flexible plan. The rest apply the cut at the next billing period or at renewal, and several need written notice first. So the mid-contract job is to free the idle seats now, put each vendor's deadline on a calendar, and shrink the count at renewal.

We re-read every page on October 20, 2026. The Microsoft MOSA row is our reading of Microsoft's invoice rules, not a vendor statement, and it is not one of the two. This is billing detail, not legal advice, and a signed order form overrides all of it.

What each vendor does with a removed seat

Short answer

Only two say a removed seat is credited mid-term: Slack on self-serve plans and Google Workspace on its Flexible plan.

ShowAll rowsCredited mid-termNot creditedAuthor’s readingNotice or act-by statedNotice not in this article13 of 13 rows

✓ Credited mid-term✕ Not credited◐ Author’s reading: our reading of the vendor’s invoice rules, not a vendor statement, and not counted in the two.Hatched cell: this article does not cover it, which is not the same as the vendor having no rule.

Vendor and plan	Removed seat credited mid-term?	When the cut applies	Notice / act-by
Slack, self-serve	✓YesProrated credit. Credit only, no cash value	The next day after deactivation, or once a member is inactive over 28 days	Not in this article
Google Workspace, Flexible	✓Yes"your payments are prorated" when you add or remove users	Payments are prorated when you add or remove users	Not in this article
Google Workspace, Annual	✕No"Only when you renew the contract. Until then, you pay for all purchased licenses."	Only when you renew the contract	Before the renewal day, with the renewal option set
Microsoft 365, MOSA account	◐Microsoft does not call this a credit. Read as yes, and not counted in the two	Previous charge deducted on the next invoice, prorated charge added	Not in this article
Microsoft 365, MCA account	✕No after day 7Removal only within seven days of buying or renewing	Only within seven days of buying or renewing	Within seven days of buying or renewing
Atlassian, monthly	✕NoBilled on the maximum users in the period	The user count on the last day sets the next month	Before the last day of the period, since that day's count sets the next month
GitHub	✕NoApplies next billing cycle, no proration	Next billing cycle	Not in this article
Notion	✕No"you will not receive credit"	The paid count is synchronized to your member count each time a billing period starts	Before the next billing period
Figma	✕No"billed for all seats," assigned or not	On annual plans, you remove the unassigned seats at renewal	Order form: banner 60 days out; changes "must typically be completed before the 30-day renewal period"
HubSpot	✕NoCurrent invoice not adjusted	Scheduled for the next billing period	At renewal, on a new order form: "You may downgrade your Subscription Services at your next renewal date upon completion of a new Order Form."
Asana	✕NoReflected on the Renewal Date	Reflected on the Renewal Date	Written notice "at least thirty (30) days prior to the end of the then-current Term"
Zoom	✕NoTakes effect at the end of the billing cycle	Takes effect at the end of the billing cycle	Order form: written notice of "termination or modification" at least 30 calendar days before the next Renewal Term
Salesforce	✕No"quantities purchased cannot be decreased during the relevant subscription term"	Not decreased during the relevant subscription term	Written notice at least 30 days before the term ends to stop the automatic one-year renewal, unless the order form differs

Swipe the table sideways. The vendor name stays in place.

Confirm the seat is really idle

Use the vendor's own number, because each defines idle differently. Slack's is 28 days without use. Google's Last sign in column is approximate, with a data lag of "a couple of hours up to 3 days". Microsoft's usage reports cover 7, 30, 90 or 180 days and typically take 24 to 72 hours to appear, and last activity means "any intentional activity". GitHub calls an enterprise user dormant after 30 days, but Git operations on private repositories do not count as activity, so someone who only pushes code to private repositories can show as dormant. Atlassian counts each named user "whether they are logged in or not". For vendors that publish no idle window, we would use 90 days from the single sign-on log. That is our choice, not a vendor figure.

Check which paper you are on

Several rules apply only to self-serve accounts. Slack's credit policy covers plans "purchased via the Slack website and paid for by credit card or self-serve invoicing." Asana's section 4.2, which holds the reduction clause, opens with "Unless otherwise specified in an Order Form." Salesforce's no-decrease clause begins "Except as otherwise specified herein or in an Order Form." Zoom says that with custom pricing or a signed contract you "may not be able to reduce your licenses directly." Microsoft says that if you bought through a Cloud Solution Provider partner, you contact the partner.

So a reduction right, if you have one, is written on your order form, not on the vendor's help page. Read the form before you plan anything.

Freeing a seat is not always lowering the bill

Atlassian's own example shows the gap. A monthly customer pays $18 per user for 10 users, removes 3 on day 5, and the page says "there won't be any deductions, refunds or credits from your billed user quantity." The bill stays at $180. The user count on the last day sets the next month, so next month starts at 7 users, or $126 by our arithmetic. Waiting cost $54. The freed seats stay usable for new hires until the period ends.

Other vendors need a second step after unassigning:

• Figma: "You are billed for all seats on your plan, whether they are available (unassigned) or unavailable (assigned to a user)." On annual plans, unassigning alone changes nothing: you remove the unassigned seats at renewal.
• HubSpot: "Removing a seat from a user unassigns the seat, but you'll continue to be billed for it. Remove the unassigned seat to adjust billing." The removal then waits for the next billing period.
• Zoom: "Before you can reduce licenses, you must first unassign them from users."
• Microsoft 365: you can't reduce while every license is assigned.
• GitHub: "Remove seats is only displayed when you have unassigned seats available."

Atlassian, monthly: remove 3 of 10 users on day 5

Billed this month (10 users at $18, no deductions, refunds or credits)$180

Next month (7 users at $18)$126

Waiting cost (3 users at $18)$54

$0$50$100$150$200

Atlassian, monthly: remove 3 of 10 users on day 5

Billed this month (10 users at $18, no deductions, refunds or credits)	$180
Next month (7 users at $18)	$126
Waiting cost (3 users at $18)	$54

Traps in the fine print

Google suspended users still bill. The help page says "Suspended users are charged the same as active users." Delete them, or move them to a Cloud Identity or Archived User license. On the Annual plan, set Renewal options to "Auto-renew my contract with fewer licenses" before the renewal day. Google then renews "for the number of user accounts you have that day."

Salesforce can re-price a smaller renewal. Section 11.2 says a renewal with a lower subscription volume "will result in re-pricing at renewal without regard to the prior term's per-unit pricing." A smaller count can mean a higher price per seat. Get the price for the lower count in writing before the notice date.

HubSpot has a floor. Seats can't go below the subscription's minimum, and HubSpot's example is a subscription that includes five seats, which can't be reduced to four.

Add-ons bill by the month. Google says that in some cases, if you remove an add-on license during the month, "we charge you for the full month for that license."

What the Google plan choice costs

At Business Starter, Google's compare page lists $100.80 per user per year on Flexible and $84 on Annual. Flexible costs 20% more per seat (100.80 divided by 84). It pays off only if you average fewer than 83.3% of the seats you would have committed to annually.

Take 100 Annual seats with 20 idle all year: $8,400 for 80 working seats, or $105 each. Flexible for those 80 would be $8,064, a $336 saving. It only works if you know the 20 are idle before you commit.

Google Workspace: 100 Annual seats with 20 idle all year

Annual, 100 seats (80 working, $105 per working seat)$8,400

Flexible, 80 seats$8,064

Saving$336

$0$2,500$5,000$7,500$10,000

Google Workspace: 100 Annual seats with 20 idle all year

Annual, 100 seats (80 working, $105 per working seat)	$8,400
Flexible, 80 seats	$8,064
Saving	$336

Slack's math is simpler. At $8.75 per member per month, applying Slack's formula to a member deactivated on day 10 of a 30-day month gives ($8.75 divided by 30) times 20 days, or $5.83 of credit. Slack's page does not say whether a 28-day inactivity credit counts from the flag or from last use, so we would not budget on it.

Dates for the calendar

If you miss the window, GitHub's example shows the price. An organization pays for 50 seats annually on May 20, removes 20 on September 30, and the change applies on May 20, about seven and a half months later.

Ask for the cut in writing

Apart from Slack's self-serve policy and Google's Flexible plan, none of the public pages or terms we read says a mid-term true-down is available. Zoom's section 2.2 says contractually available changes take effect "only upon the commencement of your next Renewal Term," and Figma and Salesforce bar decreases during the term. A mid-term reduction is a negotiated exception that has to appear on the order form.

At renewal, send the reduced seat count and the price you expect for it in one email, before the notice date.

If you cancel instead of cutting

Refund windows are short. Microsoft MCA gives a prorated refund only within seven days after start or renewal. Google Annual says "Must pay full commitment (even if you cancel early)". HubSpot's terms make payment obligations "non-cancelable" and bar refunds of unused fees for the current term. Atlassian says "Cloud renewals and upgrades cannot be refunded." Notion says it will refund the full amount if you downgrade within three days of signing up for monthly billing or 30 days of signing up for annual billing.

After any change, check the next invoice against the new seat count. Atlassian's deactivation page says "We'll stop billing your organization for this account," which sits oddly beside its no-credit rule, so we would trust the invoice over either page.

How we read the pages

Vendors read

11 vendors' billing pages and terms. The table has 13 rows because Google and Microsoft are split by plan or account type.

Pages re-read

October 20, 2026

What counts as "credited"

Only what a vendor says. Slack on self-serve plans and Google Workspace on its Flexible plan are the two that say a removed seat is credited mid-term.

Microsoft MOSA row

Our reading of Microsoft's invoice rules, not a vendor statement, and not one of the two.

Idle window

For vendors that publish no idle window, we would use 90 days from the single sign-on log. That is our choice, not a vendor figure.

Whose paper

A reduction right, if you have one, is written on your order form, not on the vendor's help page.

Limits

This is billing detail, not legal advice, and a signed order form overrides all of it.

Disclosure: AccountMade is built by The Plain Works. AI agents researched and drafted this piece.