Which State Do You Withhold Payroll Taxes For When an Employee Works and Lives in Different States?
Updated: 3 days ago
Hiring a remote employee in another state feels like a simple staffing decision. Operationally it can trigger withholding registrations, unemployment accounts, and filing obligations your payroll software never set up. Most businesses find out when the notices arrive. Here is what actually happens when you hire remotely, and how to get registered before that happens.
The hiring process usually feels simple. A manager finds great talent, the person lives in another state, HR completes onboarding, payroll adds the employee, and everyone moves forward feeling successful. Then something changes: a state agency requests payroll filings, an unemployment notice appears, withholding accounts cannot be located, or the provider asks for registrations that were never completed. A routine remote hire has become a multi-state payroll registration problem.
This is one of the most common operational issues growing businesses face, and it almost always starts with a normal decision: we hired someone remotely. The mechanics of what that hire sets in motion are worth understanding before the notices arrive, because the whole chain is preventable at the point of hire, with the right registrations in place before the first payroll run.
Does Hiring One Remote Employee Really Create New Payroll Obligations?
Yes. Many employers assume payroll obligations only change when they open an office or expand physically. Remote work changed that. A single employee working in another state may create state withholding registration, unemployment tax registration, payroll filings, labor agency requirements, local payroll obligations, and employer account setup.
The business does not need a building or office in the state; employee activity alone can create the responsibilities, which is the concept of payroll nexus. Our post on what payroll nexus is covers it in full, but the practical point for a remote hire is that the new state generally expects you to be registered there before payroll runs, not after.
Why Does Remote Workforce Growth Outrun Compliance Processes?
Remote expansion tends to happen faster than internal systems can keep up. A company hires one remote employee, then another, then a regional manager, then support staff across several states, and within months it operates in three, five, or eight states while payroll procedures still reflect a single-state organization. That produces quiet operational gaps: HR focuses on onboarding, managers focus on hiring, payroll focuses on processing, and finance assumes everything was handled.
Meanwhile registrations may not exist, unemployment accounts may be missing, work locations may be inaccurate, and filings may never begin. Nobody catches it until an agency does. The failure is not neglect; it is that no single role owned the registration step when the remote hire happened.
Not Sure Which States You've Already Triggered? We compare where your remote employees actually work against where you're registered, and submit whatever's missing within 48 hours.
Does Payroll Software Handle Remote Employee Compliance Automatically?
This is where many businesses run into trouble. The assumption is that using payroll software means it is handled. But payroll processing and payroll registration are not the same thing. Payroll systems depend on employer-provided information: the employee's work state, registration accounts, unemployment setup, tax rates, and jurisdiction assignments.
If those were never completed, payroll still processes, employees receive direct deposit, and reports generate, while agencies may see an unregistered employer, missing filings, and inactive accounts. The software works correctly; the registrations behind it do not exist. Our companion post on whether payroll software handles remote employee compliance covers that boundary directly.
What Happens When a Remote Employee Relocates?
Remote compliance issues do not only happen at hiring. They happen after the employee already exists. Someone starts in one state, relocates to another six months later, HR updates the address, payroll keeps running, and nobody reviews whether a new registration is needed. The business may still be reporting to the old work state while the new state's withholding and unemployment registrations go completely unaddressed.
This happens constantly in remote-first companies, startups, consulting firms, healthcare organizations, and staffing businesses, and most employers do not discover it until a notice arrives. The root is a distinction many businesses miss: payroll obligations follow where the employee actually works, not the mailing address on file. That makes a relocation a registration event, not just an HR update, and it deserves the same setup as a new hire.
Why Do Remote Employee Problems Surface So Long After Hiring?
The timing is what creates the confusion. The hiring decision may happen months before any issue appears. Owners often say they hired that employee last year, which is exactly the point: agencies identify missing registrations, unfiled returns, unemployment discrepancies, and work-state inconsistencies on their own timeline, long after the hire. Payroll kept running and the registration gap stayed hidden until the agency responded. This delayed visibility is the same pattern our post on why payroll notices keep coming during growth traces from the notice side.
The most common mistakes behind all of this are consistent: hiring before completing registrations, assuming the provider establishes accounts automatically, missing unemployment setup, failing to register after a relocation, incorrect work-state configuration, relying entirely on software, and overlooking nexus.
So whenever a remote employee is added in a new state, the review to run is straightforward: employee location and work-state assignment, withholding registration, unemployment registration, payroll configuration, filing requirements, and notice monitoring, ideally before the first payroll run. Registering early is a flat, predictable cost. Registering after a notice is a cleanup project, and it is what keeps remote growth from quietly turning into remote exposure.
Already Found a Gap? Close It Before the Notice Does. Every state you're missing is a flat $475 registration, submitted within 48 hours, no ongoing retainer.
Final Thoughts: What Should You Do Before Your Next Remote Hire?
Aureus Advisory Partners helps businesses identify remote employee payroll obligations, register in the states where they actually operate, and build processes that keep each remote hire compliant across every state where employees work. We are not a payroll processor. We are a strategic payroll compliance advisory firm, and registration is the step a remote hire needs before it becomes a notice.
We compare where your remote employees actually work against where you are registered, submit whatever is missing within 48 hours, and enter the account numbers into your payroll system so the next pay run is clean, not the next notice.
Review where your remote team creates obligations, close the registration gaps, and get set up before your next payroll run.
Frequently Asked Questions
Does hiring a remote employee in another state create payroll tax obligations?
Often yes. A remote employee's work location can create withholding, unemployment, registration, and filing obligations in that state, even without a physical office there. Because obligations follow where the employee works, hiring remotely in a new state generally means new registration is required before payroll should run there.
2. Do remote employees create payroll nexus?
They can. An employee working in a state can create payroll nexus, meaning payroll tax obligations arise from their presence, without the employer having any office there. This is why a single remote hire can extend your registration requirements into a new state, and why remote hires warrant a registration check at onboarding.
Does payroll software automatically handle remote employee compliance?
Generally no. Payroll platforms process payroll from the work locations and account numbers you provide; they do not open your state registrations or unemployment accounts on their own. If that setup was never completed, the software keeps processing without it, which is why remote gaps stay hidden until a notice appears.
What happens if I added a remote employee without proper registration?
Payroll usually keeps running, so nothing looks wrong, while the missing registration quietly accrues exposure. Over time this can produce rejected filings, state notices, unemployment discrepancies, and eventually penalties. The good news is that these are usually manageable when the missing registration is submitted before a notice, not after.
Does a remote employee relocating create new obligations?
Yes. Because obligations follow where the employee works, a move to a new state can create withholding and unemployment registration requirements there, just like a new hire. Updating the address alone does not address it; the relocation should trigger a registration check, or payroll will keep running on the prior state's setup.
Get Set Up Before Your Next Payroll Run. We submit the registrations, load the account numbers into your payroll system, and you're clean for the next pay run, not chasing a notice after it.
