Utah SB 162: Why 'Seller-Hosted Prewritten Software' Now Has a Statute, and What It Means for AI Agents

PwC published an analysis last week (April 23) walking through Utah's Senate Bill 162, signed March 23 and effective July 1, 2026. The bill is short. It does two things that matter for the agent economy: it puts streaming and subscription access into the sales and use tax base by statute, and it adds an explicit category for "seller-hosted prewritten computer software" alongside the older "delivered electronically" and "load and leave" categories.

If your AI agent product runs on your servers and a Utah customer pays to access it through an API, a web app, or any other remote interface, this is the statute that will be cited when an auditor asks why you did not collect tax. The Utah State Tax Commission's prior position already treated SaaS as taxable prewritten software. SB 162 takes that position out of administrative guidance and writes it into Title 59 of the Utah Code. The audit posture changes accordingly.

What SB 162 Actually Says

The operative language adds two transaction categories to Utah Code §59-12-103(1).

The first covers "amounts paid or charged for access to digital audio-visual works, digital audio works, digital books, or gaming services, including the streaming of, or subscription for access to, that content even without a download or other transfer of the property to the purchaser." This closes the gap that some streaming services had argued — that absent a transfer of the file to the buyer, no taxable sale occurs.

The second is the one AI agent operators should read carefully. SB 162 makes taxable any amount paid or charged for "the storage, use, or other consumption of prewritten computer software delivered electronically, by load and leave, or that is seller-hosted prewritten computer software." The third category — seller-hosted — is new statutory language. Utah had been getting to this result through administrative interpretation and Pub 64. Now the result is in the statute itself.

The bill also clarifies that transactions already subject to the state's Multi-Channel Video or Audio Service Tax Act are not double-taxed. Effective date is July 1, 2026.

Why This Matters for AI Agents

AI agent products almost always sit in one of two architectural patterns: the agent runs on the seller's infrastructure and the customer pays for API or web access to it (seller-hosted), or the agent runs as a desktop or local install with periodic license validation (delivered electronically). Utah's old framework left enough ambiguity in the seller-hosted bucket that some practitioners argued the access fee was a service rather than a sale of software. SB 162 forecloses that argument by name.

For an AI research agent, an AI compute service, a hosted RAG pipeline, or an agentic workflow accessible by API, the access fee paid by a Utah buyer is now expressly within the Utah tax base starting July 1. The argument that "we are providing a service, not transferring software" no longer needs to be entertained — the statute treats the access itself as the taxable transaction.

This is consistent with the direction Washington took in ESSB 5814 (effective October 1, 2025), with Maine's expansion of digital services to include audiovisual and audio content (effective January 1, 2026), and with New York's reaffirmation in Matter of Beeline.com, Inc. v. N.Y.S. Tax App. Trib. that web-based access to prewritten software remains taxable regardless of any service wrapper. State legislatures and courts are converging on the same destination: if you sell access, you sell software, and access fees follow the tax rules for software.

What Changes on July 1

Three practical things shift in Utah on the effective date.

First, AI agent operators with Utah customers and an active permit need to confirm their tax matrix now includes seller-hosted software as a taxable category at the standard 4.85% state rate plus applicable local rates (Utah's combined rates run roughly 6.1–7.6% depending on locality). If your billing system is mapping AI agent access to a "service" SKU that sits in a non-taxable category, that mapping needs to change before July 1.

Second, subscription products that previously argued non-taxability based on the absence of a download — particularly streaming-tier or trial-tier offerings — lose that argument in Utah. The "without a download or other transfer" clause is the legislature explicitly closing that door.

Third, audit risk for transactions on or after July 1 looks different than for transactions before. Pre-July transactions get analyzed under the prior administrative framework, where a taxpayer could mount a service-versus-software argument. Post-July transactions get analyzed under the statute, where the argument is unavailable.

Economic Nexus Still Applies the Same Way

SB 162 does not change Utah's economic nexus thresholds. A remote seller still establishes nexus at $100,000 in Utah-sourced gross revenue or 200 separate transactions delivered into the state in the current or prior calendar year. What changes is that the universe of revenue that counts toward those thresholds now expressly includes seller-hosted prewritten software access fees.

For AI agent operators that have been below Utah's threshold because their access fees were classified as services, the recategorization may push them over. A seller doing $80,000 in Utah API revenue that did not previously count toward sales tax nexus may, post-July, find itself with $80,000 in Utah sales for which it now needs to register, collect, and remit. The transaction count threshold is more likely to bind first — agent products with high call volume and low per-call pricing will hit 200 Utah transactions before $100,000 in revenue.

What Operators Should Do This Week

Three concrete actions, in order of priority.

Confirm Utah customer counts. Pull a list of distinct Utah-shipping addresses or Utah-billing addresses from your transaction history for the last twelve months. If you are above either nexus threshold and not registered, register before July 1. Utah accepts retroactive registrations but the nexus threshold treats the trailing window as the lookback, not just the post-effective-date window.

Update the tax classification for hosted access. Whatever line item your billing system uses for AI agent access to a Utah customer should map to a taxable software category beginning July 1. If you use a tax engine that reads transaction categories, verify the engine's Utah ruleset already accounts for SB 162. (The AgentTax engine's Utah taxability matrix is being updated to reflect SB 162 ahead of the July 1 effective date — no operator action required for AgentTax users.)

Document the policy decision. Whether you are now collecting, were collecting before, or have a defensible reason not to collect, write the analysis down. SB 162 is the kind of statutory cleanup that becomes the most-cited authority in Utah audits for the next several years. Auditors will ask why your treatment matched or did not match the statute. The defensible answer is one you wrote down before they asked.

The Broader Pattern

Utah is the eighteenth state to either enact or substantially expand digital services taxation in the last twenty-four months. The pattern is consistent: language like "delivered electronically" and "load and leave" was written for an earlier generation of software distribution and does not naturally cover the way AI agent products are sold today. Legislatures are closing the gap one state at a time.

For agent operators, the implication is operational rather than legal. The compliance question is no longer "is this taxable" — for most digital services in most states, the answer is now "yes, in some configuration." The compliance question is "do my systems compute the right answer at the right time without anyone having to think about it." That is a routing problem, not a tax-research problem.

See how AgentTax handles per-state SaaS routing — Utah included, with SB 162 already in the engine's roadmap.

This analysis is for informational purposes only and does not constitute legal or tax advice. Consult a licensed tax professional for compliance decisions.