Is SaaS taxable? In roughly 20+ US states, yes — but the classification, rate, sourcing rule, and B2B vs B2C treatment differ in every one of them. This guide gives you the full 50-state matrix, statute citations from primary DOR sources, and the sourcing rules that determine which customer’s address controls the tax. And if you’d rather not learn 45 sets of state rules — we handle the whole thing for you, end-to-end, for a single flat fee.
Is SaaS Taxable? The Short Answer for 2026
Yes, in a growing minority of states — but “taxable” means very different things in different places.
Software-as-a-Service (SaaS) sales tax is one of the most fragmented, most litigated, and least uniform areas of US sales tax. Unlike physical goods — where the taxability rules are relatively settled — SaaS taxability turns on how each state chooses to classify a hosted software subscription. And every state has picked a different classification framework.
There is no official tally of how many US states tax SaaS, and the honest answer is that any headline number depends entirely on how you treat the edge cases: B2B-only taxation, home-rule city taxation, digital automated services classifications, and situational rulings. The state-by-state table below sets out where each state stands and the authority it rests on.
Quick-reference taxability summary
Here is the high-level view before we go deep:
| Taxability tier | Approximate # of states | Example states |
|---|---|---|
| SaaS clearly taxable statewide | ~17 | New York, Texas, Washington, Pennsylvania, Tennessee, Utah, Arizona, South Carolina |
| SaaS taxable with B2B/B2C split | ~3 | Connecticut, Ohio (partial), others |
| SaaS taxable only at local level | ~2 | Colorado (state exempt, home-rule cities tax), Illinois (Chicago Lease Transaction Tax) |
| SaaS clearly exempt | ~28+ | California, Florida, Georgia, North Carolina, Virginia, Michigan |
| Situational / unclear | ~2-4 | Depends on ruling patterns, bundling, delivery method |
Why SaaS taxability is more complex than physical goods
Physical goods are simple: tangible personal property is generally taxable unless specifically exempt. Every state has understood how to tax physical property since the 1930s.
SaaS is complex for four reasons:
- No transfer of tangible property. The customer never receives anything they can touch. Whether that counts as “tangible personal property” is a legal fiction each state decides on its own.
- The service vs. product boundary is fluid. Is SaaS a service (usually exempt in most states) or a product (usually taxable)? Different states have chosen different sides.
- Bundled offerings blur the line. Most SaaS contracts include implementation, support, training, storage, and API access. The “true object” test determines the whole thing’s taxability — and it can flip based on how you structure your invoice.
- B2B vs B2C matters. A handful of states apply different rates or different exemptions depending on whether the buyer is a business or a consumer.
The three taxability buckets: taxable, exempt, situational
For planning purposes, every SaaS product in every state falls into one of three buckets:
- Taxable — you must register, collect, and remit once you cross nexus.
- Exempt — no collection obligation, but you may still need to register if you cross the economic nexus threshold (in most states, exempt sales still count toward the threshold).
- Situational — taxability depends on the true object of the transaction, the delivery method, or the buyer’s status. This is where letter rulings, private letter opinions, and audit exposure live.
If you’re a SaaS founder reading this and already thinking “I’d rather not figure this out myself” — that’s the entire reason we exist. Sales Tax Compliance USA handles SaaS sales tax taxability analysis, multi-state registration, filing, and notice management as a done-for-you service. One flat fee per state, no software for you to learn. Book a free consultation or see what our full service includes.
How States Classify SaaS for Sales Tax
Every state that taxes SaaS has picked one of four classification frameworks. Understanding which framework applies is the first step to understanding taxability — because the framework controls the sourcing rule, the exemptions, and the audit risk.
SaaS as tangible personal property (TPP)
Some states treat pre-written software as tangible personal property regardless of whether it’s delivered on a CD, downloaded, or accessed via the cloud. Under this framework, SaaS is essentially treated as a rental or lease of pre-written software.
New York taxes SaaS as pre-written computer software under NY Tax Law §1105(a), based on the position that access to pre-written software constitutes a transfer of possession sufficient to trigger sales tax. The classification turns on the specific product and transaction rather than on the SaaS label alone.
SaaS as a taxable service (data processing, information services)
Texas is the leading example of this framework. Rather than classifying SaaS as software, Texas classifies it as a “data processing service” — one of the enumerated taxable services under the Texas Tax Code.
Texas treats SaaS as a taxable data processing service. Under Texas law, 20% of the amount charged for data processing services is exempt from tax, so the taxable portion is 80% of the charge unless another rule applies. The carve-out does not apply where the service is also taxable as another kind of taxable service other than an information service (see Texas Comptroller, Data Processing Services are Taxable).
SaaS as a digital product or digital automated service
Washington created a category called “digital automated services” (DAS) specifically to capture cloud-based software and services.
Washington classifies SaaS as a “digital automated service” under RCW 82.04.192 and subjects it to retail sales tax at the standard state and local rate, subject to the statutory exclusions in that section and to product-specific classification.
The ‘true object’ test and why it matters for bundled SaaS
If your SaaS product is bundled with consulting, implementation, training, or professional services, most states apply a “true object” test to determine whether the whole transaction is taxable:
- If the true object is the software (the customer is buying software with incidental services) → taxed as software.
- If the true object is the professional service (the software is incidental to the consulting engagement) → not taxed, or taxed differently.
The true object test is one of the biggest audit exposure areas for SaaS companies. Auditors will re-characterize transactions if they think you’ve mis-invoiced. The safest approach is to separately state the SaaS subscription from professional services on every invoice — and even then, the state may push back if the professional services are inseparably tied to the software.
If your SaaS offering bundles services in ways that could trigger true-object risk, contact us for a bundling review before your next audit.
50-State SaaS Taxability Matrix (2026)
This is the meat of the guide. Each state below is categorized by taxability status, with the statute citation, state rate, and any B2B/B2C distinction. Every determination is sourced to a primary DOR document — not a third-party matrix.
How to read this table:
– Taxable = SaaS is taxable at the standard state sales tax rate (plus local).
– Exempt = SaaS is not taxable at the state level.
– Local only = state exempts SaaS but home-rule localities may tax it.
– B2B split = different treatment for business vs. consumer customers.
States that tax SaaS
| State | Status | State rate | Primary authority |
|---|---|---|---|
| Alabama | Taxable | 4% | Ala. Code §40-23-1 et seq. |
| Arizona | Taxable (retail TPT class) | 5.6% | A.R.S. §42-5000 et seq. |
| Connecticut (B2B) | Taxable at 1% | Electronically accessed canned software sold to a business for its own use is generally taxable in Connecticut under the standard sales and use tax rules, subject to any applicable exemption. | Conn. Gen. Stat. §12-407; Special Notice 2019(8) |
| Connecticut (B2C) | Taxable at 6.35% | Electronically accessed canned software bought for personal use is generally taxable in Connecticut under the standard sales and use tax rules, subject to any applicable exemption. | Conn. Gen. Stat. §12-407; Special Notice 2019(8) |
| District of Columbia | Taxable | 6% | DC Code §47-2002 |
| Hawaii | Taxable (GET) | ~4-4.5% | HRS Ch. 237 |
| Iowa | Taxable | 6% | Iowa Code Ch. 423 |
| Kentucky | Taxable | 6% | KRS 139.200 |
| Maryland | Taxable | 6% | Md. Code Tax-Gen §11-101 |
| Massachusetts | Taxable | 6.25% | Mass. Gen. Laws Ch. 64H |
| Mississippi | Taxable | 7% | Miss. Code §27-65-1 et seq. |
| New Mexico | Taxable (gross receipts) | ~5.125%+ | NMSA 1978 §7-9-3 |
| New York | Taxable | 4% (state) + local | NY Tax Law §1105(a); TSB-A-15(2)S |
| Ohio | Taxable (B2B); B2C different | 5.75% | Ohio Rev. Code §5739.01(Y)(1)(c) |
| Pennsylvania | Taxable | 6% | 72 P.S. §7201(m); Info Notice 2016-01 |
| Rhode Island | Taxable | 7% | R.I. Gen. Laws §44-18-7 |
| South Carolina | Taxable (communications) | 6% | S.C. Code §12-36-910 |
| South Dakota | Taxable | 4.2% | SDCL Ch. 10-45 |
| Tennessee | Taxable | 7% | Tenn. Code §67-6-102 |
| Texas | Taxable (data processing, 80% base) | 6.25% | 34 Tex. Admin. Code §3.330 |
| Utah | Taxable | 4.85% | Utah Code §59-12-103 |
| Washington | Taxable | Washington’s combined sales tax rate includes a state component plus varying local rates. If you need the current rate for a specific WA jurisdiction, contact us for a current review. | RCW 82.04.192 |
| West Virginia | Taxable | 6% | W. Va. Code §11-15-1 et seq. |
States that do NOT tax SaaS
| State | Status | Authority |
|---|---|---|
| California | Exempt (no TPP transfer) | Under CDTFA Regulation 1502, the sale or lease of a prewritten program is not a taxable transaction where the program is transferred by remote telecommunications from the seller’s place of business to or through the purchaser’s computer and the purchaser obtains no tangible personal property, such as storage media, in the transaction. That is the basis on which SaaS and cloud-hosted software are generally treated as exempt in California. |
| Colorado | State exempt; Denver and other home-rule cities tax | Colorado does not impose state sales tax on SaaS, but certain home-rule cities (including Denver) tax SaaS at their own local rates. If you sell SaaS into Colorado home-rule jurisdictions, contact us for a current review of your local exposure. |
| Florida | Exempt | Florida does not tax most services; no SaaS provision |
| Georgia | Exempt | GA DOR position; SaaS not classified as TPP |
| Idaho | Exempt | Idaho Code §63-3616 |
| Illinois | State exempt; Chicago Lease Transaction Tax may apply | Illinois state exempts; see Chicago section below |
| Indiana | Exempt | IC 6-2.5-1-27 |
| Kansas | Exempt | K.S.A. 79-3603 |
| Louisiana | Exempt (state); some parishes may vary | La. R.S. 47:301 |
| Maine | Exempt | 36 M.R.S. Ch. 211 |
| Michigan | Exempt | MCL 205.51 et seq. |
| Minnesota | Exempt | Minn. Stat. Ch. 297A |
| Missouri | Exempt | Mo. Rev. Stat. §144.010 et seq. |
| Nebraska | Exempt | Neb. Rev. Stat. §77-2701 |
| Nevada | Exempt | NRS Ch. 372 |
| New Jersey | Exempt (services not taxable by default) | N.J.S.A. 54:32B-1 |
| North Carolina | Exempt | N.C. Gen. Stat. §105-164.3 |
| North Dakota | Exempt | N.D. Cent. Code Ch. 57-39.2 |
| Oklahoma | Exempt | 68 O.S. §1354 |
| Vermont | Exempt (post-2015 reversal) | 32 V.S.A. §9701 |
| Virginia | Exempt | Va. Code §58.1-609.5 |
| Wisconsin | Exempt | Wis. Stat. Ch. 77 |
| Wyoming | Exempt | Wyo. Stat. §39-15-101 |
No-sales-tax states (SaaS irrelevant)
Alaska (state), Delaware, Montana, New Hampshire, and Oregon do not impose a state sales tax at all. Alaska has some local sales taxes via the Alaska Remote Seller Sales Tax Commission — SaaS treatment varies by locality.
Home-rule and local complications
Three states create their own SaaS headaches beyond state-level rules:
- Colorado: state exempts SaaS, but Denver, Boulder, Aurora, Colorado Springs, and other home-rule cities may tax it independently. Each home-rule city requires separate registration.
- Illinois: state exempts SaaS, but Chicago imposes a Personal Property Lease Transaction Tax on “nonpossessory computer leases” — which the city interprets to include many SaaS subscriptions.
- Alabama and Louisiana: local jurisdictions with limited state-administered coverage may create separate obligations.
Home-rule complexity is the single most under-covered SaaS taxability issue. If your customers are in Colorado or Chicago, that’s not something a generic taxability matrix will catch. Contact us for a home-rule review.
Not sure how this applies to your business? We handle US sales tax registration, filing and remittance for ecommerce sellers as a fully managed service, for one fee. Book a free consultation and we will review your own position with you.
Deep Dive: The 12 Most Important States for SaaS Sellers
These are the states where SaaS taxability drives real dollars — either because the state has a large SaaS-buying market, because the rules are complex, or because audit activity is high.
1. New York
- Status: Taxable
- State rate: New York’s state sales tax rate is 4%, with local sales taxes added on top; the combined rate in New York City is 8.875%.
- Authority: New York Tax Law section 1105(a), together with a long line of Department advisory opinions dealing with software delivered as a service.
- Classification: Pre-written computer software
- Sourcing: Primary use location of the customer
- B2B/B2C: Same treatment
- Notable: New York’s Department of Taxation and Finance has been the most prolific state at issuing SaaS-specific advisory opinions. Enterprise SaaS with users across multiple states can use apportionment based on user location.
2. Texas
- Status: Taxable as data processing service
- State rate: Texas taxes SaaS-related charges at the state rate plus applicable local rates, and specific taxability, sourcing, and any statutory exclusions depend on how the service is characterized. If you sell SaaS into Texas, contact us for a current review.
- Authority: 34 Tex. Admin. Code §3.330
- Sourcing: Location where the service is received
- B2B/B2C: Same treatment
- Notable: Where a Texas SaaS charge is properly treated as a data processing service, 20% of the charge is exempt, so tax lands on about 80% of it. Confirm the classification and any other exclusion before applying the 80% figure. Texas is also the largest state economy where SaaS is unambiguously taxable — this is the state that generates the most SaaS sales tax dollars for many sellers.
3. Washington
- Status: Taxable
- State rate: Washington’s combined sales tax rate consists of a state component plus local rates that vary by jurisdiction. If you need to determine the correct combined WA rate for your transactions, contact us for a current review.
- Authority: Washington’s RCW 82.04.192, which sets out the definition of a digital automated service.
- Sourcing: Primary use location; Washington accepts MPU certificates
- Notable: Washington’s B&O tax also applies to SaaS revenue in addition to sales tax — a double-hit that many out-of-state sellers miss.
4. Pennsylvania
- Status: Taxable
- State rate: Pennsylvania’s state sales tax rate is 6%. Philadelphia adds a 2% local sales tax and Allegheny County adds 1%, giving combined rates of 8% and 7% respectively.
- Authority: Act 84 of 2016 (Tax Reform Code section 7201(m)(2)); PA Sales, Use and Hotel Occupancy Tax Bulletin 16-001
- Sourcing: Location of use
- Notable: Act 84 of 2016 is what made canned software taxable when it is electronically delivered, streamed or accessed, effective 1 August 2016; the Department’s Bulletin 16-001 announced that change rather than creating it.
5. Massachusetts
- Status: Taxable
- State rate: 6.25%
- Authority: Mass. Gen. Laws Ch. 64H; Directive 06-1
- Sourcing: Location where used
- Notable: Massachusetts includes pre-written software regardless of delivery method.
6. Connecticut
- Status: Taxable with B2B/B2C rate split — the most important state-level distinction in the country
- State rate (B2B): 1%. Connecticut DRS lists canned software electronically accessed or transferred, without any tangible personal property, purchased by a business for business use among the computer and data processing services taxed at the reduced 1% rate (see DRS services subject to sales and use taxes).
- State rate (B2C): Sold for personal or other non-business use, the same electronically accessed canned software is tangible personal property and is taxed at Connecticut’s standard 6.35% rate.
- Authority: Connecticut General Statutes sections 12-407(a)(13)(B) and 12-408; DRS Special Notice 2019(8)
- Notable: If your SaaS is primarily sold to businesses, the 1% rate substantially reduces the tax burden. But you must document the business-use nature of each transaction — if you can’t, CT will assess at 6.35%.
7. Ohio
- Status: Taxable for B2B; treatment differs for B2C
- State rate: 5.75% state + local
- Authority: Ohio Rev. Code §5739.01(Y)(1)(c)
- Notable: Ohio taxes “electronic information services” and “automatic data processing” when sold to business users. Consumer-facing SaaS often falls outside these definitions. Ohio accepts MPU certificates.
8. Tennessee
- Status: Taxable
- State rate: 7% state + local (max combined ~9.75%)
- Authority: Tenn. Code §67-6-102
- Notable: Tennessee accepts MPU certificates.
9. Utah
- Status: Taxable
- State rate: 4.85%
- Authority: Utah Code §59-12-103
- Notable: Utah accepts MPU certificates and is one of the more SaaS-friendly states for enterprise apportionment.
10. Arizona
- Status: Taxable under Retail TPT classification
- State rate: Arizona imposes a statewide TPT/use tax rate of 5.6%, with separate county and city rates layered on top; combined rates vary by jurisdiction and must be confirmed against the current TPT rate tables. If you need the combined AZ rate for a specific location, contact us for a current review.
- Authority: A.R.S. §42-5000 et seq.
- Notable: Arizona’s Transaction Privilege Tax framework treats SaaS as retail. Multiple TPT classifications may apply depending on the specific SaaS offering.
11. South Carolina
- Status: Taxable as communications service
- State rate: 6% state + local
- Authority: S.C. Code §12-36-910
- Notable: SC classifies SaaS under its communications service definition, not as software.
12. District of Columbia
- Status: Taxable
- State rate: 6%
- Authority: DC Code §47-2002
- Notable: DC’s SaaS treatment is broad — the statute captures “all wireless content” and hosted software. Registration and filing due 20th of following month.
Economic Nexus + SaaS: When You Have to Register
Even in states where SaaS is exempt, you may still be required to register once you cross an economic nexus threshold — because most states include all sales (taxable and exempt) in the threshold calculation.
The Wayfair 2018 baseline
South Dakota v. Wayfair (2018) established that a state can require remote sellers to collect and remit sales tax if they exceed either a sales-dollar or transaction-count threshold. Every state with a sales tax has now enacted an economic nexus statute. See our full economic nexus guide for the constitutional background.
2026 economic nexus thresholds for SaaS companies
Most states have settled on one of a few standard threshold structures:
- $100,000 OR 200 transactions (most common, ~20 states)
- $100,000 only (Georgia, Florida, others — dropped transaction count)
- $500,000 (California, Texas, Tennessee — larger economies)
- Mississippi: $250,000
- Alabama: $250,000
- New York: $500,000 AND 100 transactions
For the complete state-by-state threshold matrix, see our economic nexus thresholds guide.
Do exempt SaaS sales count toward the threshold?
In most states: yes. This is the trap that catches SaaS founders in exempt-SaaS states like California, Florida, and Georgia. Your SaaS sales aren’t taxable — but they still count toward the state’s threshold. Once you cross the threshold, you have a registration obligation even though you have no collection obligation.
Whether you need to register when all your sales are exempt is a fact-specific question — the answer depends on the state’s exact statutory language on exempt sales, wholesale sales, and marketplace-facilitated sales. If you’re near a threshold in an exempt state, contact us for a review.
Transaction-count thresholds and why they hurt low-ACV SaaS
If your average contract value is $50 and you have 200+ US customers in a state, you’re over the transaction-count threshold — even if you’re nowhere near the dollar threshold. This is a serious issue for consumer SaaS and freemium-with-paid-tier businesses.
The good news: many states have dropped the transaction count. The bad news: many still have it.
Sourcing Rules: Which Customer Address Determines Tax
Once you know a sale is taxable, you have to figure out which jurisdiction’s rate applies. The answer isn’t always obvious for SaaS.
Bill-to vs primary use location vs user location
States use one of three sourcing rules for SaaS:
- Bill-to address — simplest; the address on the invoice determines the rate. Used by many states as default.
- Primary use location — where the customer primarily uses the software. Used by New York, Washington, and others.
- User location — where individual users of the software are located. Rare, but relevant for enterprise SaaS.
For a single-user SaaS product where the buyer and user are the same person, all three usually give the same answer. For enterprise SaaS with users across multiple states, they can give wildly different answers.
Multiple Points of Use (MPU) certificates
MPU certificates are the single most under-used SaaS tax planning tool. They let an enterprise customer with users in multiple states apportion the SaaS charge across those states — reducing the tax base in high-rate states and eliminating tax entirely in exempt states.
States that generally accept MPU certificates for SaaS include Washington, Ohio, Utah, Tennessee, Kentucky, and several Streamlined Sales Tax members. The exact acceptance rules and documentation requirements vary. For a detailed MPU walkthrough, see our MPU certificate guide.
Handling remote/distributed enterprise customers
Modern SaaS buyers have users everywhere. Your billing system needs to capture:
- Bill-to address (for default sourcing)
- Primary use location (if state uses that rule)
- Users’ locations by state (for MPU apportionment where applicable)
Most SaaS companies capture only bill-to. That’s a tax over-collection problem in some states and a tax under-collection problem in others.
Local Tax Landmines for SaaS
State-level analysis is only half the picture. Three local tax regimes catch SaaS sellers by surprise.
Chicago Lease Transaction Tax
Chicago imposes a Personal Property Lease Transaction Tax on “nonpossessory computer leases” — which the City of Chicago Department of Finance has interpreted to include many cloud-hosted software and SaaS subscriptions used by customers physically located in Chicago.
The current rate and exact scope depend on the specific facts of the SaaS offering — Chicago has issued rulings that distinguish between different categories of cloud services. If you have Chicago-based customers and haven’t looked at the Lease Transaction Tax, contact us for a review before your next audit — this is one of the highest-exposure local taxes in the country for SaaS.
Colorado home-rule cities
Colorado’s state sales tax does not apply to SaaS. But Colorado has 70+ home-rule cities that administer their own sales tax independently, and several of them tax SaaS at their own rates.
Denver taxes SaaS at 5.15% under its home-rule sales tax code, independent of Colorado state exempt treatment.
Other Colorado home-rule cities (Boulder, Aurora, Colorado Springs, Fort Collins, and others) each have their own SaaS position. Each home-rule city requires separate registration and separate filing — the state’s SUTS portal doesn’t cover them. See our Colorado home-rule guide for the full landscape.
Alabama and Louisiana
Both states have complex local jurisdiction structures where local sales tax may or may not follow the state’s SaaS position. Louisiana in particular has parish-level administration that can create surprises for out-of-state sellers.
Exemptions That Apply to SaaS
Even in states where SaaS is taxable, specific transactions may be exempt.
Resale exemption
If your customer is buying your SaaS to resell it (e.g., a reseller repackaging your product), a resale certificate can exempt the sale from tax. This is genuinely rare for SaaS — most customers are end users, not resellers. But some agency and partner relationships qualify.
Government and 501(c)(3) exemptions
- Federal government purchases: exempt in all states (Supremacy Clause).
- State and local government purchases: exempt in most (but not all) states, subject to certificate requirements.
- 501(c)(3) organizations: exempt in some states, taxable in others. California, for example, does not automatically exempt 501(c)(3) purchases. State-specific certificates required.
Manufacturing and R&D exemptions
Some states exempt software purchased for use in manufacturing or R&D. Whether SaaS qualifies for these exemptions is state-specific and often depends on how the SaaS is used. Worth exploring for enterprise customers in manufacturing-heavy industries.
Certificate management
This is where most SaaS companies get burned in audits. You accept an exemption certificate at customer signup, file it, and never look at it again. Three years later, an auditor pulls your exempt sales, finds expired or invalid certificates, and assesses tax on every transaction.
Certificates expire in some states (annual renewal in a few). Multi-jurisdiction certificates work in some states and not others. And an expired or invalid certificate leaves you — not the customer — liable for the tax.
We manage exemption certificates as part of our done-for-you service. See exemption certificate management for how we handle this.
Special Situations: Non-US SaaS Companies Selling to US Customers
If you’re a SaaS founder in Australia, the UK, Ireland, New Zealand, Canada, South Africa, or anywhere else outside the US — and you have US customers — you have the exact same sales tax obligations as a US-based SaaS company.
Do you need an EIN to register?
Most states require an EIN (or an ITIN) to register for sales tax. If your entity doesn’t have one, you’ll need to apply — the IRS issues EINs to foreign entities via Form SS-4. This can take 4-8 weeks by mail, or faster via fax for foreign applicants.
Registering without a US bank account
Some states can only remit sales tax refunds and communicate via ACH — which requires a US bank account. Not every state requires this, but several do for high-volume filers.
Foreign entity registration mechanics per state
Some states require a registered agent with a physical address in the state. Some require you to register as a foreign entity with the Secretary of State before you can register for sales tax. Some accept online registration directly with the DOR.
The specific mechanics vary by state — and this is one area where DIY sales tax software falls down completely. Automated platforms assume you’re a US entity with a US EIN and US bank account. For non-US SaaS founders, the friction is often insurmountable without help.
We register non-US SaaS companies in all 50 states as part of our standard service. No US bank account, no EIN, no problem — we handle all of it. See sales tax for non-US founders or foreign company registration.
Registration, Filing, and Ongoing Compliance
Once you know where you have nexus and what’s taxable, you actually have to run compliance. Here’s what that looks like.
Where to register first: nexus prioritization
Don’t register alphabetically. Register by exposure — the states where you have the largest revenue, the highest tax rates, and the longest historical exposure. Typical priority order:
- States with confirmed physical nexus (FBA inventory, employees, contractors)
- States where you’ve crossed economic nexus with taxable SaaS
- High-tax states with significant customer bases (NY, WA, TX, PA)
- Home-rule city obligations (Chicago, Denver)
- Lower-exposure states with confirmed economic nexus
Filing frequencies
Most states assign a filing frequency based on your tax liability:
- Monthly — high-volume filers (typically >$1,000-$5,000/month in tax)
- Quarterly — mid-volume (default in many states)
- Annual — low-volume or exempt-only filers
Filing frequencies vary state-by-state and can change as your liability changes. For most SaaS companies, quarterly is the norm at launch and monthly is required as you scale.
Voluntary Disclosure Agreements (VDAs) for retroactive exposure
If you’ve had nexus in a state for years and haven’t been collecting, don’t just walk in and register — you’ll create prospective liability plus retroactive liability for every unregistered year.
Instead, use a Voluntary Disclosure Agreement (VDA). VDAs typically:
- Limit the state’s look-back to 3-4 years (versus unlimited otherwise)
- Waive penalties (interest still applies in most cases)
- Allow anonymous negotiation before you identify yourself
- Cannot be used once the state has contacted you
VDA program mechanics vary by state — look-back periods, penalty waivers, and anonymity rules all differ. If you’re sitting on unregistered retroactive exposure, contact us before doing anything else.
Notices and audits for SaaS
SaaS audits typically focus on three things:
- Sourcing — did you apply the right state’s rate based on the customer’s location?
- Exemption certificates — do you have valid certificates for every exempt sale?
- Bundling — did you correctly apply the true object test to your SaaS + services bundles?
Getting any of these wrong can convert a small deficiency into a large assessment.
Or: Let Us Handle SaaS Sales Tax For You
You’ve now read through 4,500+ words of SaaS taxability rules, and you’re maybe halfway to understanding your actual compliance obligations. There are 45+ state DOR websites, 20+ statute frameworks, dozens of letter rulings, and hundreds of local jurisdictions still to work through.
Or you can hand it to us.
What our done-for-you SaaS service includes
- Full taxability analysis — every SKU or subscription tier, mapped to every state’s rules, with documented positions
- Nexus assessment — where you have to register, in what order, and why
- Multi-state registration — including foreign entity registration where required, no US bank account or EIN needed
- Filing and remittance — every state, every month/quarter, on time, every time
- Exemption certificate management — collection, validation, renewal, storage
- Notice handling — when a state sends you a letter, we deal with it
- Audit defence — when a state audits, we handle the audit
- Home-rule city coverage — Chicago Lease Transaction Tax, Denver, and Colorado home-rule cities included
- VDA negotiation — for any retroactive exposure
One flat fee per state, all-in. No hourly billing. No software for you to log into. No dashboards to configure. You send us your revenue data; we handle everything else.
Who this is for
- SaaS founders scaling past $1M+ ARR who realize they should have started collecting sales tax two years ago
- Non-US SaaS companies with US customers who don’t want to figure out EINs, registered agents, and 45 DOR portals
- Founders whose CFO or accountant has flagged sales tax exposure and needs a specialist to actually handle it
- Anyone who’d rather build their product than learn another set of tax rules
Not for
- Companies that want to run compliance in-house with software
- Companies looking for the cheapest possible option (we’re not it — we’re the “done properly” option)
Ready to hand this off? Book a free consultation or see exactly what our done-for-you service covers.
Frequently Asked Questions
Is SaaS taxable in all 50 states?
No. As of 2026, approximately 20+ states tax SaaS in some form. The remaining states either exempt SaaS at the state level or don’t have a state sales tax at all. Some exempt states have home-rule cities (Denver, Chicago) that tax SaaS independently.
Which states tax SaaS in 2026?
The clearly-taxable list includes New York, Texas, Washington, Pennsylvania, Massachusetts, Connecticut, Tennessee, Utah, Arizona, South Carolina, Ohio (B2B), Rhode Island, Iowa, Kentucky, Mississippi, South Dakota, West Virginia, Alabama, Maryland, DC, Hawaii, and New Mexico. See the full matrix above for statute citations.
Is SaaS taxable in California?
California generally does not tax SaaS or cloud-hosted software where the customer does not obtain possession of the program, consistent with CDTFA Regulation 1502, though taxability can turn on how the offering is delivered and bundled. If your product includes downloadable components or on-premise elements, contact us for a current review. However, if you cross California’s $500,000 economic nexus threshold, you may still need to register — because California’s threshold generally includes exempt sales.
Is SaaS taxable in Texas?
Texas Comptroller guidance treats SaaS providers as data processing service providers required to collect state sales tax plus applicable local tax on taxable charges (see Publication 96-259); the availability of any partial exclusion depends on how the service is characterized. If you sell SaaS into Texas, contact us for a current review.
Is SaaS taxable in New York?
Yes. New York taxes SaaS as pre-written computer software under NY Tax Law §1105(a), at 4% state plus local (combined typically 8-8.875%).
Is SaaS taxable in Florida?
No. Florida does not tax SaaS at the state level. Florida generally does not tax services, and there is no specific SaaS provision.
Is B2B SaaS taxed differently than B2C SaaS?
In most states, no — the tax rate and treatment are the same. But Connecticut is the biggest exception: Connecticut taxes B2B SaaS at 1% and B2C SaaS at 6.35%. Ohio also treats B2B and B2C differently under its data processing framework.
Do I have to collect sales tax on SaaS if my company is based outside the US?
Yes. US sales tax obligations apply based on where your customers are, not where you are. If you cross a state’s economic nexus threshold, you must register regardless of where you’re incorporated. There is no tax treaty that exempts foreign SaaS companies from US state sales tax. See our non-US founder guide.
What is the Chicago Lease Transaction Tax and does it apply to my SaaS?
Chicago’s Personal Property Lease Transaction Tax applies to “nonpossessory computer leases,” which the City interprets to include many SaaS subscriptions used by Chicago-based customers. Rate and scope depend on the specific facts of your SaaS offering. If you have Chicago customers, contact us for a review — this is one of the highest-exposure local taxes in the country.
What is a Multiple Points of Use (MPU) certificate?
An MPU certificate lets an enterprise customer with users in multiple states apportion the SaaS charge across those states — reducing the tax base in high-rate states and eliminating tax entirely in exempt states. States that generally accept MPU certificates include Washington, Ohio, Utah, Tennessee, and Kentucky. See our MPU guide.
Do exempt SaaS sales count toward economic nexus thresholds?
In most states: yes. Even if your SaaS is exempt in California or Florida, your California or Florida sales count toward the state’s threshold. Once you cross, you may need to register even though you have no collection obligation. Rules vary by state — if you’re near a threshold in an exempt state, get a specific review.
What happens if I haven’t been collecting SaaS sales tax and I should have been?
Don’t just register — that creates prospective plus retroactive liability. Instead, use a Voluntary Disclosure Agreement (VDA) to limit the look-back, waive penalties, and negotiate anonymously before identifying yourself. VDA mechanics vary by state. Contact us before taking any action if you’re sitting on retroactive exposure.
How do I know which state’s tax rate to charge a SaaS customer?
Depends on the state’s sourcing rule. Most default to the customer’s bill-to address. Some (New York, Washington) use primary use location. Enterprise SaaS with multi-state users may qualify for MPU apportionment. Your billing system needs to capture the right address data — most SaaS billing platforms capture only bill-to, which is not sufficient in every state.
Can I get a resale exemption certificate from my SaaS customer?
Rarely, but yes in narrow cases. Resale exemption applies when your customer is actually reselling your SaaS (e.g., a reseller repackaging it, or a partner white-labelling it). Most SaaS customers are end users and don’t qualify. Government and 501(c)(3) exemptions are more commonly applicable — but the certificate management is where audits find issues.
Last verified: 2026-07-02
This article is for informational purposes only and does not constitute tax advice. Consult a licensed tax professional before acting on any of this content.
