Remote work broke an assumption payroll systems were built on: that the state where an employee works is the state where the employer's office is.
Once that assumption fails, one employee can generate obligations in two or three states, in a city nobody registered with, and — the part that surprises clients most — can create tax and registration obligations for the employer that have nothing to do with payroll at all.
The way to get this right is to stop treating it as one question. It is three, they have different answers, and conflating them is the source of nearly every multi-state payroll error.
Question one: income tax withholding. Which state or states must the employer withhold personal income tax for?
Question two: unemployment insurance reporting. Which single state should the employee's wages be reported to for unemployment purposes?
Question three: employer nexus. Does having an employee in this state create obligations for the employer beyond payroll — income or franchise tax, sales tax registration, workers' compensation, or participation in state programs?
These have different rules and different answers, and it is entirely normal for an employee's wages to be reported to one state for unemployment while income tax is withheld for another.
The general principles, before the exceptions:
A state may tax income earned from services performed within its borders, regardless of where the worker lives. This is the source-based claim.
A state may tax all income of its residents, regardless of where earned. This is the residence-based claim.
Both claims can apply to the same dollar. An employee who lives in one state and performs services in another is potentially taxable in both, and the mechanisms that prevent actual double taxation are a credit in the residence state for tax paid to the work state, or a reciprocity agreement between the two.
Which produces the default rule for a remote employee: withhold for the state where the work is actually performed, and consider whether the residence state also requires withholding.
Some pairs of states agree that a resident of one working in the other will be taxed only by the residence state. Where such an agreement applies, the employer withholds for the residence state and not the work state.
Three things practitioners get wrong:
They are pairwise, not general. An agreement between two states says nothing about a third.
They require an employee certificate. The employee must file the applicable form with the employer to claim the treatment, and an employer applying reciprocity without the certificate on file has an unsupported position.
They cover income tax, not unemployment. The unemployment analysis is separate, and reciprocity does not change it.
The single largest trap in remote payroll, and the one most likely to produce a surprised client.
A small number of states apply a rule under which compensation earned by a nonresident working remotely for the convenience of the employee rather than out of the employer's necessity is treated as income sourced to the employer's state — meaning the employee is taxed by a state they never set foot in.
The consequences are real: an employee living in one state, working exclusively from home for an employer headquartered in a convenience-rule state, can be subject to withholding for the employer's state and taxed by their residence state, with the availability of a credit depending on whether the residence state recognizes the other state's claim. Some do not, producing actual double taxation.
These rules vary in their details, have been challenged, and are the subject of ongoing dispute between states. Any client with employees working remotely across state lines needs this checked specifically against current guidance for the states involved — it cannot be reasoned out from general principles.
The routine failure: an employee moves and payroll finds out from an address change on a benefits form three months later.
Domicile — the place a person intends as their permanent home — and statutory residency, which several states assert through day-count tests, are different concepts, and a person can be a resident of two states under their respective definitions.
The practical controls: a policy requiring employees to report a move before it happens, a payroll process that treats a work-location change as an event rather than a data update, and a part-year allocation that reflects the actual dates rather than a full-year assumption.
Unemployment wages go to one state, and the analysis follows a defined sequence rather than a judgment call. The standard test applies four factors in order, stopping at the first that resolves:
For a fully remote employee working from home, the analysis typically resolves at the first factor — the services are localized where the employee works — which means the unemployment state is frequently the employee's home state even where income tax withholding points elsewhere. That divergence is correct and it confuses clients.
Practical consequences worth flagging to clients: the employer must register with the unemployment agency in each state where wages are reported, new-employer rates and taxable wage bases differ by state, and moving an employee between states mid-year raises wage-base questions that produce over- or under-payment if handled mechanically.
Payroll is where the conversation starts. It is rarely where the exposure ends, and this section is the most valuable thing an advisor can raise early.
Local taxes. Cities, counties, school districts, and transit authorities in various states impose their own income or wage taxes with their own withholding and registration requirements. This is the most commonly missed obligation in the entire area, because a payroll system configured for state taxes may be silent about a municipality.
State income or franchise tax nexus. A single employee working in a state can establish nexus for the employer, creating income or franchise tax filing obligations. Protections that historically shielded solicitation-only activity generally do not cover an employee performing substantive work from home.
Sales tax registration. Physical presence through an employee can create a collection obligation independent of any economic threshold — which matters for clients who concluded they had no obligation in a state based on sales volume alone.
Workers' compensation coverage requirements in the employee's state.
State-mandated programs, including paid family and medical leave, temporary disability, and state-facilitated retirement programs, each with its own registration, contribution, and notice requirements.
Employment law reach — minimum wage, overtime rules, pay frequency, wage statement content, final pay timing, and required notices generally follow the employee's work location, not the employer's.
A client who hired one remote employee in a new state and thought they had a payroll question frequently has six registrations to complete.
Structured coverage is available through Multi-State Payroll Tax Compliance, the Payroll Boot Camp, the Certified Payroll Administrator and Certified Payroll Manager programs, the Payroll Operations Training and Certification Program, and How to Minimize and Eliminate Payroll Penalties.
An employee who lives and primarily works in one state but travels to others creates a separate analysis from a fully remote employee, and most clients handle it by ignoring it.
Nonresident withholding thresholds vary substantially. Some states require withholding from the first day of work performed in the state; others apply a day-count or earnings threshold. There is no general rule, and a threshold that applies in one state does not apply in the next.
The tracking problem is real. Complying requires knowing which days an employee worked in which state, which most organizations cannot produce. Expense reports and travel bookings are the practical proxy.
The risk is concentrated in high-earners, because the tax at stake scales with compensation. Executives, salespeople, and consultants traveling regularly are where the exposure is material.
The advisable posture for a client with material travel: track days deliberately for the employees whose compensation makes it worth it, and address the states they actually travel to rather than attempting a universal solution.
Discovering that a client has been withholding for the wrong state is common. What to do:
Determine the correct treatment first, for each affected state and period, before filing anything.
Register where registration was required, and expect to explain the period of unregistered activity. Voluntary disclosure programs exist in many states and generally produce a better outcome than being found.
Amend the returns in both directions — the state that was over-withheld and the state that was under-withheld. The employee may need to file amended personal returns to obtain a refund from one state and pay another, and the employer should tell them rather than leave them to discover it.
Understand the employer's own liability. An employer that failed to withhold can be liable for the tax, plus penalties and interest, even where the employee ultimately paid it. That converts a compliance oversight into a direct cost.
Address the local taxes in the same exercise, because they are usually the part still missing after the state analysis is corrected.
The framing worth giving every client with a remote employee: hiring someone in a new state is a registration project, not a payroll setting. Handled at the point of hire it takes an afternoon. Handled after two years of filings it takes voluntary disclosure agreements in several states and a conversation about who pays for it.
Generally the state where the work is actually performed, with the employee's residence state also considered — since a state may tax income sourced within its borders and may also tax all income of its residents. Double taxation is prevented by a credit in the residence state or by a reciprocity agreement, and a convenience-of-the-employer rule in the employer's state can override the general analysis entirely.
A rule applied by a small number of states treating a nonresident's remote work compensation as sourced to the employer's state when the remote arrangement is for the employee's convenience rather than the employer's necessity. It can result in an employee being taxed by a state they never entered, and where the residence state does not allow a credit, in actual double taxation. It must be checked against current state guidance rather than reasoned from principles.
By a four-factor test applied in order, stopping at the first that resolves: whether services are localized in one state; if not, whether there is a base of operations in a state where some services are performed; if not, the state from which work is directed and controlled; and if not, the employee's residence. Only one state receives the wages, and for a fully remote employee it is usually their home state — which frequently differs from the withholding state.
No. They address personal income tax withholding only, they operate between specific pairs of states rather than generally, and they require the employee to file the applicable certificate with the employer. An employer applying reciprocity without that certificate on file has an unsupported position.
Local city, county, school district, or transit taxes; state income or franchise tax nexus for the employer; sales tax registration through physical presence regardless of economic thresholds; workers' compensation coverage; state-mandated paid leave, disability, and retirement program participation; and employment law obligations covering minimum wage, pay frequency, wage statements, and final pay that follow the employee's location.
Determine the correct treatment for each state and period first, register where required — voluntary disclosure generally produces a better outcome than being found — amend returns in both directions, and tell the employee they may need amended personal returns. Note that an employer that failed to withhold can be liable for the tax plus penalties and interest even if the employee eventually paid it.


