Reviewed by Walid Qabaha, CPA, Tax Automation Specialist, July 2026

You just crossed a revenue threshold in a state you didn't plan for. Here's what that means

Economic nexus is a sales tax obligation triggered when your revenue or transaction volume in a state crosses a statutory threshold, even if you have no office, employee, or inventory there. Most controllers discover it the same way. A quarterly revenue report shows the company booked $112,000 in a state where it has never set foot, and that number alone now obligates the company to register, collect, and remit sales tax.

The trigger is quiet, which is what makes it dangerous. No state agency sends a warning when you cross $100,000 in gross sales or 200 separate transactions. The obligation attaches the moment you cross the line, and the clock on penalties and interest starts running from that date.

For a SaaS or e-commerce company scaling across the country, this scenario repeats in state after state. You expand into new markets through self-serve signups and online orders, and each new market carries its own threshold, its own measurement period, and its own rules about whether your product is even taxable. A finance team focused on ARR and burn rarely watches state-level sales totals against dozens of separate thresholds.

By the time a notice arrives or a diligence team flags it during an acquisition, the exposure has often compounded across several states and multiple filing periods. The sections below explain how economic nexus works, how to measure your exposure against each state's rules, and what to do once you find it.

Economic nexus is a sales tax obligation based on revenue or transaction volume, not physical presence

Economic nexus is a sales tax collection obligation a state imposes on a seller based on how much revenue or how many transactions that seller generates in the state, whether or not the seller has any physical location there. Cross the state's statutory dollar or transaction threshold, and you owe a duty to register, collect, and remit sales tax on your sales into that state. The seller's office locations, employee addresses, and warehouse footprint no longer control the answer.

That mechanism breaks the mental model most finance leaders carry. Physical nexus, the older standard, ties a tax obligation to a tangible presence in the state. An office in Austin created nexus in Texas. A remote employee in Denver created nexus in Colorado. Inventory sitting in a fulfillment center created nexus wherever the center stood. Under that rule, a company with no property or people in a state owed it nothing.

Economic nexus ignores presence entirely and looks only at sales into the state. A software company headquartered in Delaware, with no staff or servers anywhere near Ohio, still triggers an Ohio collection duty once its Ohio sales pass the statutory figure. The state measures your economic activity, not your physical activity, and the trigger fires automatically the moment you cross the line.

Most states now treat economic nexus as the primary test for remote sellers, and that shift matters most for SaaS providers. A company selling subscription software delivers nothing physical, ships nothing, and often has no reason to set foot in a customer's state. Under the old physical-presence rule, that company escaped sales tax in almost every market it served. Under economic nexus, the same company can owe collection duties in a dozen states purely on the strength of its subscription revenue.

South Dakota v. Wayfair created the legal basis for taxing remote sellers without physical presence

The Supreme Court's 2018 decision in South Dakota v. Wayfair gave states the constitutional authority to require sales tax collection from sellers with no physical presence inside their borders. Before that ruling, a 1992 case called Quill Corp. v. North Dakota set the rule. A state could only compel a business to collect sales tax if that business had a physical footprint there, meaning an office, an employee, inventory, or property. Remote sellers shipped into a state and owed nothing.

Wayfair overturned that physical-presence standard directly. South Dakota had passed a law taxing out-of-state sellers who exceeded $100,000 in sales or 200 separate transactions in the state, and the Court held that this kind of economic activity created enough connection to justify a collection duty. The revenue-or-transaction threshold South Dakota wrote became the template. States across the country copied the same $100,000 and 200-transaction structure almost verbatim in the months that followed.

That copying happened at wildly different speeds, which explains why your exposure looks so uneven today. Some states adopted economic nexus rules within weeks of the ruling in 2018. Others waited until 2019 or later, and a handful adjusted their numbers after the fact. States also diverged on the details the Court left open, so one state counts every transaction while its neighbor dropped the transaction count entirely and looks only at revenue.

The result is a patchwork you now have to track state by state. The Court gave states a green light but not a uniform rulebook, so each legislature set its own dollar figure, its own transaction count, and its own measurement window. A threshold you crossed in one state may sit far below the line in another, even when your sales look identical on paper.

Every state sets its own revenue and transaction thresholds, and most SaaS and e-commerce sellers hit several within a year of scaling

No two states define economic nexus the same way, so a growing seller can register correctly in nine states and remain silently exposed in a tenth. The variation itself is the risk. You clear a threshold in one state and assume you understand the rule everywhere, but the next state you scale into measures something different.

