VAT for AI Agents, LLM Credits and Token Billing in 2026

AI startups are the fastest-growing category of cross-border digital-services sellers in 2026, and almost none of them have figured out their VAT compliance yet. The product surface is unfamiliar to traditional indirect-tax engines: tokens, credits, agent runs, multi-step orchestrations, GPU-second metering, model-routing layers that resell other LLM APIs. The underlying tax rules, fortunately, are not new. Tax authorities are treating AI products the same way they treat any other digital service, with the same place-of-supply principles that have applied since the 2015 EU MOSS reform. This guide covers how VAT applies to the specific shapes AI startups ship, where the edge cases are, and what to do about them.

1. AI products are digital services for VAT

Every major VAT and GST jurisdiction has, since at least 2015, classified electronically supplied services (digital services) as a distinct category with destination-based taxation. The EU defines them in Article 7 of Council Implementing Regulation 282/2011: services delivered "essentially automated and involving minimal human intervention." That definition was written for SaaS, downloads, and online ads. It applies cleanly to AI inference.

Specifically, the following AI product shapes are all digital services for VAT purposes:

• LLM API access billed per token (OpenAI, Anthropic, Google, Mistral, Cohere, your fine-tuned model on your own infrastructure).
• AI agents billed per run, per task, per session, or per orchestration step (autonomous coding agents, research agents, customer support agents).
• AI co-pilots and assistants embedded in other products (a Cursor-style code editor, a Claude-in-Slack integration, a Notion AI feature).
• Pre-paid AI credits and tokens sold in batches (a $50 credit pack, 1M tokens, $1,000 of compute time).
• AI-generated outputs sold as standalone products (generated images, generated audio, transcriptions, summaries).
• Fine-tuning and training services sold as one-off engagements or subscriptions.
• Vector database queries, embedding services, retrieval-augmented generation (RAG) infrastructure billed per call.

None of these are exempt. None are zero-rated. None have a special AI carve-out. The standard rate of the customer's country applies to B2C; the reverse charge applies to B2B with a valid VAT number.

2. Place of supply

The defining VAT question for any cross-border AI product is "where does the supply happen?" Because the supply is electronic and the seller has no physical presence at the customer's location, tax authorities apply the destination principle: the supply is deemed to occur where the customer is, regardless of where the AI infrastructure runs.

This means:

• An AI startup in San Francisco selling LLM API access to a French consumer charges French VAT (20% standard rate). The fact that the inference happens on AWS us-east-1 is irrelevant.
• An AI agent platform in London selling autonomous coding agents to a German consumer charges German VAT (19%). UK seller, German customer, German VAT rate.
• A New York AI co-pilot selling to a UK consumer charges UK VAT (20%) and registers with HMRC under the Non-Established Taxable Person regime.

For B2B sales, the reverse charge applies under Article 196 of the EU VAT Directive (intra-EU) and similarly under domestic rules in the UK, Switzerland, Norway, Australia, Singapore, and most other jurisdictions. The buyer self-accounts for VAT on its return; the seller invoices without VAT but must validate the VAT number via VIES (or HMRC for the UK) and capture it on the invoice. Full explainer: reverse charge VAT explained.

3. The voucher question: when does VAT apply to AI credits?

AI startups commonly sell pre-paid credit packs: a $50 credit balance that the customer spends down over time on inference. The VAT question is whether the supply happens at the moment of credit purchase or at the moment of credit consumption. The answer depends on whether the credit is a single-purpose voucher (SPV) or multi-purpose voucher (MPV) under EU VAT law.

Single-purpose voucher (SPV)

A single-purpose voucher entitles the holder to a single specific supply at a known VAT rate and known place of supply. Most AI credit packs qualify because the credit can only be spent on one type of supply (inference) at one rate (the standard digital-services rate of the customer's country). Under Article 30b of the EU VAT Directive, VAT is due at the moment the SPV is sold, not at the moment it is consumed.

Practical implication: when a French consumer buys $50 of OpenAI credits, French VAT is due on the $50 at the time of sale, even if they consume the credits over the next year. The seller charges 20% French VAT on the $50 purchase.

Multi-purpose voucher (MPV)

A multi-purpose voucher entitles the holder to multiple possible supplies at different rates or in different places. VAT is deferred to the point of consumption rather than sale. AI credits rarely qualify as MPVs because the entire range of available supplies (inference) is a single category at a single rate. The exception is where the credits can be redeemed across multiple distinct services with different VAT treatment (e.g., a marketplace credit that can buy AI inference in country A or physical hardware in country B).

For most AI startups, treating credits as SPVs is correct and operationally simpler. Charge VAT at the moment of credit sale.

4. The reseller question: LLM API resale

A common AI startup pattern is reselling another provider's LLM. Examples: a code-generation product that wraps OpenAI's API; a research agent that calls Anthropic Claude; a multi-LLM router that picks between providers per query. The VAT treatment runs in two parallel layers.

Layer 1: Your input cost. When OpenAI charges you for API usage, that is OpenAI's taxable supply to your business. If you are VAT-registered (and the supply qualifies for reverse charge under your jurisdiction's rules), you self-account; if not, OpenAI charges VAT directly. Either way, the cost has been settled by the time you invoice your customer.

