Remote Employee in Texas, Sales Everywhere: When a Single $50K W-2 Worker Triggers Physical Nexus Before You Hit Any State's Economic Threshold
You run a SaaS company with $75,000 in annual revenue. You hire one remote engineer in Texas at $50,000 a year. You have zero Texas customers. Congratulations — you now have physical nexus in Texas and a sales tax collection obligation on every taxable sale into the state. No $500,000 threshold required. No 200-transaction minimum. One W-2 employee on day one is enough. Here's how remote workers create tax obligations that blindside growing companies every year.
Key Takeaways
- • One employee = immediate nexus: A single W-2 remote worker in a state creates physical nexus from their first day — no revenue floor, no transaction count, no waiting period
- • 1099 contractors can trigger it too: Ongoing contractor relationships (not one-off projects) are treated as agent nexus in most states
- • Strictest states: New York, California, and Illinois apply the broadest agent-nexus definitions and enforce them aggressively
- • Nexus doesn't vanish on termination: Most states maintain trailing nexus for months after an employee leaves — you can't just fire your way out of compliance
- • Dual nexus is common: When you later cross the economic nexus threshold in the same state, you now have two independent nexus triggers — terminating the employee no longer clears your obligation
What Counts as an "Agent" Creating Physical Nexus
Physical nexus through people — sometimes called "agent nexus" — is one of the oldest principles in state tax law. Long before South Dakota v. Wayfair established economic nexus in 2018, states could assert taxing authority over any company with a human representative conducting business within their borders.
Three categories of workers can create agent nexus:
W-2 Employees
This is the clearest trigger. Any W-2 employee physically located in a state creates nexus for the employer. It does not matter whether the employee is a salesperson, an engineer, an accountant, or an executive assistant. It does not matter whether they work from a company office or their kitchen table. The employee's physical presence in the state is attributed to the company. Every state with a sales tax recognizes this standard.
1099 Contractors with Ongoing Relationships
Independent contractors are more nuanced. A contractor hired for a single, discrete project — like redesigning your website over three months — generally does not create nexus. But a contractor with a continuous, regular relationship with your company can. Examples that commonly trigger nexus:
- A fractional sales rep who solicits orders on your behalf in the state
- A service technician who performs installations or repairs for your customers
- A consultant retained on an ongoing monthly basis who represents your company to clients
- A leased worker from a staffing agency performing regular duties at a location in the state
The test most states apply: does the contractor act as an agent of the company on a regular, systematic basis? If yes, their presence creates nexus as if they were an employee.
Leased and Staffing-Agency Workers
Workers provided through staffing agencies or professional employer organizations (PEOs) can also create nexus. Even though the staffing agency is technically the employer of record, the worker is performing services on your behalf in the state. Most states look through the staffing arrangement to the economic reality: if the worker is doing your company's business in the state, your company has nexus there.
How Agent Nexus Differs from Economic Nexus
The fundamental difference is timing. Economic nexus is threshold-based — you must exceed a specific revenue or transaction count (typically $100,000 in sales or 200 transactions) before the obligation kicks in. Physical nexus through an employee is instantaneous. The moment your new hire starts work, nexus exists.
| Factor | Economic Nexus | Agent/Employee Physical Nexus |
|---|---|---|
| Trigger | Revenue/transaction threshold exceeded | Employee's first day of work in the state |
| Revenue requirement | $100K–$500K depending on state | $0 — no revenue required |
| Lookback period | Rolling 12 months or calendar year | None — immediate |
| When it ends | When revenue drops below threshold (with trailing provisions) | When employee leaves the state (with trailing provisions) |
| Most common for | High-volume e-commerce sellers | Remote-first SaaS companies and service firms |
This distinction is why remote-first companies are particularly vulnerable. A traditional retailer grows into economic nexus gradually — they can see the $100,000 threshold approaching and prepare. A SaaS startup that hires its first engineer in Texas has nexus overnight, often before the founders even realize there's a sales tax implication.
Worked Example: $75K-Revenue SaaS Company Hires in Texas
Let's trace what happens step by step when a small SaaS company creates physical nexus through a remote hire.
The Company
DevStack is a two-person SaaS startup incorporated in Delaware, with both founders working from home in Oregon (no sales tax). Annual revenue: $75,000 from B2B subscriptions across 12 states. Texas revenue: $8,000. Texas's economic nexus threshold is $500,000. DevStack is nowhere close.
The Hire
DevStack hires a full-stack engineer in Austin, Texas. Salary: $50,000. The engineer works remotely from their apartment. DevStack now has a W-2 employee physically present in Texas.
The Nexus Trigger
On the engineer's first day, DevStack has physical nexus in Texas. The company must register for a Texas sales tax permit and begin collecting Texas sales tax on taxable sales to Texas customers. Texas taxes SaaS — so DevStack's $8,000 in Texas subscription revenue is now subject to the state's 6.25% sales tax (plus any local rates). Estimated annual liability: $500–$660 depending on the customers' local tax jurisdictions.
The Hidden Complexity
DevStack now needs to determine: Is their SaaS product taxable in Texas? (Yes — Texas taxes data processing services and SaaS.) What are the local tax rates for each customer's location? What filing frequency will Texas assign them? (Likely quarterly at this volume.) Will they also need to file a Texas franchise tax return? (Possibly — physical presence through an employee creates income/franchise tax nexus too, though that's a separate analysis.) One hire just created a compliance cascade.
States with the Strictest Agent-Nexus Definitions
While every state with a sales tax recognizes employee presence as a nexus trigger, three states stand out for applying particularly broad definitions of what constitutes an "agent" and enforcing those definitions aggressively.
New York
New York's Tax Law defines nexus-creating activities broadly. Any employee, agent, or representative regularly soliciting business in the state — or regularly performing services in the state on behalf of the company — creates nexus. New York has also applied its "convenience of the employer" rule aggressively: if an employee works remotely in New York for their own convenience (not because the employer requires it), the employer still has nexus. The New York economic nexus threshold requires both $500,000 in sales and 100 transactions, but a single remote worker bypasses both prongs entirely.
California
California's Revenue and Taxation Code establishes nexus through any person — employee, agent, or representative — who operates in the state on behalf of the retailer. California's economic nexus threshold is $500,000 with no transaction count, making it one of the highest in the country. But a $30,000-a-year part-time contractor in Los Angeles creates nexus that the $500,000 threshold would never reach. California also has trailing nexus provisions — physical nexus continues through the end of the quarter in which the presence ceases, plus the following quarter.
Illinois
Illinois applies a broad interpretation of physical nexus that includes any agent or employee maintaining a place of business in the state, soliciting orders, or delivering goods. The Illinois economic nexus threshold is $100,000 or 200 transactions. But Illinois is particularly strict about contractor relationships — even independent sales reps who operate under their own business name can create nexus for the companies they represent if the relationship is ongoing and systematic.
What Happens When the Employee Leaves: Does Nexus Dissolve or Linger?
This is one of the most misunderstood aspects of physical nexus. When your remote employee in Texas quits, gets laid off, or relocates to another state, your physical presence in Texas ends. But your nexus obligation may not end on the same day.
The treatment varies by state:
- Immediate cessation: A handful of states treat nexus as ending when physical presence ends, with no trailing period. However, you still owe returns for all periods when nexus existed.
- End of current period: Some states maintain nexus through the end of the current filing period (month, quarter, or year) after the employee departs.
- Explicit trailing provisions: California maintains nexus through the end of the current quarter plus the following quarter. New York generally maintains nexus through the end of the current year.
- Ambiguous or unaddressed: Many states have no explicit guidance on when physical nexus ends after an employee departs. In these cases, the conservative approach is to continue collecting and filing through at least the end of the current calendar year.
The practical takeaway: you cannot terminate an employee on December 15 and assume your nexus obligation ends on December 16. Plan for at least one additional quarter of compliance after the physical presence ceases.
The Interaction: Physical Nexus Now, Economic Nexus Later
Consider what happens to DevStack two years after hiring their Texas engineer. The company has grown — Texas revenue is now $120,000 annually, well above the hypothetical $100,000 standard economic nexus threshold (though Texas's actual threshold is $500,000). DevStack now has both physical and economic nexus in Texas.
This dual-nexus situation has important implications:
- Redundant triggers: If DevStack later terminates the Texas employee, they still have economic nexus through revenue. The compliance obligation continues uninterrupted.
- Voluntary disclosure complications: If DevStack discovers they should have been collecting Texas sales tax but didn't register, the voluntary disclosure agreement timeline typically starts from the earliest date nexus was established — which is the employee's first day, not the date economic nexus was crossed.
- Audit exposure: States auditing companies with dual nexus can assert jurisdiction from the earlier of the two triggers. If you hired a remote worker in 2023 but didn't register until you crossed the economic threshold in 2025, the state can seek back taxes from 2023.
The lesson: register when the first nexus trigger occurs — don't wait to see if you'll also cross the economic threshold.
Practical Steps for Remote-First Companies
If your company hires remote workers across multiple states, here's how to stay ahead of physical nexus obligations:
1. Map Your People Footprint Before Each Hire
Before extending an offer to a candidate in a new state, check whether that state has sales tax and whether your product is taxable there. This is especially important for SaaS companies, since SaaS taxability varies widely by state. If the state taxes your product and you have customers there, a hire in that state creates an immediate compliance obligation.
2. Register Promptly After Hiring
Most states expect registration before the first taxable transaction after nexus is established. Some states, like North Carolina, impose a 30-day registration deadline. Others expect registration by the start of the next filing period. Don't wait months after hiring to register — the gap between nexus creation and registration is a period of non-compliance.
3. Track Contractor Relationships Too
Maintain a list of all ongoing 1099 contractor relationships with their state locations. Any contractor who regularly acts on your company's behalf — especially those in sales, customer success, or service delivery roles — may be creating nexus. Review this list quarterly.
4. Document Departure Dates
When an employee leaves or a contractor relationship ends, document the exact date physical presence ceased in that state. This date determines when trailing nexus provisions start and when you can potentially stop collecting tax (assuming no other nexus trigger exists).
5. Use Voluntary Disclosure If You're Behind
If you've had remote employees in states where you haven't been collecting sales tax, don't just register and hope the state doesn't look back. Contact the state about a voluntary disclosure agreement before registering — VDAs typically limit the lookback period and waive penalties, saving significantly more than the cost of professional guidance.
Frequently Asked Questions
Yes. A W-2 employee working in a state — even from their home — constitutes physical presence and creates nexus for your company in that state. This is true regardless of the employee's role, salary, or whether they interact with local customers. The employee's physical location is what matters, not their job function. This applies even if your company has zero revenue from that state.
Last Updated: May 5, 2026
Disclaimer: This information is provided for educational and informational purposes only and does not constitute tax, legal, or financial advice. Tax laws and regulations change frequently. While we strive to keep this information accurate and up-to-date, we make no representations or warranties of any kind about the completeness, accuracy, reliability, or suitability of this information. Please consult with a qualified tax professional or attorney for advice specific to your business situation. Always verify current requirements with the official state tax authority.