ZenkenAI
Published: Updated:

Claude Enterprise Contract Guide 2026: Terms, Minimum Seats, SLA & Approval Doc

Claude Enterprise Contract
Table of contents 13 items
Zenken is featured as an OpenAI customer story

If your company is moving from a few experimental Claude seats to a formal, organization-wide rollout, the next step is almost always Claude Enterprise. Unlike the self-serve plans you can buy with a credit card, Enterprise is a custom quote with an annual agreement, a service level guarantee, and security controls that your IT and legal teams will want to review.

This guide explains, in plain business English, how Claude Enterprise contracts are structured in 2026, what the typical minimum seat count is, how billing works, and exactly what to put in your internal approval document so that legal, IT-security, and strategy can sign off without endless back-and-forth.

How Claude Enterprise contracts are structured

Claude (made by the AI company Anthropic) sells its product in two very different ways:

  • Self-serve plans (Free, Pro, Max, Team): you sign up online, pay monthly or annually by card, and start immediately. No salesperson required.
  • Enterprise: a negotiated agreement handled by Anthropic’s sales team. You receive a custom quote, sign a Master Services Agreement (the main contract that governs the relationship) plus an order form (the document listing seat count, price, and term), and you are usually billed by invoice rather than card.

The Enterprise tier is designed for organizations that need centralized control over many users, stronger security guarantees, and a contract their legal department can actually read and amend. If you only need a handful of seats, the Team plan is the right starting point — see our Claude plan comparison for the full breakdown.

Minimum seat count (20 self-serve / 50 sales-assisted)

Enterprise is priced per seat. Per Anthropic’s official support documentation, the minimum is 20 seats for self-serve (online) purchase and 50 seats for a sales-assisted purchase. Organizations buying fewer than that are steered toward the Team plan instead.

PlanWho it fitsMinimum seatsHow you buy
Team StandardSmall teams, departments5Self-serve (card)
Team PremiumTeams needing extra features5Self-serve (card)
EnterpriseCompany-wide deployment20 self-serve / 50 salesSales quote (invoice)

If you are sitting just below the threshold, it is worth asking your sales contact whether the gap can be bridged, since the Enterprise security features are often the real reason companies want to move up.

Why annual contracting is the default

Enterprise agreements are almost always annual (a one-year commitment), and here is why that benefits both sides:

  • Predictable budgeting — finance teams get a fixed annual cost rather than a fluctuating monthly card charge.
  • Better unit pricing — committing for a year typically unlocks a lower per-seat rate than month-to-month would.
  • Procurement fit — most Japanese companies run annual budget cycles and prefer a single yearly purchase order over recurring card payments.

Multi-year terms are sometimes available for larger deployments. If your organization is not ready for a year-long commitment, the Claude pricing guide covers the flexible monthly self-serve options.

Payment options (invoice billing, bank transfer, annual lump sum)

A common blocker for Japanese accounting teams is that self-serve plans only accept credit cards. Enterprise removes that obstacle:

  • Invoice billing — Anthropic issues an invoice, and you pay on standard net terms instead of charging a card.
  • Bank transfer — payment by wire transfer is supported, which suits companies that avoid corporate cards for large amounts.
  • Annual lump sum — the full year is billed at once, simplifying expense recognition.

One practical note for Japanese buyers: Anthropic is a registered “qualified invoice issuer” under Japan’s invoice system (registration number T7700150134388), and from April 1, 2026 it adds 10% Japanese consumption tax (JCT) to all plan prices. This means qualifying corporate buyers can claim the input-tax credit using Anthropic’s qualified invoices; you can verify the number on the National Tax Agency’s qualified-invoice-issuer registry. Confirm the exact treatment with your tax advisor. For all plans, invoices and receipts can be downloaded from Settings → Billing → Invoices in your account.

SLA (uptime guarantee) and credits for downtime

A Service Level Agreement (SLA) is a written promise about uptime — how often the service will be available. Claude Enterprise comes with a negotiated uptime SLA confirmed in your contract. Do not assume a specific headline figure (such as 99.99%); the guaranteed number is set during your agreement. For reference, Anthropic’s published API Priority Tier targets 99.5% uptime, and the public status page shows roughly 99.2–99.6% historical uptime over the trailing 90 days.

Crucially, the SLA is not just a marketing number. If Anthropic fails to meet the contractually agreed level, the agreement typically provides service credits (a partial refund applied to future billing) as a remedy. For comparison, self-serve Pro and Team plans carry a best-effort commitment but no contractual SLA. You can monitor live availability at Anthropic’s public status page (linked below), which is useful evidence to attach to your approval document.

SSO/SCIM, audit logs, and data retention controls

This is the section your IT-security team cares about most. Enterprise unlocks the governance features that make a large rollout safe:

  • SSO (Single Sign-On) — employees log in through your existing identity provider (such as Okta or Microsoft Entra ID), so access follows your corporate password and multi-factor rules.
  • SCIM — automated user provisioning, meaning seats are created and revoked automatically when employees join or leave, with no manual cleanup.
  • Audit logs — a record of who did what and when, which auditors and compliance officers can review.
  • Data retention controls — administrators can set how long conversation data is kept. Importantly, business inputs and outputs on commercial plans are not used to train Claude’s models by default.
  • Role-based admin — fine-grained control over who can manage billing, members, and settings.

