Do You Charge Sales Tax on an AI Subscription?

Whether you charge sales tax on an AI subscription depends on three separate questions that most founders collapse into one: where your customer is, whether what you sell is taxable there, and whether you have crossed the threshold that obliges you to register. You can be selling a fully taxable product to a customer in a taxing jurisdiction and still have no obligation, because you are under the registration threshold. Answer the three in order and the picture usually resolves in an hour.

This is not tax advice, and thresholds move. What follows is the structure the question actually has, with the current headline numbers from official sources so you know what you are checking.

Question one: where is the customer, not where are you

The instinct is to reason from where your company is registered. For digital services sold to consumers, that is usually the wrong starting point.

In the EU, business-to-consumer supplies of telecommunications, broadcasting and electronically supplied services are taxed where the customer resides, not where the supplier is. The European Commission's place of taxation guidance sets this out directly. A software subscription sold to a private individual in Portugal is a Portuguese VAT question, whatever your own address says.

In the US, the equivalent shift happened with the 2018 Wayfair decision, which allowed states to require sales tax collection from remote sellers with no physical presence, based on economic activity in the state instead. The Sales Tax Institute maintains a readable FAQ on economic nexus if you want the case history.

So: build your customer list by jurisdiction before you do anything else. That list is the input to both remaining questions.

Question two: is an AI subscription taxable there

This is where AI subscriptions get genuinely ambiguous, and where a lot of confident internet advice is wrong.

In the EU the answer is simple: electronically supplied services are within scope of VAT, and the rate is the customer's country rate. There is no meaningful category argument to have.

In the US there is no single answer, because SaaS taxability is decided state by state. Some states tax software as a service, some tax digital goods but not SaaS, and some tax neither. The practical consequence is that your product can be taxable in one state and not in the neighbouring one, on identical transactions.

Three specifics worth deciding explicitly, because they change the classification:

• Is the customer buying access, or an output? A subscription to use a tool and a per-report deliverable can land in different categories in the same state.

• Is there a human service component? Bundling consulting or setup into the subscription can change how the whole invoice is treated, in either direction.

• Are you selling to businesses or consumers? In the EU this decides who accounts for the VAT. In the US it decides whether a resale or exemption certificate applies.

Write your answer down with the date you checked it. When someone asks in eighteen months why the invoice is structured this way, that note is the entire audit trail.

Question three: have you crossed a threshold

You can be selling a taxable product into a taxing jurisdiction and owe nothing, because thresholds exist specifically so that tiny cross-border sales do not create registration obligations everywhere.

The EU figure is a single aggregate across all your other member states, introduced on 1 January 2019. Under it, the place of supply stays where you are established, which is why many small European sellers charge only their home rate for a long time.

The US number is the South Dakota model that most states copied. Several have since modified it, some raising the dollar figure and some dropping the transaction count entirely, so treat 100,000 or 200 as the shape rather than the answer for any specific state.

What to do once you cross

In the EU, the mechanism is the One Stop Shop. You register in one member state and file a single return covering B2C sales into all the others, applying each customer's national rate. The Commission's OSS portal is the primary reference. The alternative, registering separately in every country where you have a customer, is what OSS exists to spare you.

In the US, there is no equivalent single filing. You register per state, collect at the local rate, and file per state on that state's schedule. This is the point where most solo founders stop doing it manually.

Getting the plumbing right early

Two decisions cost almost nothing now and are painful to retrofit:

1. Capture and store customer location at signup, with whatever evidence your payment processor gives you. Reconstructing where customers were two years ago is close to impossible.

2. Decide whether your listed price includes tax or excludes it, and say so on the pricing page. Changing that later reads as a price rise to every existing customer, which is a much worse conversation than getting it right at launch.

Most payment providers will calculate and collect the right rate once you tell them where you are registered. What they will not do is decide whether you should be registered. That part stays yours. If you are still designing the billing side, our guide to adding payments to an AI-built app covers where these fields belong.

The honest summary

For a small AI product selling mostly at home, with a scatter of international customers, you are very often below every threshold that matters and the correct answer is your home country's normal rules. The risk is not that you are secretly non-compliant on day one. The risk is that you cross a threshold quietly in month fourteen, notice in month twenty-six, and owe backdated tax you never collected.

So the useful habit is not solving this perfectly today. It is putting one calendar reminder every quarter to check revenue by jurisdiction against the two numbers in the table above.

FAQ

Do I charge VAT on an AI subscription to an EU consumer?

If you are over the EUR 10,000 cross-border threshold, yes, at the customer's national rate, and OSS is the filing mechanism. Under it, your home country's rules generally apply.

Is SaaS taxable in the US?

It depends on the state. There is no federal answer, and states differ on whether software as a service, digital goods, or neither are taxable. You have to check per state where you have nexus.

Does an AI subscription count as a digital service or a professional service?

In the EU, a self-serve subscription is an electronically supplied service. Where a human does substantive work as part of the package, the classification can change, which is one reason to keep consulting on a separate invoice line.

What happens if I never registered anywhere?

The exposure is backdated tax plus interest and penalties in each jurisdiction where you crossed a threshold. It is a solvable problem when caught early and an expensive one when caught late, which is the entire argument for the quarterly check.

Should I raise prices to cover the tax?

That is a pricing decision, not a tax one. The cleaner move is deciding tax-inclusive versus tax-exclusive display before launch. Our post on how to price an AI product covers the trade-off, and the wider set of models lives in our AI monetization strategies guide.