What Happened in Indiana (in Human Words)

Indiana DOR reviewed a company that offered generative AI servicesprimarily a chatbot that could
write, analyze, code, and solve problems. Customers accessed the chatbot through the provider’s website or a free app,
and could also use an API to integrate the chatbot’s capabilities into their own applications.

The key facts: customers did not download the chatbot software, did not receive any software or
programming code, and did not get a permanent ownership interest in software. They were paying for access to a
hosted service that produced outputs.

Based on those facts, Indiana concluded the charges were for a servicenot a taxable transfer of
prewritten computer software and not a taxable transfer of specified digital products.
Result: not subject to Indiana sales/use tax.

This isn’t Indiana declaring “all AI is tax-free forever.” It’s Indiana saying:
“Given this delivery model and these facts, this looks like a service under our existing framework.”
In sales tax land, details aren’t “details.” They’re the whole movie.

Indiana Sales Tax Basics: What Gets Taxed (and What Usually Doesn’t)

A fast way to understand Indiana’s approach is to think in three buckets:

1) Tangible personal property (including certain software)

Indiana imposes sales tax on retail transactions involving tangible personal property. Indiana law and
guidance generally treat prewritten computer software as taxable when it’s transferredespecially when
it’s delivered electronically as a download (think paid apps, desktop software, or downloadable plugins).

2) Specified digital products (only certain types, and only in certain circumstances)

Indiana’s “specified digital products” category is narrower than many people assume. It’s essentially:
digital audio works, digital audiovisual works, and digital books.
And Indiana’s framework focuses on when the seller transfers the product to an end user and grants a
right of permanent use that isn’t conditioned on ongoing payment.

3) Services (generally not taxed unless specifically enumerated)

Here’s the part that often surprises non-tax people: in Indiana, most services are not taxable unless the
state specifically lists them as taxable. So the game becomes: is the customer buying “stuff” (taxable), or buying a
service experience (usually not taxable)?

The chatbot ruling basically says: this AI offering, delivered by remote access with no software transfer and no permanent
digital product, fits the “service” bucket.

SaaS vs. Downloaded Software: Indiana’s Bright Line

Indiana’s guidance draws a meaningful distinction between:

• Downloaded software (often taxable): the customer receives software on their device, even if the license is time-limited.
• Remotely accessed software / SaaS (often not taxable): the customer accesses software hosted elsewhere, typically through the internet,
  without downloading the underlying software.

In fact, Indiana guidance explains that prewritten computer software that is remotely accessed over the internet
(including cloud computing) is not considered a retail transaction and therefore is not subject to Indiana sales/use tax,
so long as the customer doesn’t download it.

Why does this matter for AI? Because most AI chatbots are, operationally, a flavor of “access the model in the cloud,”
not “install a program.” That delivery model is doing heavy lifting in the ruling.

One nuance: Indiana also warns that if you provide a paid app/applet in a separate transactioneven if it merely “lets you access”
the remotely hosted servicethat separately sold download can be taxable. Translation: “free companion app” and “paid companion app”
can live very different tax lives.

Why a Generative AI Chatbot Looks Like a Service

A generative AI chatbot subscription is weird in a way that helps Indiana’s analysis: customers aren’t really buying a “copy”
of something. They’re buying ongoing capabilitya continuously available system that processes prompts and returns outputs.

Key factors Indiana relied on

• No software delivered (electronically or physically). Customers weren’t handed code, installers, or downloadable programs.
• Remote access only. The chatbot was accessed via a web interface, a free app, or an API.
• No permanent ownership interest. Access ended when payment stopped; customers didn’t walk away with a permanent product.
• Not a specified digital product. The service did not fit Indiana’s narrow categories like digital books, digital audio works, or movies.

Put differently: the customer isn’t paying for a “digital good” in the sense Indiana taxes; they’re paying for an ongoing service
that happens to be delivered using software behind the curtain.