Most states settled on a $100,000 revenue threshold, and many stop there. A shrinking group still keeps a 200-transaction count that triggers nexus even when revenue stays low, which catches high-volume, low-price sellers first. States also disagree on what "revenue" means. Some measure gross sales, including exempt and wholesale transactions, while others count only taxable retail sales. A seller under the taxable-sales line in one state can sit well over the gross-sales line in another with the identical revenue.

SaaS makes the calculation harder because states do not agree on whether software delivered over the internet is taxable at all. Texas taxes SaaS as a data processing service, New York treats it as prepackaged software, and California generally does not tax it. So a SaaS company faces two open questions in every new state at once. Have you crossed the nexus threshold, and is your product even taxable once you have. The revenue that creates a filing obligation in one state may create no collection duty in another where the same product is exempt. The table below lays out the current figures state by state.

Economic nexus thresholds by state for SaaS and e-commerce sellers

Each state sets its own economic nexus threshold, and the figures below reflect the most common states where SaaS and e-commerce sellers scale into an obligation. Verify every number against the linked state source before you rely on it, because states revise these rules more often than most finance teams expect.

These figures reflect a snapshot and change with regularity. Several states, including California, Washington, Illinois, and North Carolina, have already repealed the 200-transaction count that many first adopted after 2018, which means a seller with high order volume and low revenue may no longer trigger nexus in states where it once did. Confirm the current threshold, measurement period, and transaction count directly with each state's revenue department before you register or decide you are exempt, because relying on an outdated figure creates the same exposure as ignoring the rule entirely.

Identify which states you've triggered by reviewing trailing revenue and transaction counts against each state's measurement period

Pull state-level revenue and order counts from your billing or ERP system, then compare each state's totals against that state's specific measurement window. You can diagnose your exposure today from data you already own, well before any state mails a notice. Export a report that breaks gross sales and transaction counts down by ship-to or bill-to state, covering at least the trailing 24 months so you can test both common lookback formats.

State lookback windows fall into two camps, and the difference decides whether you have triggered. Some states measure the previous or current calendar year, so your counter resets each January. Others measure a rolling trailing 12 months, which means you can cross a threshold mid-year on a metric that looked safe last quarter. Run each state's numbers against its own window rather than applying one rule everywhere, because a company sitting at $95,000 in a calendar-year state may already be over the line in a trailing-12-month state with the same sales.

SaaS companies routinely miscount because their raw sales report hides three categories that states treat differently. Marketplace-facilitated sales are the first blind spot. When a marketplace collects tax on your behalf, some states still count those gross sales toward your threshold even though you owe nothing on them, which can push you over faster than your direct revenue suggests. Check whether each state excludes marketplace sales from the nexus calculation before you subtract them.

Bundled services and free trials create the second and third gaps. If you sell software packaged with implementation or support, states that tax the bundle differently than its parts can change both your revenue figure and your taxability question. Free trials matter because a handful of states count every separate transaction toward a 200-transaction threshold regardless of dollar value, so a high-volume freemium product can trip a transaction count while its revenue stays modest.

Build a simple tracker with one row per state, its threshold, its measurement window, and your current trailing figures. Refresh it every quarter so you catch a crossing in the month it happens, not the year after.

Uncollected sales tax in a triggered state becomes a company liability, with penalties and interest accruing from the original trigger date

The tax you failed to collect becomes money you owe out of your own revenue, because the state holds the seller responsible for remitting sales tax whether or not the customer ever paid it. Once you cross a threshold and keep selling without registering, every taxable transaction after that date builds a liability the state can assess later. You cannot go back and bill customers from two years ago for tax you should have charged, so the shortfall comes directly off your margin.

Penalties and interest push the number well past the raw tax owed. States assess interest from each original due date, so a liability that began eighteen months ago has been accruing that entire time. Failure-to-file and failure-to-pay penalties stack on top, and the combined addition varies by state. Several states also allow personal liability assessments against responsible officers, which means a CFO or Controller can be pursued individually when the company cannot pay.

The retroactive math is what turns a minor oversight into a material exposure. A company that crossed a threshold in January and registers the following December owes tax on every intervening sale, plus interest on each, rather than a clean going-forward obligation. Delay compounds the problem, because the lookback period grows with every month you wait.

Two events surface unaddressed economic nexus more often than a routine state audit, and both raise the stakes for finance leadership. Acquirers run sales tax exposure as a standard line in due diligence, and an uncollected multi-state liability shows up as a purchase-price adjustment, an escrow holdback, or a reason to walk. State audits are the other trigger, and auditors who find one uncollected jurisdiction routinely request records for every state where you sell. Either event converts a quiet balance-sheet gap into a negotiated dollar figure, which is why confirming exposure before someone else does belongs on the finance team's agenda rather than the accounting department's backlog.

