Indiana and Illinois Both Said AI Chatbots Aren't Taxable. Here's Why That's More Complicated Than It Sounds.
Two states issued administrative guidance in 2025 finding that access to generative AI chatbot services is not subject to state sales tax. Indiana's Department of Revenue ruled in July. Illinois's Department of Revenue followed in September. Both reached the same headline conclusion. Both used the same conceptual framework to get there.
If you sell or buy AI services and you're looking for a clean answer, this looks like good news. It's not that simple.
Indiana Goes First
On July 23, 2025, the Indiana Department of Revenue issued a revenue ruling addressing whether charges for a generative AI chatbot service — a hosted platform providing AI-generated content through a subscription — are subject to Indiana sales tax.
The ruling found: no, they are not.
The reasoning tracks Indiana's definitions of taxable digital goods and prewritten software. Under Indiana law, taxable transfers involve customers acquiring a permanent right to use digital content or software — either by download or by gaining ownership-level access. In this case, customers accessed the AI platform through a web interface. They did not download the underlying model. They did not acquire ownership or control over the AI software. When a customer's subscription ended, they retained nothing.
Because no taxable transfer occurred — no software changed hands, no digital content was permanently acquired — Indiana classified the transaction as a nontaxable service. The ruling treats accessing a hosted AI model the same way it would treat accessing any hosted software platform: as a service, not a sale of a digital good or prewritten software.
The practical implication for Indiana-based users of AI chatbot platforms: no sales tax owed at the state level on those charges, under current law.
Illinois Reaches the Same Conclusion, Differently
Two months later, on September 16, 2025, the Illinois Department of Revenue issued General Information Letter ST 25-0050-GIL in response to a technology company offering AI chatbot access through its website and mobile app.
Same conclusion. Different statutory path.
Illinois doesn't generally tax services. It taxes tangible personal property and a defined set of enumerated taxable items. SaaS — software that is accessed remotely and never transferred to the customer — has long been treated as a nontaxable service in Illinois, because the customer isn't buying software, they're buying access to a service.
The IDOR applied that same framework to the AI chatbot. Because nothing was physically transferred or installed, and because the customer was accessing hosted functionality rather than acquiring software, the transaction looked like SaaS. SaaS is not subject to Illinois sales tax. The AI chatbot access wasn't either.
Illinois arrived at "not taxable" through a different door than Indiana, but the underlying logic is similar: no transfer of property, no taxable transaction.
Then There's Chicago
Before you conclude that "Illinois says AI chatbots aren't taxable" and move on, there's a fact that matters considerably: Chicago has its own tax.
Effective October 1, 2023, the City of Chicago expanded its Personal Property Lease Transaction Tax to cover access to AI platforms. The tax rate is 9%. It applies to charges for the use of AI platforms that are accessed or used in Chicago.
This is not a state tax. It is a city-level transaction tax. It applies regardless of how the state has characterized the transaction. The Illinois Department of Revenue ruling that classifies AI chatbot access as a nontaxable service does not affect Chicago's transaction tax.
If you sell AI services and you have customers in Chicago, or if you purchase AI services as an operator headquartered in Chicago, you need to treat that activity differently from the rest of Illinois. The state says not taxable. The city says 9%.
This is not an unusual situation in state and local tax. Local rates and local taxes frequently impose obligations that don't exist at the state level — and AI commerce is no exception.
What the Rulings Have in Common
Both Indiana and Illinois applied SaaS-era definitions to an AI-native product. Neither state has created a statutory category specifically for generative AI, large language models, or AI inference services. Both states reached their conclusions by asking the same fundamental question: did a taxable transfer occur?
That question, and the frameworks states use to answer it, predates AI by decades. The "true object" test — what is the buyer really paying for? — is the same analysis that determined how to tax cloud computing in 2012, how to tax SaaS in 2015, and how to tax AI chatbots in 2025.
The consistent answer across Indiana and Illinois: if a customer is accessing a hosted service without acquiring ownership of software or digital content, the transaction looks more like a service than a sale, and nontaxable services don't produce a tax obligation in states that use this framework.
This framework is coherent, but it has a fragility. The conclusion holds as long as the statutory language and the product structure remain aligned. Change the product — add a downloaded component, offer API keys that constitute a software transfer, grant customers the right to run the model on their own infrastructure — and the analysis changes. Change the statute — as a growing number of states are doing by expanding their digital taxability rules — and the analysis changes again.
The 48-State Gap
Indiana and Illinois represent two data points. Forty-eight states, plus the District of Columbia and numerous localities, have not issued specific guidance on the taxability of generative AI services.
Some of those states will follow the Indiana/Illinois pattern: applying SaaS-era frameworks and reaching non-taxable conclusions. Others will take a different view. States that broadly tax "computer services" or "digital automated services" may find that AI chatbot access falls squarely within those definitions — particularly after several states have moved to remove exclusions that previously protected service-flavored transactions from the tax base.
Washington state, for instance, removed the "human effort" exclusion from its definition of digital automated services effective October 1, 2025 — a move that potentially expands the taxable base to include AI services delivered without meaningful human intervention. The reasoning that saved AI chatbot operators in Indiana and Illinois would not produce the same result in Washington under the same facts.
For anyone building or purchasing AI services, the state-by-state divergence creates real compliance complexity. "Indiana says it's not taxable" is not transferable to other states without running the analysis again under each state's specific statutes, definitions, and administrative guidance. And in most states, there is no guidance yet at all.
What This Means for AI Commerce Operators
If you're building on AI services or operating AI agents that purchase compute, inference, or data services on your behalf, these rulings confirm something useful: the legal classification of AI service transactions is being settled on a state-by-state basis through existing frameworks, not through new AI-specific legislation. That means the compliance burden requires understanding those frameworks in each relevant jurisdiction — not waiting for a federal answer or a uniform approach.
For customers in Indiana and Illinois at the state level, the analysis currently points toward non-taxable treatment for pure hosted AI access with no software transfer. For customers in Chicago, the analysis points toward 9% regardless. For customers in 48 other states, the answer depends on a jurisdiction-by-jurisdiction examination.
The broader pattern to watch: as more states issue AI-specific guidance in 2026, the picture will either converge (most states apply SaaS frameworks to reach non-taxable conclusions) or diverge (some states legislate AI services into taxable status). Both outcomes have implications for AI operators' pricing, margin modeling, and nexus configurations.
Washington's April 1 transition deadline — also arriving today — is a reminder that the landscape is actively changing. See our earlier analysis of Washington's SB 5814.
This analysis is for informational purposes only and does not constitute legal or tax advice. Consult a licensed tax professional for compliance decisions.