Table of Contents
Remote work has changed where businesses hire. For many growing organizations, the ability to recruit talent from anywhere has opened doors that simply did not exist a few years ago. A business based in Indiana can hire a specialist in Colorado, a sales representative in Florida, or an operations manager in Illinois without opening a physical office in any of those states. One remote employee working from a home office can seem like a minor administrative detail. It rarely stays that way.
Most Indiana employers who add a remote worker in another state aren’t trying to cut corners on compliance. They found a good candidate, made the offer, and moved on to the next problem. What they didn’t account for is that the moment an employee sits down at a desk in Colorado, North Carolina, or Tennessee, a set of legal obligations attaches to the employer in that state. Some of those obligations have deadlines that predate the first paycheck.
That is the compliance reality remote employee tax compliance brings, and it catches businesses off guard, not because they were careless, but because nobody told them upfront. The picture shifts considerably once a company has people working across state lines, and knowing what triggers those responsibilities is the first step to staying ahead of them.
Where It Starts: Nexus
The legal concept underlying most of these issues is nexus. It refers to the connection a business has with a state that gives that state authority to impose its laws on the business. For years, nexus was mostly about physical offices and storefronts. A business that had a location in Ohio had nexus in Ohio. One that didn’t, generally didn’t.
Remote work changed that. When a full-time employee works from their home in another state, they create a physical presence in that state on the employer’s behalf. In most states, that presence is enough to establish a nexus and trigger registration, withholding, and other employer responsibilities.
For Indiana businesses with out-of-state employees, the question isn’t whether your company intended to operate in another state. It comes down to whether someone on your payroll works there. If they do, that state most likely has a claim on your attention and your compliance budget.
State Income Tax Withholding
The most immediate obligation for employers with remote employees in different states is state income tax withholding. Most states with a personal income tax require employers to withhold from employees’ wages earned within their borders. The rule follows the employee’s physical work location, not the employer’s headquarters.
An Indianapolis company with a marketing analyst working remotely from Michigan owes Michigan state income tax withholding on that person’s wages. That requires registering with Michigan’s Department of Treasury, setting up the correct withholding rate, and submitting those payments on Michigan’s schedule. The same logic applies in any state where the employee works full-time.
State income tax withholding rates and filing requirements vary by state. Some states have flat rates; others use brackets. Remittance schedules vary, too. Running them all correctly in parallel is a coordination challenge that goes well beyond a typical single-state payroll setup.
There is one additional layer worth understanding. Several states operate under what’s called a “convenience of the employer” rule. Arkansas, Connecticut, Delaware, Nebraska, New York, and Pennsylvania apply this rule, which means that if your employee is working remotely out of personal convenience rather than a business necessity, the employer’s state may still assert the right to tax those wages alongside the employee’s home state. Most states offer tax credits to prevent employees from being taxed twice on the same income, but the setup requires attention. Getting the withholding configuration wrong across two states creates exposure that compounds with every pay period.
State Payroll Tax Registration
Withholding is one part of the multi-state payroll compliance picture. State payroll tax registration is a separate step that must be completed before the first paycheck runs.
Operating in a new state as an employer typically requires registering as a foreign entity doing business there. It also means opening a withholding account, enrolling in that state’s unemployment insurance program, and reporting the new hire to that state’s new-hire reporting agency. Most states want the new-hire report within 20 days of the hire date. A few want it sooner.
Each of these registrations produces account numbers and credentials that your payroll system needs to process wages correctly. Running payroll without them means errors are baked in from the start, and those errors cost considerably more to unwind than they would have cost to prevent.
For Indiana employers hiring their first employee in a state where they’ve never operated, building at least 45 days of lead time before the start date is a realistic minimum. That window allows registrations, payroll configuration, and coverage setup to land before the first pay period opens.
Unemployment Insurance Obligations
Each state administers its own unemployment insurance program, and employer contributions go to the state where the employee works, not to the employer state of incorporation. A growing business with remote workers in six states is managing six separate unemployment insurance accounts, each with its own rate, wage base, and reporting schedule.
State unemployment agencies are increasingly cross-referencing federal employment records and W-2 filings to identify employers with payroll activity in their state but without a corresponding registration. The gap between when the employer’s duties began and when they eventually registered is the period that draws penalties and back contributions.
Staying informed about unemployment insurance requirements in each applicable state is an ongoing responsibility, not a one-time setup. Rates change. Wage bases are adjusted annually. An employer who correctly configured a state account three years ago may be running the wrong contribution calculation today if nobody reviewed the setup after the state updated its parameters.
Workers' Compensation Coverage
Workers’ compensation is state-regulated, and the requirements vary considerably. Some states require coverage from day one of employment, with no employee count threshold. Others have minimums, though those thresholds are often lower than employers expect. A few states, including North Dakota, Ohio, Washington, and Wyoming, require employers to carry coverage through the state fund rather than a private insurer.
Here is where many Indiana businesses run into a problem they didn’t see coming. An existing Indiana workers’ compensation policy doesn’t automatically extend to employees in other states. Coverage must be added specifically for each location. Consider a scenario where a remote employee in Georgia slips and injures their back while working from home. If the policy doesn’t include Georgia, the employer may be facing an uninsured liability and a workers’ compensation claim at the same time.
Most insurers can add state endorsements to an existing policy. That conversation needs to happen before a remote employee starts in any new state, not after a claim surfaces.
Wage and Hour Laws by State
Federal wage and hour law under the U.S. Department of Labor sets a national minimum, but states can exceed it and many do. Minimum wage, overtime calculations, meal and rest break requirements, pay frequency, and final paycheck timing are all governed at the state level, and the rules don’t follow a single pattern.
California requires overtime after eight hours in a day, not just 40 in a week. Several states have minimum wages well above the federal floor. Colorado, Illinois, Michigan, and Oregon all have paid sick leave mandates with their own accrual rates and carryover rules. Final paycheck timing differs, too: some states require same-day payment upon termination, while others allow the normal pay cycle to run out.
A blanket company-wide HR policy built around Indiana’s requirements won’t satisfy those variations. Each employee’s work location determines which state’s wage and hour laws govern their employment, so remote work policy compliance has to account for where people actually sit.
Local Payroll Taxes
State-level requirements are the main event, but they’re not always the full picture. Some cities and counties layer local payroll taxes on top of state requirements. New York City, Philadelphia, Columbus (Ohio), and parts of Kentucky are examples of jurisdictions that impose their own local income or payroll taxes on wages earned within their borders.
For an Indiana business with a remote employee working from within one of those jurisdictions, local taxes are a real employer responsibility that can be easy to miss when the focus is on getting state-level registrations done. Payroll systems that handle multi-state compliance don’t always catch local-level requirements automatically. Someone has to know to look for them, and that requires knowing exactly where each employee works.
Employee Classification
Tax and payroll requirements aren’t the only area where state differences create risk. Worker classification standards vary too, and some states apply tests that are considerably stricter than what the Internal Revenue Service uses.
The IRS relies on a multi-factor analysis to distinguish employees from independent contractors. California’s ABC test takes a different approach: it presumes workers are employees by default unless the employer can demonstrate otherwise across three specific criteria. New Jersey applies similar logic. An arrangement that holds up as a legitimate contractor relationship under federal guidelines may not survive scrutiny under the laws of the state where that worker actually operates.
Consider an Indiana company that has been paying a software developer in California as a 1099 contractor for 18 months. If California’s labor department reviews that relationship and reclassifies the worker as an employee, the liability runs back to day one: unpaid payroll taxes on both sides, unemployment insurance contributions, workers’ compensation exposure, and wage penalties, all retroactive. That is not a hypothetical risk. California’s labor enforcement agencies actively pursue misclassification cases.
For Indiana employers using contractor arrangements with out-of-state workers, the question isn’t whether the arrangement worked somewhere else. It’s whether it would survive scrutiny under the specific rules of the state the worker performs work in.
Questions to Ask Before Hiring
Many multi-state compliance problems start earlier than employers realize. By the time someone asks whether the company is set up to pay a new hire legally, that person is often already onboarded, and the first paycheck is two weeks out.
The more useful habit is asking the compliance questions before extending an offer. Does this employee’s work location create a tax nexus? Which state’s income tax withholding rules apply, and is the company already registered there? What workers’ compensation coverage is required, and does the current policy extend to that state? Is there a state unemployment insurance account in place? Are there wage and hour rules in that state that differ from what the company applies in Indiana?
None of those questions is complicated to answer, but they take time to act on. Most state registrations take four to six weeks to process. Payroll systems need to be reconfigured before wages are processed, not after. Waiting until a start date is confirmed to begin the setup process is exactly how employers end up running payroll with the wrong withholding from the first pay period. For Indiana businesses adding employees in states they’ve never operated in, making these questions part of the offer process is far less painful than including them in an audit response.
Managing Compliance Across States
The practical foundation of remote workforce compliance is knowing where every employee physically works and keeping that information up to date. It sounds simple, but it breaks down in practice more often than most employers expect. Address changes, temporary relocations, and permanent moves all carry compliance implications. An employee who spends three months working from a family member’s house in another state may create a short-term withholding requirement there. An employee who permanently relocates shifts the employer’s duties in the new state from the day of the move, not the day the HR system is updated.
In practice, the requirements build outward from there: state registration before the first paycheck, payroll configuration aligned with each state’s rules, insurance coverage extended to new locations, and ongoing monitoring of unemployment rates, income tax withholding tables, and wage requirements as states update them.
For growing Indiana businesses with employees across multiple states, managing this in-house without a dedicated compliance function is an increasingly difficult lift. The more states involved, the more parallel systems the employer is running simultaneously, and the more likely it is that something gets missed.
WorkSmart Systems helps Indiana businesses manage multi-state payroll, tax, and HR compliance through the PEO model. With experience supporting employers across 47 states, WorkSmart helps growing organizations expand their workforce without building compliance infrastructure from scratch or finding out what’s missing when a state agency comes calling.
If your business has remote employees working outside Indiana and you’re not certain whether your payroll and tax obligations are fully in order, that’s a conversation worth having before a state agency initiates one for you.
Contact WorkSmart Systems to talk through your current employee locations and what compliance steps apply to your situation.
FAQs
Does hiring a remote employee create tax obligations in another state?
Yes, in most cases. A full-time employee working from their home in another state establishes a physical presence there on behalf of the employer. That typically triggers state registration, income tax withholding, unemployment insurance enrollment, and workers’ compensation requirements in the state where the employee works.
Do employers need to register in a state for just one remote employee?
For most states, yes. A single full-time remote employee is generally sufficient to establish nexus and trigger employer registration and withholding obligations in that state. Some states have de minimis exceptions for workers who are present for only a few days per year, but a full-time remote worker who lives and works permanently in another state brings the full set of requirements with them.
How do remote employees affect payroll taxes?
Each employee’s physical work location determines which state’s payroll tax rules apply to their wages. An employer with remote workers in multiple states manages separate payroll tax obligations in each of those states, including different withholding rates, remittance schedules, and filing requirements. State unemployment insurance contributions also follow the employee’s work location rather than the employer’s headquarters.
What state taxes apply to remote employees?
The main state tax obligations are income tax withholding and unemployment insurance contributions, both governed by the state where the employee performs work. Some states also have local payroll taxes layered on top. Certain states apply the “convenience of the employer” rule, which can create dual withholding obligations if the employee is working remotely for convenience rather than necessity.
How do employers stay compliant with remote workers in other states?
Accurate records of where each employee physically works are the foundation. From there, employers need to register in each applicable state before the first paycheck, configure payroll to match each state’s withholding requirements, extend workers’ compensation coverage to each new work location, enroll in state unemployment insurance programs, and monitor ongoing changes to each state’s rules. Working with a Professional Employer Organization that already has multi-state infrastructure in place is one of the most efficient ways for small and mid-sized businesses to handle this.
What are the biggest compliance risks with out-of-state remote employees?
The most common risks are failing to register in new states on time, withholding income taxes for the wrong state, carrying inadequate workers’ compensation coverage, missing unemployment insurance enrollment, and applying home-state wage and hour rules to employees in states with different requirements. These risks accumulate retroactively and tend to be discovered during state audits or employee complaints, at which point penalties, back payments, and interest have often been building for months or years.
Does employee location affect employer taxes?
Yes, directly. Each state where an employee works can assert its own payroll tax, income tax withholding, and unemployment insurance requirements on the employer, regardless of where the company is headquartered. Being registered only in Indiana does not limit the tax and compliance responsibilities that arise when employees perform work in other states. For Indiana businesses with remote employees in multiple states, each state is essentially a separate compliance environment running concurrently.