AgentTax
This article is for informational purposes only and does not constitute tax, legal, or accounting advice. Consult a qualified tax professional before making compliance decisions.
Practical Guide

Is SaaS Taxable in Utah? Yes — and Since July the Statute Reaches Access That Was Never Permanent and Never Downloaded

Beardsley Rumble|2026-09-16|9 min read

Key Takeaway: Utah taxes SaaS, and since July 1, 2026 it does so under a statutory category written for it rather than an administrative reading of the tangible-property rules. The definition that carries it — Utah Code § 59-12-102(127) — reaches prewritten software "accessed through the internet or a seller-hosted server, regardless of whether (a) the access is permanent; or (b) any downloading occurs." Nobody drafted that with autonomous agents in mind; it covers them anyway. And the rate you owe is never the 4.85% state rate — the floor at any Utah address is 6.35%, the ceiling 10.05%.

The Short Answer

Utah's sales tax base is an enumerated list: § 59-12-103(1) taxes the transactions it names, and a service Utah has not named is not in the base. Software is named twice. § 59-12-103(1)(p) imposes tax on "amounts paid or charged for the storage, use, or other consumption of: (i) prewritten computer software delivered electronically or by load and leave; or (ii) seller-hosted prewritten computer software."

That second clause is new. It arrived with S.B. 162 (2026 General Session), whose enrolled copy I read this morning; Section 4 reads, in full, "This bill takes effect on July 1, 2026." The same bill inserted the § 59-12-102(127) definition. Before July, Utah reached hosted software by treating prewritten software as tangible personal property — § 59-12-102(141)(b)(v) still provides that "tangible personal property" includes "prewritten computer software, regardless of the manner in which the prewritten computer software is transferred" — and taxing its use in state under § 59-12-103(1)(l). That route still exists; it is no longer the one an auditor has to take.

One definitional trap runs the other way from what most summaries assume: § 59-12-102(105)(b)(ii) provides that "product transferred electronically" does not include computer software. Utah's digital-products category and its software category are disjoint, so reasoning about an agent product by analogy to digital goods reads the wrong subsection.

The Definition Is the Find

Read § 59-12-102(127) again with a metered API in front of you:

"Seller-hosted prewritten computer software" means prewritten computer software that is accessed through the internet or a seller-hosted server, regardless of whether: (a) the access is permanent; or (b) any downloading occurs.

Both escape hatches an agent operator would reach for are closed by name. The access is momentary — permanence is irrelevant. Nothing is transferred to the buyer — downloading is irrelevant. What remains is the only question that decides a Utah agent transaction: is what you sell prewritten computer software?

Utah answers that in § 59-12-102(103): prewritten software is software not designed and developed by its author to the specifications of a specific purchaser. Three refinements matter. Custom software sold onward to anyone other than the original purchaser becomes prewritten, under (103)(b)(ii). Prewritten software modified or enhanced "to any degree" to a purchaser's specifications stays prewritten, under (103)(b)(iii). And the only exit from that second rule, under (103)(c), is modification charges that are reasonable and separately stated on the invoice.

So Utah's line is not technological. Fine-tuning a general model for one customer does not make the result custom; it makes it prewritten software with a possibly-severable modification charge attached. The invoice does work the architecture cannot.

Utah does exempt custom software, and the exemption reaches hosted delivery: the Tax Commission's *Publication 64, Sales Tax Information for Computer Service Providers, says charges for using custom software are nontaxable and, separately, that "license fees for remotely accessed custom software are not taxable." An agent genuinely built to one customer's specification, hosted by you, accessed over an API, is outside Utah's base — until the second sale, which (103)(b)(ii) converts. A single-tenant deployment of a multi-tenant product is not custom software; it is prewritten software deployed alone.

The Allocation Rule Is a Pamphlet, and Its Denominator Is People

Utah has a multiple-points-of-use rule, and for an operator whose buyers span states it decides the bill. Publication 64:

If remotely accessed software is used at more than one location and at the time of the transaction, the buyer provides the seller a reasonable and consistent method for allocating the transaction between those locations, the seller must source the transaction to those locations. If the buyer does not provide the seller with a method of allocating a transaction that is used in multiple locations, the seller must source the transaction to the buyer's address.

Two features distinguish this from every other apportionment regime I have read this quarter. No certificate is required — no form, no exemption document, nothing for a state to lose; the buyer hands over a method and the seller "must" follow it. And the seller has no discretion: the duty attaches once a reasonable and consistent method arrives, and the default when none arrives is the buyer's address, not an apportionment the seller invents.

Then there is the denominator. Publication 64's Example 5 gives the Commission's own illustration of a reasonable method:

A reasonable method of allocation would be, for example, allocating the sales price based on the number of Buyer's employees in Utah using the ASP software and the total number of Buyer's employees in the four states using the ASP software.

Employees. That is the tenth place-of-use rule I have logged this quarter whose worked denominator counts human beings — alongside Chicago's users-based affidavit, Michigan's repealed certificate regime, New York's user metering and California's draft Regulation 1600.2, whose comment period closes on September 24. Maryland's Tax-Gen. § 11-101(e-1)(1)(ii), naming "equipment that makes use of" the service, remains the outlier that contemplates machines at all.

Utah's text is the most forgiving of the ten, because "reasonable and consistent" is the whole standard and the employee count is an example rather than the rule. A buyer whose Utah usage is machine-driven can propose a machine-shaped denominator — calls, tokens, jobs, configured agents — and nothing in Publication 64 forbids it. That is an argument to document and reserve, not a settled answer; no Utah authority has addressed it and nobody has litigated it.

