Is SaaS taxable in Idaho? A developer's guide to Idaho's software tax rules

If you're building a product that needs to calculate SaaS sales tax for your customers, this guide is for you. It covers Idaho's SaaS tax rules and rates, what to account for when you build sales tax calculation into your product, and how ZipTax returns accurate Idaho rates through an API without you building and maintaining a rate engine.

Idaho SaaS sales tax at a glance

Product Taxability Rules

State Registration & Collection Triggers

Which types of software does Idaho tax?

Idaho draws its line at delivery method, not use case, and it draws that line in a different place than most states. Alabama and California tax a downloaded copy of software while exempting the cloud-accessed version. Idaho exempts both, and only taxes software when it physically ships on media the customer keeps.

That's a narrower taxable scope than you'll encounter in most other states. It's always best to classify rules at the product level rather than assuming Idaho behaves like its peers: two states can both say 'SaaS is exempt' and mean completely different things for your billing logic.

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

Under current rules, you don't. Whether a subscription is accessed remotely or downloaded, the sales tax on it is $0 in Idaho. There's no pending law that changes this: Idaho isn't on the 2027 timeline California, Colorado, and a handful of other states are working through. It's a stable exemption, not an impending one.

The rate question shows up only when a transaction crosses into Idaho's one taxable category: prewritten software delivered on physical media the customer keeps, or loaded onto hardware you ship. If any part of your catalog has a physical-media SKU alongside your SaaS offering, you still need a working rate engine for that slice of the business, even though your core subscription product owes nothing.

Option 1: Use the ZipTax Sales Tax API

You send the buyer's address at the point of sale, and the API resolves the jurisdiction and returns the applicable rate and taxability.

To calculate a live rate against an Idaho address, use the v60 endpoint:

Bash

curl -G https://api.zip-tax.com/request/v60 \
    -H "X-API-KEY: <apiKey>" \
    -d key=your-api-key \
    --data-urlencode "address=11321 W Chinden Blvd, Boise, ID, 83714"

Explore the REST API documentation to verify complete payload structures.

Pass a product taxability code alongside the address so the response can tell you the SaaS line is exempt and the physical-media line, if you sell one, is taxable, rather than hard-coding either answer into your checkout. Review Taxability Information Codes (TICs), or search for the correct product code for your catalog.

Three things to do with that response. Apply the exemption at the product level, not the order level, so a bundled order with one taxable physical-media line and one exempt SaaS line comes out right. Store the taxability basis on the transaction, not just the result, because rebuilding why a line was exempt later from a bare rate is lossy. Store the effective date too, even though Idaho's rule isn't currently in flux, so a later transaction carries whatever rule was in force at the time.

What an API will not tell you: your company's physical presence or economic registration status in Idaho. Tracking whether you've crossed the $100,000 threshold and must legally register remains on your side of the integration.

Option 2: Build and maintain it yourself

A real choice if your catalog is simple and you already hold jurisdiction data for other reasons. If you take this route, Idaho needs these things handled:

• A delivery-method classification, not a product-category one. The operative question for every SKU is how it reaches the customer: remote access, electronic download, or physical media, not what kind of software it is.
• A bundle rule. Software loaded onto storage media that ships with other hardware is taxable; the same software delivered as a download or accessed remotely is not. The same product can be exempt or taxable purely based on packaging.
• Threshold accumulation on the gross basis. Check economic nexus thresholds against gross sales. Idaho does not carve out exempt sales the way California's tangible-personal-property-only test does. Tax-exempt digital revenues count in full.
• A resort-city flag for physical-media sales. If you ship a CD, DVD, or branded USB drive into one of Idaho's 23 resort cities (Ketchum, Sun Valley, McCall, Sandpoint, and others), check whether that city's local option tax applies before assuming the statewide 6% is the whole story. Resort cities can tax anything already subject to state sales tax, which includes your physical-media line even though it never touches your SaaS line.

Four things to watch out for:

1. Assuming a "no download exemption," the way Alabama or California work. The most common cross-state implementation error on this page: carrying over a rule from a state that taxes downloaded software and applying it to Idaho, where downloads are exempt right alongside remote access.
2. Treating "resort city tax" as a local sales tax layered on everything. It isn't. It's capped at whatever is already state-taxable, so it can reach your physical-media SKU without ever reaching your core subscription product.
3. Miscounting the nexus threshold. Idaho includes exempt sales in its $100,000 nexus threshold. Build your threshold monitor on total gross sales into Idaho, not just taxable sales, to avoid under-registering.
4. Marketplace facilitator overlap. If you sell through a marketplace facilitator that already collects and remits for you, those sales absolutely still count toward your own individual $100,000 economic nexus threshold calculation in Idaho.

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

