Is SaaS taxable in Utah? A developer's guide to the state's SaaS tax rules and SB 162

If you are designing checkout logic, billing workflows, or platform architecture for a software company, this guide outlines Utah's statutory software tax rules, economic nexus requirements, and how to source rates using the Ziptax Sales Tax API.

Utah SaaS sales tax at a glance

Product Taxability Rules

State Registration & Collection Triggers

Which types of software does Utah tax?

Utah classifies software based on its underlying functionality and standard availability rather than the delivery mechanism.

Bundling, mixed transactions, and implementation charges specific to Utah SaaS sales tax

Utah applies strict bundling rules under Utah Code § 59-12-102. If a SaaS provider bills a non-taxable service (such as custom consulting, data migration, or training) alongside a taxable SaaS subscription under a single, non-itemized fee, the entire invoice amount becomes subject to sales tax.

To preserve the tax-exempt status of professional services, configure your billing engine to itemize each product and service on a separate line. When billing complex enterprise bundles, search for the correct product code and review Taxability Information Codes (TICs) to ensure items are cataloged accurately at checkout.

SB 162 also established statutory coordination rules: services already taxed under Utah's Multi-Channel Video or Audio Service Tax Act (Utah Code Ann. Title 59, Chapter 26) are exempt from sales tax to avoid duplicate taxation.

How do you charge the correct sales tax rate for SaaS in Utah?

Utah is a destination-based sourcing state under Utah Code § 59-12-107. Sales of remotely accessed software must be sourced to the buyer's location where the software is accessed or used.

Combined rates range from 6.35% to 9.55%, depending on the applicable local taxing jurisdictions.

Option 1: Use the Ziptax Sales Tax API

Manually maintaining tax boundaries across Utah's complex taxing jurisdictions is impractical. The state overlays county taxes, municipal option taxes, transit district levies, and resort community taxes that diverge within individual 5-digit ZIP codes.

Using the Ziptax v60 API endpoint, you pass the customer's rooftop address at checkout to instantly return the combined tax rate and jurisdiction breakdown:

Bash

curl -G https://api.zip-tax.com/request/v60 \
    -H "X-API-KEY: <apiKey>" \
    -d key=your-api-key \
    --data-urlencode "address=451 S State St, Salt Lake City, UT, 84111"

To configure payload parameters and tax calculation workflows, explore the REST API documentation.

Implementation details for developers:

• Rooftop Geocoding: Apply the API's full jurisdiction result rather than a flat ZIP code approximation. ZIP code boundaries in Utah frequently cross municipal lines that determine whether transit or local option taxes apply.
• Effective Date Tracking: If your billing engine calculates historical adjustments or amended billing runs, program your tax engine to apply tax to remote SaaS transactions on or after July 1, 2026. Pure SaaS transactions prior to July 1, 2026, remain non-taxable under historical administrative rulings.
• Exemption Lifecycle Management: Utah allows enterprise buyers using software in multiple jurisdictions to issue Streamlined Sales Tax exemption certificates for multiple points of use (MPU). Use automated workflows to manage exemption certificates rather than maintaining static exemption forms manually.
• Scalable Compliance: When expanding registration footprints across multiple states, you can set up merchant management to streamline multitenant tax collection and automated filing.

Option 2: Build and maintain custom tax logic

If your engineering team chooses to build and maintain an internal rate calculation table for Utah, your engine must resolve four distinct operational components:

1. Address-Level Resolution: Utah's Department of Revenue divides the state into dozens of localized tax zones. Five-digit ZIP codes are insufficient; your checkout system must resolve 9-digit ZIP+4 data or exact coordinates.
2. Resort Community Tax Overlays: Under Utah Code §§ 59-12-401 and 59-12-402, designated resort towns where transient lodging capacity exceeds permanent population (including Park City, Alta, Moab, and Brian Head) levy a primary Resort Communities Tax (up to 1.10%) and an Additional Resort Communities Tax (up to 0.60%). These levies sit on top of municipal, transit, and county option taxes.
3. Nexus Accumulator Logic: Your accounting logic must monitor gross revenues delivered to Utah against the $100,000 threshold across the current or preceding calendar year, including both direct and marketplace sales.
4. Historical Effective Dates: Your data models must separate remote SaaS transactions occurring before July 1, 2026 (exempt) from those occurring on or after July 1, 2026 (taxable).

A few things to watch out for if you take this route with Utah:

1. Don't rely on a 5-digit ZIP code. Utah's own rate lookup tool recommends the full street address or a nine-digit ZIP+4, because county, city, transit, and resort-district layers don't follow ZIP boundaries and several can sit inside the same code.
2. The resort community tax is easy to miss if you're modeling Utah as "state plus county." It only applies in specific municipalities, it isn't a flat statewide add-on, and in some towns a second "additional resort" layer stacks on top of the first.
3. Streaming-only digital content just became taxable. Before July 1, 2026, streaming access to video, audio, books, and games without a download sat in a compliance gap under Utah's prior guidance; SB 162 closed it, with a carve-out for anything already taxed under the state's Multi-Channel Video or Audio Service Tax Act. A system built before mid-2026 needs an update, and any transaction dated before that needs the prior treatment preserved.
4. Watch the gross-revenue count, not a transaction count. Utah repealed its 200-or-more-transaction nexus prong effective July 1, 2025; don't build threshold logic around a transaction count that no longer applies.