Which raises the vintage. Publication 64 is marked "Rev. 5/12" — May 2012. The allocation rule an agent operator must follow in Utah today is fourteen-year-old administrative guidance, written before the statute it now sits beside, in a two-page pamphlet whose own footer says it "does not contain all sales or use tax laws or rules."

Rates: Never 4.85%

Utah's state rate is often quoted as 4.85%. No Utah buyer pays that. I extracted every row from the Tax Commission's combined rate charts for Q3 2026 (in effect July 1) and Q4 2026 (in effect October 1) this morning:

  • Minimum: 6.35%, at 49 locations across 8 counties — Beaver, Carbon, Duchesne, Emery, Millard, Piute, San Juan and Sanpete. Composition: 4.85% state, 1.00% local sales and use, 0.25% county option, and a further 0.25%.

  • Maximum: 10.05%, at MIDA Salt Lake City.

  • Salt Lake City 8.45%; Provo, Orem, Sandy, West Jordan and West Valley City 7.45%; Park City 9.55%. Ogden moves from 7.25% to 7.45% on October 1, 2026.

One instruction on those charts deserves a second read: "These rate charts should not be used for sourcing sales from out-of-state sellers to locations in Utah. Out-of-state sellers should source their sales based on the ZIP +4 of the customer's address." Utah asks remote sellers for nine digits of precision.

What Utah Does Not Tax

Because § 59-12-103(1) is an enumerated list, most services fall outside it, and Publication 64 names several agent operators actually sell as nontaxable: "converting data from one form to another"; customer service or technical support; computer monitoring; diagnostics; web page development; "data backup or disaster recovery service in the absence of a repair"; and separately stated installation charges.

"Converting data from one form to another" describes a great many inference calls. It does not follow that an inference API is nontaxable — if the customer pays to access your hosted model, § 59-12-103(1)(p)(ii) reaches the access regardless of what the model does with the data. Utah's line runs between buying a result and buying access to the software that produces it, and what decides it is largely what you charge for rather than what you built. One bundling rule follows from the same logic: per Publication 64, if an optional software maintenance contract mixes taxable and nontaxable products not separately itemized on the invoice, 40 percent of the purchase price is subject to tax.

How AgentTax Handles Utah

Verified against the live engine this morning, $1,000 into Utah with nexus configured:

  • All fifteen categories compute at 6.35% — $63.50. SaaS, API access, compute, data processing, cloud infrastructure, model access, digital goods, licences, subscriptions, services, data purchases, agent labour, marketplace fees, storage and consulting return the same figure: the state floor, which is the right default for a zipless call.

  • All eight seeded Utah ZIPs reconcile exactly against the Tax Commission charts — every figure in the rate list above, including the Ogden step. A ZIP we do not carry (84770, St. George) returns the 6.35% floor with a ZIP_UNKNOWN advisory rather than a guess.

  • Utah has no per-category rules in our matrix, and every response says so with a STATE_DEFAULT_NO_CATEGORY_RULE advisory. Utah is carried as partially covered — three cells, for SaaS, digital goods and tangible property — and everything else is the state default. We disclose that rather than let a uniform number imply a determination we have not made.

  • Consulting computes at 6.35%, and that is an over-collection. Utah's base is enumerated and consultancy is not in it. This is an instance of a known cross-state classification defect already logged for review rather than a new Utah finding — Utah is the tenth state where the same routing produces the same over-charge.

  • Storage computes at 6.35% against Publication 64's nontaxable "data backup or disaster recovery service in the absence of a repair." Whether our storage category means bare capacity or capacity plus vendor application functionality needs analysis before it is a defect. Logged, not filed.

  • We do not compute multiple points of use in any state, and we source on five-digit ZIPs rather than ZIP+4. A calculation returns the full-price figure at the five-digit rate: the correct amount to remit before an apportionment claim, and the wrong amount to treat as final if your workload spans jurisdictions or your buyer sits on a ZIP+4 boundary.

The 6.35% base was itself corrected upward from 6.10% in the last fortnight, after a review of the Streamlined Sales Tax board's Utah rate file found the old figure sat 25 basis points below the lawful floor at every Utah address. The eight ZIP add-ons were rebased in the same change, so every combined rate above is unchanged by it.

What to Watch

Whether the Tax Commission ever updates Publication 64. It is the operative guidance on allocation, custom software and bundled maintenance for an industry that did not exist when it was written, and S.B. 162 gave the Commission an obvious occasion to revisit it.

Whether anyone proposes a machine-shaped denominator under the "reasonable and consistent" standard, and whether the Commission accepts it. Utah's rule is the most permissive of the ten I have logged, which makes it the cheapest place to test the question — and whether California's Regulation 1600.2 drafters look at Utah's certificate-free approach before September 24, when written comments close. Utah has run a mandatory-on-the-seller, no-paperwork allocation regime for fourteen years, a longer track record than any alternative currently on the table.

No state has issued guidance addressing agent-initiated commerce directly. Everything above applies human-drafted categories to machine transactions — analysis, not settled law.

Try it on your own transaction types. Run a Utah SaaS transaction now (no account), or get a free API key. Compare it with Utah's S.B. 162 in prospect, Washington's digital automated services hook, Massachusetts's control test and Maryland's machine-naming sourcing statute; see every state in the 50-state SaaS taxability guide and the AI agent sales tax hub.

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.*