If you're building a product that needs to calculate SaaS sales tax for your customers, this guide covers Wisconsin's SaaS tax rules and rates, what to account for when you build sales tax calculation into your product, and how Ziptax returns accurate Wisconsin rates through an API without you building and maintaining a rate engine.
Wisconsin SaaS sales tax at a glance
Product Taxability Rules
| Does Wisconsin tax SaaS? | No. Exempt as a nontaxable data processing service when the vendor operates and controls the server, the customer has no physical access to it, and any local download is incidental to the service. |
|---|---|
| Is a law change pending? | No. Checked directly against Wisconsin Department of Revenue guidance; nothing currently changes this. |
| Base State Tax Rate | 5% |
| Local Combined Rate Range | 5% where no county tax applies, up to 7.9% in the City of Milwaukee once the county and city taxes stack on top of the state rate. Not resolvable from ZIP code alone. |
| Primary Data Sources | Wisconsin Department of Revenue |
State Registration & Collection Triggers
| What triggers a tax collection requirement? | Meeting either of these conditions (whichever happens first): Economic nexus: gross sales into Wisconsin exceeding $100,000 in the current or previous calendar year. No transaction-count component; Wisconsin repealed its 200-transaction test in 2021. Physical nexus: an office, inventory or other property, or an employee working in Wisconsin. |
|---|---|
| What revenue counts toward the $100,000 threshold? | Gross sales into Wisconsin, which the Department of Revenue defines to include taxable, nontaxable, and resale sales. |
| Does exempt SaaS revenue count toward the $100,000 limit? | Yes, it counts toward the threshold limit. However, Wisconsin does not require sellers to register for a permit if 100% of their sales are exempt, so hitting this threshold only triggers a registration duty if you also make a taxable sale. |
| Lookback Calculation Window | Current or previous calendar year (a fixed calendar-year test, not a rolling 12-month window). |
| Are marketplace sales included? | Yes, for the threshold count. Sales a marketplace provider facilitates on a seller's behalf count toward that seller's own $100,000 gross sales figure, even though the marketplace provider is the one required to collect and remit the tax on those sales. |
| SST State (Streamlined Sales Tax)? | Yes. Wisconsin has been a Full Member of Streamlined Sales Tax since October 1, 2009. |
| Primary Data Sources | Wisconsin Department of Revenue, Streamlined Sales Tax Governing Board |
Which types of software does Wisconsin tax?
Wisconsin taxes software based on who controls the server and whether what the customer gets is possession of software or just access to a service, not based on a dedicated SaaS statute. Prewritten computer software is defined as tangible personal property no matter how it reaches the customer, which is why downloaded and physical-media software are both taxable.
Remote access to software the vendor hosts and controls, with no more than an incidental local download, falls outside that definition instead.
| What you sell | Taxable in Wisconsin |
|---|---|
| SaaS, accessed remotely, vendor controls the server, any download merely incidental | No |
| SaaS where the customer operates or controls the server, or a required download isn't merely incidental | Likely yes on that portion. Treat it as a separate, taxable line until you confirm otherwise. |
| Prewritten (canned) software, downloaded or on physical media | Yes, regardless of delivery method |
| Custom software written to a specific customer's specifications and not later resold to anyone else | No |
| Modifications to prewritten software, built to a specific customer's specs and separately stated on the invoice | No |
| Specified digital goods (digital audio works, digital audiovisual works, digital books) | Yes, unless the same good would be exempt in its tangible form |
| Other electronically delivered content, such as access to an online database or information product | Varies. Some of these fall under a separate taxable "additional digital goods" category (e.g., pricing/valuation databases). Confirm before assuming exempt. |
| SaaS bundled with tangible goods | Split the bundle. Tangible line items are taxable and the software portion follows its own rule. If the invoice does not separate them, the whole charge is exposed. |
Bundles are where implementations break, the same as anywhere else. Apply taxability per line item, not per order: a SaaS subscription that ships a required piece of hardware, a non-incidental local client, or a physical onboarding kit stays exempt on the pure-access portion, but the tangible or locally-controlled portion is taxable, and an undifferentiated lump sum drags the whole invoice into taxable territory.
How do you charge the correct sales tax rate for SaaS in Wisconsin?
Under current rules, you mostly don't. Because remotely hosted SaaS that meets the data processing test is exempt, the sales tax on that subscription sold to a Wisconsin customer is $0.
That changes the moment any part of the deal stops looking like pure hosted access: a downloaded client that isn't incidental, customer control over the hosting environment, physical media, a bundled tangible good, or a specified digital product sold alongside the subscription all bring tax back into the picture, and Wisconsin has no pending transition to plan around, so this is the steady state, not a temporary one.
When some portion of a sale is taxable, engineering teams have two options for calculating the correct rate on that portion: call a real-time sales tax API, or manually build and maintain an internal rate engine.
Option 1: Use the Ziptax Sales Tax API
You send the buyer's address at the point of checkout, and the API evaluates the exact boundary lines, including whether the address sits inside the City of Milwaukee and which county's rate applies there.
To calculate a live rate against a Wisconsin 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=200 E Wells St, Milwaukee, WI, 53202"To verify complete payload structures, explore the REST API documentation.
With that response:
- Multiply by the combined rate rather than assembling it from the components.
- Store the jurisdiction on the transaction, because rebuilding it later from an address is lossy.
- Store the effective date too, since Milwaukee's city and county rates only started in 2024 and a stored rate is only right until the next change.
What an API will not tell you: whether your company has crossed a nexus threshold in Wisconsin, and whether a specific local or bundled component of a hybrid product is enough to make the whole charge taxable. Both stay on your side of the integration.
Option 2: Build and maintain it yourself
Worth considering if you already hold jurisdiction data for other reasons. If you take this route, Wisconsin needs four things handled:
- A product taxability decision separate from the rate lookup. SaaS is exempt only when it passes the Department of Revenue's three-part test: the vendor controls the server, any local download is incidental, and nothing else taxable is bundled in. Downloaded or physical-media software and specified digital goods are taxable regardless of that test.
- Threshold accumulation on the right basis. Wisconsin's $100,000 threshold is measured on gross sales, which the Department of Revenue defines to include taxable, nontaxable, and resale sales, not just taxable ones. That means exempt SaaS subscription revenue counts toward it, and sales a marketplace facilitates on your behalf count too, even though the marketplace is the one collecting.
- Address-level rate resolution for whatever portion of a transaction is taxable. Wisconsin stacks a state rate, a county rate that varies by county, and, in one city only, a city rate on top of both.
- An effective date on every rule. Milwaukee's city and county rates both started January 1, 2024, and the Department of Revenue's own guidance on software and digital goods carries its own revision dates, which can shift the detail of a rule without changing the headline exemption.
Five things to watch out for:
- ZIP-based shortcuts. The City of Milwaukee itself spans three counties, Milwaukee, Washington, and Waukesha, each with a different county tax rate, so a Milwaukee address can combine to 7.9%, 7.5%, or 7.0% depending on which county it actually falls in. A city name or ZIP code alone can miss the difference, so resolve the full street address.
- Treating remote access as automatically exempt. The Department of Revenue's exemption is a three-part test, not a blanket rule for anything delivered over the internet: the customer must have no control over the vendor's server, any download must be incidental rather than the point of the sale, and nothing else taxable can be bundled in. A product that gives customers meaningful control over the hosting environment, or ships a non-incidental client application, risks failing that test on the affected piece.
- Assuming exempt SaaS revenue doesn't count toward registration. Wisconsin's $100,000 threshold is measured on gross sales, which the Department of Revenue explicitly defines to include nontaxable and resale sales alongside taxable ones. A pure-SaaS seller can cross that threshold on subscription revenue alone and still need to register, even while owing $0 in tax on every one of those sales.
- Treating the premier resort area tax as a catch-all local rate. A handful of Wisconsin tourist towns, including Wisconsin Dells and the Village of Lake Delton at 1.25% and several others at 0.5%, add a local tax on top of the state and county rate. It applies only to specific retail, lodging, food service, and amusement businesses, not to software or data processing services, so it normally doesn't apply to a SaaS seller even on a taxable digital-goods line, but a bundled retail or amusement offering in one of those towns would need it factored in.
- Rate and jurisdiction changes landing off-cycle. Milwaukee's city and county rates both took effect January 1, 2024, and new premier resort area taxes in Sturgeon Bay and Minocqua take effect July 1, 2026. A stored rate is right until the next change, and nothing tells you when that happened unless you're tracking effective dates.
When does a SaaS business have to collect sales tax in Wisconsin?
Registration and collection are two separate obligations with completely different triggers. Conflating them is where most engineering implementations go wrong, and it is especially easy to get wrong in an exempt state, where it's tempting to assume no tax means no obligations at all.
To get this right in Wisconsin, have your application and billing stack track these two operational rules.
Rule 1: Monitor your registration triggers (nexus)
You must legally register to file with the state the moment either of these conditions is met:
- Physical presence: an employee working in Wisconsin, an office, inventory held in the state, or leased server capacity.
- Economic threshold: check economic nexus thresholds. Your gross sales into Wisconsin, including exempt SaaS revenue and sales facilitated through a marketplace, cross $100,000 in the current or previous calendar year.
Rule 2: Apply the correct collection logic
A pure-SaaS seller can cross Wisconsin's $100,000 threshold on subscription revenue alone, since the test counts gross sales rather than taxable sales.
Once registered, your billing system should calculate tax at $0 on every exempt SaaS line and submit zero-dollar returns on schedule, the same outcome as any other exempt state, just reached by a route that doesn't exclude the exempt revenue from the count.
Registration becomes a live tax-collecting event the moment any revenue is actually taxable: a non-incidental downloaded client, customer control over hosting, physical media, a bundled tangible good, or a specified digital product sold alongside the subscription.
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.
- Rooftop Precision: Resolves rates across 12,000+ U.S. tax jurisdictions using exact address and coordinate-based lookups, eliminating the accuracy liabilities of ZIP-based shortcuts, including Wisconsin's county and single-city rate layers.
- 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.
- The TaxCloud Runway: When your transaction volume scales or your users demand automated filing and remittance services, you can pair Ziptax with TaxCloud for the rest of compliance. You get a lightweight API to deploy today and a filing and remittance backend ready when you need it.
Get Wisconsin SaaS tax rates from an API
Address-level rates for every Wisconsin jurisdiction, plus the rest of the US., Canada, and select other markets.
Frequently asked questions
Do you have to register in Wisconsin if your SaaS product is exempt there? No, provided 100% of your sales are exempt. Wisconsin's $100,000 economic nexus threshold is measured on gross sales into the state, which the Department of Revenue defines to include taxable, nontaxable, and resale sales. However, Wisconsin does not require a business to hold a seller's permit if all of its sales are exempt from sales and use tax. If you cross the $100,000 gross sales threshold strictly on exempt SaaS subscriptions, you establish economic nexus, but you do not need to register until you make a taxable sale. Registration and taxability are independent tests: registration turns on whether you have nexus AND make taxable sales; taxability turns on what you sell.
Does Wisconsin tax software differently depending on how it's delivered or hosted?Yes, and control over the server matters more than the download itself. Software a customer downloads, receives on physical media, or otherwise takes possession of is taxable prewritten computer software, regardless of delivery method. Software the customer only accesses remotely, with the vendor keeping control of the server and any local download limited to an incidental piece, is exempt as a nontaxable data processing service. Custom software built to one customer's specifications, and not later resold to anyone else, is also exempt.
Can you use a ZIP code to get the Wisconsin sales tax rate? Not reliably in every case. The City of Milwaukee itself spans Milwaukee, Washington, and Waukesha counties, and each county applies a different county tax rate on top of the state rate and the city's own tax. Two addresses that share a Milwaukee ZIP code or city name can land in different counties and combine to different rates. Resolve the rate from the full street address instead of a ZIP-level or city-level lookup.
Does the City of Milwaukee's sales tax apply to SaaS? No, not to a SaaS subscription that qualifies for Wisconsin's exemption, since a local tax only applies to a sale that's taxable in the first place, and Milwaukee's 2% city tax is no exception. It becomes relevant the moment something in the same account is taxable: a non-incidental downloaded client, a bundled tangible good, or a specified digital product sold to a Milwaukee-area customer, in which case the applicable combined rate depends on which of the three counties underlying that Milwaukee address the sale is sourced to.
Sources
- SaaS and cloud computing exemption, delivery-based taxability of prewritten software, custom software treatment: Wisconsin Department of Revenue, "Sales and Use Tax Treatment Computer: Hardware, Software, Services" (Guidance Document Number 100204). https://www.revenue.wi.gov/Pages/FAQS/pcs-computerc.aspx
- Prewritten computer software as tangible personal property: Wisconsin Department of Revenue, "What transactions are subject to the sales tax in Wisconsin?" (Guidance Document Number 100218). https://www.revenue.wi.gov/Pages/FAQS/ise-taxable.aspx
- Digital goods, specified digital goods, and additional digital goods: Wisconsin Department of Revenue, "What are digital goods and are they taxable?" (Guidance Document Number 1000115). https://www.revenue.wi.gov/Pages/FAQS/ise-diggoods.aspx
- Seller's Permits and Pure-Exempt Registrations: Wisconsin Department of Revenue, "Sales and Use Tax Permits" (Fact Sheet). https://www.revenue.wi.gov/Pages/FAQS/pcs-seller.aspx
- State and county sales tax rates, Milwaukee city and county tax: Wisconsin Department of Revenue, "What is the sales tax rate in Wisconsin?" (Guidance Document Number 100047). https://www.revenue.wi.gov/Pages/FAQS/pcs-taxrates.aspx
- Premier resort area taxes: Wisconsin Department of Revenue, "What is the premier resort area tax?" (Guidance Document Number 100190). https://www.revenue.wi.gov/Pages/FAQS/pcs-premier.aspx
- Economic nexus and the $100,000 threshold, calendar-year lookback: Wisconsin Department of Revenue, "Remote Sellers: Wayfair Decision" (Guidance Document Number 100241); "Remote Sellers Common Questions" (Guidance Document Number 100195). https://www.revenue.wi.gov/Pages/Businesses/remote-sellers.aspx
- Marketplace facilitator collection duty and threshold treatment: Wisconsin Department of Revenue, "Marketplace Providers and Sellers" (Guidance Document Number 100223); "Marketplace Seller Common Questions" (Guidance Document Number 100272). https://www.revenue.wi.gov/Pages/FAQS/ise-marketplace-sellers.aspx
- Streamlined Sales Tax (SST) status: Streamlined Sales Tax Governing Board, Wisconsin state detail. https://www.streamlinedsalestax.org/state-details/wisconsin