When does a SaaS business have to collect sales tax in Utah?

Software companies must distinguish between registration triggers (nexus) and tax calculation logic. Here’s how to determine when you have to collect SaaS sales tax in Utah.

1. Monitor Your Nexus Triggers

You are legally required to register with the Utah State Tax Commission as soon as you meet either threshold:

• Physical Presence: Maintaining an office, leased server space, warehouse inventory, remote sales representatives, or resident employees within Utah.
• Economic Threshold: Generating more than $100,000 in gross revenue from sales delivered into Utah during the current or preceding calendar year. You can periodically check economic nexus thresholds across all active sales states.

2. Apply the correct rate and classification once you're registered

Once registered, collect sales tax on all taxable prewritten software sales sourced to the customer's address in Utah.

Utah doesn't have a phase-in period to manage for SaaS itself. The Tax Commission's position that remotely accessed software is taxable predates SB 162, so once you have nexus, you charge the applicable combined rate at checkout immediately; there's no interim zero-collection stage like a state with a future SaaS effective date.

What does vary line-by-line is the rate and, for content platforms, the classification. The combined rate depends on the specific delivery address, including whether a resort community tax applies, and a digital-content seller needs to know that streaming-only access became taxable July 1, 2026, with transactions before that date keeping the prior treatment.

Where Ziptax fits into your tech stack

Ziptax provides real-time rate infrastructure tailored to software platforms, checkout systems, and recurring billing stacks:

• Rooftop Accuracy: Precisely pinpoints local option, transit, county, and resort community levies without relying on generalized ZIP codes.
• Developer-First API: Returns low-latency JSON responses ready to integrate into Stripe, Chargebee, or proprietary custom billing architectures.
• Predictable Pricing: Pay based on live API volume without long-term contract lock-ins. To select an API tier, view Ziptax pricing.
• Automated Filing Runway: As transaction volume grows, pair Ziptax with certified filing solutions to streamline SST remittance and multijurisdictional reporting.

If you need technical assistance sizing your API payload or mapping custom software SKUs, contact the Ziptax team.

Get Utah SaaS tax rates from an API

Ziptax Sales Tax API rates for Utah, plus the rest of the US, Canada, and select other markets. Free starter plan, then usage-based pricing.

Frequently asked questions

Does Utah tax SaaS differently depending on how it is delivered?

No. Following the effective date of 2026 SB 162, Utah taxes prewritten computer software across all distribution methods: cloud-hosted SaaS, electronic downloads, load-and-leave, and physical media. Truly custom software created specifically for a single client remains exempt.

What was the legal impact of Utah's 2026 SB 162?

Effective July 1, 2026, SB 162 expanded Utah Code §§ 59-12-102 and 59-12-103(1)(l) to explicitly bring remotely hosted prewritten computer software (SaaS) into the sales tax base, reversing earlier administrative letter rulings that had treated cloud access as non-taxable. It also established sales tax on streaming-only digital audio-visual, audio, book, and gaming content, while exempting services already covered by the Multi-Channel Video or Audio Service Tax Act.

Can I rely on a 5-digit ZIP code to charge Utah sales tax?

No. Utah local sales tax boundaries do not align with ZIP codes. Multiple local option rates, public transit districts, and resort community taxes apply within single postal zones. Destination sourcing requires address-level or 9-digit ZIP+4 precision.

Does Utah have a transaction-count threshold for economic nexus?

No. Effective July 1, 2025, Utah Senate Bill 47 eliminated the 200-transaction nexus test. Remote sellers only establish economic nexus if gross revenue from Utah sales exceeds $100,000 in the current or preceding calendar year.

Sources

1. Prewritten Software Tax Base: Utah Code § 59-12-103 (Sales and Use Tax Base)
2. Senate Bill 162 (2026 General Session): 2026 Utah Senate Bill 162 (Online Sales Tax Amendments)
3. Senate Bill 47 (2025 General Session): 2025 Utah Senate Bill 47 (Sales and Use Tax Remittance Amendments)
4. Remote Seller Registration Guidelines: Utah State Tax Commission Remote Sellers
5. Marketplace Facilitator Provisions: Utah Code § 59-12-107.6 (Marketplace Facilitators)
6. Resort Communities Tax Authority: Utah Code § 59-12-401 (Resort Communities Tax)
7. Combined Local Tax Rates: Utah State Tax Commission Sales Tax Rates
8. Streamlined Sales Tax Governing Board: Streamlined Sales Tax Utah State Details