That’s why the ruling is especially relevant to vendors selling:
AI chatbot subscriptions, AI copilots, AI writing assistants,
AI coding tools, and API-based AI access.

What Could Flip the Result to “Taxable”

If you’re an AI vendor, the ruling is helpfulbut it’s not a magic cloak of invisibility. Small product decisions can change the tax answer.
Here are common “taxability tripwires” to watch for.

1) You sell a downloadable component (even a “helper”)

If a customer pays to download an app, desktop agent, plugin, or appletand it’s sold separatelyIndiana guidance suggests that piece can be
taxable as electronically delivered software. Even if it’s basically a fancy doorknob for the service.

2) You bundle taxable digital products with AI access

Bundling is where perfectly good invoices go to die. If your subscription includes access to AI plus something that looks like a taxable
specified digital product (for example, a “digital book” that is transferred for permanent use), you can create tax exposure.

Practical example: You sell “AI Chatbot Pro + Prompt Engineering eBook (yours forever).” That “yours forever” part matters. If the eBook is
treated as a specified digital product transferred for permanent use, the bundle analysis becomes more complicatedand may tilt taxable depending
on structure and pricing.

3) The “true object” starts to look like taxable software

Even when access is remote, states sometimes look at what the customer is really buying. Indiana’s ruling treated the chatbot as a service in
part because of the lack of software transfer and the nature of the offering. But if you cross into a model where you effectively provide
downloadable software (or charge for software functionality delivered as a taxable software product in that state), the analysis can shift.

4) You add (or hide) taxable items inside an all-in-one price

If taxable and nontaxable elements are mashed together into one charge with no separation, you may lose flexibility. Clean product packaging and
clean invoicing are not just “finance hygiene”they’re tax risk controls.

5) You sell in other states (where SaaS is taxable)

Indiana is not the United States of America’s final boss of sales tax. Many states tax SaaS or digital services more aggressively, and some local
jurisdictions treat AI access as taxable in their own right. If you’re multistate, Indiana’s ruling is a useful data pointnot a nationwide shield.

A Billing & Product-Design Playbook for AI Vendors

Here’s a practical playbook to align your generative AI offering with the facts that supported Indiana’s nontaxable conclusionwithout turning your
product roadmap into a tax memo.

Design & delivery

• Keep access remote: web app + hosted infrastructure + API access (no customer downloads of the core software).
• If you offer an app, consider making it free: Indiana guidance treats free apps differently than paid downloads.
• Avoid paid “connectors” that are separately sold downloads unless you’re ready for software tax analysis.

Contract language

• Emphasize that the customer receives access to a hosted service, not ownership of software.
• Clarify there is no transfer of software or code and no permanent right to a digital product.
• Make it explicit that access terminates if payment stops (where that is true).

Invoices & SKU strategy

• Separate line items for anything that could be taxable (downloads, training videos, eBooks, paid plugins).
• Keep your “AI access subscription” line clean and clearly described (e.g., “Hosted AI chatbot service subscription”).
• If you must bundle, document the price allocation and be consistent across customer types.

Compliance reality check

Even if a transaction is not taxable in Indiana, you still need to think about:
nexus thresholds, registration obligations, exemption certificates (if relevant), sourcing rules, and how your tax engine
classifies the SKU in other states. The goal is “right tax in the right place,” not “no tax anywhere.”

And if you’re not sure? One of the most underrated compliance moves is requesting guidance (or a private letter ruling)
in high-revenue states where your tax posture is uncertain. Paying for clarity is often cheaper than paying for surprise.

FAQ: The Questions Everyone Asks (Usually After the Invoice Sends)

Is Indiana saying “AI is never taxable”?

No. Indiana is saying that, under the facts in the ruling, the chatbot subscription and API access looked like a
nontaxable servicebecause there was no software transfer and no taxable specified digital product transferred for permanent use.

What if my AI tool includes a downloadable desktop client?

That’s where you should slow down. Downloadable software is often treated differently than remote access. If the customer pays
to receive software electronically, Indiana’s guidance suggests you may have a taxable software transaction (at least for that component).

