Table of Contents
Hiring someone in another state feels like a straightforward win. You found the right person, they accepted the offer, and your team gets stronger. What most employers do not think about at that moment is that adding a worker in a new state is, from a legal standpoint, a bit like opening a branch office there. The obligations follow the employee, not the employer’s address.
Indiana businesses have been running into this more and more. Remote work made geography feel less relevant to hiring decisions, and in many ways it is. But expanding your team geographically brings a layer of legal responsibility that most growing companies are not fully prepared for. Payroll setup, tax registrations, leave laws, workers’ compensation, and employee classification all look different depending on which state your people work in, and those differences are not always obvious until an audit or a complaint makes them impossible to ignore.
This is what employers most commonly overlook, and where the real exposure tends to build.
Payroll Is More Complicated Than It Looks
Payroll is where most multi-state compliance issues begin. It is also the area where penalties accumulate the fastest, because the clock starts on registration requirements the moment an employee begins working in a new state.
Every state where you have employees working generally requires its own payroll tax registration and its own unemployment insurance account. Some states have city or county income taxes layered on top of that. Ohio alone has several hundred local taxing jurisdictions, each with its own rates and deadlines. Pennsylvania is similar.
An Indiana employer who expands into either of those states and runs payroll the same way they always have is likely mishandling withholding from week one. The IRS and state departments of revenue offer little flexibility for late registrations or underwithholding. Penalties accumulate, and they do so faster than most employers expect.
Then there is nexus. Once you have a worker physically located in another state, even a single remote employee working from home, you typically have a taxable presence there. That can trigger state business tax registration requirements on top of payroll, which catches many employers off guard.
Getting the payroll structure right for employees in new states must happen before the first paycheck is issued. The cost of fixing it after the fact, in time and penalties, is almost always higher than doing it correctly from the start.
Wage and Hour Laws Vary by State
The Fair Labor Standards Act, enforced by the U.S. Department of Labor, establishes federal minimum wage and overtime requirements. Many employers treat those federal standards as the full picture. Most states have their own wage and hour laws, and many set the bar considerably higher.
Minimum wage is the obvious example. Several states now have minimums above $16 per hour, and some local governments have pushed rates even higher than the state level. An Indiana employer who brings on employees outside their home state and pays them at Indiana’s rate is out of compliance before the first week is over.
Overtime rules are less obvious but equally important. Federal law triggers overtime after 40 hours in a workweek. California triggers it after 8 hours in a single day. If your time tracking is built around a weekly calculation and you have California-based employees, you are likely underpaying overtime without realizing it. That kind of gap tends to surface during audits, not internal reviews.
Meal and rest breaks are another area where states diverge sharply. Some mandate paid rest periods at specific intervals. Others require unpaid meal breaks after a certain number of hours. A few defer entirely to federal guidance. Managing employees in multiple states means a single attendance and break policy probably does not hold up everywhere. State-by-state wage and hour compliance is the kind of thing that reads like a minor administrative issue until it becomes a formal wage claim.
Paid Leave Laws Are Not Consistent Across States
Not long ago, paid sick leave was a benefit employers offered on their own terms or not at all. That has changed. More than a dozen states now require it, and the rules vary from one state to another.
Accrual rates differ. Eligible uses differ. Some states allow employees to carry over their full balance from year to year. Others cap it. Oregon, Colorado, California, and several others mandate paid sick leave for any employee working in those states, regardless of where the employer is based. If your team spans several of these states, you are managing different sick leave obligations in each jurisdiction.
Paid family and medical leave is a separate layer on top of that. States including Washington, Connecticut, Oregon, and Colorado have built their own funded programs, independent of the federal Family and Medical Leave Act. Each program requires employer and employee payroll contributions, plus its own state agency registration. Missing those registrations creates liability that compounds quietly over time.
Most HR teams at growing companies underestimate both how many states have these requirements and how often they change. Offering one generous leave policy that clears every state’s minimum is one approach, but it only works reliably if someone is actively tracking what those minimums are.
Workers' Comp Does Not Follow Your Employees
Workers’ compensation is state-administered. There is no federal program covering private employers nationwide, and each state sets its own coverage requirements, benefit levels, and approved carriers.
An Indiana employer relying on an Indiana-only policy for employees working in Illinois or Texas has a real coverage gap. If one of those employees is injured on the job, the employer may face direct liability for those costs, as well as penalties for failing to carry the required coverage in that state. It is a scenario that surfaces when claims are filed, not something that gets flagged in advance.
A few states, including Ohio and Washington, require employers to purchase workers’ compensation through a state-run fund rather than a private insurer. Rates and reporting requirements also differ, so even employers with coverage need to confirm that it is structured correctly for each location where their people work.
Contractor Rules Change State to State
Independent contractor arrangements are already one of the higher-risk areas in employment law. Bring on workers outside your home state and that risk increases, because each state gets to apply its own classification rules.
Different states use different tests to determine whether a worker qualifies as an independent contractor. California’s AB5 law uses a strict ABC test. Other states have their own frameworks. Indiana’s standard does not mirror California’s, and an arrangement that holds up under Indiana law may not survive scrutiny in another state.
Misclassification consequences can include back payroll taxes, penalties, unpaid benefits liability, and workers’ compensation exposure. Employers using contractors across multiple states need to evaluate those arrangements under each state’s rules, not once at the company level. Most do not, which is why misclassification shows up so frequently when multi-state operations face audits.
Your Employee Handbook Probably Has Gaps
A handbook written for Indiana employees covers Indiana requirements. The moment you have people working in other states, some of what is in that document may not apply to them, and things that should be there for them likely are not.
Final paycheck timing is a clear example. Indiana allows employers until the next regular payday to issue a final paycheck after someone leaves. California requires it on the last day of employment in most termination situations, including any accrued vacation. Colorado operates differently again. An employer who follows standard Indiana practice for a departing California employee is already in violation, even if every other aspect of the termination was handled correctly.
Anti-discrimination protections vary as well. Federal law covers specific protected classes and applies to employers above a certain size. Many states go further, extending protections to additional categories or applying them to smaller employers than federal law reaches. A handbook that only references federal standards leaves those gaps open.
Some companies address this with state-specific addenda that note where local law differs from the general policy. Others maintain separate handbooks for certain states. Workplace policy differences by state are significant enough that either approach is reasonable. What does not work is assuming one document covers all of it.
Remote Hires Do Not Simplify the Compliance Picture
Some Indiana employers learn this the hard way. They did not open a new office. They simply brought on someone who lives in another state and works from home. The assumption is that Indiana rules still apply. Usually, they do not.
HR compliance for remote employees follows the work location. The employee’s home is their legal worksite, and that determines which state’s wage laws, paid leave requirements, workers’ compensation rules, and payroll tax obligations apply. Where your headquarters sits is largely irrelevant to what another state expects from you as their employer.
What makes this easy to miss is that remote hiring does not feel like expansion. There is no lease signed, no new address, no announcement. But from a compliance standpoint, expanding your team geographically through remote hires triggers the same employer responsibilities as opening a physical office in that state. The obligations are the same. The visibility is not.
What Working With a PEO Actually Changes
For most Indiana employers, the core challenge is not understanding that multi-state hiring compliance matters. It is managing those obligations across multiple states without a dedicated compliance team for each one.
A Professional Employer Organization handles this through a co-employment arrangement. The PEO shares employer responsibilities with the client company and, because an established PEO already operates across many states, it brings existing registrations, accounts, and compliance infrastructure with it. WorkSmart Systems, based in Indianapolis, supports clients with employees across 47 states. Payroll tax registrations, state unemployment insurance accounts, workers’ compensation coverage, and leave administration are all handled within that relationship from day one.
For a company bringing on employees outside their home state for the first time, that means not having to research each state’s requirements independently or build new accounts before every hire. It also means having support when state laws change, which happens regularly. Paid leave requirements alone have shifted in several states over the past few years, and keeping up with those changes is an ongoing responsibility, not a one-time task.
Multi-state compliance issues do not surface on their own schedule. They tend to appear during audits, or when a state unemployment agency sends a notice, or when an employee files a wage complaint, by which point the errors have often been accumulating for months. The cost to fix them, back taxes, penalties, policy corrections, and potential legal exposure, is almost always higher than addressing the setup correctly from the start.
If your Indiana business already has people working in other states, a review of your current structure is worth doing now. If you are planning to add employees in new states, getting the right setup in place before that first hire is far easier than fixing it after.
Payroll registrations, leave policies, workers’ comp coverage, classification practices, and handbook language all need to reflect where your people actually work, not just where your company is headquartered.
WorkSmart Systems helps Indianapolis employers and Indiana businesses with distributed teams build that structure correctly and keep it up to date as things change. If you are not sure where your gaps are, that is exactly where the conversation starts. Get ahead of it before your next out-of-state hire opens a problem you didn’t see coming.
FAQs
What do employers need to know when adding employees in another state?
More than most expect going in. Before that first paycheck runs, you need a payroll tax account in the new state, state income tax withholding set up for that location, enrollment in the state’s unemployment insurance program, and confirmation that your workers’ compensation policy actually covers that state. Beyond payroll, the new state’s wage and hour rules, paid leave laws, and anti-discrimination requirements may differ from what your current policies reflect. Each state has its own setup, so treating every new location as its own compliance review is the right approach.
Does where an employee works affect payroll taxes?
It does, and the impact is more immediate than most employers realize. State income tax withholding follows the work location, not the company’s address. So if you have a remote employee working from home in another state, you need a payroll tax account in that state before they receive their first check. Some states also layer local or municipal taxes on top of state withholding. The IRS handles the federal side, but state and local obligations run on separate tracks entirely.
Do HR policies need to change for employees in different states?
Often, yes, and the gap is bigger than people expect. A handbook or policy written around Indiana law will miss requirements that apply in states like California, Oregon, or Colorado. Minimum wage rates, overtime rules, paid sick leave accrual, final paycheck timing, and protected class definitions all vary. Most companies address this by adding state-specific sections to their existing handbook rather than starting from scratch, which works well enough as long as someone is keeping those sections current.
Do remote employees create compliance obligations in the state where they live?
They do. The employee’s home is their worksite under most state laws, and that is what determines which state’s rules apply to them. It does not matter that your office is in Indiana. If someone works from home in Colorado, you owe Colorado payroll taxes, Colorado unemployment insurance contributions, workers’ compensation coverage that includes Colorado, and compliance with Colorado’s wage and leave laws. Where your company is based does not change what that state expects from you as an employer.
What are the main risks of multi-state hiring without proper compliance?
The risks that tend to cost the most are payroll tax penalties from missed state registrations or incorrect withholding, wage and hour violations when the wrong state’s rules get applied, workers’ compensation liability when an employee gets injured in a state your policy does not cover, and misclassification exposure when a contractor arrangement that works in Indiana does not hold up under another state’s classification test. None of these announce themselves early. They surface during audits or after complaints, at which point the bill is considerably higher than it would have been.
How does a PEO support multi-state workforce compliance?
WorkSmart Systems operates under a co-employment model, which means it shares employer responsibilities with client companies across all the states where their people work. The practical effect is that payroll tax registrations, state unemployment accounts, workers’ compensation coverage, and leave administration are handled within that existing relationship rather than requiring each client to build new infrastructure every time they hire in a different state. WorkSmart already operates across 47 states, so the setup is there when clients need it.
What is nexus and why does it matter when hiring out of state?
Nexus is what lawyers call the connection between a business and a state that triggers tax or regulatory obligations there. Having even one employee working in a state, whether in an office or at home, is usually enough to establish it. Once nexus exists, you typically owe that state payroll taxes and unemployment insurance contributions, and depending on the state, there may be broader business registration requirements as well. It is worth getting clear on your nexus exposure before a new hire’s start date, not after.