Do I get a refund for removing a seat mid-period?

No automatic refund. Access ends immediately and the seat is freed for reassignment, but you've already paid for it through the current period — so reassign it rather than buying another.

Why is my bill so much higher than `seats x $25`?

You almost certainly have Premium seats at `$100`/mo (`$80` annual). Check the `Seat Tier` column in Members and the itemized lines on the Billing page.

Does a pending invite cost money before the person accepts?

Yes. Sending the invite reserves and bills the seat immediately. Revoke unaccepted invites from the `Pending` tab to stop the charge going forward.

What's the smallest Team plan I can have?

Five seats. Even with 2-3 active people you are billed for 5.

Who can change seats?

Owners and Primary Owners purchase or reduce seats; Admins can reassign someone between Standard and Premium via the `Seat Tier` dropdown.

Can I get usage-based pricing instead of seats?

Anthropic's API is usage-based. Team and seat-based Enterprise on Claude.ai are seat-based, though you can add extra usage credits separately.

Troubleshooting

Claude Team Billing Doesn't Match Seat Count: Fix

Invoice charges 10 seats but the admin panel shows 7 members. The usual causes: pending invites bill immediately, Premium seats cost 5x Standard, and mid-cycle removals are paid but freed for reassignment. How to reconcile, as of June 2026.

Published: May 23, 2026 Updated: Jun 15, 2026 Author: AI Productivity Guide Team 🌐 查看中文版本

Your Claude Team invoice charges for 10 seats. Organization settings > Members shows 7 active people. Finance wants to know where the other 3 went. This is almost never a billing bug. The fastest reconciliation: open the Pending tab in Members and the Billing page, then compare seat tiers (Standard vs Premium) line by line, not raw headcount. Pending invites bill from the moment you send them, a single Premium seat costs the same as five Standard seats, and a seat you removed mid-cycle was already paid for through the period even though the person is gone. Count those three buckets and the mismatch usually closes to zero.

Pricing and proration rules below are accurate as of June 2026; Anthropic adjusts Team plan mechanics periodically, so confirm against your own Billing page.

What changed in 2026 (read this first)

Two things make today’s invoice different from older Claude Team guidance:

Seats now come in two tiers. A Standard seat is $25/month ($20 on annual). A Premium seat is $100/month ($80 on annual) and ships ~5x the usage plus heavier Claude Code limits. Your invoice lists them as separate lines. A team of “7 people” can easily be 4 Standard + 3 Premium, and the dollar total looks like far more than 7 seats.
Proration is immediate, not deferred. Per Anthropic’s billing docs, adding a member mid-cycle charges the prorated amount right away; removing one gives no automatic refund, but the seat is freed for you to reassign. So a removed person does not spawn a phantom extra line — you simply already paid for that seat this period and can hand it to someone else.

If your old mental model was “removed seats keep billing as a ghost line until renewal,” update it: the seat is paid-through-period and reassignable, which is why the headcount drops but the charge does not.

Which bucket are you in

Symptom	Most likely cause	Where to check
Dollar total way over `seats x $25`	Some seats are Premium (`$100`)	`Billing` page line items; Members `Seat Tier` column
Seat count higher than visible people	Pending invites still occupy seats	Members → `Pending` tab
Headcount dropped but charge didn’t	Mid-cycle removal, already paid through period	Compare removal date to renewal date
Extra fractional charge	Prorated mid-cycle addition	`Billing` line with a partial date range
Phantom members you never invited	SSO JIT / SCIM auto-provisioning (Enterprise)	Members list vs IdP user list
Off by exactly the minimum	Team plan has a 5-seat floor	`Billing` → seat count never drops below 5

Common causes

Ordered by hit rate, highest first.

1. Premium seats cost 5x Standard

This is the most common “the number is way too high” surprise in 2026. One Premium seat ($100/mo monthly, $80 annual) equals the price of four-to-five Standard seats ($25/$20). A 7-person team with 3 Premium seats bills like roughly 19 Standard seats in dollar terms.

How to judge: Organization settings > Members shows a Seat Tier column per person. Count Standard vs Premium separately, then check the Billing page line items — they are itemized by tier.

2. Pending invites occupy seats immediately