What if we provide a mobile app?

A free app that simply enables access to a remotely hosted service may be treated differently than a paid app sold for consideration.
The detailswhat’s paid, what’s transferred, and how it’s billedcan affect taxability.

Does “API access” change the result?

In this ruling, no. Indiana treated API access similarly because customers still weren’t receiving software or code and weren’t obtaining
permanent ownership of the underlying software.

Do I need to collect Indiana sales tax if I sell AI services to Indiana customers?

Based on the ruling’s fact pattern, the AI chatbot service itself was not subject to Indiana sales/use tax. But you should still evaluate your
full product bundle, any downloadable components, and your broader compliance obligations. When in doubt, consult a SALT professional.

Real-World Experiences: The Messy Middle of AI + Sales Tax (Bonus)

Even when the law is fairly clear, the lived experience of “AI + sales tax” is rarely calm. It’s more like a group project where one person
names the file FINAL_v7_really_final_THIS_ONE and another person invoices the customer for “AI stuff” with no description.
Here are common real-world scenarios companies run into when they try to operationalize rulings like Indiana’s.

Experience #1: The invoice label that accidentally becomes a tax position

Many tax disputes begin with the most innocent thing imaginable: an invoice line that says “Software subscription.”
If you’re selling a hosted generative AI chatbot service in Indiana, you want your documents to reflect reality:
“hosted service,” “remote access,” “AI chatbot service,” or “API access service.” Not because labels magically change statutes,
but because labels influence how auditors (and automated tax engines) categorize your transaction in the first place.

Experience #2: The “free app” is fine… until someone monetizes it

Product teams love a good companion app. “It’s just a wrapper,” they say. “It just logs you in,” they say. Then one day, a premium feature
gets added, the app store listing includes a price, and suddenly you’ve got an electronically delivered software sale that may have its own tax
treatmenteven if your core AI service remains remotely hosted. Indiana guidance draws distinctions between free access tools and paid downloads,
so monetizing the wrapper can unintentionally create a new taxable item.

Experience #3: Bundles are where compliance goes to get complicated

Marketing loves bundles because bundles sell. Tax teams hate bundles because bundles blur the “true object” of the transaction.
A common AI bundle looks like: “AI access + training + templates + an eBook + priority support.” Some of those items can be services,
some can look like digital products, and some can be taxable in certain states depending on delivery and permanence.
The most practical fix is boring but effective: separate SKUs, separate line items, and clear descriptions.
If you must bundle, document why your allocation is reasonable and keep it consistent.

Experience #4: Customers ask for “no tax” as if it’s a coupon code

Enterprise customers often push back on sales tax chargessometimes correctly, sometimes creatively. Even when Indiana supports nontaxability
for a hosted AI chatbot service, customers operating across multiple states may have internal rules, exemption positions, or procurement systems
that default to “taxable SaaS.” The result: your billing team spends time explaining that Indiana’s treatment can differ from other states.
Having a short, prepared explanation (and internal documentation mapping your SKU to the relevant guidance) saves real time.

Experience #5: Multistate reality hits fast

The most common “aha” moment is realizing that Indiana is just one stop on a 50-state tour. A company may be non-taxable in Indiana because
the offering is a service accessed remotely, but taxable in a different state that taxes SaaS broadlyor taxable in a local jurisdiction that
treats certain cloud-based access as a lease of software. The operational lesson: don’t build your tax logic around one ruling.
Build it around product attributes (download vs. remote access, permanence, bundled components, separate consideration) and then map those
attributes state-by-state. That approach scales as AI products evolve.

Bottom line: Indiana’s ruling is helpful because it confirms that, under Indiana’s current framework, a generative AI chatbot delivered as remote access
with no software transfer and no permanent digital product can be treated as a nontaxable service. The real-world work is making sure your product,
contracts, and invoices consistently tell that same storyespecially as features, pricing, and packaging change over time.