Once you've confirmed exposure, you have three paths: register and collect going forward, file back returns, or negotiate a voluntary disclosure agreement

Once you've confirmed exposure, you choose among three remediation paths, and the right one depends on how far back your liability reaches and how many states you triggered. Straight registration works when you crossed a threshold recently and owe little or nothing in back tax. You register with the state, start collecting, and file going forward. The uncollected liability behind you stays small enough that penalties and interest don't justify a more involved process.

Filing back returns makes sense when you've accrued liability but the exposure sits in one or two states and the numbers are manageable. You register, then file returns covering the periods since your trigger date, paying the tax you should have collected plus whatever penalties and interest the state assesses. States rarely waive those additions when you come forward through standard registration, so the full retroactive cost lands on the company.

A voluntary disclosure agreement changes the math when your exposure is large or spread across several states. A VDA is a negotiated deal with a state's revenue department where you disclose your unregistered activity in exchange for two concessions. The state caps your lookback period, usually at three or four years even if you triggered nexus earlier, and it abates penalties, sometimes reducing interest as well. You typically enter the negotiation anonymously through a tax advisor, so the state doesn't know your identity until terms are set. That structure protects you from committing to a liability figure before you understand what the state will accept.

The choice between these paths moves your total liability by real dollars, not rounding. A company with five years of uncollected tax in eight states pays far less through eight VDAs than through eight back-filings with full penalties and uncapped lookback. A company with three months of exposure in one state wastes time and advisory fees pursuing a VDA it doesn't need. The size of the gap decides the path.

Before you file or register anything, bring in a tax advisor who handles multi-state remediation. Registering in a state signals that you have nexus, and once you register, the option to negotiate a VDA for the prior period usually closes. Filing first and asking questions later can lock you into the most expensive path by accident. A short conversation about your trigger dates and state-by-state exposure tells you which route protects the most cash.

Taxwire monitors thresholds and automates registration and filing so finance teams don't discover nexus after the fact

Taxwire tracks your revenue and transaction counts against every state's threshold in real time, so you learn you're approaching nexus before you cross it. Manual checks happen quarterly at best, and thresholds move in states you weren't watching. Taxwire connects to your billing and ERP systems and runs the comparison continuously. Each state's status updates as your trailing figures move, so the alert arrives before the obligation attaches rather than after a quarterly report surfaces it.

Once you cross a threshold, Taxwire handles the registration and filing work that otherwise turns into a multi-state administrative burden. US state registrations run $150 per state, and returns are $100 per return. Taxwire's in-house tax team reviews every return before it goes out, which means the finance team is not left to reconcile rate discrepancies or respond to state notices on their own. For a company scaling into ten or fifteen states at once, full compliance setup takes one week.

Taxwire closes the detection gap by monitoring thresholds continuously rather than quarterly, and it closes the filing gap by handling registration, returns, and back-filing across every state where you owe. Both gaps are what allow a triggered threshold to sit unaddressed for months.

If you're evaluating options, start with the Taxwire platform overview to see how monitoring and filing work together. Finance leaders comparing tools should read our breakdown of the best sales tax automation software and our guide to sales tax compliance for SaaS companies before committing to any single approach.

Frequently asked questions about economic nexus

Does economic nexus apply to SaaS?

Economic nexus applies to SaaS in every state that both taxes software-as-a-service and has enacted a remote-seller threshold. The complication is taxability, not nexus itself. States like New York, Texas, and Washington tax SaaS revenue, while states like California generally do not, so a SaaS company can trigger nexus in a state where its product turns out to be exempt. You still track the threshold in both cases, because the state expects a registration even when your specific service is not taxable.

What counts toward the transaction threshold?

Most states count the total number of separate retail sales into the state during the measurement period, regardless of dollar value. A $10 order and a $10,000 order each count as one transaction toward a 200-transaction limit. Several states have repealed their transaction counts entirely and now measure only revenue, so a low-price, high-volume seller should confirm whether the count still applies before assuming exposure.

Does economic nexus expire if my sales drop below the threshold?

Nexus does not end automatically the moment your sales fall below a state's threshold. Most states require you to keep collecting for a defined period, often the remainder of the current year plus the following year, and you must formally close your registration through the state's revenue department. Stopping collection or filing without deregistering leaves you exposed to penalties for missed returns.

How does marketplace facilitator law affect my nexus?

Marketplace facilitator laws shift the collection duty for sales made through platforms like Amazon or Shopify Marketplace to the platform itself, so the facilitator remits tax on those transactions. Those sales may still count toward your economic nexus threshold in some states, which means marketplace revenue can create a registration obligation for your direct sales even when you never collected on the marketplace orders. Check each state's rule, because states differ on whether facilitated sales are included in the threshold calculation.