TLDR
- Roughly half of US states impose some form of sales tax on SaaS, and the rules differ enough that a product taxed in Texas may be exempt in California.
- Economic nexus thresholds, not physical offices, are what most SaaS companies trip over: sell enough into a state and you owe tax there, regardless of where your servers sit.
- Partial taxability states like New York create the most confusion: SaaS sold to businesses may be taxed differently than SaaS sold to consumers.
- The compliance burden compounds fast after $500K ARR, and most early-stage founders discover their exposure after an audit notice, not before.
- Automated tax engines like Anrok, Avalara, and TaxJar exist specifically to handle SaaS product taxability determinations state by state.
Understanding SaaS sales tax by state is one of the more consequential compliance gaps for US software companies. Roughly 25 states currently tax SaaS in some form, ranging from full taxation on all software subscriptions to partial rules that only tax SaaS when it functions like a data processing service or when the customer is a consumer rather than a business. States like Texas, New York, and Pennsylvania tax SaaS broadly. States like California, Florida, and Virginia do not. Economic nexus thresholds, typically $100,000 in sales or 200 transactions per state per year, create filing obligations without any physical presence required.
Why SaaS Founders Get This Wrong
The assumption that digital products escape sales tax made sense in 1990. States wrote their sales tax codes around tangible personal property, and software that never touched a physical disk seemed safe. That era ended with the 2018 Supreme Court ruling in South Dakota v. Wayfair, which let states impose sales tax obligations on remote sellers based on economic activity alone.
Most SaaS founders know Wayfair happened. Fewer understand how aggressively states have moved since then. As of their current published guidance, over 20 states have explicitly addressed SaaS taxability through statutes, regulations, or formal administrative rulings. The answer varies, and in several states it depends on facts about your product that are not obvious from the outside.
The other common mistake: treating all software as one category. States draw lines between canned software, custom software, SaaS accessed remotely, and software delivered electronically. The same product, priced identically, can fall into different taxability buckets across state lines. This matters for fintech SaaS margins that are already tighter than founders expect.
Which States Tax SaaS? The Full Taxability Table
The table below reflects each state’s published position on remotely accessed software as a service. “Partial” means the state taxes some SaaS but exempts other types, typically based on whether the customer uses the software for business input, whether the product functions like data processing, or whether the subscription grants a license to prewritten code.
| State | SaaS Taxable? | Notes |
|---|---|---|
| Alabama | Yes | Taxes SaaS as a computer software service |
| Alaska | No state tax | No statewide sales tax; some local jurisdictions may vary |
| Arizona | No | Remotely accessed software generally not taxable |
| Arkansas | Yes | SaaS taxed as a digital product |
| California | No | SaaS not taxable when no tangible medium is transferred |
| Colorado | No | Cloud-based SaaS generally exempt |
| Connecticut | Yes | Taxes SaaS as a data processing service |
| Delaware | No sales tax | No statewide sales tax |
| Florida | No | SaaS is not taxable; no clear statutory basis to tax it |
| Georgia | No | Remotely accessed software is not tangible personal property |
| Hawaii | Yes | General excise tax applies broadly, including to SaaS |
| Idaho | No | SaaS not subject to sales tax |
| Illinois | Partial | Taxes SaaS if it involves personal property; complex fact-based determination |
| Indiana | No | SaaS generally not taxable |
| Iowa | Yes | Taxes SaaS as a specified digital product |
| Kansas | Yes | SaaS subject to sales tax |
| Kentucky | Yes | Taxes SaaS explicitly as a digital product since 2018 |
| Louisiana | Partial | Business-use exemptions available; depends on customer type |
| Maine | No | SaaS not taxable |
| Maryland | Yes | Taxes SaaS as a digital product |
| Massachusetts | Partial | Taxes SaaS that constitutes a “transfer of prewritten software” |
| Michigan | No | SaaS is not taxable under current guidance |
| Minnesota | Yes | Taxes SaaS as prewritten computer software |
| Mississippi | Yes | SaaS taxable as a computer software service |
| Missouri | No | SaaS not taxable |
| Montana | No sales tax | No statewide sales tax |
| Nebraska | Yes | Taxes SaaS as a computer software maintenance service |
| Nevada | No | SaaS not taxable |
| New Hampshire | No sales tax | No statewide sales tax |
| New Jersey | Yes | SaaS taxable as specified digital products |
| New Mexico | Yes | Gross receipts tax applies to SaaS |
| New York | Partial | Taxes SaaS when it functions as a taxable information service or is used for entertainment; B2B exemptions available |
| North Carolina | Yes | SaaS taxable as a digital product |
| North Dakota | No | SaaS not taxable |
| Ohio | Yes | SaaS taxable as an electronic information service |
| Oklahoma | No | SaaS not taxable |
| Oregon | No sales tax | No statewide sales tax |
| Pennsylvania | Yes | Taxes SaaS as a computer service |
| Rhode Island | Yes | SaaS taxable as a specified digital product |
| South Carolina | No | SaaS not taxable under current rules |
| South Dakota | Yes | Taxes SaaS broadly under post-Wayfair framework |
| Tennessee | Yes | SaaS taxable as a computer software service |
| Texas | Yes | Taxes SaaS as a data processing service at 80% of the sale price (per Texas Comptroller guidance) |
| Utah | Yes | SaaS taxable as prewritten computer software |
| Vermont | Yes | Taxes SaaS as specified digital products |
| Virginia | No | SaaS not taxable |
| Washington | Yes | Taxes SaaS under its broadly written B&O and retail sales tax |
| Washington DC | Yes | SaaS subject to sales tax as a digital product |
| West Virginia | Yes | SaaS taxable as a digital automated service |
| Wisconsin | Yes | SaaS taxable as a digital good |
| Wyoming | Yes | SaaS taxable as a digital product |
Texas deserves a closer look because its rule is unusual. Per the Texas Comptroller’s published guidance, the state taxes SaaS as a data processing service, but only on 80% of the sales price. The remaining 20% is treated as a nontaxable component. It is one of the few states with a built-in statutory discount for the service element.
New York is the other state that confuses founders most often. The state taxes SaaS when it functions as an information service or entertainment, but provides exemptions when the software is used exclusively by the purchasing business internally. A payroll SaaS sold to a company for internal HR use may be exempt. That same company selling customer-facing SaaS to consumers faces a different analysis.
What Is Economic Nexus for SaaS, and When Does It Trigger?
Physical nexus is the older concept: an office, an employee, or a warehouse in a state creates a tax collection obligation. Economic nexus is what matters now for most SaaS companies. After Wayfair, states can require remote sellers to collect and remit sales tax once they exceed a defined sales volume or transaction count in that state.
The most common economic nexus threshold is $100,000 in annual sales or 200 transactions into a state. Most states adopted this framework directly after Wayfair. A smaller number use different thresholds. California, for example, uses $500,000 as its sales threshold with no transaction count minimum. Kansas, at various points, has attempted to assert nexus with no threshold at all, though that position has been legally contested.
| State | Sales Threshold | Transaction Threshold |
|---|---|---|
| California | $500,000 | None |
| Texas | $500,000 | None |
| New York | $500,000 | 100 transactions |
| Most other states | $100,000 | 200 transactions |
| Washington | $100,000 | None (transactions removed) |
| Pennsylvania | $100,000 | None |
| South Dakota | $100,000 | 200 transactions |
Hitting the threshold creates a registration and filing obligation, not just a collection obligation. You have to register with the state’s department of revenue, determine whether your product is taxable there, collect the correct rate on taxable sales, and file periodic returns. Failure to register after crossing the threshold creates back liability, often with interest and penalties, even if you never collected a dollar from customers in that state.
One nuance worth knowing: most states look at total gross sales into the state when measuring nexus, not just taxable sales. So even if your SaaS turns out to be exempt in a given state, your exempt sales may still count toward the nexus threshold. Crossing the line triggers registration. Whether you then collect tax depends on taxability.
The FintechSpecs SaaS Tax Exposure Scan: A Four-Step Framework
Most SaaS founders do a one-time nexus check and forget about it. That approach breaks down as revenue grows and the customer base spreads across new states. The FintechSpecs SaaS Tax Exposure Scan is a repeatable quarterly process, not a one-off exercise.
Step 1: Map Revenue by Customer State
Pull every subscription payment from the past 12 months and tag it to the customer’s billing address state. Your payment processor or billing platform should have this data. Stripe’s tax reporting exports, Chargebee’s revenue reports, and Recurly’s analytics all produce state-level breakdowns. What you are looking for: states where you are approaching the standard $100,000 or $500,000 economic nexus thresholds, as a practical monitoring trigger, FintechSpecs suggests flagging states where you have reached roughly 80% of the applicable threshold in annual revenue or transaction count. Those are approaching-threshold states that need monitoring next quarter.
Step 2: Check Taxability Status for Each At-Risk State
For every state where you are near or above the economic nexus threshold, confirm whether your specific product category is taxable. Do not assume “SaaS” is a single category. Look at whether your product involves a license to prewritten software, access to a hosted service, or delivery of a digital product. States like Illinois and Massachusetts require a fact-specific analysis. The state revenue department’s published guidance or a tax advisor’s written opinion is worth having here.
Step 3: Identify Registration Gaps
Compare your list of threshold-crossing states against the states where you are currently registered to collect sales tax. Any state where you crossed the threshold but are not registered is a gap. Those represent potential back liability. Many states have voluntary disclosure programs that let you come forward, pay back taxes, and receive a waiver of penalties. Acting before an audit is almost always better than responding to one.
Step 4: Automate Forward-Looking Compliance
Once you know where you have exposure, manual tracking does not scale. At a few hundred customers across 20 states, the quarterly filing burden becomes material. This is when tax engines earn their keep. Tools like Anrok, Avalara, and TaxJar integrate directly with billing systems and handle nexus monitoring, taxability determination, rate calculation, and return filing. The comparison of how these tools handle SaaS-specific taxability rules is covered in the Anrok vs Avalara vs TaxJar breakdown published separately.
How Do SaaS Sales Tax Filing Rules Work Once You Have Nexus?
Registration is step one. After that, the filing calendar matters. States assign filing frequencies based on your sales volume in that state. Low-volume sellers typically file annually or quarterly. Higher-volume sellers may be required to file monthly. Getting assigned to a monthly schedule in Texas or New York while still doing it manually is where companies start missing deadlines.
Filing dates vary by state. California sales tax returns are typically due the last day of the month following the close of the reporting period. Texas uses the 20th of the following month for monthly filers. States also have different rules about what counts as the filing date versus the payment due date. Some states allow an extended filing deadline if payment is made on time. Others treat late filing and late payment identically.
The Streamlined Sales Tax (SST) program simplifies some of this. SST member states have harmonized their tax bases and administrative rules to make multi-state compliance easier. SST membership does not change whether SaaS is taxable in those states, but it does reduce the administrative variation in how returns are filed and rates are reported. For the current list of full member states, refer to the SST Governing Board’s published membership page.
For founders using a merchant of record versus a standard payment processor, the compliance responsibility shifts. A true merchant of record like Paddle or Lemon Squeezy takes on the sales tax obligation as the seller of record, which removes the filing burden from the SaaS company entirely. That tradeoff comes with fees and some loss of billing flexibility, and it is worth understanding before assuming it is the simpler path.
Which States Are the Highest-Risk for SaaS Companies?
High-risk here means: taxable, large customer populations, actively auditing remote sellers, and no obvious exemption for B2B use cases. Five states meet all four criteria.
Texas
Texas taxes SaaS as a data processing service, and the Texas Comptroller actively enforces against remote sellers. The $500,000 economic nexus threshold is higher than most states, but any SaaS company with meaningful US revenue crosses it quickly. Per the Texas Comptroller’s published rules, only 80% of the sales price is subject to tax, an unusual structure that still results in real tax liability on large contracts.
Pennsylvania
Pennsylvania taxes SaaS and has a $100,000 nexus threshold. The state’s Department of Revenue has issued guidance treating remotely accessed software as a taxable computer service. There is no blanket B2B exemption. Enterprise SaaS sold to Pennsylvania businesses is taxable, full stop.
New York
New York’s partial-taxability rules are the most complex in the country for SaaS companies. The key question is whether the software constitutes a taxable information service. The state has a $500,000 threshold with a 100-transaction minimum, making it relevant only for companies with significant New York revenue, but the taxability analysis itself is required regardless of deal size.
Washington
Washington taxes SaaS under its broadly written retail sales tax and B&O (business and occupation) tax framework. The Washington Department of Revenue applies both taxes to software services, and the B&O tax applies to gross revenue, not profit. Even unprofitable SaaS companies owe B&O tax on Washington revenue. The $100,000 nexus threshold uses only a sales test after the state removed the transaction count.
Connecticut
Connecticut taxes SaaS as a data processing and information service. The state has been aggressive in its treatment of cloud services since 2019 and has a $100,000 threshold. Connecticut also applies sales tax to maintenance and support contracts associated with taxable SaaS, which can catch companies off guard when enterprise customers request service agreements.
States Where SaaS Is Not Taxable: What That Actually Means
California, Florida, Virginia, and most other “non-taxable” states have not passed legislation to tax SaaS, or have issued guidance explicitly excluding remotely accessed software from their sales tax base. That does not mean zero compliance work. It means you may not need to collect sales tax from customers in those states, but you may still need to register if you cross the economic nexus threshold, file returns showing zero tax due, and document why your sales are exempt.
Florida is an instructive case. The state taxes tangible personal property and a short list of specifically enumerated services. SaaS is not on that list. But if your SaaS product delivers any element that Florida might classify as a taxable communication service or a digital product sold at retail, the analysis changes. The general exemption is not a blanket pass for every product architecture.
California’s position is that SaaS is not taxable because no tangible personal property changes hands and no electronically downloaded software is delivered to the customer. However, California’s $500,000 nexus threshold means any reasonably successful SaaS company needs to register there and file returns, even if every return shows zero tax collected. The compliance burden exists even in the absence of tax liability.
How Do Partial Taxability States Work in Practice?
Illinois provides the clearest example of partial taxability complexity. The state has long taxed prewritten software delivered electronically, but has treated remotely accessed SaaS (where no software is ever transferred to the customer) as potentially exempt. The distinction turns on whether the customer “obtains” software or merely “uses” it through the seller’s infrastructure. Illinois has not fully resolved this question with binding statutory language, leaving many SaaS products in a gray zone.
Massachusetts taxes SaaS when it involves the transfer of prewritten software, even if that transfer occurs electronically. The practical question is whether accessing software through a browser constitutes a “transfer.” The Massachusetts Department of Revenue has issued rulings addressing specific product types, but blanket guidance covering all SaaS is not available. Companies with Massachusetts customers should get a product-specific taxability determination, not rely on a general exemption.
Louisiana taxes SaaS sold to consumers differently from SaaS sold for business inputs that qualify for the business-to-business exemption. The exemption application process requires documentation from the buyer, meaning the administrative burden is partly on the SaaS vendor to collect and retain exemption certificates. This is standard in many states, but Louisiana’s exemption certificate requirements are more detailed than average.
What to Do Next If You Have Not Checked Your Exposure
Start with your billing data. Pull revenue by customer state for the past 12 months. Flag every state where you are approaching the applicable economic nexus threshold, typically $100,000 in annual sales or 200 transactions for most states, and $500,000 for California, Texas, and New York. Those are the states to analyze first.
Cross-reference that list against the taxability table above. For states that show “Yes” or “Partial,” confirm whether your specific product type falls within the taxable category. If you sell to a mix of business and consumer customers, the analysis may differ by customer type in states like New York and Louisiana.
Once you know where you have exposure, registering through voluntary disclosure programs in states where you have historic liability will almost always result in penalty waivers. Most states offer these programs, and the terms are generally favorable compared to what happens during an audit.
For ongoing compliance, a dedicated SaaS tax engine is the correct infrastructure investment above roughly $1M ARR. Manual tracking across a dozen states becomes a material operational risk, and the cost of a tax engine is small relative to the exposure from non-compliance. The 12 best sales tax filing services for SaaS companies covers the leading tools with SaaS-specific capabilities, including how Anrok handles product taxability classification differently from Avalara’s general-purpose approach.
If you are evaluating whether a merchant of record removes this burden entirely, the comparison in the Stripe vs Paddle vs Lemon Squeezy vs Polar analysis covers exactly when the MoR model makes sense and what you give up to get it.
Frequently Asked Questions
Is SaaS taxable in all US states?
No. Roughly half of US states impose some form of sales tax on SaaS. States like California, Florida, and Virginia do not tax SaaS under their current rules. States like Texas, Pennsylvania, New York, Washington, and roughly 20 others do tax it, though the specific rules and rates vary. Five states have no statewide sales tax at all: Alaska, Delaware, Montana, New Hampshire, and Oregon.
What is economic nexus for a SaaS company?
Economic nexus is the obligation to collect and remit sales tax in a state based on sales volume or transaction count, without any physical presence. The threshold in most states is $100,000 in annual sales or 200 transactions into that state. California, Texas, and New York use a $500,000 sales threshold. Crossing the threshold triggers registration and filing obligations, even if your SaaS product turns out to be exempt in that state.
Does a B2B SaaS exemption exist in states that tax SaaS?
Some states offer business-to-business exemptions or sales-for-resale exemptions that can apply to SaaS. Louisiana and New York have exemptions for SaaS purchased for qualifying business input use. Texas does not offer a general B2B exemption for its data processing service category. In most states that broadly tax SaaS, selling to a business does not automatically exempt the sale. Buyers must provide a valid exemption certificate, and the product must qualify under the specific exemption category.
How does Texas tax SaaS differently from other states?
Per the Texas Comptroller’s published guidance, Texas classifies SaaS as a data processing service and taxes it at 80% of the sales price, with 20% treated as nontaxable. Most states that tax SaaS apply the full rate to the full sales price with no built-in discount for the service component.
Does where my SaaS servers are located affect state tax obligations?
No. States that tax SaaS do not base taxability on server location. What matters is where the customer is located and uses the software. A company with all servers in Virginia selling SaaS to customers in Texas still owes Texas tax on those sales if the economic nexus threshold is crossed. Physical presence of infrastructure does not determine tax jurisdiction for SaaS sales.
When should a SaaS company hire a sales tax specialist versus using software?
Tax software handles rate calculation, nexus monitoring, return filing, and SST registration well. It cannot replace professional advice on product taxability determinations, handling audit inquiries, or navigating voluntary disclosure negotiations. Companies with complex product architectures, SaaS bundled with professional services, or significant exposure in partial-taxability states like New York and Illinois should have a CPA or sales tax attorney review their product classification decisions. Software handles execution; professional judgment handles interpretation.
What happens if a SaaS company has not filed in states where it has economic nexus?
The company has potential back liability for uncollected tax, plus interest and penalties that vary by state. Most states offer voluntary disclosure programs that allow companies to come forward, pay back taxes for a limited lookback period (typically three years), and receive a waiver of penalties. The window to act voluntarily closes once a state initiates an audit. Discovery during an audit typically results in the full lookback period, full penalties, and no negotiated terms.
Does a merchant of record handle SaaS sales tax automatically?
Yes, when you sell through a true merchant of record like Paddle or FastSpring, the MoR takes on the legal obligation to collect and remit sales tax as the seller of record. Your company does not need to register in individual states for those sales. The tradeoff is that MoR fees are higher than standard payment processing, and the MoR controls parts of your billing and checkout experience. This model works well for pure SaaS products but creates complexity when product lines include non-SaaS components or when enterprise buyers require direct invoicing from your entity.
The Bigger Picture on SaaS Tax Exposure
The SaaS industry spent two decades operating under rules written for a different economic model. The Wayfair decision changed the legal framework, and states have spent the years since actively updating their guidance to capture remote digital services. The gap between “we assumed this was exempt” and “this is clearly taxable” has closed considerably, and it continues to close as more states pass explicit SaaS taxability legislation.
What makes SaaS tax exposure different from most compliance risks is that it compounds quietly. A company that crossed Texas’s $500,000 threshold three years ago and never registered now has three years of uncollected tax on Texas customers, interest on that amount, and potential penalties. The customers paid without tax because it was never charged. The company cannot go back and collect it. The liability belongs to the company.
The practical implication for founders: treat SaaS tax exposure as a quarterly finance review item, not a one-time legal question. Revenue grows, customer geography shifts, and state legislatures update their rules regularly. Running the four-step exposure scan described above each quarter costs less than an hour of finance team time. Finding the exposure on your own terms, before a state finds it first, is the only option that preserves negotiating room. Building this into your compliance readiness process early avoids the kind of back-tax discovery that shows up in due diligence and derails fundraising rounds.
