Reference
What changes when you employ across state lines?
The short answer
Employment obligations follow where the work is physically performed, not where the company is headquartered or where payroll runs. One employee in a new state can trigger income tax withholding registration, unemployment insurance registration, workers’ compensation coverage, state-specific leave entitlements, required new-hire notices, and final-pay timing rules that differ sharply from your home state. None of it is difficult individually. All of it is expensive to retrofit after people have already been hired.
The rule underneath all of it
Obligations attach to the location of the work. Not the entity’s state of incorporation, not where the payroll system sits, not where the manager is. This sounds obvious and is routinely missed, because remote hiring makes it possible to acquire an obligation without anyone in the company noticing a decision was made.
The common pattern: an excellent candidate is hired in a state where the company has never employed anyone, the offer goes out, and the registration work begins afterwards — which means the first payroll runs before the accounts exist to file it against.
What a new state actually requires
Determine first whether the activity creates a filing obligation for the entity itself, not only for payroll. Then register with the state revenue department for income tax withholding and with the labor or workforce agency for unemployment insurance. Both take time, both have lead times that cannot be compressed by wanting them to be, and neither is reliably backdatable without penalty.
Confirm workers’ compensation coverage extends there. Many policies do not without an endorsement, and a few states will not accept a private policy at all, requiring participation in a state fund. Discovering that after an injury is the worst possible sequence.
Then the employment terms themselves
State-specific paid leave and sick leave accrual. Pay transparency obligations that attach to the job posting rather than the offer. Required new-hire notices. Final-pay timing rules, which differ sharply — some states require payment on the last day, others allow the next regular cycle, and getting it wrong carries penalties in several.
A national handbook that quietly contradicts local law is worse than no handbook, because it documents the wrong standard in writing. State addenda are the workable answer.
Where the exposure accumulates quietly
Local jurisdictions, not states, are the most common blind spot. Municipal sick leave ordinances, local income taxes, and predictive scheduling rules apply by work location and change on their own timetable. A company tracking obligations at state level will miss all of them.
Employees who move without telling anyone are the second. Someone relocates, updates their address in a self-service portal, and nobody treats it as a compliance event. Withholding continues to the old state, and the correction is retroactive.
Doing it in the right order
Registration before the offer, wherever the timeline permits. Where it does not, register the moment the offer is accepted rather than the moment payroll fails. Build a standing checklist per state rather than solving each expansion from first principles, and treat an address change as a trigger for it.
Done deliberately, a new state takes a few weeks of unglamorous preparation and then stops being a topic. Done reactively, it produces penalty notices, amended filings, and an employee whose first month was spent on payroll problems that were not their fault.
| Obligation | Lead time | Retrofit cost if missed |
|---|---|---|
| Income tax withholding registration | Days to weeks | Penalties and amended filings |
| Unemployment insurance registration | Weeks | Back contributions and penalties |
| Workers’ compensation coverage | Days, or longer in fund states | Severe if a claim arises |
| State leave and sick accrual | Immediate | Retroactive accrual |
| Pay transparency in the posting | Before posting | Penalties in several states |
| New-hire notices | At hire | Documentation gap in a dispute |
| Final-pay timing rules | At termination | Statutory penalties |
| Local ordinances | Varies | Frequently missed entirely |
Common questions
Does one remote employee really trigger all of this?
Does a PEO remove this problem?
What about employees who work in two states?
How do we find gaps we already have?
Where this sits
This page supports Compliance — the practice that does this work.

