Introduction
You launched a SaaS. You picked up paying customers in 30 states inside a year. Then someone on Twitter said "Wayfair" and your stomach dropped.
Here is the founder reality on SaaS sales tax. That $0.99 seat plan now triggers a tax obligation in states you have never set foot in. Back taxes plus penalties can wipe a year of runway in one notice. The good news: this is solvable in a single quarter, and you do not need a CPA on payroll to do it.
This piece covers three things. First, the two flavors of nexus and how each one shows up for SaaS. Second, what changed after Wayfair and the post-Wayfair state thresholds, with at least five named state values. Third, a 90-day checklist you can run yourself to get registered, collecting, and filing where you owe.
Let's get into it.
Body
Economic vs Physical Nexus, With SaaS-Specific Examples
Two things create sales tax nexus. Physical nexus comes from a foothold in the state. Economic nexus comes from the size of your sales into the state.
Physical nexus is the older rule. It shows up when you have an office, an employee, a server, a contractor, or inventory in the state. One remote engineer living in Colorado creates Colorado physical nexus from day one. One 1099 contractor in California does the same in California. A leased desk in Austin does it in Texas.
Economic nexus is the newer rule. It triggers when your sales into a state cross a revenue or transaction count, even with zero people or property there. A self-serve SaaS that books $110K through New York or $120K through Washington crosses economic nexus in those states.
Here is the trap most founders miss. Cloud hosting on AWS does not create nexus by itself. Your code sitting in an AWS region is not your code in that state. But a single contractor there does, and so does a single full time hire who moved last quarter.
Map your team and your billing footprint before you map anything else. Both kinds of nexus stack.
Post-Wayfair: What Actually Changed
South Dakota v. Wayfair (2018) is the line in the sand. Before Wayfair, you needed physical presence to owe sales tax. After Wayfair, revenue or transaction count alone is enough.
Most states wrote their own thresholds within 18 months. Most copied the South Dakota template: $100K in sales or 200 transactions, whichever you hit first. Some states picked a higher floor. A few dropped the transaction count entirely.
For SaaS, the consequence is real. A Delaware C corp with one office can owe filings in 20+ states by year three, with zero hires outside the HQ.
There is a second question that trips up founders. The nexus question is "do I owe filings here?" The taxability question is "is SaaS even taxable here?" Those are not the same question, and the answers vary by state.
A few quick examples of how SaaS taxability splits across states. New York taxes SaaS. California does not. Texas taxes SaaS as a "data processing service," and only 80 percent of the price is taxable. Ohio taxes B2C SaaS but exempts most B2B SaaS. The pattern is messy on purpose, and you have to check each state on its own.
State-by-State Threshold Ranges (5+ Specific States)
Thresholds cluster around two numbers: $100K of revenue or 200 transactions. The exact rule and the SaaS taxability swing wide. Here are six named states to anchor the picture.
California. $500K of revenue, no transaction count. SaaS is not generally taxable, so the threshold matters only if you also sell taxable goods or services. Threshold is high; tax exposure is often low.
New York. $500K of revenue AND 100 transactions, both required. SaaS is taxable. If you sell to a lot of New York customers, you will cross both lines.
Texas. $500K of revenue, no transaction count. SaaS is taxable as a "data processing service" at 80 percent of price. Big state, real exposure.
Washington. $100K of revenue, no transaction count. SaaS is taxable. The low floor catches a lot of early stage SaaS.
Florida. $100K of revenue, no transaction count (effective 2021). SaaS is not generally taxable, so the threshold mostly affects sellers of taxable goods. Filing duties can still apply.
Illinois. $100K of revenue OR 200 transactions. SaaS is not generally taxable in most cases, though digital products are.
A few patterns to take away. Thresholds cluster at $100K or $500K. A 200 transaction tripwire shows up in many states. Crossing a threshold does not always mean you owe tax, but it can still trigger a filing duty.
State tax thresholds also change. Kansas removed its $100K floor in 2021. Louisiana dropped the 200 transaction trigger in 2023. Always verify the current state rule before you register or file. Bookmark each state's Department of Revenue page.
The 90-Day Founder Action Checklist
You can run the full play in one quarter. Here is the week by week.
Days 1-14: Pull the data. Export 12 months of invoices from Stripe, Chargebee, or whatever bills your customers. Group by ship-to state, or by billing state if you do not capture ship-to. Build a simple table: state, revenue, transaction count. This is your raw exposure map.
Days 15-30: Map nexus exposure. For each state with more than $50K of revenue or more than 150 transactions, look up the current threshold. Flag every state where you are at 80 percent or higher of either threshold. Flag every state you have already crossed.
Days 31-45: Determine taxability. For each flagged state, look up whether SaaS is taxable there. TaxJar's state guides and Avalara's free SaaS taxability matrix are the two fastest references. Do not buy software yet. The goal here is a yes/no per state.
Days 46-60: Register where required. Use each state's Department of Revenue portal. Register only where you have crossed the threshold AND SaaS is taxable. Registration is free in most states and takes under an hour per state.
Days 61-75: Set up collection. Configure your billing tool to charge sales tax in the states you registered. Stripe Tax, Paddle, and Chargebee all handle this. Stripe Tax is the cheapest path under roughly $5M of ARR.
Days 76-90: File and decide on automation. File your first returns. Decide whether to keep filing by hand (works fine under 10 states) or buy a tool. TaxJar, Avalara, and Anrok are the common picks once filings cross 10 jurisdictions.
One last note for SaaS tax compliance. If you are already 18 months past threshold in a state with no registration, look up voluntary disclosure agreements (VDAs) before you walk in the front door. A VDA caps back taxes to a fixed look back, usually three or four years, and waives penalties. Going in cold can mean ten years of back taxes.
Key Takeaways
- Two flavors of nexus: physical (office, contractor, hire, server, inventory) and economic (revenue or transactions per state).
- Wayfair changed the game in 2018: revenue or transaction count alone is now enough; physical presence is no longer required.
- Thresholds cluster at $100K or $500K of revenue, with a 200 transaction tripwire common across many states.
- Threshold trip does not always mean tax owed: SaaS taxability varies by state (NY taxes it, CA does not, TX taxes 80 percent of it as data processing).
- A 90-day plan covers the full path from "I have no idea" to "I am registered, collecting, and filing where I owe."
- Use a VDA if you are already over threshold and unregistered: it caps back taxes and waives penalties.
Conclusion
The back tax bill that wipes runway is avoidable. The states are not going to forget about you. They are already cross referencing Stripe data and 1099-K filings to spot unregistered SaaS sellers, and the notice cycle has gotten faster every year since 2020.
The cost of getting ahead of it is one focused quarter and a spreadsheet. The cost of waiting is six figures of back tax exposure plus penalties plus interest, and the awkward call to your investors about why net burn just spiked.
Pull the data this week. Map your exposure next week. You can be registered, collecting, and filing by the end of the quarter, with no surprise letters in your mailbox.
Growthy is in open alpha — AI bookkeeping built for SaaS founders. Get Early Access.