Does hiring a remote employee in a new state create sales tax nexus?

Does hiring a remote employee in a new state create sales tax nexus?

The default rule is yes. A W-2 employee who works from a home office or any fixed location in a state creates physical nexus for sales tax in that state on the first day of employment. The trigger is presence, not sales volume. A brand with zero taxable sales into a state can still carry a registration obligation on the day its first W-2 is processed there.

State “engaged in business” provisions are the statutory foundation. California defines “engaged in business in this state” under Cal. Rev. & Tax. Code §6203 to include retailers who have any representative operating in the state for purposes related to selling, delivering, installing, or taking orders. Texas covers the same concept under Tex. Tax Code §151.107, which extends to any person who maintains a place of business, employs a representative, or otherwise conducts sales-related activity in the state. New York’s definition under NY Tax Law §1101(b)(8) reaches sellers who have employees, agents, or independent contractors in the state soliciting business or maintaining a market.

These provisions predate South Dakota v. Wayfair, Inc., 138 S. Ct. 2080 (2018) by decades. Economic nexus, the sales-threshold approach the Wayfair ruling authorized, supplements physical nexus but does not replace it. Both triggers operate independently. A brand with zero taxable sales into California but a single W-2 working from any California city has physical nexus under Cal. Rev. & Tax. Code §6203, regardless of whether it has ever crossed California’s $500,000 economic nexus threshold.

Illinois and Massachusetts apply the same framework. Illinois use tax obligations attach to retailers “engaged in the business of selling” tangible personal property to Illinois purchasers under 35 ILCS 120, and the Illinois Department of Revenue applies that standard to in-state employees independent of the remote-seller economic nexus threshold. Massachusetts frames the obligation under Mass. Gen. Laws ch. 64H, § 1, which covers retailers maintaining a place of business in Massachusetts through employees or representatives, consistent with the state’s pre-Wayfair physical nexus standards.

The misread that creates exposure: economic nexus thresholds ($100,000 in most states, $500,000 in California and Texas, and $500,000 with 100 transactions in New York) are volume measures applied to sales activity. The remote hire makes those measurements irrelevant. One W-2 in any of these states is physical nexus on day one.

Which employee roles create nexus, and which don't

Most roles create nexus. Very few are safe. The practical posture for a multi-state ecommerce brand is to treat any W-2 in a new state as a nexus event and route it to the compliance function on the same day as the offer letter.

Sales representatives carry the most aggressive interpretation. An in-state sales rep is the paradigm case that “engaged in business” provisions were originally written to address. Every state with an active physical nexus standard treats an in-state sales rep as nexus-creating on day one. The risk concentration is real: brands frequently hire sales reps before registering in a target market, meaning the rep’s presence creates the compliance obligation before finance has seen the headcount update.

Engineering, product, and technical roles are not a safe harbor. The common misread is that a software engineer doesn’t “sell” anything and therefore doesn’t create nexus. State “engaged in business” provisions are not limited to sales-facing roles. California’s §6203, Texas’s §151.107, and New York’s §1101(b)(8) each address a range of business operations broader than soliciting orders. An engineer working on the brand’s ecommerce infrastructure from a home office in Texas is conducting business in Texas. That meets the §151.107 standard.

Customer support, operations, and finance roles sit in the same category. State provisions do not carve out back-office functions. The relevant analysis is whether the employer maintains a presence in the state through the employee’s activity. A customer support team operating from Massachusetts satisfies that test under Mass. Gen. Laws ch. 64H, § 1.

What changes across role types is the intensity of the auditor’s scrutiny, not whether the obligation exists. California, New York, and Texas trace nexus to the first day an employee operated in the state regardless of function. A remote hire from 2022 who left by 2023 may still produce trailing nexus exposure in California if the brand never registered.

Once registration is in place, sales tax compliance software like TaxCloud, Avalara, or TaxJar can handle multi-state calculation and filing regardless of which role triggered the obligation.

How 1099 contractors compare to W-2 employees for nexus purposes

Moving a hire to 1099 status does not eliminate the nexus risk in most states. Several states explicitly extend physical nexus treatment to independent contractors performing sales-related functions. The remaining states carry enough statutory ambiguity that treating contractor classification as a safe harbor is a compliance error for most brands operating across multiple states.

California takes the most aggressive position. Cal. Rev. & Tax. Code §6203 covers persons who have “any agent, canvassing agent, salesperson, or representative” operating in the state for sales-related purposes. The CDTFA’s interpretation treats in-state independent contractors who solicit orders or perform sales functions as nexus-creating at the same standard as W-2 employees. A 1099 sales rep based in Los Angeles creates nexus in California.

New York holds a similar position under NY Tax Law §1101(b)(8)(iii), which expressly extends nexus treatment to “independent contractors” who conduct sales solicitation or other qualifying business activity on behalf of an out-of-state seller.

Texas covers “agents” in Tex. Tax Code §151.107, and the Comptroller’s guidance treats in-state independent contractors performing sales-related activity as nexus-creating for the same reasons an in-state employee would be.

Non-sales contractors face a less settled, state-dependent analysis. Most nexus provisions focus on sales-related activity, so a 1099 graphic designer, copywriter, or developer sits in a grayer zone than a 1099 sales rep. Document the contractor’s scope of work and verify the state’s position before concluding no nexus exists.

Reclassifying a W-2 as a 1099 to avoid nexus is not a recognized safe harbor. Tax authorities look through classification to substance: the same work at the same location under similar direction and control means the nexus analysis tracks the arrangement’s substance, not the filing form.

Why P.L. 86-272 doesn't protect against sales tax obligations