Layer 2: Your resale. When your business invoices the end customer (B2C consumer or B2B buyer), that is a separate taxable supply. The place of supply is the customer's country, the rate is the destination rate, and the VAT is yours to collect and remit. Whether OpenAI charged you VAT on Layer 1 is irrelevant to Layer 2.

Common mistake: treating OpenAI's input VAT as a pass-through and not charging your end customer VAT on the resale. This is not how VAT works. You are a VAT-registered seller (or required to be) on Layer 2 regardless of how Layer 1 is taxed. The amount of VAT you owe on Layer 2 is calculated on the resale price, not the margin.

5. Registration: when does an AI startup have to register?

The most expensive mistake AI startups make is missing the registration trigger. Below the threshold, you are out of compliance from the first sale and accruing penalty exposure even if no tax authority has noticed yet. Major thresholds for nonresident AI startups:

For an AI startup selling B2C globally, expect to need EU OSS plus UK plus 3 to 5 APAC registrations within the first 12 to 24 months of meaningful traction. Full threshold table.

6. The B2B-only escape hatch

AI startups that sell only to B2B customers with valid VAT numbers can sometimes avoid most registrations. Here's the logic: in B2B cross-border supplies, the buyer self-accounts for VAT under the reverse-charge mechanism. The seller does not collect or remit VAT. If 100% of your supplies are B2B reverse-charge, you may not have a registration obligation in the destination country.

The catch: you still need to validate every buyer's VAT number at the time of supply (VIES for EU, HMRC for UK) and keep the validation receipt as evidence. EU case law (notably Mecsek-Gabona) holds the supplier liable for VAT if the buyer's number was invalid when the supply was made and the supplier did not take reasonable steps to verify. The free tax-ID validator handles batch checks.

The B2B-only escape hatch breaks the moment a single B2C consumer buys your product. Most AI startups have at least some self-serve B2C revenue (consumers signing up with a credit card and a personal email), even if they pitch as B2B. The honest assessment is that "B2B only" is rarely actually B2B only.

7. Edge cases specific to AI products

API trials and free tier credits

Free credits given to attract usage are not taxable supplies. No VAT applies because there is no consideration. The moment a customer pays for additional credits, VAT applies on the paid portion only.

Per-second GPU billing

Treated identically to per-token billing: each metered charge is a separate taxable supply at the time of invoicing or payment. Stripe Billing, Chargebee, and Recurly all handle metered billing with VAT applied per charge automatically.

Multi-step agent runs with intermediate failures

If your agent platform charges for failed runs (because tokens were spent on the partial output), VAT applies to the charged amount regardless of whether the run completed. If you refund failed runs, the refund triggers a VAT credit note.

Bring-your-own-key (BYOK) models

If your customer brings their own OpenAI API key and you only charge for the orchestration layer, VAT applies to your orchestration fee, not to the underlying LLM cost (which is OpenAI's taxable supply directly to the customer, not yours).

White-label resale to other AI startups

If you sell wholesale AI infrastructure to other AI startups who resell to end consumers, your supply to them is B2B and reverse-charged in most jurisdictions. They handle the consumer-facing VAT. This is the cleanest revenue line for compliance.

8. What to do this week

• Run an exposure check. Sync your Stripe account to the free exposure dashboard and see every jurisdiction where your AI revenue has crossed a registration threshold. No account required.
• Validate your B2B customer VAT numbers. Bulk-check existing customers using the tax-ID validator. Any customer whose number fails VIES is being reverse-charged in error and you owe destination-country VAT on those supplies.
• Identify your first registration. For most AI startups selling globally, the EU Non-Union OSS scheme is the highest-value first registration because it covers all 27 EU member states with one quarterly return through Irish Revenue. EU OSS scheme explained.
• Set up evidence capture. Make sure your billing system captures the two pieces of customer-location evidence (typically billing address plus payment country) for every B2C charge. Customer location evidence.
• Document your AI product as a digital service. Keep a one-pager describing your product as an electronically supplied service for VAT purposes. This is the document tax authorities will ask for during an audit.

9. Frequently asked questions

10. Related reading

• EU OSS scheme explained
• Reverse charge VAT explained
• Customer location evidence for digital services
• Nonresident SaaS VAT/GST registration thresholds (2026)
• Place of supply rules for digital services
• VAT for SaaS subscriptions, proration and refunds
• VAT & GST questions answered