Sales Tax Nexus vs Payroll Tax Nexus for Scaling Companies

Sales tax nexus and payroll tax nexus share a word and nothing else. One is a revenue department's claim on transactions; the other is a labor commissioner's claim on where work physically happens. A company can trip either wire without coming near the other, and the companies that get burned are almost always the ones that treat clearing one threshold as proof the other is handled too. That assumption is wrong, and it's the single most expensive assumption in this piece.

Sales tax nexus thresholds in 2026

South Dakota v. Wayfair, decided in 2018, tore out the old rule that a state needed a warehouse or an office inside its borders before it could tax a company's sales there. Economic activity became enough on its own. Every state with a sales tax has now implemented economic nexus rules flowing from that single ruling. The question that actually matters for a scaling company is which states have already claimed nexus over you, and at what dollar figure, not whether nexus rules exist anymore. It's which states have already claimed nexus over you, and at what dollar figure.

Most states settled on $100,000 in sales as the line. Twenty-five states run a flat dollar threshold with no transaction count attached, so a handful of large invoices trips nexus just as fast as thousands of small ones now. Most founders picture nexus as something high-volume consumer sellers deal with, when a B2B company invoicing a handful of clients at a substantial price apiece hits the same wall. A few states set the bar much higher, and those are the ones that catch growing companies off guard because founders assume they have runway. California requires $500,000 in gross sales of tangible personal property. Texas sets the same $500,000 mark on gross revenue. New York wants both $500,000 and 100 separate transactions across the prior four sales tax quarters. Alabama and Mississippi are at $250,000.

The direction of travel is toward simplicity, and simplicity here means a lower practical bar, not a friendlier one. Alaska repealed its 200-transaction test effective January 1, 2025, leaving $100,000 in gross sales as the sole trigger. Utah did the same as of July 1, 2025. Illinois followed on January 1, 2026, dropping its transaction count so that any remote seller clearing $100,000 in gross receipts over a rolling 12-month window has nexus, full stop. Dropping the transaction test sounds like a technical cleanup, but it tightens the net around exactly the wrong companies for that outcome: high average order value, small customer list, the classic B2B software profile that used to slide under a 200-transaction floor while sitting on real revenue.

Software deserves its own paragraph, because the rules there are still being drafted in real time, not settled. Louisiana started taxing SaaS and information services on January 1, 2025, catching software companies that never thought of themselves as having a Louisiana footprint. Multiple states have passed new SaaS tax laws in recent years. California carves out an exemption for SaaS delivered remotely, but bundle that software with a taxable service or a piece of hardware and the exemption partly evaporates, a distinction that matters enormously for companies packaging platform and services together. Several additional states are evaluating software taxation, so a state silent on software today may not stay that way through next year's legislative session.

None of this sits still once a threshold is crossed, either. More than 500 local rate changes occurred across more than 13,000 taxing jurisdictions in 2024 alone, so a rate configured correctly at registration can be stale within two quarters. Measurement periods compound the difficulty: some states look at the current calendar year, some use a trailing 12 months, some isolate a single quarter. A company sitting near a threshold in three different states needs three different clocks running, not one spreadsheet with a single total. Marketplace sales add a final wrinkle. In some states, including California, sales made through a platform still count toward a seller's own threshold even when the marketplace collects and remits the tax itself, so a founder who assumes Amazon "handled it" may already be closer to nexus than the direct-sales numbers suggest.

Payroll tax nexus triggers and the zero-dollar threshold

Sales tax nexus takes time to build. Payroll tax nexus doesn't, and that asymmetry is the detail most companies misjudge. One employee performing work inside a state creates full employer obligations there immediately. No revenue floor, no grace period, no wait-and-see. The payroll clock starts on day one of a hire, while the sales clock might not ring for a year or more, and treating the two as running on the same schedule is where the exposure comes from.

"Full obligations" isn't a figure of speech. A single new-state hire can require state income tax withholding registration, an unemployment insurance account, workers' compensation coverage, local tax withholding in cities that impose their own layer, paid leave compliance, and foreign qualification with the Secretary of State. Depending on the state, it can also trigger corporate income or franchise tax filing obligations that have nothing to do with where the company sells anything.

California is the case study everyone in this space eventually learns cold. Mosey's California nexus guide states that employment tax nexus attaches the moment a single employee works in the state, and registration has to happen before that person's first paycheck goes out. Separately, income and franchise tax nexus kicks in once California payroll exceeds $75,707 for 2025 or 25% of total company payroll, whichever number is smaller. One hire, or one employee relocation, can trigger EDD registration, workers' comp, foreign qualification, and an income tax filing obligation at the same time, four compliance streams stacked on top of a decision that probably got made in a team messaging thread.

New York adds a wrinkle known as the convenience rule: if a remote employee works outside New York for their own convenience rather than because the job requires it, New York still taxes the wages as though the work happened inside the state. Todd Unger Esq.'s analysis notes that a company's New York withholding obligation can follow an employee who relocates to Connecticut, long after anyone in HR stopped thinking about New York.

Contractors don't offer an exit ramp. States look past the label and examine what the person actually does, so a full-time contractor working a fixed schedule, on company equipment, taking daily direction, creates the same nexus exposure a standard hire would. And the protection companies reach for reflexively, a federal statute called 86-272 limiting state income tax on out-of-state sellers, is far narrower than most people assume. It shields only companies selling tangible goods whose in-state activity is limited to soliciting orders. SaaS companies, consulting firms, and subscription businesses generally get no cover from it. A single remote engineer can obligate a company to file corporate income tax returns in a state it never opened an office in and never crossed a sales threshold in, and that exposure stays invisible until an audit or a due diligence process goes looking for it.

