Share
The moment you hire someone who lives in a different state than your business — or send an employee to work temporarily in another state — you’ve entered multi-state payroll territory. It doesn’t matter if it’s one employee or one hundred. The filing requirements, tax registrations, and withholding rules apply regardless of how many people trigger them.
For most mid-size employers, multi-state payroll complexity grows faster than headcount. A hospitality company that opens a second property in a neighboring state. A healthcare group that acquires a clinic 200 miles away. A manufacturer that hires a remote sales rep who works from home in a state where you have no physical presence. Each scenario creates a distinct set of compliance obligations that most payroll teams weren’t trained to handle when they first came up.
Where Employees Work vs. Where They Live: The Residency Rule
Most states follow the same basic principle: employees pay income tax in the state where they perform the work. If your employee drives to your Georgia facility every day, they owe Georgia income tax on those wages. That’s the work-state rule.
But most states also tax their residents on all income earned anywhere. So if that employee lives in South Carolina and commutes to Georgia, South Carolina also wants a piece. The employee owes income tax in both states — and you, as the employer, need to withhold for both.
The saving grace is the resident credit. Most states allow residents to claim a credit for taxes paid to another state, which prevents actual double taxation for the employee. But it doesn’t eliminate the employer’s withholding obligation. You still need to register in both states, run withholding calculations under both state tax tables, and file returns in both. The credit is the employee’s problem to claim on their personal return — not something you handle on the payroll side.
Reciprocity Agreements: Where They Help and Where They Don’t
Some states have reciprocity agreements that simplify things. Under a reciprocity agreement, employees who live in one state and work in another only pay income tax in their state of residence — not the work state. The employee files a non-resident exemption certificate with you, and you withhold only for their home state.
Reciprocity agreements sound great. The problem is that not many states have them, and they only apply between specific pairs of states. Pennsylvania has reciprocity with several neighboring states. Illinois has reciprocity with Iowa, Kentucky, Michigan, and Wisconsin. But most state pairs — including many common commuter corridors — have no agreement at all. Don’t assume reciprocity applies without checking the specific state combination.
A second issue: reciprocity agreements can end. When New Jersey terminated its reciprocity agreement with Pennsylvania in 2017 (it was later reinstated), employers with cross-border employees had to immediately set up dual-state withholding on short notice. Reciprocity is a convenience, not a permanent feature of the tax code.
State Tax Registration: What You Have to Do Before the First Paycheck
Before you can withhold state income tax for an employee working in a new state, you need a state withholding account. Before you can pay state unemployment insurance on their wages, you need a state UI account. Both require separate registrations with separate state agencies — and the timelines vary. Some states complete registrations in days. Others take weeks.
This is the part that catches employers off guard. You hire a remote employee in a new state. They start work. You need to pay them in two weeks. But your state registration isn’t complete yet. Running payroll without the account number isn’t technically possible in most payroll systems — and running it anyway and fixing the registration later creates filing complications that can trigger penalty notices months down the road.
The fix is straightforward: start the registration process as soon as you know an employee will be working in a new state, not after they’re already on the payroll. For remote hires, that means starting registration concurrent with extending the offer, not after their first day.
Temporary Work Travel: The Rule Most Companies Miss
If you send employees to work temporarily in another state — for a project, a job site, a training, a conference — you may trigger that state’s payroll tax obligations even if the stay is brief. Most states use a threshold of some kind: a number of days worked in the state, or a dollar amount of wages earned there, before withholding requirements kick in. The problem is that thresholds vary widely and change often.
Some states have no de minimis threshold at all — one day of work creates a filing obligation. Others set a 14-day or 30-day threshold before withholding is required. Without tracking which employees travel where and for how long, it’s almost impossible to know when you’ve crossed into obligation territory. For companies with field employees, traveling sales teams, or technicians who move between states regularly, this is an active compliance risk that most payroll teams aren’t tracking.
Unemployment Insurance in Multi-State Situations
State unemployment insurance adds another layer. The general rule is that UI is paid to one state per employee — the state where the employee is “base state” under a four-part localization test. If the employee performs most of their work in one state, that state gets the UI. If they’re truly mobile across multiple states, you apply the test in order: where is most work performed, where is the base of operations, where is direction and control exercised, where does the employee live.
For employees who are clearly based in one state, this isn’t complicated. For regional managers, traveling technicians, or employees who split time fairly evenly across states, the analysis takes real thought — and the answer affects UI rate experience in the state you choose. Getting it wrong doesn’t just create a filing problem; it can affect your experience rating and future UI tax rates in states where you’ve been over- or under-contributing.
How Netchex Handles Multi-State Payroll
Multi-state payroll is one of the areas where a capable payroll platform makes the most difference. Netchex handles state and local tax calculations across all active states, manages multiple withholding accounts within a single payroll run, and keeps up with rate and rule changes so your team doesn’t have to. When you add an employee in a new state, the system flags the registration requirement and helps you set up the account before the first payroll processes.
For employers expanding into new states or managing distributed remote workforces, that kind of built-in compliance infrastructure is the difference between multi-state payroll being a manageable process and a quarterly fire drill. Talk to a Netchex consultant about your specific state footprint.
Frequently Asked Questions
Yes. If an employee performs work in a state — including working remotely from their home — you typically have nexus in that state and must register for state income tax withholding and state unemployment insurance. The fact that your company has no physical office there doesn’t matter. What matters is where the work is performed. Some states have de minimis thresholds before registration is required, but most require registration as soon as you have an employee working there.
If a reciprocity agreement exists between your employee’s work state and home state, and the employee files the appropriate exemption certificate with you, you withhold only for their home state — not the work state. This simplifies things significantly. However, reciprocity agreements exist only between specific state pairs, not universally. Always verify whether a specific pair of states has an active agreement before applying this treatment, and watch for changes — agreements can be suspended or terminated.
Running payroll without a valid state account number creates complications when it’s time to file quarterly returns and remit taxes. The state has no account to apply payments to, which can result in penalty notices, interest, and a messy correction process. The right approach is to start the registration immediately when you know an employee will work in a new state — before their first payroll run, not after. For remote hires, start the process concurrent with extending the offer.
UI goes to one state per employee, determined by a four-part localization test: first, where most work is performed; second, where the employee’s base of operations is; third, where direction and control comes from; fourth, where the employee lives. Apply the test in order and stop at the first factor that clearly applies. For employees who are genuinely mobile across multiple states without a clear base, document your analysis carefully — the state you choose affects both your filing obligations and your future UI experience rating.
Managing Payroll Across Multiple States?
See how Netchex handles multi-state tax calculations, registrations, and compliance across your full workforce in a single payroll run.
This guide reflects publicly available product information and independent reviewer data (G2, Capterra, Trustpilot, Yelp, Better Business Bureau, Reddit, Software Advice, GetApp) as of 2026. Feature availability and pricing may vary by plan. Contact each provider for current details.
Disclaimer: Any product roadmap or future plans provided herein are for informational purposes only. They do not represent a commitment to deliver any material, code, feature, or functionality. Plans may change without notification. The development, release and timing of any features or functionality described remain at the sole discretion of Netchex, its affiliates, and partners. Netchex does not give legal, tax, or accounting advice. You are responsible for ensuring your use of Netchex product meets your individual business and compliance requirements.
Related events
Best Patriot Software Alternatives for HR & Payroll
Netchex vs isolved: Payroll & HR Comparison
Netchex vs OnPay: Payroll & HR Comparison