What Team cannot do that Enterprise can (matrix)

Both Team and Enterprise are business plans, but the gap matters once you scale. Here is the practical difference:

CapabilityTeamEnterprise
Admin console & billingYesYes
SSO (Single Sign-On)LimitedYes (full)
SCIM auto-provisioningNoYes
Audit logsLimitedYes
Contractual SLANoYes (set in contract)
Custom contract / amendmentsNoYes
Invoice & bank transferCard onlyYes
Dedicated support contactNoYes
Minimum seats520 self-serve / 50 sales

In short, Team gets you a shared workspace quickly; Enterprise gets you the contract, security, and uptime guarantees an enterprise audit demands.

Hand this list to your legal team before they read the Master Services Agreement:

  • Data ownership — confirm your inputs and outputs remain your property and are not used for model training.
  • Confidentiality — verify the mutual non-disclosure terms cover your trade secrets.
  • Liability cap — check the limit on Anthropic’s financial liability and whether it is acceptable for your use case.
  • Term and renewal — note the one-year term and whether it auto-renews; calendar the cancellation notice window.
  • Termination rights — understand how either side can exit and what happens to your data afterward.
  • Governing law — confirm which jurisdiction applies and whether a Japanese-language version or local addendum is available.
  • Acceptable use — align Anthropic’s usage policy with your internal compliance rules.

IT-security checklist

For the IT-security review, confirm each of the following can be satisfied:

  • SSO integration works with your identity provider.
  • SCIM provisioning is configured so leavers lose access automatically.
  • Audit log export meets your retention and monitoring requirements.
  • Data residency and retention settings satisfy your internal policy.
  • The contractual SLA and the public status page are acceptable evidence of reliability.
  • Admin roles are scoped so that billing and membership are separated where needed.

If you also plan to let developers use Claude Code (written “クロードコード”, the command-line coding tool), note it is included with no separate charge and shares the same usage allowance — details in our Claude Code pricing article.

Items to include in an internal approval document

When you write the proposal that goes to your decision-makers, include these sections so approval is fast:

  1. Purpose — the business problem Claude solves and the departments that will use it.
  2. Plan and seat count — Enterprise, with the proposed number of seats (remember the 20 self-serve / 50 sales-assisted minimum).
  3. Annual cost — the quoted per-seat price multiplied by seats, shown as a yearly figure in Japanese yen, including 10% Japanese consumption tax.
  4. Payment method — invoice or bank transfer, annual lump sum, with the tax note above (qualified-invoice-issuer registered, input-tax credit available).
  5. Security summary — SSO, SCIM, audit logs, and the no-training-on-your-data point.
  6. SLA — the contractual uptime guarantee and the service-credit remedy.
  7. Comparison — why Enterprise over Team (use the matrix above).
  8. Rollout plan — the timeline below.
  9. Owner — the internal champion responsible for the project.

Rollout timeline (inquiry to contract to launch)

A typical Enterprise rollout from first contact to live usage looks like this:

StageActivityTypical duration
1. InquiryContact sales, share seat estimate and goalsA few days
2. QuoteReceive custom pricing and order form1 week
3. ReviewLegal and IT-security checklists1–3 weeks
4. SignatureSign agreement and order formA few days
5. SetupConfigure SSO, SCIM, admin roles1 week
6. LaunchOnboard users, run training sessionsOngoing

Plan for roughly four to six weeks end to end, with the legal review usually being the longest step. Starting that review early is the single best way to shorten the whole process.

FAQ

Q. What is the minimum number of seats for Claude Enterprise? A. 20 seats for a self-serve (online) purchase and 50 seats for a sales-assisted purchase, per Anthropic’s official support docs. Below that, Anthropic generally recommends the Team plan, which starts at 5 seats.

Q. Can we pay by invoice instead of a credit card? A. Yes. Invoice billing and bank transfer are standard for Enterprise, which is why many Japanese finance teams choose it.

Q. Is the data we send to Claude used to train its models? A. No. On commercial plans, your business inputs and outputs are not used for model training by default.

Q. What does the Enterprise SLA actually guarantee? A. It guarantees the uptime level set in your contract and provides service credits if uptime falls short. Confirm the specific figure in your agreement rather than assuming a headline number.

Q. Which Claude models can Enterprise users access? A. The current lineup — Claude Sonnet 4.6 (the standard model), Claude Opus 4.8 (the top-tier model released in May 2026), and Claude Haiku 4.5 (the fast, lightweight model).

Q. Is Anthropic a qualified invoice issuer in Japan? A. Yes. Anthropic is a registered qualified invoice issuer (registration number T7700150134388) and adds 10% Japanese consumption tax to all plan prices from April 1, 2026, so qualifying corporate buyers can claim the input-tax credit. Consult your tax advisor for the exact handling. If you run into account or access issues during setup, our Claude troubleshooting guide can help.

References