Registration and taxability are separate questions, and in Idaho that separation matters more than usual, because almost everything a typical SaaS company sells is exempt.

Rule 1: Monitor your registration trigger (nexus)

You must register to file with the state the moment either of these conditions is met:

• Physical presence: an employee working in Idaho, an office, inventory, or other property in the state.
• Economic threshold: your gross sales into Idaho cross $100,000 in the current or previous calendar year. There's no separate transaction-count prong to track.

Rule 2: Apply the correct billing logic once registered

• If every product you sell is SaaS, a download, custom software, or a digital subscription, your billing system should calculate tax at $0 and submit zero-dollar returns on schedule once you're registered. Idaho's exemption applies regardless of your registration status.
• If any part of your catalog ships on physical media, your billing system needs to apply Idaho's 6% rate to that line, plus a resort city's local option rate if the ship-to address is inside one, while continuing to zero-rate the SaaS and download lines on the same invoice.

Where ZipTax helps

If you're building a custom billing engine, a niche ERP, or a B2B SaaS platform, you don't need an enterprise compliance suite just to calculate an accurate checkout rate. You just need a fast, reliable endpoint.

ZipTax handles the infrastructure layer of sales tax calculation so your team can focus on your core product.

• Product-Level Taxability: Resolves exemption and taxability per line item, not per order, so a bundled sale with one exempt SaaS line and one taxable physical-media line comes back correct without custom logic on your end.
• Engineered for Platforms: Built specifically to embed live tax calculations directly into checkout workflows, API endpoints, and marketplace billing frameworks.
• Frictionless Pricing: Designed for cost-conscious development teams who want to pay strictly for active calculation calls without committing to heavy enterprise software contracts.

Get Idaho SaaS tax rates from an API

Address-level rates and product-level taxability for Idaho, plus the rest of the US, Canada, and select other markets. Free starter plan, then view ZipTax pricing for usage-based rates as you scale.

Frequently asked questions

Do you have to register in Idaho if your SaaS product is exempt there?

Yes, if your gross sales into Idaho cross $100,000 in the current or previous calendar year, or you have physical presence in the state. Idaho calculates this economic threshold using "gross sales," meaning your completely exempt SaaS revenue and downloaded software sales must be included in your count. Registration and taxability are independent tests: a company can be required to register, file on schedule, and remit $0, because every sale was exempt.

Does Idaho tax software differently depending on how it's delivered?

Yes, but the line sits in a different place than in most states. Idaho exempts both remotely accessed software (SaaS) and software delivered electronically or by load-and-leave, treating both as not tangible personal property. Only prewritten software sold and delivered on physical storage media the customer keeps, such as a CD, DVD, or flash drive, is taxable, along with any software loaded onto hardware you ship. States like Alabama and California tax the download and exempt the cloud version; Idaho exempts both and taxes only the physical copy.

Can a city add its own sales tax on top of the state's in Idaho?

Yes, but narrowly. Twenty-three Idaho cities, mostly resort towns such as Ketchum, Sun Valley, McCall, and Sandpoint, can levy a local option sales tax. Each city chooses its own scope, and some limit it to lodging, liquor by the drink, and restaurant food, but a resort city's local tax can never reach anything that isn't already subject to the state sales tax. Since SaaS and downloaded software aren't state-taxable, no resort city's local tax applies to them either; it can only reach your physical-media sales, if you make any.

Is custom software taxable in Idaho?

No. Idaho exempts the transfer of custom software regardless of the form or means by which it's delivered, the same treatment it gives SaaS and downloads, just under a separate rule. Software built by assembling preprogrammed modules or loading parameters into an existing program doesn't count as custom for this purpose and is taxed under the ordinary prewritten-software rules instead.

Sources

1. SaaS, downloaded software, and physical-media taxability: Idaho Admin. Code r. 35.01.02.027, "Computer Equipment, Software, and Data Services," authorized by Idaho Code § 63-3616, effective March 31, 2022.IDAPA 35.01.02.027
2. Economic nexus and marketplace facilitators: Idaho State Tax Commission, Online Sellers Guide.tax.idaho.gov
3. State sales tax rate: Idaho State Tax Commission, Sales and Use Tax Basics Guide.tax.idaho.gov
4. Resort city local option tax: Idaho State Tax Commission, City Sales Tax.tax.idaho.gov
5. Streamlined Sales Tax (SST) status: Streamlined Sales Tax Governing Board, Public Notice: 2026 Streamlined Sales Tax Member State Annual Compliance Reviews, Executive Director Initial Report.streamlinedsalestax.org