Inviting a teammate reserves and bills a seat the moment you send it, before they accept. Three unaccepted invites are three paid seats with no visible active member.

How to judge: Organization settings > Members → the Pending tab. Count those, add active members, and the sum should match the seat count on the invoice.

3. Mid-cycle removal: paid through period, no refund

Removing a member ends their access immediately and frees the seat for reassignment, but Anthropic does not auto-refund the remainder of the cycle. So the admin panel drops to 7 while the invoice still reflects the seats you held and paid for during the period.

How to judge: Compare each removal date in your records to the renewal date. Seats removed after the cycle started were already paid; reassign them rather than expecting a credit.

4. Mid-cycle additions add a prorated line

Adding a seat partway through a cycle charges the prorated remainder immediately. For annual plans the proration is roughly (price x seats x 12) x (remaining days / 365). Add three seats mid-month and you see fractional charges on top of the base.

How to judge: Billing page line items → look for entries with a partial date range or a fractional amount.

5. The 5-seat minimum

Team plans bill a minimum of 5 seats. If you scaled down to 3 active people, you are still charged for 5. This trips up small teams that shrank.

How to judge: Billing → if the charged seat count is 5 but you have fewer people, that is the floor, not an error.

6. SSO / SCIM provisioning is creating shadow seats

If your org uses SSO with just-in-time (JIT) provisioning, every new identity that signs in claims a seat. On Enterprise, SCIM auto-provisioning does the same and, if deprovisioning is misconfigured, leaves seats held by people removed in the IdP. (SCIM is an Enterprise feature; Team relies on SSO JIT plus invite links.)

How to judge: Members list vs your IdP user list. Any Claude member not in the active IdP set is a shadow seat.

7. Billed under a different interval than expected

Annual Team subscriptions charge yearly and show mid-year seat changes as prorated adjustments on the next charge. Monthly subs settle each month. Confusing the two produces “this doesn’t match” every time.

How to judge: Organization settings > Billing → confirm the billing interval (monthly vs annual) and renewal date.

Before you start

Export the member list: Organization settings > Members → Export CSV (gives name, email, role, and seat type).
Open the invoice line items at claude.ai/admin-settings/billing (Organization settings > Billing).
Get your IdP user list if SSO/SCIM is in play.
Decide whether you want to reduce the count or just understand it — these have different next steps.

Information to collect

Invoice number and date range.
Current member count broken down by status (active, pending) and seat tier (Standard, Premium).
Member add/remove dates with timestamps (from the CSV export plus your own offboarding records).
Whether SSO JIT or SCIM auto-provisioning is enabled.
Billing interval (monthly vs annual) and renewal date.
Plan tier (Team vs Enterprise) — the rules differ, and SCIM is Enterprise-only.

Step-by-step fix

Step 1: Reconcile by tier and status, not headcount

Open Billing and read the seat lines. They are split by tier. Then open Members and the Pending tab. Your reconciliation is:

billed seats  =  active Standard + active Premium
              +  pending invites (Standard + Premium)
              +  seats removed this period but already paid
              (with a floor of 5 total)

If that equals the invoice seat count, billing is correct. The dollar total should be (Standard seats x $25 or $20) + (Premium seats x $100 or $80) plus any prorated adjustments. If those reconcile, you are done. If not, file a ticket (Step 6).

Step 2: List and revoke stale invites

Organization settings > Members → Pending tab. Anyone who hasn’t accepted in 7+ days is probably not coming. To cancel:

Pending tab → menu button (right of the invite) → Remove from team

Each revoked invite frees a seat going forward. It does not refund the current period’s prorated charge, but it stops the bleed.

Step 3: Reassign, don’t repurchase, freed seats

Because removals don’t refund but do free the seat, reassign before buying more. To move someone between tiers (e.g., demote an idle Premium seat to Standard):

Organization settings > Organization → find the member → Seat Tier dropdown → Standard

To reduce total seats once they’re empty: Organization settings > Organization → Manage under “Total seats” → click - for that tier. Note: only Owners and Primary Owners can purchase or reduce seats; Admins can reassign tiers.

Step 4: Audit SSO / SCIM-provisioned accounts

If using SSO or (Enterprise) SCIM:

1. Export the current member list from Claude (Members → Export CSV)
2. Export the current active-user list from Okta / Entra ID / Google Workspace
3. Diff — any Claude member not in the IdP active set is a shadow seat

Remove shadow seats with menu button → Remove from team. For Enterprise, fix SCIM deprovisioning rules in the IdP so this stops recurring; for Team SSO, tighten the group that gets JIT-provisioned.

Step 5: Confirm interval and project the next invoice

Organization settings > Billing → confirm interval (monthly vs annual) and renewal date. The Projected total shown on the Billing page excludes tax and is the cleanest forward estimate. Validate it against:

next invoice ~= (active Standard at renewal x $25 or $20)
              + (active Premium at renewal x $100 or $80)
              + (any invites still pending at renewal)
              + (prorated additions during the upcoming cycle)

If the projected total is still higher than expected after cleanup, escalate.

Step 6: File a billing ticket if numbers still don’t reconcile

If after the tier check, invite cleanup, and SCIM audit the invoice still doesn’t match by a non-trivial amount, contact Anthropic support with:

Subject: Team invoice seat-count mismatch — invoice [NUM] dated [DATE]

Organization: [name / ID]
Invoice [NUM] charges [X] seats: [n] Standard + [m] Premium.
Members panel shows: [active] active, [pending] pending, seat tiers [n2] Standard + [m2] Premium.
Removed this period: [list with dates].
Expected charge: [X-expected] seats.

Please clarify the [X] - [X-expected] = [delta] difference.

Attach the Export CSV member list.

Step 7: Set up an internal monthly reconciliation

Calendar a 15-minute seat reconciliation for the day before each renewal. Confirm pending invites, idle Premium seats, and offboarded members before the charge lands.

How to confirm it’s fixed

Re-run Step 1 after cleanup; active + pending + paid-removed should equal the billed seat count, and the tier-weighted dollar math should match the Billing total.
The Projected total on the Billing page should now equal what you expect for next cycle.
Wait for the next invoice and confirm the seat count and tier split match the Members panel exactly.
Cross-check with finance that the Standard and Premium line items match their forecast.
For SSO/SCIM teams, confirm with your IdP admin that provisioning and deprovisioning are bi-directional with Claude.

Long-term prevention

Make one person (usually IT or RevOps) accountable for Claude Team seat management.
Default new members to Standard; promote to Premium only on demonstrated need — it is the single biggest cost lever.
Set a reminder 2 days before each renewal to audit seats and the Pending tab.
Add Claude Team to your offboarding checklist so removed people’s seats get reassigned, not left paid-and-idle.
For SSO/SCIM teams, document and tighten the IdP group that maps to Claude seats.
Read each invoice line item by tier, not just the total — the tier split is where the dollars hide.

Common pitfalls

Comparing today’s active headcount to last month’s invoice. They never match; the invoice is a historical, tier-weighted snapshot.
Multiplying everyone by $25 and ignoring that Premium seats cost 4-5x more.
Expecting a refund when you remove a seat mid-period — there isn’t one; reassign the freed seat instead.
Forgetting the 5-seat minimum on small teams.
Counting only active members and excluding the Pending tab.
Assuming SCIM applies on Team — it is an Enterprise feature; Team uses SSO JIT and invite links.

FAQ

Do I get a refund for removing a seat mid-period? No automatic refund. Access ends immediately and the seat is freed for reassignment, but you’ve already paid for it through the current period — so reassign it rather than buying another.
Why is my bill so much higher than seats x $25? You almost certainly have Premium seats at $100/mo ($80 annual). Check the Seat Tier column in Members and the itemized lines on the Billing page.
Does a pending invite cost money before the person accepts? Yes. Sending the invite reserves and bills the seat immediately. Revoke unaccepted invites from the Pending tab to stop the charge going forward.
What’s the smallest Team plan I can have? Five seats. Even with 2-3 active people you are billed for 5.
Who can change seats? Owners and Primary Owners purchase or reduce seats; Admins can reassign someone between Standard and Premium via the Seat Tier dropdown.
Can I get usage-based pricing instead of seats? Anthropic’s API is usage-based. Team and seat-based Enterprise on Claude.ai are seat-based, though you can add extra usage credits separately.

Tags: #Claude #Troubleshooting #billing