Do I need to charge tax for my AI app? Sales tax and VAT rules for AI founders selling globally

If you’re selling an AI app, AI agent, chatbot, or any other AI-powered software, there’s a good chance you’ll need to charge sales tax, VAT, or GST somewhere.

That’s because tax authorities don’t treat AI as a brand-new product category. Instead, they classify it under existing rules for software-as-a-service (SaaS), digital services, or electronically supplied services. In other words, your app might be built with the latest AI models, but from a tax perspective, it’s usually just another digital product.

Unfortunately, this catches many founders off guard.

Some assume AI is still too new for governments to have figured out how to tax it. Others believe the tax they paid to OpenAI or Anthropic covers their own obligations. And an increasing number of founders launch apps built with tools like Lovable and assume the built-in payment system must also handle tax compliance.

None of those assumptions are true.

If you’re selling AI functionality under your own brand, you’re responsible for understanding where your app is taxable, when you need to register, and who is liable for collecting and remitting those taxes.

The good news is that the rules become much easier to navigate once you understand a few concepts.

In this guide, you’ll learn:

• Whether AI apps are taxable
• When you need to charge sales tax, VAT, or GST
• Why your customers’ location matters more than yours
• The difference between income tax and sales tax
• How software founders simplify global tax compliance as they grow

TL;DR: Do I need to charge tax for my AI app?

In most cases, yes. Tax authorities treat AI apps as SaaS or digital services, not a new category, so the same sales tax, VAT, and GST rules already on the books apply to you.

• In the US: you owe once you cross a state’s economic nexus threshold, commonly $100,000 in annual sales. Below that, you’re usually not required to collect, though a handful of states, like Illinois, exempt certain AI/SaaS delivery models outright.
• Outside the US: there’s often no threshold at all. The EU and UK apply VAT from your first sale to a consumer, so one international customer can create an obligation before you’ve thought about it.
• Selling to a business customer: the reverse charge mechanism can shift the VAT obligation to them, but only once you’ve validated their VAT number, not just their email domain or company size.

The safest assumption isn’t that your AI app is tax-free — it’s that it’s taxable until you’ve confirmed otherwise, since Illinois, Kentucky, Texas, and the EU have all already ruled on this, just not the same way.

What VAT, GST, and sales tax actually mean

VAT, GST, and sales tax are consumption taxes charged to the end customer. A key difference from income tax is that you collect it at the point of sale and remit it to the tax authority; thus, you’re the collection agent, not the payer.

The tax is based on the buyer’s location. For example, if someone from Germany buys your AI app, you charge German VAT, even if you’re in California.

B2C vs. B2B treatment

• When you sell to a consumer (B2C), you collect VAT and remit it.
• When you sell to a VAT-registered business (B2B), however, the reverse charge mechanism applies in most jurisdictions. In this scenario, the business buyer handles the tax instead of you. This only works when you validate their VAT registration number at checkout.

The rule itself is simple. The tricky part is making sure you have the documentation to apply it correctly.

While reviewing customer invoices, Daniel Yeromka, founder and CEO of HostZealot, realized his team had been treating some customers as B2B without validating their VAT status:

There was a big difference between ‘this customer looks like a business’ and ‘is VAT reverse charge applicable to this deal.’

Today, HostZealot only applies B2B VAT treatment after collecting and validating the customer’s VAT number at checkout.

US sales tax and economic nexus

Economic nexus is the sales threshold that ties your business to a state’s tax authority. Cross it, and you must register, collect tax on every new sale, and file returns in that state — starting immediately, not once you get around to it.

If you’re US-based and selling internationally, crossing this threshold doesn’t pause your EU VAT obligations, or the other way around — you’re tracking both at once.

That’s why so many AI founders are surprised to discover they’re responsible for tax compliance much sooner than expected.

Why this catches AI app sellers off guard

Modern AI apps can be built in a weekend and attract paying customers worldwide before the founder has thought about accounting. The technical barriers to launching have collapsed, but the regulatory ones haven’t.

Much of the confusion comes from a few common misconceptions.

Myth #1: “AI isn’t taxable because it’s too new.”

Tax authorities don’t build new systems for new technology — they apply the ones that already exist. To most tax authorities, an AI chatbot or coding copilot is just another digital service; the model running behind it doesn’t change how the sale is taxed.

Most US states fit AI software into existing categories: SaaS, prewritten software, or data processing. Most other countries classify it as an electronically supplied service under existing VAT or GST rules.

Myth #2: “OpenAI already charged me tax.”

When your AI provider charges VAT or sales tax on your API bill, that tax covers one sale — from them to you. When you sell subscriptions to your own customers, that’s a separate taxable transaction, and your provider has no part in it.

