Hiring Remote Employees in Another State: What to Know
The question we hear most from employers moving fast on a great remote candidate is some version of "wait, do we need to do anything special because they live in a different state?" The honest answer to hiring remote employees in another state is yes — usually more than employers expect, and usually solvable, but not something to discover after the offer's already out. Our guide to hiring remote employees covers the full process; this page is the compliance layer specifically.
Hiring someone who lives and works in a different state than your business is registered in isn't illegal or unusual — it happens constantly. What changes is that the employee's state, not just yours, now has a legitimate claim on parts of the employment relationship: taxes get withheld differently, some labor protections follow the employee's location, and your business may owe registration or reporting it didn't owe before.
Why the employee's state matters, not just yours
The core shift to understand: employment law and payroll tax obligations generally follow where the work is actually performed, not where your company is headquartered. If your business is based in one state and you hire someone who works from home in another, that other state typically has a real claim on parts of the relationship — even though your office never moves.
This is a well-established area of regulation, not a remote-work-era gray zone. The U.S. Department of Labor and each state's own labor agency have long-standing rules about wage and hour law, workers' comp, and unemployment insurance tied to where employees actually work — remote hiring just means more employers are running into these rules for the first time.
We've seen this catch even careful employers off guard, because the trigger isn't revenue, headcount, or how long the arrangement lasts — it's simply that one person is doing the job from that state. A single remote hire in a new state can obligate a business the same way opening a small branch office would, just without the office.
State registration and payroll tax nexus, plainly
"Nexus" is the term that comes up constantly in this context, and it just means a sufficient connection to a state that triggers a tax or registration obligation there. Having one employee physically working from a state is often enough on its own to create payroll tax nexus, even if your business has no office, warehouse, or other presence there at all.
- You'll typically need to register your business with that state's tax agency for income tax withholding purposes before running payroll for someone working there.
- Most states also require registering with their unemployment insurance agency, and paying into it, once you have an employee working from that state.
- Some states have reciprocal agreements affecting where tax is withheld if an employee lives in one state and occasionally works in another — this gets more complex for employees who split time across states.
- None of this is optional or a courtesy step. Skipping registration doesn't remove the obligation; it just means the obligation is unmet, with penalties that accrue the longer it goes unaddressed.
If your business doesn't yet have an EIN or needs to confirm how it's structured for a new state's filings, the IRS — Employer ID Numbers is the starting reference for federal employer identification — state registration is a separate, additional step layered on top of your federal setup, not a replacement for it.
Widen the pool once the compliance basics are clear
Once you know which states you can realistically hire into, post the role free on Jobedly and let AI agents rank applicants from across that wider pool.
Post a job freeWhat actually changes across state lines
It helps to see the moving pieces side by side, because "compliance" as a single word hides how many genuinely separate systems are involved.
| Compliance area | What changes across states |
|---|---|
| Income tax withholding | Withholding rules, rates, and required state registration follow the employee's work state, not the employer's home state |
| Unemployment insurance | Employers generally register and pay into the state where the employee works, sometimes triggered by a single employee |
| Minimum wage and overtime | State (and sometimes city) minimum wage can exceed federal minimum wage, and overtime rules vary by state |
| Paid sick leave and leave laws | A growing number of states and cities mandate paid sick leave or other leave types the employer's home state may not require |
| Workers' compensation | Coverage requirements and carriers are typically state-specific, and out-of-state employees usually need coverage under that state's system |
| Final paycheck timing | States differ, sometimes significantly, on how quickly a final paycheck must be issued after termination or resignation |
| New-hire reporting | States require new-hire reports to a state agency, generally based on the employee's work location |
None of these are exotic edge cases — they're standard, well-documented parts of employment law in every state. The complexity isn't that any single rule is obscure; it's that hiring across several states means tracking several parallel sets of these rules at once instead of just one.
Multi-state payroll basics
Once you have employees working from more than one state, payroll itself gets meaningfully more involved — this is the part most first-time remote employers underestimate, because payroll "just working" in a single-state business hides how much of that simplicity was location-dependent.
- Confirm each employee's actual work state — this should be their physical work location, not their mailing address or where your company happens to be based.
- Register for income tax withholding and unemployment insurance in each state where you have an employee working, before running their first payroll.
- Use payroll software or a payroll provider that explicitly supports multi-state withholding — hand-calculating this correctly across several states is realistic for one or two employees and error-prone beyond that.
- Track each state's minimum wage, overtime, and leave requirements separately; defaulting to your home state's rules for everyone is a common and costly mistake.
- Set a calendar reminder to re-check requirements periodically — state rules change, and "we checked this once two years ago" is a common way multi-state employers drift out of compliance without noticing.
A practical approach before you extend the offer
You don't need to solve every state's employment law before hiring your first out-of-state remote employee — you need a short checklist run consistently every time a new state enters the picture.
- Confirm the employee's actual physical work state during the offer stage, not after they've started.
- Check whether your payroll provider already supports that state, or what it takes to add it, before the start date, not the week of the first paycheck.
- Register for state income tax withholding and unemployment insurance in that state ahead of the first payroll run.
- Confirm workers' comp coverage extends to that state, or obtain coverage that does.
- Note that state's minimum wage, overtime, and leave requirements specifically, and apply them rather than defaulting to your home state's rules.
- When genuinely unsure, get a short paid consultation with an accountant or employment attorney rather than guessing — the cost of getting this wrong compounds quietly over time in ways a one-time consultation fee doesn't.
A reasonable way to think about scope: the first out-of-state hire is the hardest one, because you're setting up processes from zero. The second and third in the same state are easy — the registration and payroll setup already exist. It's each new state, not each new employee, that adds real one-time work, which is worth knowing before you assume hiring remotely across five states is five times the effort of hiring across one.
Getting the compliance basics right doesn't need to slow down the actual hiring. Once you know which states you can realistically support, the sourcing and interview side of remote hiring — covered in our pages on assessing remote readiness and interviewing remote candidates — can move at full speed against a wider, cross-state applicant pool.
Post once. Let the AI agents do the sorting.
Post a job free on Jobedly and our AI agents surface and rank qualified candidates 0–100 so you spend time on the shortlist, not the pile.
Post a job freeFrequently asked questions
Do I have to register my business in every state where I have a remote employee?
Which state's labor laws apply to a remote employee — mine or theirs?
What is payroll tax nexus?
Can I just apply my home state's payroll rules to an out-of-state remote employee?
Do I need a local address or office to hire someone in another state?
Is this page legal or tax advice?
Glossary
- Payroll tax nexus
- A sufficient connection to a state, often triggered by a single employee physically working there, that creates a tax registration and withholding obligation in that state.
- Unemployment insurance registration
- The process of registering with a state's unemployment agency and paying into its system, generally required once an employer has an employee working in that state.
- New-hire reporting
- A state-mandated report employers must file when hiring a new employee, generally based on the employee's work location.
- Multi-state payroll
- Payroll processing that accounts for different tax withholding, minimum wage, overtime, and leave rules across two or more states at once.
- Work state
- The state where an employee physically performs their job, which generally determines which state's employment laws and tax rules apply, regardless of the employer's home state.