6 Ways Remote-First Companies Trip Over Multi-State Tax Rules

6 Ways Remote-First Companies Trip Over Multi-State Tax Rules

You hired a great engineer in Colorado. You did not think of it as opening a Colorado tax office. The state did.

That is the core problem with remote company multi-state tax: every hire is also a footprint. Most founders treat "remote-first" as a hiring perk and a Slack philosophy. The tax code treats it as a map of new jurisdictions you just signed up for, one W-2 at a time. The bill rarely arrives the year you make the mistake. It arrives two years later, with penalties and interest stapled to it.

Here are six ways distributed teams trip over remote company multi-state tax rules, and what each one actually costs.

Remote company multi-state tax starts with one employee creating nexus

Nexus is the legal trigger that says a state can tax you. For decades you needed an office or a warehouse to create it. Now a single employee working from their kitchen does the job.

Under factor-presence and physical-presence standards, one W-2 employee performing work in a state generally creates a payroll factor there, and that often establishes corporate income or franchise tax nexus. So your Delaware C-corp, headquartered in Texas, now owes a return in Colorado because of one hire. Not sales tax. Income or franchise tax, on a slice of your total profit apportioned to that state.

The thing nobody tells you: you can owe a state return even if you never sold a dollar to a customer there. The employee alone did it.

Payroll registration, unemployment insurance, and local taxes stack up per state

Income tax nexus is the headline. The paperwork underneath it is where the hours go.

Each new state with an employee generally means you register for state income tax withholding, register for state unemployment insurance (SUTA) and start paying it, and in many places file local or city taxes on top. SUTA rates and wage bases differ by state, so payroll math that worked for one team member breaks the moment you add the second state.

Here's the pattern: it is not one form per state. It is a recurring filing calendar per state. Five states with one employee each is not five times the work of one — it is five separate compliance relationships, each with its own deadlines, logins, and penalty schedule.

Convenience-of-the-employer rules can tax a remote worker twice

This is the one that surprises people, and it favors the state, not you.

A handful of states — including New York, Pennsylvania, Delaware, Connecticut, Nebraska, and Arkansas — apply a "convenience of the employer" rule. New Jersey adopted a reciprocal version in 2024. The rule says this: if your employee works remotely from another state for their own convenience, but the job could be done at your in-state office, that state can still tax their wages as if they never left.

Translation: your New York-based company hires someone who moves to Florida and works remotely. Florida has no income tax — but New York can still claim the wages, because the move was the employee's convenience, not your business necessity. The employee can end up taxed by their home state and New York. A 2025 New York Tax Appeals Tribunal decision upheld the rule and set a high bar for what counts as "necessity," so this is not going away.

If you have employees tied to an office in one of these states, this rule belongs in your offer letters, not just your tax return.

Workers' comp coverage does not follow employees across state lines

Founders assume their workers' compensation policy is national. It usually is not.

Workers' comp is regulated state by state. A policy written for your headquarters state often does not automatically cover an employee injured while working in another state — you frequently need an "other states" endorsement or a separate policy for each location. Skip it, and a single home-office injury can mean an uncovered claim plus a state penalty for operating without required coverage.

This one rarely shows up in a tax review, which is exactly why it slips through. It is an insurance gap that behaves like a tax surprise.

One reimbursement and benefits policy rarely fits every state

You wrote one expense and benefits policy. Several states wrote their own rules on top of it.

States like California and Illinois require employers to reimburse necessary business expenses — home internet, a portion of a personal phone, supplies — and a flat "we don't reimburse" policy can violate state labor law. Federally, an accountable plan under Treas. Reg. §1.62-2 keeps qualifying reimbursements out of taxable wages, but only if you document them correctly. Paid sick leave, final-paycheck timing, and pay-transparency rules also vary by state.

A single national handbook is efficient right up until it is non-compliant in three of the states where you employ people.

Ignoring it does not make it cheaper — it makes it more expensive

The most common move is to wait. No state has called, so it must be fine.

It is not fine; it is accruing. Unregistered payroll and unfiled state returns generally do not have a statute of limitations clock running in your favor — the clock often does not start until you file. So a state can reach back across every year you had an employee there, then add failure-to-file and failure-to-pay penalties plus interest on top.

Consider the math on a representative example. Say you've had two employees in a state for three years, total wages of about $300,000, and the state's apportioned income tax, penalties, and interest come to roughly 6% of those wages once everything is added up. That's about $18,000 — for a state you forgot you were operating in. Voluntary disclosure programs, handled early, often cut the penalty portion sharply. Waiting for the notice does the opposite.

Get your remote company multi-state tax handled before it compounds

If you have employees in three or more states and you have not registered payroll, withholding, and unemployment insurance in each, you do not have a someday problem. You have a today problem that is quietly getting bigger.

This is exactly the work Bookkeeper360 is built for — multi-state payroll and the books behind it, working in Xero and QuickBooks for distributed and remote-first teams. They handle the per-state registrations, withholding, and unemployment insurance setup so you are not learning each state's filing calendar the hard way.

Read Bookkeeper360's verified reviews on Sam's List, then book an intro call and bring a simple list: every state where you have an employee, and how long they have been there. That one list tells a good multi-state team most of what they need to know — and it is the fastest way to find out whether you owe back filings before a state finds out first.