A wholesaler charging tax on the coffee beans it sells to you doesn’t erase the café’s obligation to charge tax when it sells coffee to customers. AI works the same way: your provider is responsible for its sale to you, you’re responsible for yours to your customers.

Myth #3: “My app builder handles tax.”

Processing a payment and handling tax compliance are not the same job. Lovable, Bolt, and Replit let founders launch products without writing code, and their bundled payment options make it feel like everything’s handled.

A payment button charges a card. It doesn’t register you for VAT in Germany, track your economic nexus in California, or file your quarterly returns. Those stay yours until you choose a solution that explicitly assumes them.

See also: How to monetize your Lovable app: Add paid plans without writing a single line of code

The international trap

The biggest surprise hits on a founder’s first international sale. US founders expect a revenue threshold before tax kicks in — that’s how the US works, not how most of the world does.

The EU has taxed digital services from the first euro since 2015, and an AI app is no exception. It is a digital service like any other, taxed under the same non-union OSS rules as every SaaS seller.

A solo founder with five customers in France or Germany can already owe EU VAT while still months or years from tripping US economic nexus. This is one of the biggest reasons AI founders end up non-compliant without realizing it.

Bogdan Nicholas, co-founder of VINspectorAI, an AI-powered vehicle inspection tool, wasn’t thinking about international tax when he launched:

I was focused on the product, not whether selling to a customer in Germany made me liable for VAT there. We’d been making sales for months before I realized ‘digital services’ have their own tax rules… When we finally got proper advice, the potential back-taxes and penalties were north of $20,000.

Nicholas found out after roughly 200 sales across three EU countries, then had to retroactively register for VAT in each one.

Discovering a VAT obligation often raises another question: “Isn’t this already covered by the taxes I pay on my business income?” The answer is no.

Income tax and sales tax aren’t the same bill

Paying income tax on your AI app’s profits doesn’t excuse you from collecting sales tax — they’re two separate obligations, calculated differently and owed to different places.

The IRS requires you to report every dollar of income regardless of whether a 1099 (the tax form Stripe, app stores, and other platforms send you (and the IRS) once your payouts cross a reporting threshold) shows up.

Below that threshold, no form arrives, but the income is still taxable.

You can owe income tax on a strong year with zero US sales tax exposure, and you can trigger EU VAT on a single sale while still years from your first US economic nexus threshold on that same revenue. Confusing the two is one of the most common mistakes among first-time AI founders, and the table above is the fastest way to keep them straight.

Once you separate these obligations, the next challenge is understanding that even sales tax rules are not universal.

Why AI tax treatment depends on the state, not the technology

The same AI app can land in three different tax categories depending on which state your customer sits in. States classify AI services using categories written for SaaS, prewritten software, or data processing — not for AI specifically — and those categories rarely line up.

The state line matters more than what your AI agent does under the hood. Two products solving the exact same problem can land on opposite sides of a taxable line simply because one reads as SaaS under Illinois’s rules and the other reads as an information service under New Jersey’s.

This is also where misclassification creates real exposure. An AI agent that compiles data, ranks it, and hands the customer a report looks a lot like a taxable information service, even if you built it as “just a SaaS tool.”

Most states also expect you to document how you classified each sale, not only what you charged, so keep that reasoning on file the same way you’d keep any other compliance record.

The same rules vary globally. The EU and UK may require VAT registration from your first sale, while other countries only require it after you pass a revenue threshold.

AUD 75,000 and CAD 30,000 sound small next to the US’s $100,000, and an AI app with modest traction in either market can cross them faster than founders expect.

And tax is only one piece of the cost equation.

The true cost of AI apps has three layers — most founders only price for one

The invoice your customer receives is only part of the total cost of selling an AI app. Most founders price for the first layer and get blindsided by the other two once they scale.

Layer one: API costs

Every call to OpenAI, Anthropic, or another model provider shows up on your books as a deductible business expense, and it needs to be tracked separately from revenue, not netted against it.

Fragmented AI stacks, where one vendor handles the model, another handles vector storage, and a third handles hosting, make costs harder to track and create more opportunities for unexpected charges.

Layer two: The sales tax or VAT you owe when you sell to your own customers

This is the layer the rest of the guide covers, and it’s the one many vibe coders miss entirely until a state notice or an EU customer’s invoice request forces the question.

Layer three: The compliance overhead of staying registered, calculating rates, and filing

According to the FinOps Foundation’s 2026 State of FinOps report, 73% of enterprises say their AI costs have exceeded original projections,, and tax administration is part of why: every new state or country you sell into adds its own filing calendar on top of the API bill.

Sales tax compliance for AI founders: What Freemius handles as merchant of record

The founders who stop losing sleep over multi-state tax rules hand the entire liability to a merchant of record and keep the rest of the stack for themselves. A merchant of record doesn’t just calculate the rate: it takes on the legal responsibility for collecting, filing, and remitting sales tax and VAT everywhere you sell, across every plan change, trial conversion, and renewal.

