Indiana Says an Optional Download Doesn't Make Your Hosted Platform Taxable. Utah Wrote the Opposite Rule Five Days Later.

Indiana's Department of Revenue issued Revenue Ruling No. 2026-04-RST on June 26, 2026. It became publicly visible in mid-July. The holding is narrow and, on its face, unremarkable: fees for access to a cloud-based educational platform offering simulated trading, analytical tools, and educational content are not subject to Indiana sales and use tax.

The part worth your attention is the sentence about the download. The taxpayer also offered an optional downloadable application. Indiana concluded that this did not change the answer. The customer still received only online access to software, so the transaction remained a nontaxable service.

That is a useful fact pattern, because it is the fact pattern of nearly every AI agent product sold today: hosted inference behind an API, plus an SDK, CLI, or desktop client that the customer may or may not install.

Why the Download Question Comes Up At All

Ask an agent operator what makes them nervous about sales tax and the SDK comes up quickly. The intuition runs like this: hosted access is a service, a downloaded binary is software, and shipping the second might contaminate the first — converting an untaxed subscription into a taxable transfer of prewritten software.

In Indiana that intuition has a statutory basis worth understanding, because the statute is unusually explicit about where the line sits.

IC 6-2.5-4-16.7 makes a person a retail merchant when they sell, rent, lease, or license for consideration the right to use prewritten computer software delivered electronically. Then it carves the ground out from under the obvious reading. A transaction in which an end user purchases, rents, leases, or licenses the right to remotely access prewritten computer software — over the internet, over private or public networks, or through wireless media — is expressly not a transaction in which software is delivered electronically.

Indiana did not arrive at "SaaS is not taxable" through administrative inference. The legislature wrote the carve-out into the statute.

The second door is the specified digital products provision, and it is narrower still. A retail transaction occurs when a person electronically transfers a specified digital product to an end user and grants a right of permanent use that is not conditioned on continued payment. Both elements are required. And "specified digital products" reaches only digital audio works, digital audiovisual works, and digital books.

Run 2026-04-RST through both doors and the result follows mechanically. The platform is remote access, so IC 6-2.5-4-16.7 does not reach it. The educational and analytical content is not an audio work, an audiovisual work, or a book, and the subscription is conditioned on continued payment, so the specified digital products provision does not reach it either. Nothing was permanently transferred. No taxable transaction occurred.

The optional download loses because it does not create either missing element. It confers no permanent right of use, and the underlying value the customer pays for still sits on the seller's servers. It is an access method, not the thing sold.

This is the same analytical spine Indiana used in its July 2025 ruling on generative AI chatbot access, where customers reached a hosted model through a web interface and retained nothing when the subscription lapsed. What 2026-04-RST adds is the answer to the question that ruling left open, because that taxpayer had no download at all: an ancillary client does not flip the result.

Read the Limits Before You Rely On It

Three caveats, and they matter more than the holding.

A revenue ruling is not a regulation. Indiana issues these in response to a specific taxpayer describing specific facts, and the Department is bound as to that taxpayer on those facts. It is persuasive evidence of how the Department reasons. It is not authority you can wave at an auditor examining a materially different product.

The download in question was ancillary. Nothing in the reported holding suggests the downloadable app carried standalone function or value. An operator shipping a genuinely capable local model, a perpetual license, or a client that keeps working after the subscription ends is not in this fact pattern, and should not read this ruling as covering them. Where the local component does real work, the general question of how a mixed transaction gets classified remains unresolved across the states — the True Object Test, pro-rata allocation, and all-or-nothing approaches all have adherents, and I would not represent that any of them is the answer.

It is an Indiana ruling. Which brings us to the timing.

Utah Wrote the Opposite Rule Five Days Later

Utah's SB 162 took effect on July 1, 2026 — five days after 2026-04-RST issued. It adds "seller-hosted prewritten computer software" to the taxable categories in Utah Code §59-12-103(1), alongside the older "delivered electronically" and "load and leave" language. Utah's streaming and subscription provision reaches amounts paid for access "even without a download or other transfer of the property to the purchaser."

Set the two side by side. Indiana says: remote access is not delivery, and an optional download does not change that. Utah says: remote access is its own taxable category, and the absence of a download does not save you.

Both states looked at the same commercial reality — customers paying for access to software running on someone else's machine — and wrote rules that reach opposite conclusions. Neither is confused. They made different policy choices about whether the tax base follows the transfer of property or the payment for access, and the legislatures wrote those choices down.

The practical consequence is that the download is a distraction in both jurisdictions. In Indiana it does not create a taxable transfer. In Utah it is not needed for one. An operator who reorganizes their product architecture around whether a client binary ships is optimizing against a factor that neither state's rule turns on.

What This Means for Agent Operators

The instinct to look for a portable answer to "is my agent product taxable" is the thing to give up. There is no such answer, and 2026-04-RST plus SB 162 in the same week is a clean demonstration of why.

What travels is the diagnostic. For any state you have exposure in, work these in order.

1. Find out whether the state taxes access or transfer. This is the threshold question and it sorts most states quickly. Indiana taxes transfer and expressly excludes remote access. Utah, since July 1, taxes access by name. New York reaches remote access as prewritten software. The answer determines whether the rest of your analysis matters at all.

2. Ask whether continued payment is a condition. In transfer states, a subscription that dies when the invoice stops is doing a lot of work for you. A perpetual license is a different transaction, and it is the one most likely to be taxable in a state that would otherwise leave you alone.

3. Identify what the customer is actually paying for. If the hosted component is the product and the client is a convenience, Indiana's reasoning is available. If the local component carries independent value, you are in mixed-transaction territory, which is genuinely unsettled and should be treated as an open exposure rather than a solved one.

4. Do not let architecture drive the analysis. Shipping or withholding an SDK is a product decision. Make it on product grounds. It is not the tax lever it feels like.

5. Date your positions. Utah's rule is four weeks old. California's SB 122 brings electronically delivered prewritten software and SaaS into the base on January 1, 2027. A determination made against the 2025 map is already stale in at least two states.

What to Watch

Indiana's carve-out for remote access sits in statute, not guidance, which makes it durable against administrative drift but vulnerable to exactly one thing: an amendment. Utah just demonstrated how quickly a legislature can add a category when it decides the base has leaked. Indiana's General Assembly has not moved in that direction, but the states writing seller-hosted software into their statutes now outnumber the ones carving it out.

The narrower thing to watch is whether any state addresses the ancillary-download question head-on rather than in passing. Indiana answered it inside a ruling about an educational platform. The agent economy would benefit from someone answering it about an SDK.

Tracking which states tax access, which tax transfer, and which changed their answer this quarter is not work that scales by hand across fifty jurisdictions. AgentTax classifies each transaction against current per-state rules and shows the statutory basis for the determination in the response. See how it works at agenttax.io, or start with our state-by-state SaaS taxability guide and the AI agent sales tax 50-state guide. For the ruling itself, Indiana publishes revenue rulings in the Indiana Register.

This analysis is for informational purposes only and does not constitute legal or tax advice. This post reflects AgentTax's current interpretation of evolving law. Consult a licensed tax professional for compliance decisions.