Table of Contents
Most companies cross their first state line with confidence. They found the right candidate, extended an offer, and assumed the hard part was over. It rarely is.
The moment someone starts working for you in a state where your business hasn’t operated before, a clock starts. Tax accounts need to be opened. Workers’ compensation coverage has to extend to that location. New hire reports go to a different agency on a different deadline. Wage rules that applied in your home state may not apply there at all. None of that waits for a convenient time, and most of it has to be in order before the first paycheck goes out. Miss enough of it, and you’re not dealing with a paperwork backlog. You’re looking at backdated penalties, audit exposure, and back-pay corrections that tend to grow well past whatever the original oversight was.
We see this regularly at WorkSmart. Across 47 states and hundreds of client companies, the problem is rarely carelessness. It’s an assumption. Someone assumes that what they set up in Indiana carries over to the next state, or that compliance can be sorted out once the person is onboarded. That’s precisely where multi-state hiring compliance breaks down, and where most of the real risk starts to build.
Here are five places where those assumptions go wrong most often.
1. Treating Your Home State's Rules as the Default
Most multi-state compliance problems start the same way: someone assumes that federal regulations cover everything, or that their current payroll setup will stretch cleanly into a new state without any additional steps.
Federal law sets a floor. Individual states go well above it, and not uniformly. The minimum wage in one state might be several dollars higher than the next. Overtime rules that seem straightforward under federal law get modified by state formulas. Paid leave requirements that exist in California or Massachusetts don’t exist in Indiana at all. Break and meal period rules are written very differently depending on where the work is done. None of this is trivial variation. In practice, it can mean rebuilding how you calculate compensation for a single employee in a single location.
The thing that catches employers off guard most often is simpler than all of that. Payroll obligations follow the employee, not the company’s location. If someone is doing the job from Colorado, Colorado’s rules apply to them. Doesn’t matter that your office, your bank, and your payroll provider are all in Indianapolis.
That gets more complicated when an employee moves. Say someone works the first half of the year in Indiana, then relocates to Illinois in July. Your withholding obligations shift the day they move. Many payroll systems don’t pick that up unless someone manually updates the record. If nobody catches it, you keep withholding for Indiana while the employee quietly builds a tax liability in Illinois, and states can look back three to five years when they audit. One missed relocation isn’t a small problem.
When companies hiring employees in different states treat federal law as the full picture, every decision that follows gets built on a shaky foundation. Classification, payroll setup, and notice requirements: all inherit the same flawed starting point.
2. Skipping State Business Registration Before the First Payroll Runs
Knowing that another state’s rules apply is one part of the problem. Getting the actual registrations done before the first paycheck goes out is where many companies fall short, and the gap between those two is where penalties start.
Hiring your first employee in a state where you’ve never operated typically requires registering as a foreign entity doing business there. On top of that, one employee immediately creates obligations across multiple state agencies: a withholding account for state income tax, an unemployment insurance account, workers’ compensation coverage for that location, and new-hire reporting to the state agency that handles it. Most states want that report within 20 days of the hire. Some want it sooner.
Where companies run into trouble isn’t usually ignorance of any of that. It’s sequencing. Registration gets treated as something that can happen in parallel with onboarding, or after the fact. But a paycheck can’t be processed correctly without the account numbers those registrations produce. Run payroll before you have them and you’ve got withholding errors baked in from the start, errors that cost considerably more to unwind than they would have cost to prevent.
Worth flagging specifically: if you post a remote role without locking down geography and your new hire turns out to be in a state you’ve never operated in, the registration clock starts the moment they begin work. States have gotten much better at identifying payroll activity without a corresponding registration. When that gap surfaces, it rarely comes up alone. It tends to pull up a broader review of records going back several years.
For companies working through hiring employees across state lines requirements for the first time, building a 45-to-60-day window before a new hire’s start date isn’t being overcautious. It’s the only realistic timeline that gives registration, payroll configuration, and notice setup enough room to land without your first payroll running on holes you haven’t closed yet.
3. Getting Employee Classification Wrong for That State
Getting registered in a state gets your business through the door. Whether the people working for you are actually being treated correctly under that state’s law is a different question, and the federal and state answers don’t always match. Misreading where those obligations start is one of the most common errors multi-state employers make.
Under federal rules, the IRS uses a multi-factor test to sort contractors from employees. Many states use a stricter one. California’s ABC test flips the default assumption: workers are presumed to be employees unless the company can prove otherwise across three specific criteria. New Jersey applies similar logic. So a worker your company is treating as a 1099 independent contractor may already be a W-2 employee in the eyes of the state they’re working from, regardless of what your agreement says.
This comes up most often when companies hire remote employees in another state and use contractor arrangements that worked fine at home without checking whether those arrangements hold up under the new state’s rules. When they don’t, the liability goes back to day one: unpaid payroll taxes, unemployment insurance contributions, workers’ compensation, wage-violation exposure. Both the employer and employee portions of payroll taxes are included. Plus interest. Plus penalties.
And it’s not just long-running relationships at risk. If a contractor’s day-to-day work starts looking enough like employment that the state would call it that, the determination can reach back to when the engagement started. By the time a state labor department looks at it, the unpaid obligations have often been piling up for a year or more.
Before bringing anyone on as a contractor across state lines, the question isn’t whether the arrangement worked somewhere else. It’s whether it would survive scrutiny under the specific rules of the state they’re working from. If you don’t know that answer going in, the liability of finding out later comes with it.
4. Running Payroll Before the Setup Matches the State
Getting classification right is one layer. Actually paying and reporting for that person correctly under state law is another, and in multi-state hiring those two things don’t take care of each other automatically.
State payroll tax registration isn’t transferable from one state to another. Each state with an income tax requires its own withholding account, its own remittance schedule, its own filing procedures. Unemployment insurance rates get assigned to your specific employer account based on your industry and claims history in that state, not what you’ve got elsewhere. Workers’ compensation policies need to be updated to specifically cover the new location. Some counties and cities stack local income tax on top of all of that.
Run payroll before the setup is in place, and you’re either withholding nothing or sending money to the wrong place. The employee ends up with a tax bill they weren’t expecting at filing. You end up with penalties for missed or late deposits, calculated as a percentage of the unpaid amount per pay period, and those penalties stack up faster than most employers expect across multiple cycles.
One situation that bites companies particularly hard: adding a remote employee in a state where you already have people, but where the state has quietly updated its tax rates or contribution requirements since you last checked. The payroll system runs on whatever was configured last time. It won’t flag the change on its own. You can be running payroll correctly for years in a given state and still have it go wrong because no one reviewed the setup when the rules shifted.
Employees who travel for work or do temporary projects in other states add another wrinkle. Most states have de minimis thresholds before withholding obligations kick in, typically in the 10-to-30-day range, but those thresholds vary and are not all clearly published. An employee on a two-month project at a location your company has never tracked may create an obligation your payroll system has no mechanism to detect unless someone is actively monitoring work locations. That’s one of the reasons multi-state hiring compliance for remote workers can’t be treated as a one-time setup problem.
Payroll compliance across multiple states is maintenance work. When withholding errors go undetected long enough, they don’t usually get found internally. They show up when an employee files their state return, spots the mismatch, and files a complaint.
5. Overlooking State-Specific Notice and Posting Requirements
Payroll errors make noise fast. A check is wrong, a filing bounces, someone calls. Notice and posting failures are quieter. They sit in the background until something goes wrong, and by then the documentation gap is already part of the record. A structured HR compliance checklist that accounts for state-specific notice requirements is one of the more practical ways to stay up to date as those rules shift.
Every state requires employers to deliver certain notices to employees, and most require specific workplace postings, too. What varies dramatically is which ones, in what form, and when. Some states require a written wage notice at the time of hire that spells out the pay rate, pay frequency, and the employer’s legal name. Some require sick leave disclosures. Others require anti-harassment notices delivered directly to each employee at the start of employment, not just hung somewhere in the office. Skipping any of these doesn’t just create fine exposure. It gives up one of your main defenses if a wage claim or workers’ compensation dispute ever comes up. An employer who can’t produce a required wage notice from the hire date loses a lot of ground when a former employee’s version of events is the only one documented.
Pay transparency laws complicate this further because they reach into the hiring process itself, before anyone is technically an employee. Several states now require salary ranges to appear in job postings, and some of those laws apply to any posting that’s visible to residents of that state, not only ones explicitly targeting local candidates. Post a role publicly without geography restrictions, and a listing visible in Colorado or New York may trigger disclosure requirements you weren’t tracking. That’s a compliance obligation that starts before the first interview.
What makes this harder to manage than registration or payroll is the pace at which the rules change. Oregon added payroll practice disclosure requirements for new hires in January 2026. Washington stepped up enforcement of prevailing wage requirements at the same time. A state that had no relevant mandate two years ago might have one now, and there’s no automated notification when that happens. Registration gaps tend to surface quickly because payroll breaks. Notice gaps can sit quietly for years, showing up only when a claim is filed, and the document that was supposed to exist isn’t in the file.
What These Mistakes Have in Common
A 2026 survey of HR, payroll, and business professionals found that 25% of multi-state employers had paid a penalty or fine for state employment compliance in the past two years. Nearly 24% missed a registration, filing, or reporting deadline. Roughly 25% said a government audit would be the most damaging thing that could happen to their organization. Those aren’t outlier numbers.
In most of those cases, nobody was trying to cut corners. The hire got made, the start date landed, and the underlying setup either kept pace or it didn’t. Companies behind those numbers were growing fast, running on assumptions that had worked before, and didn’t find out those assumptions had a problem until a state agency pointed it out.
Audits rank so high on that list because they don’t stay contained. A registration gap pulls in a review of related filings. A withholding error in one period means a look at the others. The original mistake is just the starting point for what gets scrutinized. And beyond the financial side, compliance gaps have a measurable effect on employee retention that most companies don’t connect to the compliance failure until well after the fact.
Growing businesses in Indiana and across the Midwest tend to run into this from both directions. Operations spread across multiple states, but the internal HR capacity to manage that scope doesn’t always expand at the same pace. The obligations that fall through that gap don’t announce themselves. A state agency is usually the first to find them.
Every one of these mistakes is easier to prevent than to fix. Getting the structure right before the first hire in a new state costs a fraction of what it takes to untangle things after payroll runs incorrectly, a classification is challenged, or a required notice is missing from a file.
WorkSmart Systems has worked alongside small and mid-sized businesses operating across 47 states since 1998. As a certified PEO (CPEO), we handle state registrations, payroll tax setup, workers’ compensation compliance, notice requirements, and ongoing monitoring so the infrastructure keeps pace with your growth. The companies that hire across state lines without incident aren’t the ones with the biggest HR teams. They’re the ones with a process built to handle it before problems had a chance to develop.
If your company is preparing to hire in a new state, or you’ve already hired and want to know where you actually stand, act now rather than wait for a notice to tell you. Every week a compliance gap goes unaddressed is another week it qualifies for a longer lookback. The companies that come to us after a penalty notice almost always say the same thing: they knew something wasn’t set up right, but figured it could wait.
Talk to the WorkSmart team before your next out-of-state hire.
FAQs
What do employers need to do before hiring in another state?
More than most people expect. At minimum: register the business as a foreign entity in that state, open a state income tax withholding account, set up state unemployment insurance, confirm your workers’ compensation policy actually covers that location, and report the new hire to the state agency. Most states give you 20 days to file that report, and some want it faster. The piece employers routinely underestimate is timing. These aren’t tasks you complete during onboarding. They need to be finished before the first paycheck runs. Building a 45-to-60-day window before the start date is the only way to avoid gaps.
Do I need to register my business in another state just to hire one employee?
Almost certainly yes, especially if it’s a full-time permanent role. One employee is typically enough for a state to say your business has a presence there, which triggers registration and the tax accounts that go with it. People sometimes assume they can quietly run payroll for a while and deal with registration later. That tends to go badly. States are much better now at cross-referencing payroll filings with registered entities, and when they find the gap, they don’t just ask you to register. They open a broader review.
What taxes does an employer pay for an out-of-state employee?
The taxes follow the employee’s work location, not your company’s address. That means state unemployment insurance in whatever state they’re working from, state income tax withholding sent to that state’s revenue agency, workers’ compensation premiums for that location, and local taxes if the county or city levies them. Your federal obligations, meaning Social Security, Medicare, and FUTA, stay the same no matter where anyone works. What changes is everything sitting on top of those.
What happens if an employee moves to a different state mid-year?
Your withholding obligation changes the day they move, not when you find out about it. From that point forward, you’re supposed to be withholding for the new state and registered to do so. If the move slips through undetected and you keep remitting to the old state, the employee ends up with a tax liability they weren’t expecting, and you’ve been filing to the wrong jurisdiction the whole time. Neither of those is a quick fix. Both come with penalties, and the employee often finds out when their state tax return doesn’t add up.
What happens if I run payroll in a new state without completing registrations first?
Practically speaking, your payroll system processes the check but handles the tax piece incorrectly. Either nothing gets withheld, or it goes somewhere it shouldn’t. Down the road, the employee gets a surprise when they file their state taxes. You get penalty notices for late or missing deposits, calculated as a percentage of what was owed for each pay period it was late or missing. Then there’s the audit risk. States look back several years when reviewing payroll compliance, so one pay period of errors doesn’t stay one pay period.
How often do state employment compliance requirements change?
Constantly, and without much warning. Minimum wage rates, paid leave rules, pay transparency requirements, unemployment insurance contribution rates, and notice obligations: all of these move on schedules that vary by state and don’t coordinate with each other. Some states update annually. Some change mid-year. Some pass legislation that takes effect 90 days later with no centralized notice to employers. If your business has people in multiple states, you need someone or something actively tracking them, not just reviewing it when a problem arises.
Is there a compliance checklist for hiring remote employees in another state?
Yes, though “checklist” can be misleading if it implies you do it once and move on. The setup checklist covers six things: foreign entity registration, state income tax withholding account, unemployment insurance registration, workers’ compensation coverage for that location, new hire report filed with the state agency, and required new hire notices delivered to the employee. That gets you to a compliant first paycheck. What the checklist doesn’t capture is the ongoing piece: tax rate changes, updated notice requirements, and employees shifting where they actually work. Getting the first hire right and then failing to maintain the setup is one of the more common ways companies end up back in the same problem a year later.
What's the difference between a W-2 employee and an independent contractor for multi-state purposes?
The honest answer is that it depends on which state you’re asking. Federal classification rules and state classification rules don’t always land on the same answer. A contractor relationship that’s clean under IRS guidelines may not hold up under California’s ABC test or New Jersey’s similar framework, both of which assume someone is an employee and require the company to prove otherwise. If the state decides the person was misclassified, the liability isn’t just limited to the future. It goes back to the start of the engagement and covers unpaid payroll taxes, unemployment insurance, workers’ compensation contributions, and any wage claims attached to it.