12 States That Tax SaaS Revenue — and What the Economic Nexus Threshold Means Once You're Liable to Collect

The Two-Question Framework: Taxability First, Then Nexus

Before registering anywhere, a SaaS company needs to answer two questions in sequence for each state where it has customers:

1. Is SaaS taxable in this state? If the state does not tax SaaS, you have no sales tax collection obligation for your software product regardless of your revenue. Stop here.
2. Have I crossed the economic nexus threshold? If SaaS is taxable in the state, you still need to exceed the state's revenue or transaction threshold before you are required to register, collect, and remit.

Getting this order wrong is costly in both directions. Registering in a state where SaaS is exempt means you are collecting tax you do not owe (and filing returns you do not need to file). Ignoring a state where SaaS is taxable because you assumed the threshold had not been met means you are accumulating retroactive exposure that a VDA will eventually need to address.

The 12 States That Tax SaaS Revenue

The following 12 states have issued formal guidance, rulings, or legislation classifying SaaS as subject to sales tax. The legal basis varies — some treat SaaS as pre-written (canned) software, others as a digital good, and a few tax it as a specifically enumerated service.

Two patterns stand out. First, Texas and New York have significantly higher thresholds ($500,000) than the other 10 states ($100,000). A SaaS company with $200,000 in Texas revenue and $150,000 in Pennsylvania revenue has a collection obligation in Pennsylvania but not Texas. Second, the combined state and local rates vary from 6.25% (Massachusetts) to 10.25% (Washington) — meaning the financial impact of non-compliance differs substantially by state.

8 States With No SaaS Tax but Active Economic Nexus Thresholds

These states do not tax SaaS but still have economic nexus thresholds. If you sell other taxable items — implementation services, training, hardware, downloadable software, or physical goods — you may still have a collection obligation.

For a pure SaaS company — no hardware, no downloads, no on-site implementation — these states generally require no sales tax collection. But the moment you bundle a taxable component (a hardware device, a downloadable desktop app, on-site training billed separately), the calculus changes. The SaaS economic nexus rules in Florida, Georgia, and Pennsylvania are worth reviewing even if your core product is exempt, because adjacent services often are not.

SaaS vs. Custom Software: How States Draw the Line

The distinction between "SaaS" and "custom software" is not academic — it determines taxability in most of the 12 states listed above. Several states tax SaaS (as pre-written or canned software) but exempt custom software developed for a single customer. The classification turns on three factors:

The gray area: a SaaS product with significant professional services for custom development. If a company charges $50,000/year for a SaaS subscription and $80,000 for custom module development specific to one client, the subscription portion is likely taxable as SaaS while the custom development portion may be exempt — but only if the charges are separately stated on the invoice. Bundling them into a single line item risks the entire amount being treated as taxable in most states.

Texas provides the clearest example of this split. The Comptroller treats "data processing services" (which includes SaaS) as taxable at the state rate, but custom programming services are exempt. The key: the exemption requires that the software be "created solely for a single customer" and not offered to any other buyer. A SaaS vendor that builds a custom integration for one client can exempt the integration fee but must collect tax on the monthly subscription.

Threshold Details for the 12 Taxable-SaaS States

The lookback periods and threshold mechanics vary state by state. Here is what SaaS companies need to know about each:

• Texas ($500,000): Uses a rolling prior 12-month lookback. Only the revenue prong applies — no transaction count. The higher threshold means smaller SaaS companies are not captured, but the 8.19% combined rate makes Texas one of the most expensive states for non-compliance once you are over the line.
• New York ($500,000 and 100 transactions): Requires both prongs to be met simultaneously. A SaaS company with $600,000 in NY revenue but only 50 customers does not have nexus. This dual-prong test is unusual and benefits companies selling high-value contracts to a small number of enterprise clients.
• Pennsylvania ($100,000): Revenue-only threshold. No transaction count prong. SaaS is taxable as canned computer software — the state issued guidance explicitly confirming that cloud-based software accessed via browser qualifies. The 6% state rate (plus up to 2% in Philadelphia) applies.
• Washington ($100,000): Revenue-only threshold with a prior or current calendar year lookback. SaaS is taxable as a "digital automated service" under Washington's B&O (Business & Occupation) and retail sales tax framework. The combined rate often exceeds 10%, making Washington the highest-rate state for SaaS sellers.
• Ohio ($100,000 or 200 transactions): Either prong triggers nexus. SaaS is taxable as "automatic data processing and computer services." Ohio applies a reduced rate to certain computer services, so verify the specific rate for your product category.
• Connecticut ($100,000 and 200 transactions): Both prongs required — similar to New York. The 6.35% rate applies to SaaS as "canned or pre-written software."
• Remaining 6 states: South Carolina, Tennessee, Utah, Massachusetts, West Virginia, and Louisiana all use $100,000 or 200-transaction thresholds (either prong triggers nexus). Lookback periods are generally calendar year or rolling 12 months. Check individual state guidance for rate specifics, as local surcharges vary significantly in Tennessee and Louisiana.

Worked Example: $750K ARR SaaS Startup Mapping Its Registration Obligations

Consider a B2B SaaS company based in Ontario, Canada with $750,000 USD in annual recurring revenue. The company sells a project management platform accessed entirely via browser — no downloads, no hardware, no on-site implementation. Its revenue is concentrated in five U.S. states:

The result: out of 5 states and $750,000 in revenue, this company has a current collection obligation in exactly one state (Pennsylvania) and a near-term obligation in one more (Washington). California — its largest market — is irrelevant for SaaS sales tax. New York and Texas will not trigger for at least another year at current growth rates. The company's immediate compliance cost is one state registration and one set of periodic filings, not five.

Cross-Border Considerations for Canadian SaaS Companies

Canadian SaaS founders selling into U.S. states face the same economic nexus thresholds as domestic sellers. The state does not care where the company is incorporated — nexus is triggered by the volume of sales into the state. But several practical considerations apply:

• Currency conversion: U.S. economic nexus thresholds are in USD. If you invoice in Canadian dollars, convert each transaction at the exchange rate on the transaction date (or use the average rate for the period if the state permits). The monthly subscription payment counting rules apply to each converted amount.
• Registration as a foreign entity: You will register as a "foreign" business (meaning out-of-state, not international). Most states use the same registration form regardless of whether you are foreign to the state from another U.S. state or from another country. You may need a U.S. mailing address for correspondence.
• GST/HST is entirely separate: Your Canadian GST/HST obligations do not interact with U.S. state sales tax. You may owe GST/HST on services performed in Canada and U.S. sales tax on sales into taxable states simultaneously. The two systems are independent — there is no credit or offset.
• Tax treaties do not apply: The Canada-U.S. tax treaty covers income tax, not sales tax. There is no treaty-based exemption from state sales tax collection obligations.
• Nexus for income tax: Having economic nexus for sales tax purposes may also create income tax nexus, potentially subjecting the Canadian company to state corporate income tax on U.S.-sourced revenue. This is a separate analysis that requires tax advisor input.

What to Do Once You Determine You Have a Collection Obligation

If you have crossed the economic nexus threshold in a state that taxes SaaS, the compliance path is straightforward:

1. Register for a sales tax permit in the state. Do not begin collecting tax before registration — collecting without a permit is illegal in most states.
2. Update your billing system to charge the correct state and local sales tax rate on invoices to customers in that state. For SaaS, the rate is typically based on the customer's location, not yours.
3. Begin filing returns on the schedule assigned by the state (monthly, quarterly, or annually, usually based on your sales volume). File even in periods with zero tax collected.
4. Address any retroactive exposure. If you crossed the threshold months or years ago, you may owe back-tax for the period between when you should have started collecting and when you actually did. A voluntary disclosure agreement can limit that exposure.
5. Monitor other states. If you are growing, states where you are currently below the threshold will eventually be triggered. Set internal revenue alerts at 75% of each state's threshold to give yourself lead time for registration.