P.L. 86-272, codified at 15 U.S.C. §§ 381-384, limits a state’s ability to impose net income tax on an out-of-state company whose only in-state activity is soliciting orders for tangible personal property, where those orders are approved outside the state and the goods are shipped from outside the state. In that narrow scenario, the statute bars the income tax imposition.

It has no application to sales tax.

A brand hiring a sales rep in Illinois may hear that P.L. 86-272 covers the exposure. That may be accurate for Illinois income tax under the right conditions; it says nothing about whether the rep creates sales tax nexus under 35 ILCS 105 and 35 ILCS 120.

The statutory scope is narrow by design: solicitation of orders for tangible personal property only, approved outside the state, with no in-state activity beyond what is incidental to solicitation. The Multistate Tax Commission revised its Statement of Information Concerning Practices of MTC Under P.L. 86-272 in September 2021, clarifying that internet-based activities (live chat with in-state customers, post-sale customer service, online return initiation, and product troubleshooting) fall outside the protection even for income tax purposes. Ecommerce brands conducting those activities as a matter of course find the income tax protection narrower than assumed.

For sales tax, P.L. 86-272 provides no protection. A sales rep in Illinois meets the physical nexus standard; a customer support hire in New York meets §1101(b)(8); an engineer in Texas meets §151.107.

The practical consequence: a brand that cites P.L. 86-272 as the reason not to register for sales tax in a state where it has a W-2 employee has misapplied the statute. The registration obligation remains, and each taxable transaction processed in that state without registration adds to the uncollected amount and to the penalty exposure that accumulates quietly until an auditor reaches it.

Registration timing: before the first transaction, not the first quarterly return

When a hire creates physical nexus in a new state, the registration obligation does not wait for the next quarterly return. Most states require registration before the next taxable transaction. If the employee starts on a Monday and the brand processes an order into that state on Tuesday, the registration obligation existed before that Tuesday transaction.

States differ on their exact framing, but the general pattern is that collection responsibility attaches when nexus is established, and registration is supposed to precede collection. A brand that establishes nexus on day one and continues processing orders without registering is failing to collect on every transaction that follows.

State-specific registration timing across the most common remote-hire states:

• California: registration required before making sales as a retailer engaged in business in the state (Cal. Rev. & Tax. Code §6203).
• Texas: physical nexus obligations for in-state presence attach immediately; permit and collection required before conducting business in the state (Tex. Tax Code §151.107).
• New York: registration required before making taxable sales in the state (NY Tax Law §1101(b)(8)).
• Illinois: registration required before beginning taxable sales activity in the state (35 ILCS 105; 35 ILCS 120).
• Massachusetts: registration as a vendor required upon establishing nexus (Mass. Gen. Laws ch. 64H, § 1).

The gap finance teams actually experience: the offer letter is signed before finance sees it. The employee starts work before anyone flags the new-state exposure. The quarterly return cycle passes. By year-end, the brand has processed months of taxable transactions into a state where it should have been registered since the hire’s first day.

Once registered, the brand is responsible for calculating and collecting on all taxable sales into that state across every applicable local jurisdiction. A state like Illinois stacks county, city, and special district rate components on top of the state base rate. TaxCloud calculates across all 13,000+ jurisdictions through one API call, so adding a new-state registration does not add proportional calculation complexity; the new state folds into the same infrastructure handling every other state in the footprint.

Wiring the HRIS feed to the nexus map

The hire decision lives in people-ops. The compliance consequence lands in the nexus map. At most brands operating across 10 or more states, these two are not connected, and that gap is where year-end surprises originate.

Gusto, Rippling, Justworks, and ADP each capture the employee’s state of residence as a required payroll field on day one. State income tax withholding attaches immediately, so the HRIS system always knows which state the employee is in. That same data point is the physical nexus trigger for sales tax. The information exists in the system; it just does not flow to the function that needs it.

The pattern that produces late discovery:

1. People-ops hires a senior engineer who lives in Massachusetts. Offer letter signed April 12.
2. Employee is onboarded in Rippling on April 28. Massachusetts payroll withholding begins.
3. Finance learns about the Massachusetts W-2 in January during year-end form processing.
4. By then, nine months of taxable transactions have been processed into Massachusetts without a registration under Mass. Gen. Laws ch. 64H, § 1.

The fix is a trigger at step 2, not a reconciliation at step 4.

The operational workflow that catches it:

1. HRIS onboarding adds any new state of residence. An alert goes to the finance or operations lead who owns the nexus map.
2. Finance checks: does the brand have an active registration in that state?
3. If not: initiate registration before the employee’s start date, or immediately after, before any further transactions into that state.
4. Registration confirmed: the compliance layer begins calculating, collecting, and filing.

This workflow requires a defined handoff, not a custom integration: who owns the nexus map, who receives the state-hire notification, and what the SOP is when a new state appears in the HRIS record. For most brands the answer to all three is unclear, which is why remote hires are the most underreported physical nexus trigger in multi-state ecommerce and discovery typically happens at year-end or audit rather than at the offer letter.

The discovery and the decision live in people-ops. The compliance infrastructure picks up from there. Once a new-state registration is in place, TaxCloud handles calculation across 13,000+ jurisdictions through a single API, routes consolidated Streamlined Sales Tax (SST) filing across the 24 participating states (23 full members plus Tennessee as an associate member), and builds the documentation trail that audit defense requires. On Shopify or Shopify Plus, the integration is native, with no manual configuration per new state. The registration triggered by a hire folds into the same infrastructure handling every other state in the footprint, with no proportional increase in manual work.