Why fast-scaling companies hit both exposure windows simultaneously and earlier than expected

Growth events don't respect the boundary between these two systems. A fundraise, a product launch, or a new work-from-anywhere policy tends to push revenue and headcount into new states at once, because both are downstream of the same decision to scale. Companies rarely cross a sales threshold in isolation from hiring into new territory. The two happen together, driven by the same underlying momentum. Treating them as separate compliance projects fails.

AI-driven products have compressed the timeline further. A company can go from zero revenue to a meaningful run rate in months instead of years now. Founders clear their first $100,000 in sales, the most common nexus threshold in the country, faster than any prior generation of startups managed it, often before anyone has built so much as a spreadsheet to track which states matter.

Remote hiring is the faster trigger of the two, by a wide margin, because it has no floor to clear. Sales nexus accumulates gradually against a dollar target. Payroll nexus arrives the day an offer letter gets signed and the new hire logs on from a state the company has never operated in before. A five-person distributed engineering team spread across five states means five sets of payroll obligations already exist, in full, regardless of what the sales numbers look like in any of those states.

The discovery moment tends to arrive at the worst possible time: M&A due diligence. Acquirers run state-by-state nexus reviews and payroll registration audits as a matter of course, and deals have stalled when a target company's remote workforce turned out to be missing basic state registrations that should have existed for years. Nobody budgets for a compliance gap surfacing mid-negotiation.

California illustrates the mismatch cleanly, again. The same state that sets a $500,000 sales threshold, giving a company real lead time, applies a zero-dollar payroll threshold that fires the instant the first California-based employee starts work. A company can be genuinely years away from California sales nexus while already carrying full payroll registration obligations there. Enforcement isn't getting gentler about any of this, and payroll nexus gaps that once went unnoticed can surface during audits or due diligence reviews.

Operational requirements for each compliance clock: registration, monitoring, and filing for both systems

Crossing a sales tax threshold sets off a specific sequence. Register for a sales tax permit in the state, generally before the next taxable transaction after the threshold is crossed, then work out which products or services are even taxable there, since taxability rules for digital goods and SaaS vary sharply state to state. Rate configuration has to be accurate at the moment of registration and then kept current, given the pace of local rate changes across more than 13,000 jurisdictions. Returns get filed on whatever schedule the state assigns, monthly, quarterly, or annual depending on volume. Monitoring has to continue in every state the company hasn't crossed a threshold in yet, because that's not a one-time check. It's ongoing, permanently.

The payroll side runs its own sequence, and it starts earlier. Registering with the state tax authority for income tax withholding needs to happen promptly, before payroll obligations begin. An unemployment insurance account needs opening. Workers' compensation coverage has to meet that state's specific requirements. Local tax rules need checking, since some cities layer their own withholding on top of the state's. Additional state business registration requirements may apply depending on the jurisdiction. Separately, the income and franchise tax factor thresholds need checking too: in California, crossing $75,707 in payroll is a distinct trigger from the employment tax registration that happened the day the first employee started.

Both chains become manageable with the same tool: a state-by-state matrix tracking employee locations, revenue against thresholds, measurement periods, and filing deadlines in one place. Visibility into where the company already stands is the prerequisite for everything else, not an afterthought bolted on once problems appear. Measurement period differences make this matrix a living document rather than a snapshot: a company sitting near a threshold in late Q3 in a trailing-12-month state could cross it in a month nobody flagged on the calendar, simply because that state doesn't measure on the calendar year everyone defaults to thinking in.

The two systems need reviewing together, at specific moments: when new hires land in new states, at revenue milestone check-ins, at a fundraise closing, during a shift in remote-work policy, during any M&A process. Each of those is a trigger for a joint review across sales and payroll at once, because the events that create one kind of exposure tend to create the other at the same time. Documentation discipline matters as much as the underlying compliance itself. Registration confirmations, filing receipts, and payroll account numbers across every jurisdiction need to be kept in a form a company can produce fast, because the paper trail gets scrutinized in an audit or a diligence process. Whether the taxes got paid is only half the question.

The cost of letting either compliance clock run unmonitored

The dollar figures involved aren't small. Riseworks' Global Payroll Compliance Report for 2026 puts non-compliance costs at over $7 billion annually in IRS penalties alone, with penalty rates running from 2% to 15% of unpaid taxes. That range should reframe how a scaling company thinks about deferring registration, since a missed deposit is a percentage of the total tax bill, not a flat fee, compounding with interest on top of it.

The payroll-specific penalty list is long enough to be its own deterrent. IRS deposit failures run 2% to 15% of unpaid taxes plus interest. FLSA recordkeeping violations can run up to $1,100 per employee. Failing to adjust withholding for the 2026 Social Security wage base of $184,500 can trigger significant penalties, which is precisely the kind of gap that gets found during audits. Research found small businesses paid $30,000 for every compliance mistake made in 2024, a cost few budget for. These aren't hypothetical costs sitting in a regulation nobody enforces.

Scale changes the arithmetic, and not in the company's favor. EY has estimated that correcting payroll errors at a company with 1,000 employees could run as high as $922,131 annually, a figure that reflects how errors compound across multiple states and multiple filings rather than any single mistake in isolation. That's the real argument for building the monitoring systems described above before growth forces the issue. The cost of ignoring either clock doesn't stay flat as headcount and revenue climb: it scales right alongside the company, and it becomes visible on an audit notice or a due diligence checklist, by which point it's already the expensive kind of problem to fix.