Rule one: income tax follows the work (mostly)
The default principle: wages are taxable where the work is physically performed. An employee who lives in South Carolina and works your North Carolina jobsites owes NC tax on those days' wages, and you, the employer, are the one expected to withhold it. The employee's home state generally taxes everything too, then credits taxes paid to the work state, so the worker isn't double-taxed, but the employer's withholding obligation runs to the work state first.
- Reciprocity agreements simplify some borders: pairs of states (heavily in the Midwest and mid-Atlantic) agree to tax only residence, an employee files one certificate and you withhold for their home state only. Know whether your border has one; it changes everything
- Thresholds vary wildly: some states tax from day one of work performed there; others waive withholding under a day-count or dollar floor. A crew doing two days across the line may or may not trigger obligations depending on which line
- No-income-tax states (TN, TX, FL, NV, WA and friends) remove the withholding question in that direction, but not unemployment, and not the reverse direction
Rule two: unemployment goes to ONE state, the four-factor test
Unlike income tax, SUI (state unemployment insurance) is paid to exactly one state per employee, chosen by a uniform cascade every state uses: (1) where is the work localized, mostly performed, with out-of-state work incidental? If that answers it, done. If not, (2) where's the employee's base of operations? Then (3) where's the place of direction and control? Then (4) where does the employee live? For a Charlotte-based crew doing occasional SC jobs, the work is localized in NC, all SUI goes to NC, even for SC job days. Getting this wrong in either direction (paying two states, or the wrong one) is common and fixable, but it unravels quarterly filings.
Rule three: workers' comp wants coverage where the work happens
Comp policies list covered states, work performed in a state not on the policy can mean an uncovered injury, which is the catastrophic version of this topic. Crews that regularly cross a line need that state added ('3A' coverage in policy terms) before the first job, not after the first claim. Monopolistic states (Ohio, Washington, Wyoming, North Dakota) run state funds and need their own arrangements.
The registration cascade nobody warns you about
The first employee regularly working in a new state typically triggers, in order: state withholding registration, possibly SUI registration (if the four-factor test lands there for anyone), comp coverage, and, the one that surprises, local layers where they exist (municipal income taxes in Ohio and Pennsylvania, occupational taxes in Kentucky, and similar). Remote employees are the same event: hiring a work-from-home admin in another state is 'expanding to' that state, payroll-wise, on day one. (The single-state baseline setup: Hiring Your First Employee: The Payroll Setup Checklist .)
What this looks like for real businesses
- Charlotte trades company with Fort Mill SC jobs: NC and SC withholding by workday (no reciprocity on that border), SUI stays NC under localization, SC added to the comp policy. Routine once set up; a mess retroactively
- Kansas City anything: the state line runs through the metro. MO/KS withholding by workday plus KC's earnings tax is Tuesday, not an edge case
- Trucking: interstate drivers get special treatment, federal law (the Amtrak Act) taxes an interstate driver's wages only in their state of residence, a rare mercy that most non-trucking payroll people have never heard of
- The DC metro: DC, MD, and VA reciprocity means residence-state withholding for most, one of the places the simple answer is actually simple
Keeping it clean without a compliance department
The system that works at small scale: track work location per employee per day (field software or timesheets already know), configure payroll software with every active state, the software calculates once told, but only if told, and calendar the quarterly filings per state. Or hand the whole layer to whoever runs your books and payroll together, which is our pitch exactly: multi-state setup, day-count tracking, and filings as part of the monthly rhythm. Payroll Administration for Small Businesses
Frequently asked questions
We did cross-border work for two years without registering. How bad?
Usually fixable at the cost of some back filings and modest penalties, states are notably gentler with voluntary registrations than with discovered ones (a worker's unemployment claim being the usual discovery). Clean it up before it finds you; the exposure only grows.
Does one day across the line really trigger all this?
Sometimes technically yes, practically it depends on the state's thresholds and enforcement posture. The honest framework: occasional single days are a risk judgment; recurring work is an obligation. When a border becomes part of your service area, register.
Primary sources