The Claude Team invoice says you were charged for 10 seats this month. The admin panel shows 7 active members. The numbers don’t match and finance is asking why. This is almost never a billing bug — it is one of three predictable accounting behaviors: seats removed mid-cycle continue to bill through the period end, mid-cycle additions are prorated and roll into next invoice, and pending invites count as occupied seats. Reconcile by reading the invoice line items against the seat audit log, not by counting current members.
Common causes
Ordered by hit rate, highest first.
1. Seats removed mid-cycle still billed through period end
Anthropic bills seats on a per-period basis. Removing a member mid-cycle does not retroactively refund — that seat stays on the invoice until renewal. The admin panel reflects the current count (7), but the invoice reflects max seats during the period (10).
How to judge: Audit log → look for seat removals in this billing period. Count: (current active) + (removed mid-cycle) usually equals the invoice count.
2. Pending invites occupy seats
Inviting a teammate reserves a seat immediately, even before they accept. If you sent 3 invites that have not been accepted, those are 3 paid seats with no visible “member.”
How to judge: Admin → Members → look for status “invited” or “pending.” Count those + active members.
3. Mid-cycle additions add a prorated line item
Adding a seat on day 12 of a 30-day cycle adds (30-12)/30 of one seat’s price to this invoice. If you added 3 seats partway through, you may see fractional charges in addition to the base.
How to judge: Invoice line items → look for entries labeled “prorated” or with a partial date range.
4. Billed under a different cycle than expected
Annual Team subscriptions charge yearly but show seat changes mid-year as prorated adjustments on the next charge. Monthly subs charge differently. Confusing the two leads to mismatched expectations.
How to judge: Settings → Billing → confirm billing interval (monthly vs annual). Annual plans accumulate small adjustments.
5. SSO / SCIM provisioning is creating shadow seats
If your team uses SSO with SCIM auto-provisioning, every new identity in your IdP gets a seat automatically. People removed in the IdP may still hold seats if SCIM deprovisioning is misconfigured.
How to judge: Admin → Members → look for seats with no recent activity. Cross-reference against your IdP user list.
6. Workspace owner is counted as a separate billable seat
In some plans the workspace owner / admin holds a billable seat even though it looks “free” in the UI. Easy to miscount by excluding them.
How to judge: Total seats on invoice = (admin) + (members). Confirm whether your plan includes the admin gratis.
Before you start
- Export the invoice line items from Settings → Billing → Invoices.
- Pull the audit log for the same date range (member added / removed events).
- Get your IdP user list if SSO/SCIM is in play.
- Decide whether you actually want to reduce the count, or just understand it — these have different action steps.
Information to collect
- Invoice number and date range.
- Current admin panel member count and statuses (active, invited, suspended).
- Audit log events: member additions and removals with timestamps.
- Whether SSO / SCIM auto-provisioning is enabled.
- Billing interval (monthly vs annual).
- Plan tier (Team, Enterprise) — these have different rules.
Step-by-step fix
Step 1: Reconcile by counting events, not current state
Open the invoice. Note the seat count it charges for. Then open the audit log for the same date range and count:
seats at period start (S0)
+ seats added during period (A)
- seats removed during period (R) — but these still bill until period end
= invoice count should equal max(S0 + A, S0)If audit log + math = invoice count, billing is correct. If they don’t match, file a ticket.
Step 2: List and cancel stale invites
Admin → Members → filter “invited.” Anyone who has not accepted in 7+ days is probably not coming. Revoke those invites:
Members → select pending invite → RevokeEach revoked invite frees a seat going forward (not retroactively for this invoice).
Step 3: Audit SSO / SCIM-provisioned accounts
If using SSO with SCIM:
1. Pull current member list from Claude
2. Pull current active user list from Okta / Azure AD / Google Workspace
3. Diff — any Claude member not in IdP is a shadow seatRemove shadow seats in Claude admin. Verify SCIM deprovisioning rules in the IdP so this stops happening.
Step 4: Confirm plan and billing interval
Settings → Billing → check:
- Plan tier (Team monthly, Team annual, Enterprise)
- Billing interval and renewal date
- Whether admin holds a billable seat
Annual plans look “off” each month because prorated adjustments accumulate; reconcile against the full annual sum, not month-to-month.
Step 5: Project next invoice
Based on current member count + any pending changes:
Next invoice = (active members at next renewal date)
+ (any invites still pending at renewal)
- (refunds for over-paid seats, if any)
+ (prorated additions during this upcoming cycle)If the projection is still higher than expected, escalate.
Step 6: File a billing ticket if numbers still don’t reconcile
If after audit + invite cleanup + SCIM check the invoice still does not match your math by a non-trivial amount, file a ticket:
Subject: Team invoice seat-count mismatch — invoice [NUM] dated [DATE]
Workspace: [name / ID]
Invoice [NUM] charges for [X] seats.
Our audit log for the period shows: [S0] start, [A] additions, [R] removals.
Expected charge: [X-expected] seats.
Please clarify the [X] - [X-expected] = [delta] seat difference.Attach the exported audit log CSV.
Step 7: Set up an internal monthly reconciliation
Before next cycle, calendar a 15-minute “seat reconciliation” the day before renewal. Removes the next month’s surprise.
Verify
- Re-export invoice and audit log after cleanup; the math should now reconcile.
- Wait for next billing cycle and confirm the new invoice matches your seat count exactly.
- Cross-check with finance that the line items match what they expected.
- Confirm with your IdP admin that SCIM provisioning and deprovisioning is bi-directional with Claude.
Long-term prevention
- Make a single person responsible for Claude Team seat management (usually IT or RevOps).
- Set a calendar reminder 2 days before each renewal to audit seats.
- Standardize a “remove on offboarding” checklist that includes Claude Team.
- For SSO/SCIM teams, document the IdP group that maps to Claude seats — keep it tight.
- Cancel invites that have been pending more than 7 days automatically (or manually weekly).
- Read each invoice line item, not just the total — line items expose what is actually billed.
Common pitfalls
- Comparing today’s active count to last month’s invoice. They will never match — the invoice is a historical snapshot.
- Forgetting that removing a seat does not refund the current period.
- Assuming SCIM deprovisioning is enabled by default — it usually is not.
- Counting only “active” members and excluding pending invites and suspended accounts.
- Renewing on annual + adding seats mid-year, then being surprised at the prorated bump.
FAQ
- Do I get a refund for removing a seat mid-period? No. Seats bill through the end of the period regardless of removal date.
- When does a pending invite stop counting as a seat? When the invite is revoked, expired, or accepted (accepted just converts pending → active, still billed).
- Are admins free? Depends on plan. Some Enterprise plans include admin gratis; Team typically does not.
- Can I get a usage-based plan instead of seats? Anthropic’s API has usage-based pricing. Team / Enterprise on Claude.ai are seat-based.
- How precise are the line items? To the cent. If you disagree by more than a rounding-cent, file a ticket.
Related
- ChatGPT Team seat not active
- Claude beginner guide
- Claude Projects guide
- Claude prompt best practices
- Claude tool call stuck on pending
Tags: #Claude #Troubleshooting #billing