Verified decision guide
Claude Enterprise Billing: Current and Legacy Seats
Identify which Enterprise contract bills Claude Code: current Enterprise, legacy Chat / Chat + Claude Code, or Standard / Premium seats.
Direct answer · Enterprise subscription authentication
The seat label determines whether usage is included
Identify the Enterprise seat cohort before budgeting: the current Enterprise seat includes Claude Code access but no usage; all consumption is billed separately. Legacy Chat and Chat + Claude Code also separate seat fees from usage. Legacy Standard/Premium seats include an allowance; only Premium includes Claude Code access. Renewal and funding paths depend on the contract.
Open Organization settings → Organization and match the seat label below. The current public price is $20/seat/month, billed annually, plus usage. A customer's legacy fee, negotiated price and renewal date remain Unknown — account_dependent.
Match the contract before estimating a bill
| Enterprise cohort / seat | Seat fee and usage | Claude Code access |
|---|---|---|
| Current Enterprise | Public $20/user/month, annually billed. Seat fee covers access; consumption is charged separately from the first token. | Included with the seat; usage still needs funding and available spend limits. |
| Legacy usage-based: Chat | Contract-specific annual seat fee; usage is separate. | No Claude Code entitlement from this seat. |
| Legacy usage-based: Chat + Claude Code | Contract-specific annual seat fee; usage is separate. | Yes. |
| Legacy seat-based: Standard | Contract-specific flat seat fee includes an allowance; enabled usage credits cover continuation. | No Claude Code entitlement from this seat. |
| Legacy seat-based: Premium | Contract-specific flat seat fee includes an allowance; extra usage is billed at month-end. | Yes. |
Both legacy families are closed to new contracts and transition to the single Enterprise seat at the next contract renewal. Do not replace that account-specific event with a site-wide migration date. Team Standard/Premium is a separate plan; its funding rules are in the organization usage-credit guide.
Identify how the organization pays for consumption
| Billing channel | Funding | If work stops |
|---|---|---|
| Current self-serve Enterprise | Prepaid credits shared by the organization. | An authorized billing manager checks both balance and spend limits; buy credits or adjust the binding limit as appropriate. |
| Sales-assisted Enterprise | Monthly invoice in arrears. | Check spend limits; an exhausted prepaid balance is not the default explanation. |
| Enterprise through AWS Marketplace | Monthly in arrears, following the documented sales-assisted billing behavior. | Identify the Marketplace contract before applying self-serve top-up instructions. |
| Legacy seat-based Enterprise continuation | Enabled usage credits, charged on actual usage at month-end. | The owner checks included allowance, enabled continuation and applicable spend limits. |
API rates remain model- and feature-dependent. The Enterprise billing article specifies a 1.1× rate for US-only inference on Opus 4.6, Sonnet 4.6 and later models. An access seat, a funded balance and a spending cap answer three different questions.
- Record the seat label and whether the contract is current usage-based or legacy seat-based.
- Confirm self-serve, sales-assisted or AWS Marketplace billing from the organization's contract and billing settings.
- Match the user's Claude Code entitlement, funding and spend limits. Use an Owner, Primary Owner or a custom role with Billing set to Can manage for current Enterprise billing changes.
- Confirm Claude Code authentication. An
ANTHROPIC_API_KEYcan bill the separate API account; use/statusand the authentication and extra-usage guide to identify that path. - Before renewal, obtain the applicable seat quote and consumption terms. Do not carry the legacy included allowance into a current Enterprise forecast.
Derived example: 10 current seats at the public list price imply $2,400/year in seat fees before usage, tax and any negotiated adjustment. That arithmetic establishes no token allowance or total annual bill. Public documents cannot determine your contract's price or renewal date.
Sources and freshness
- Claude Enterprise current and legacy billing
- Claude Enterprise seat access matrix
- Claude current public Enterprise price
- Claude Team and legacy Enterprise usage credits
- Claude Code API-key authentication priority
TraceCheck maintainer: review weekly and before renewal or purchasing advice. Recheck seat names, public price, funding channels, access and inference qualifications against the customer's contract; there is no universal legacy renewal date.
For current plans and allowances, see the product guide.