Managing Payroll for Remote Employees in Multiple States

You found the perfect hire. She lives in another state. The offer letter took ten minutes — and then payroll asked which state to withhold for, and you discovered that one remote employee just enrolled your company in a new state's tax system: withholding accounts, unemployment registration, maybe local taxes, possibly a rule that taxes her in a state she never sets foot in. Here's the working map for multi-state remote payroll in 2026 — where to withhold, where unemployment goes, and the traps (reciprocity, "convenience" rules, city taxes) that generate most of the cleanup projects.

Which state's taxes do you withhold?

The default rule is simpler than the exceptions: withhold for the state where the employee physically performs the work — which for a remote employee means their home state, not your headquarters state. A Miami company hiring a developer in Atlanta withholds Georgia tax, because the work happens in Georgia.

That default gets modified by three things — reciprocity agreements, convenience-of-the-employer rules, and employees who split time across states. The quick reference:

Two more baseline facts: nine states have no personal income tax to withhold (Florida, Texas, Tennessee, Nevada, Washington, South Dakota, Wyoming, Alaska, New Hampshire) — but every state still runs unemployment tax, so "no income tax" never means "no registration." And an employee's resident state generally taxes all their income while crediting taxes paid to work states, which is how double taxation is usually (not always) avoided.

What is the "convenience of the employer" rule — and who does it bite?

A handful of states — New York most aggressively, along with Delaware, Nebraska, and Pennsylvania (each with its own variations, and Connecticut and New Jersey applying mirror-image versions against states that have such rules) — source a remote employee's wages to the employer's state unless the employee works remotely out of the employer's necessity rather than personal convenience.

Translation: a New York company's employee who moved to Florida and works from home by choice can still owe New York income tax on those wages. New York presumes remote work is for convenience and audits this actively; a genuinely required out-of-state arrangement (a bona fide employer office requirement, specialized facilities, employer-mandated location) can rebut it, but the bar is high and documentation matters.

Where it hurts most: an employee in a no-tax state (Florida, Texas) working for a convenience-rule employer gets no home-state credit to offset the New York tax — the rule effectively imports state income tax into their tax-free state. Where it double-hurts: two states claiming the same wages, with credits that don't fully reconcile.

If you're an employer in one of these states building a remote team — or a Florida company acquiring one — this is the single rule worth professional review before, not after, the hires. It's hedged, litigated, and fact-specific; treat any simple summary (including this one) as a starting point.

When does reciprocity make life easier?

Reciprocity agreements are bilateral deals — mostly among neighboring mid-Atlantic and Midwest states — that let an employee who lives in State A and works in State B pay income tax only to their home state. Classic pairs and clusters include Pennsylvania–New Jersey, Maryland–Virginia–D.C., and various Midwest combinations (Illinois, Indiana, Kentucky, Michigan, Ohio, Wisconsin appear in several).

Mechanics for the employer: the employee files the work state's exemption certificate with you; you then withhold for the home state instead. Three cautions — reciprocity covers wages only (not business or investment income), it exists only where an actual agreement exists (never assume), and without the exemption form on file you should withhold normally for the work state. For fully remote employees, reciprocity rarely matters (home state = work state); it's the hybrid and commuter cases where it earns its keep.

Where does unemployment tax go?

State unemployment insurance (SUI) follows different logic than withholding: each employee's wages are reported to exactly one state, decided by the Department of Labor's four-factor "localization of work" test, applied in order:

1. Localization — where is the work actually performed? A fully remote employee's services are localized in their home state. Done; that's the answer for most remote hires.
2. Base of operations — for multi-state workers, where does the employee start/return, keep equipment, receive direction?
3. Place of direction and control — where is the work directed from?
4. Residence — the tiebreaker.

Practical upshot: your remote hire in Georgia means a Georgia SUI account with Georgia's wage base and your assigned new-employer rate — not your home state's. Wage bases range wildly ($7,000 in Florida to $78,200 in Washington for 2026), so an identical salary carries different unemployment costs by state. Get the state wrong and you'll eventually refile in the right one — while chasing refunds from the wrong one.

What about local taxes and the other state programs?

The layer everyone forgets until a notice arrives:

• Local income/wage taxes — Ohio municipalities, Pennsylvania's local earned-income taxes (plus LST), Philadelphia's wage tax, New York City's resident tax, Kentucky occupational license taxes, and more. If your remote employee lives in one of these, there's likely a local withholding obligation.
• State disability and paid family/medical leave programs — a growing list of states (California, New York, New Jersey, Washington, Colorado, Massachusetts, Oregon among them) require premiums, some employer-paid, some employee-withheld.
• Workers' compensation — coverage requirements follow the employee's work state, including for a home office.
• New-hire reporting — to the work state's directory, generally within 20 days (faster in some states).

How do you set up a new state correctly?

The onboarding sequence for each new employee state:

1. Confirm the worker is actually an employee — if you're tempted to "just 1099 it" to skip all this, read our 1099 vs W-2 comparison first; misclassification penalties dwarf registration hassle.
2. Register for the state withholding account (skip only in true no-income-tax states).
3. Register for SUI and note your new-employer rate and wage base.
4. Check local taxes, disability/PFML programs, and workers' comp for that state.
5. Load the state into payroll software, collect the state's W-4 equivalent (and any reciprocity exemption form), file the new-hire report.
6. Calendar the state's deposit and filing cadence — then fold it into your regular payroll tax rhythm.

A hedged example: a Coral Gables agency hires two remote staff — a designer in Georgia and an account lead in Columbus, Ohio. Georgia: withholding account + SUI account, done. Ohio: withholding + SUI + Columbus municipal withholding, plus a check for the employee's school-district tax. Neither hire affects Florida payroll (no state income tax; Florida reemployment tax continues for Florida staff). Total setup: a few hours plus a few weeks of waiting on account numbers — versus months of penalty notices if discovered late. Details vary by city and rate; the sequence doesn't.

Most companies discover this landscape after the first out-of-state paycheck, usually via a notice. That's recoverable — registrations can be backdated, filings caught up, penalties often abated for first-time issues. Problems come here to get solved. WAYG's payroll service handles multi-state registration, withholding logic, and every state's filings as one system.

FAQ

Our employee moved states and told no one. Now what?

It happens constantly. Register in the new state effective from the move date, correct withholding going forward, and file amended/prorated reports where materially off. Then add a policy: address changes must be reported before the next payroll, because taxes, benefits, and workers' comp all key off location.

Is there a minimum number of days before a state taxes a traveling employee?

Sometimes — several states have de minimis thresholds (a set number of days or a wage floor) before nonresident withholding kicks in, while others technically apply from day one. Track workdays by state for anyone who travels; the data answers every version of this question.

Do we owe corporate taxes in a state just because one employee works there?

An employee can create business-tax nexus (income/franchise tax, registration to do business) in many states, though thresholds and outcomes vary. It's a separate analysis from payroll — flag it with your tax advisor whenever you enter a new state.

What about employees who want to work abroad for a few months?

International remote work adds foreign payroll, treaty, and permanent-establishment questions that dwarf state issues — get specific advice before approving it. Domestically, a temporary stint in another state may still trigger that state's rules depending on duration.

Can we just pay everyone as if they worked at HQ?

That's the most common — and most expensive — simplification. Wrong-state withholding means the employee owes their real state with penalties while chasing refunds from yours, SUI lands in the wrong fund, and unwinding it spans multiple agencies. Set each state up correctly once; it's cheaper in every scenario.

Reviewed by the WAYG tax team · Updated July 2026