Claude licenses for the public sector: how to buy them and what to consider

In October, two public bodies asked us for help buying Claude licenses: one in Ecuador and one in an Argentine province. Their questions were alike: which plan, how it is paid and what paperwork is needed. No Anthropic page answers that for a Spanish-speaking state, so we built this guide from the official sources read on November 11, 2026.

The order we recommend: first define who will use it and for what, then choose the plan, and only then open the purchase file. Procurement rules vary by country, by body and by province. We do not cite them here because we did not verify them one by one: each body has its own regime and the last word belongs to its legal team.

The figures below come from claude.com/pricing and the help centers for Team and Enterprise (updated September 1, 2026), as of Nov 11, 2026. Prices exclude taxes and may change.

In practice: a group of 5 to 30 people who want to try it starts on Team. A unit that already knows it needs auditing or automatic user provisioning with SCIM starts on Enterprise. If the body needs an invoice instead of a card, the route is sales-assisted, which means talking to sales and starting from 50 seats. For the full Team versus Enterprise comparison, see our note on Claude Team and Enterprise for 20 to 150 users.

Three facts frame the conversation with your treasury office. Team is paid by card. Self-serve Enterprise accepts card or ACH, and activation waits for payment, which with ACH can take up to five business days. Invoicing appears only on sales-assisted Enterprise.

What we cannot state: purchase orders and payment terms (net terms) are not in the official sources we reviewed. If your file requires them, the question goes to Anthropic sales in writing, and the answer goes into the file.

On the receipt, Anthropic’s documentation on Team invoices says it is emailed to the organization’s billing address and can be downloaded from Organization settings > Billing. It is an Anthropic receipt. To understand how it is recorded, our guide on contracting and invoicing Claude for a company (in Spanish) covers Argentina and Mexico, with sources from each tax authority.

Anthropic is a company based abroad. For a public body that brings three concrete things to settle before choosing a plan:

The underlying question, whether the body’s procurement regime allows buying from a foreign supplier and by which procedure, is not ours to answer. Each body and each province has its own regime. What we can say is where to look: the portal of Ecuador’s Servicio Nacional de Contratación Pública (SERCOP), which hosts the Sistema Oficial de Contratación Pública, and COMPR.AR, the electronic procurement system of Argentina’s national administration, according to its own terms. An Argentine province may run a different system. Open the current rules for your jurisdiction with your legal team.

There is another route for bodies that already have a cloud contract: Anthropic states on its government page that the Claude API is available through Amazon Bedrock and Google Cloud Vertex AI. That is API access, not Claude seats, and it is a separate contract with different terms.

When IT or security reviews a new tool, the same questions come up. Public sources answer these, by plan:

One caution: Anthropic’s government page details certifications such as FedRAMP, which are US programs, and notes that Claude Enterprise does not hold that authorization. They do not replace your country’s requirements.

This is what appears in the Claude Code data usage documentation, checked on Nov 11, 2026. Under commercial terms (Team, Enterprise and API), Anthropic does not train generative models on code or prompts, unless the customer chooses to share data in an improvement program. Standard retention on those plans is 30 days, and zero data retention is enabled per organization for eligible accounts; it does not come with standard Enterprise.

On where processing happens: the Enterprise help center lists US-only inference (US-only inference) and customer-managed encryption keys in your own cloud. We did not find a residency option in Ecuador or Argentina. If your body requires data to stay in the country, this may be a blocker, and it is better that it surfaces before purchase.

The part that does not depend on Anthropic is yours: what information gets loaded. Citizens’ personal data and classified information have their own rules in each country, and what enters the tool is the body’s decision. To start, use public or non-sensitive internal information.

Buying big before knowing what the tool will be used for is costly to undo. A bounded pilot gives evidence for the file: which tasks, who, how many seats and how success is measured.

A reasonable pilot has a group of a few people, two or three concrete tasks (for example summarizing internal regulations, drafting reply templates or tidying spreadsheets), non-sensitive information, a named owner and a closing criterion agreed beforehand. A Team plan is enough for that. How to design the evaluation is covered in our note on how to evaluate an AI training pilot. No note can guarantee a result: the pilot exists to find out whether it works in your body.

Buying licenses is not adopting the tool. A team that does not know what to ask, what to review and what not to upload leaves seats idle or uses them with risk. Our training starts from the body’s real tasks and its information rules. Format details are in Claude training for companies.

Duotach implements Claude and trains teams. It does not sell or resell licenses, does not issue Claude invoices and has no commercial partnership with Anthropic. The body contracts the license directly with Anthropic. This note is general information with official sources, not legal, tax or procurement advice. For the legal framework of your purchase, ask your legal team.

We did not verify the public procurement rules of each country and province, purchase order and payment-term conditions, or the taxes applicable to the purchase.