What Are 8 Multistate Tax Pitfalls for Online Businesses With Remote Teams?
If multistate tax were a highway, are you gliding through yellow lights because “we’re online, not local”? That illusion is expensive. One remote hire in the wrong zip code can flip half your map to flashing red.
Today, we’ll sprint through eight pitfalls that quietly create nexus, force registrations you didn’t plan for, and booby-trap your filing calendar. You’ll leave with a practical plan you can run this week. No jargon, no detours, just crisp steps that keep your returns on time and your notices quiet.
Summary of what this blog covers
- The eight multistate tax traps that ambush online brands with remote employees and how to disarm them fast
- Practical checklists for nexus assessment, registrations, and a living state + city filing calendar
- Simple, founder-ready scripts for marketplace vs. DTC mapping, P.L. 86-272, and voluntary disclosures
1) Running 2023 rules in a 2026 world
The pitfall: You’re still quoting “$100,000 or 200 transactions” like it’s carved in stone. Post-Wayfair, many states rewrote the rules. Several dropped the 200-transaction trigger and now care almost entirely about dollar thresholds.
Aha moment: Economic nexus isn’t a bronze plaque. It’s a living spreadsheet.
What to do now:
- Build a state-by-state economic nexus matrix with three columns you update quarterly: threshold, how to measure it, and whether transactions still matter.
- Add a channel column so you don’t double-collect when marketplaces already collect and remit.
- Tie to your P&L cadence: review thresholds at the same time you close the month.
Founder script: “On day one of each month, update the nexus matrix. If any state turns ‘Yes’ for the threshold, open the registration ticket the same day. No exceptions.”
2) Treating a remote employee like they’re invisible
The pitfall: A single employee can trigger sales/use tax, income or franchise tax, withholding/payroll registrations, and sometimes city filings. A home office is still a place where your business operates.
Aha moment: One laptop on a couch is a “presence” for nexus.
What to do now:
- Pre-hire checklist: business registration, sales/use tax permit, income/franchise account, payroll withholding + unemployment, workers’ comp, city license.
- Role-based risk review: sales, technical services, and in-state managers increase exposure.
- Calendar the first due dates the same day you receive account numbers.
3) Believing marketplaces “handle everything”
The pitfall: Marketplaces collect/remit for marketplace orders. Your Shopify DTC site is different. You may still owe returns in “marketplace states,” and you own DTC configuration.
Aha moment: “Marketplace handles it” means only marketplace orders. DTC is still your tax baby.
What to do now:
- Split mapping: Marketplace-collected → clearing liability; DTC-collected → DTC liability.
- Monthly tie-out: marketplace statement vs. recorded tax.
- Shop app nuance: treat Shop-channel orders like marketplace activity.
- Return cadence: some states require returns even when marketplaces remit all tax for that channel.
4) Hiding behind P.L. 86-272 while your website does more than sell
The pitfall: Modern internet activities (interactive chat beyond orders, post-sale portals, cookie personalization) can blow the 86-272 shield in many states.
Aha moment: If your site does more than “please buy this,” your immunity might be a costume.
What to do now:
- Website inventory: what can a user do after the sale? Live chat? Cookies beyond solicitation?
- Write a one-page 86-272 memo: site features, why protection applies (or not), states’ interpretations.
- Apportionment reality: if protection falls, add the state to your income/franchise footprint.
5) Forgetting city and county business taxes
The pitfall: NYC Unincorporated Business Tax, San Francisco Gross Receipts Tax, and similar local regimes can apply if a remote worker lives there.
Aha moment: Zip codes can be tax codes.
What to do now:
- Add a city layer to your nexus matrix: NYC, SF, LA, Portland, Philadelphia, Seattle, etc.
- Track headcount by city. HR triggers nexus review on moves.
- Calendar city due dates near state filings.
6) Ignoring gross-receipts and franchise taxes in “no-income-tax” states
The pitfall: Washington B&O tax on gross receipts, Texas franchise tax, and similar obligations run on different triggers than sales tax.
Aha moment: One threshold doesn’t rule them all.
What to do now:
- Footprint by tax type: sales/use, income/franchise, gross receipts/B&O, city business taxes.
- Set filing frequency and internal payment cutoffs per lane.
- Texas/Washington specifics: know thresholds, EZ computation, separate sales tax nexus for DTC.
7) Calendar failures: you collect correctly, then miss the first return
The pitfall: Compliance usually fails on the calendar, not on the return. Notices arrive. Penalties nibble.
Aha moment: Compliance usually fails on the calendar, not on the return.
What to do now:
- Build a master calendar: Secretary of State reports, sales/use (state + city), income/franchise, payroll/withholding, unemployment, marketplace zero-dollar returns.
- Assign owners/backups; store credentials securely.
- Set internal cutoffs and reserve cash before due dates.
- Attach reconciliations: marketplace tie-out, DTC tax by state, payroll totals.
8) Skipping voluntary disclosure or limited lookback
The pitfall: You panic-file every return with full penalties instead of using voluntary disclosure agreements (VDAs) that offer shorter lookback and penalty relief.
Aha moment: The best time to fix past-due exposure is before the state finds you.
What to do now:
- Pause and triage: exposure dollars, periods, risk level.
- Check VDA programs and anonymous contact options.
- Prioritize high-penalty jurisdictions or active city regimes.
- Stage cleanup to avoid cash crunches.
A channel-aware mapping that actually reconciles
- Marketplace orders → record platform-collected sales tax to Marketplaces: Tax Clearing liability; reconcile monthly to settlement statements.
- DTC orders → configure tax by state in e-commerce platform; post to DTC Sales Tax Liability; reconcile monthly.
- Shop app nuance → treat Shop-channel orders like marketplace activity.
- Include both in nexus matrix.
The remote-team nexus map (reusable)
- Hire/relocate employee → run pre-hire nexus check for state and city.
- Register where necessary: sales/use, income/franchise, local business tax, payroll/withholding, unemployment, workers’ comp, Secretary of State.
- Configure systems: sales tax by channel, payroll withholding by state/city, marketplace vs. DTC toggles.
- Start returns: add to calendar with credentials and bank limits; set internal cutoffs.
- Quarterly review: refresh nexus matrix, update P.L. 86-272 memo, audit headcount by city.
Your essential artifacts (the time-savers)
- Nexus matrix with threshold dates and channel notes.
- Registration dossier: account numbers, portal logins, bank tokens, approval letters.
- Filing calendar with owners, backups, due dates, internal cutoffs.
- Marketplace tie-out: facilitator tax vs. statements and bank activity.
- P.L. 86-272 web memo documenting site features and position.
- Remote-employee log: addresses, start dates, job functions, home-office stipends.
Bottom line in two lines
Remote teams and omnichannel selling make nexus a moving target. The winners treat multistate tax like a product launch: precise scope, tight documentation, and disciplined updates when rules change.
Ready to swap uncertainty for a plan you can trust?
Insogna will run your nexus assessment, complete the right registrations, and build a living state + city filing calendar your team can operate without guesswork. We’ll segment marketplace vs. DTC, document P.L. 86-272, and guide voluntary disclosures if needed.
Book an eCommerce Multistate Tax & Nexus Review today. Walk out confident, filing on time, with zero hesitation.
Frequently Asked Questions
Do marketplaces completely remove my sales tax responsibilities?
No. Marketplaces usually collect and remit for marketplace orders only. You still own DTC collection and filing where you have nexus. Some states require returns even when the marketplace remits 100% for that channel. Use a channel-aware calendar and monthly marketplace tie-outs.
How does a single remote employee create tax exposure?
Physical presence creates nexus for several tax types. A remote employee may trigger sales/use, income or franchise, withholding, unemployment, and even city obligations. Use a pre-hire checklist and open registrations before the start date.
What exactly is P.L. 86-272 and why do eCommerce sites trip it?
P.L. 86-272 can shield out-of-state sellers of tangible goods from state income taxes if activity is limited to soliciting orders. Many states interpret modern internet activities (interactive chat beyond ordering, post-sale support portals, cookie personalization) as beyond solicitation. If your site does more, assume exposure and apportion income.
We’re in “no income tax” states. What else could we owe?
Plenty. Gross receipts taxes (Washington B&O) and franchise taxes (Texas) run on different triggers than sales tax. Track each tax type separately, register when thresholds are met, and schedule filings with internal cash cutoffs.
We discovered two years of past-due sales tax in three states. Should we just file and pay?
Pause. Many states offer voluntary disclosure agreements (VDAs) with shorter lookback and reduced penalties if you approach them before they contact you. Have a CPA or enrolled agent initiate anonymous outreach where allowed, then stage payments so you don’t strain cash.