Freemius pairs that tax liability transfer with the rest of the commercial layer an AI app actually needs:

• Subscription management that handles upgrades, dunning, and renewals automatically, so a plan change doesn’t also become a manual tax recalculation
• Customer portal where buyers update their own VAT ID and pull EU VAT-compliant invoices, without a support ticket landing in your inbox
• Affiliate platform for tracking commissions if other builders promote your AI app, with payouts and attribution handled in one dashboard
• Software licensing that protects paid AI features behind real access control, not just a paywall on the pricing page

None of it requires you to become a part-time tax analyst on top of running an AI company. The liability, the licensing, the invoicing, and the payouts move to Freemius — what stays with you is the product.

A quick decision path for your AI app

If you’re feeling overwhelmed, don’t try to learn every tax rule at once. Handling this yourself comes down to four ongoing jobs:

1. List every state and country where you already have paying customers, not just where your company is registered.
2. Check how each state classifies your specific app — SaaS, data processing, or information service — instead of assuming “AI” fits one category everywhere.
3. Track cumulative US revenue and transaction count monthly against each state’s nexus threshold, since many states now trigger nexus on revenue alone.
4. Register for VAT the moment you take on a non-US customer — or before, if you can see one coming. The EU and UK apply VAT from the first sale with no minimum threshold, so there’s no grace period to register after the fact.

Or you can hand all four to a merchant of record like Freemius and stop tracking them yourself.

An MoR takes over the classification calls, the threshold monitoring, the registrations, and the filings, across every state and country you sell into. The trade-off is straightforward: keep the paperwork and the control that comes with it, or hand over the liability and get that time back for the product.

Either path works. The only bad option is ignoring the obligations until tax authorities or customers force you to deal with them.

See how Freemius handles tax compliance end to end.

FAQ — Tax compliance for AI app sellers

Do I need to charge sales tax on an AI subscription app?

In most states, yes. AI subscriptions are typically taxed the same way as SaaS, unless your state specifically exempts cloud-delivered software, as Illinois now does.

Do I need to charge tax for my AI app if I only have a few customers?

In the US, usually not yet, since most states require you to cross a nexus threshold first. Outside the US, potentially yes immediately, since the EU and UK apply VAT from your very first sale.

Do I need to charge VAT if I’m based in the US and sell to Europe?

Yes. VAT is based on the customer’s location, not yours, so a US company selling to an EU consumer owes EU VAT starting with that first sale.

What counts as a “digital service” or “electronically supplied service”?

Any service delivered automatically over the internet with minimal human involvement — software, apps, and AI tools that customers access online without a physical product being shipped.

Do I charge tax to business customers the same way as consumers?

No. For B2B sales to VAT-registered businesses, the reverse charge mechanism usually shifts the tax obligation to the buyer, provided you validate their VAT number at checkout.

Does OpenAI or Anthropic collect sales tax for me?

No. The tax they charge you covers their sale to you — your sale to your own customers is a separate taxable transaction you’re responsible for.

Does using an AI app builder like Lovable or Bolt mean tax is handled for me?

No. Built-in payment tools process the charge, but they don’t register you for VAT, monitor your nexus, or file your returns.

What’s the revenue threshold before I need to register for sales tax?

Most US states set it at $100,000 in annual sales, though the exact rules vary by state. Outside the US, thresholds are often lower or nonexistent — the EU and UK tax from the first sale.

Is there a state that doesn’t tax AI services?

Yes. Illinois ruled in September 2025 that cloud-delivered AI tools aren’t taxable, treating them like SaaS. Other states, like Kentucky, tax AI-powered applications directly, so this varies state by state.

Can a merchant of record handle AI app tax compliance?

Yes. A merchant of record like Freemius takes on full legal responsibility for classifying, collecting, filing, and remitting sales tax and VAT on your behalf, across every state and country you sell into.

Can I just block sales from high-compliance countries?

You can, but you’re leaving revenue on the table. EU, UK, and Australia represent a significant portion of global SaaS buyers. Blocking them limits your addressable market more than the merchant of record fee would cost.

Does using Stripe Tax eliminate the need for a merchant of record?

No. Stripe Tax calculates and collects the correct tax rate at checkout, but you remain the seller of record. You’re still responsible for registering in each jurisdiction, filing returns, remitting the tax, and responding to audits. Stripe Tax reduces the manual calculation work, but it doesn’t transfer legal liability.

How do I know if my AI product is classified as SaaS or a data processing service?

Most jurisdictions classify hosted AI tools as SaaS or electronic services, which are taxable. If you’re uncertain, consult a tax advisor in the jurisdictions where you sell. The classification affects your rate and your filing obligations.