So, your team is remote-first. Maybe you’ve got folks in Portland, a designer in Austin, a developer in Boise, and a customer success lead working from a cabin in Vermont. Sounds dreamy, right? It is — until the tax man comes knocking. And honestly, he will. Because when your employees work from different states, you’re not just building a culture — you’re building a sales tax nexus.
Let’s be real: sales tax nexus for remote-first teams is a tangled web. But it’s not impossible to navigate. You just need to know where the tripwires are. And maybe, a little patience. Here’s the deal.
What the heck is “nexus” anyway?
Nexus is just a fancy word for “connection.” In tax world, it means your business has enough of a presence in a state that the state can demand you collect and remit sales tax. Before 2018, you mostly only had nexus if you had a physical location — like an office or a warehouse. But then came the South Dakota v. Wayfair Supreme Court decision. And boom — economic nexus was born.
Now, even a single remote employee in a state can create physical nexus. And if you sell enough stuff to customers in a state — say, $100,000 in sales or 200 transactions — you get economic nexus too. For remote-first teams, this is a double whammy.
Physical nexus: the employee trap
Here’s where it gets sticky. If your marketing manager works from her home in Colorado, congratulations — you likely have nexus in Colorado. Even if you don’t have a lease or a sign out front. The state sees that employee as your “presence.” And they want their cut.
I’ve seen startups freak out about this. But honestly? It’s manageable. You just need to track where your people are — and I mean really track it. Because someone might move to a new state without telling you. Happens all the time. Suddenly, you’ve got nexus in a state you never planned for.
The economic nexus threshold — it’s not uniform
Economic nexus thresholds vary by state. Most use $100,000 in sales or 200 transactions. But not all. Texas? $500,000. California? $500,000 too. And some states — like Kansas — have weird rules about counting marketplace sales. It’s a patchwork quilt, and it’s ugly.
For remote-first teams, you’re not just dealing with your own sales. You’re dealing with where your employees live, where your contractors work, and even where you store inventory. Yes, even if that “inventory” is just a box of swag in someone’s garage.
Marketplace facilitators: a hidden layer
If you sell on Amazon, Etsy, or Walmart Marketplace, those platforms often collect and remit sales tax for you. But not always. And if you have remote employees in states where you sell through a marketplace? Well, that physical nexus might override the marketplace’s responsibility. It’s a gray area that makes tax pros scratch their heads.
So, sure — you can rely on marketplace facilitators for some protection. But don’t assume it covers everything. Check the fine print. Or better yet, talk to a tax advisor who’s seen this movie before.
Tracking employee locations — the boring but vital work
You know what’s not sexy? Spreadsheets. But you need one. Or better, a proper HR system that tracks employee addresses and updates them when someone moves. Because here’s the thing: a remote employee who spends two weeks working from their parents’ house in Florida? That might not create nexus. But a remote employee who moves to Florida permanently? That’s a different story.
Some states have “convenience of the employer” rules — meaning if the employee works from home for their own convenience (not because you require it), you might avoid nexus. But other states — like New York — are aggressive. They’ll say: “If the employee is here, you’re here.” Period.
What about contractors and freelancers?
Ah, the gray zone. Independent contractors can create nexus too — in some states. It depends on how much control you have over them. If a contractor in Oregon is basically acting like an employee (using your equipment, following your schedule, doing core business functions), a state might argue they’re a de facto employee. And bam — nexus.
My advice? Don’t assume contractors are safe. Document their independence. Have clear contracts. And if you have a contractor in a state where you also have lots of customers? Well, that’s a red flag worth investigating.
Practical steps to stay compliant (without losing your mind)
Alright, enough doom and gloom. Let’s talk solutions. Here’s what actually works for remote-first teams:
- Audit your team’s locations quarterly. Seriously. Send out a quick survey. “Hey team, where are you living right now? Any moves since last quarter?” Make it easy. Use a tool like Deel or Rippling that auto-tracks this stuff.
- Register for sales tax in every state where you have nexus. Yes, it’s a pain. Yes, it costs money. But the penalties for not registering? Much worse. Start with states where you have employees, then move to states where you have economic nexus.
- Use automated sales tax software. Avalara, TaxJar (now part of Stripe), or Vertex. These tools integrate with your ecommerce platform and calculate tax in real-time. They also handle filing. Worth every penny.
- Keep an eye on “click-through” nexus. Some states say if you have affiliates or referral partners in their state, you have nexus. Even if you don’t have employees there. It’s old-school, but it’s still on the books in places like New York and California.
And here’s a pro tip: don’t forget about local sales tax. Some states — like Colorado, Alabama, and Louisiana — have county and city-level taxes. If your remote employee lives in a specific city, you might need to collect tax at that local rate. It’s a nightmare, but software handles it.
The cost of getting it wrong
Let me paint you a picture. A SaaS company based in Delaware (no sales tax!) thought they were safe. They hired a remote team member in Texas. Didn’t register. Didn’t collect tax. Two years later, a Texas audit revealed $340,000 in uncollected sales tax, plus penalties and interest. The company almost folded.
That’s the risk. States are getting smarter. They share data. They audit remote companies more aggressively now. And with the rise of remote work, states are hungry for revenue. Don’t be a target.
A quick table for the visual learners
| State | Economic Nexus Threshold | Physical Nexus from Remote Employees? |
|---|---|---|
| California | $500,000 | Yes |
| Texas | $500,000 | Yes |
| New York | $500,000 | Yes (aggressive) |
| Florida | $100,000 | Yes |
| Colorado | $100,000 | Yes |
| South Dakota | $100,000 | Yes |
Notice something? Every state with a threshold also considers remote employees as physical nexus. So you’re almost always double-exposed. Fun, right?
What about international remote workers?
Oh, you thought this was just a US problem? Nope. If you have a remote employee in Canada, the UK, or Australia — you might trigger VAT or GST obligations. The rules are different, but the principle is the same: presence creates obligation. For global teams, you need a global strategy. And probably a very good accountant.
I won’t lie — this part is messy. But start with the countries where you have the most employees or the most revenue. Prioritize. You can’t solve everything at once.
Building a nexus-aware culture
Here’s the thing — compliance isn’t just a finance problem. It’s a people problem. Your remote team needs to understand that where they live matters. Not in a creepy surveillance way, but in a “hey, we need to know so we don’t get fined” way.
Make it part of onboarding. “Welcome to the team! By the way, we need your current address for tax purposes. If you move, please update it within 30 days.” Put it in your employee handbook. Send reminders. Make it painless.
And if someone wants to work from a van traveling across state lines? Well, that’s a whole different conversation. But for most remote-first teams, a little transparency goes a long way.
The bottom line (no pun intended)
Sales tax nexus for remote-first teams isn’t a one-time thing. It’s a living, breathing challenge that evolves as your team grows and moves. You’ll make mistakes. You’ll miss a state registration. You’ll probably pay a late fee at some point. That’s okay — as long as you learn and adjust.
The companies that thrive in this environment are the ones that treat tax compliance like a muscle — something you exercise regularly, not something you think about once a year. Automate what you can. Ask for help when you need it. And never assume you’re “too small” for a state to notice.
Because in the end, remote work is about freedom. But freedom without responsibility? That’s just chaos. And chaos doesn’t scale.
So take a breath. Look at your team map. And start building that nexus strategy — one state at a time.