You found the perfect candidate. Strong background, great culture fit, available to start in two weeks. There's just one thing. They live in a different state.

Most small business owners think about this the way they'd think about any other hire. A little paperwork, some payroll setup, done. Then reality hits: that single remote hire just triggered a full compliance chain reaction, and nobody at the company is positioned to catch it.

This is one of the most common ways growing companies accidentally create expensive problems for themselves.

What actually happens when you hire across state lines

Employment law follows the employee, not the company. Federal rules set the floor. State and local laws stack on top. And once an employee is physically working in a new state, that state's rules apply to them, regardless of where your headquarters sit.

A single remote hire in a new state can trigger:

• State tax registration and withholding account setup
• Unemployment insurance registration
• Workers' compensation coverage
• State-specific new hire reporting
• Required labor law postings (physical AND digital for remote workers)
• State-specific handbook policies and addenda

Miss any one of these, and you've created a compliance exposure that compounds every pay period.

The numbers aren't small

A 2026 FoxHire study surveyed 1,000 HR, payroll, and business professionals about multi-state hiring. The results:

• 25 percent of employers paid penalties, interest, or fines related to multi-state compliance in the past two years
• 23.8 percent missed a registration, filing, or reporting deadline
• 24.7 percent had to issue back pay or wage corrections
• 48 percent delayed hiring or expansion because they weren't sure about compliance requirements
• 50 percent told qualified candidates they couldn't be hired due to state-specific compliance concerns

That last stat deserves a second read. Half of employers have turned away candidates they wanted to hire because figuring out the compliance piece felt like too much. These aren't bad employers. They just don't have the infrastructure to move confidently.

Where small companies usually get tripped up

A few of the most common traps, in no particular order:

Wage and hour differences

California requires daily overtime (not just over 40 hours per week) and mandatory meal and rest breaks. Massachusetts has treble damages for Wage Act violations. Several states have minimum wages well above federal. Running payroll on federal rules in a state that requires more is a fast path to back pay owed.

The "convenience of the employer" rule

At least six states, including New York, can tax out-of-state remote employees as if they worked in-state. This creates potential double taxation. Most states offer credits to offset, but the paperwork and confusion are real.

Worker classification

California's AB5 sets a stricter test for who can legitimately be classified as an independent contractor. That same contractor arrangement that works in one state may be illegal in another. Misclassification can trigger back taxes, penalties, and owed benefits.

Pay transparency laws

New York and California require salary ranges in job postings. Colorado, Washington, Illinois, and several others have their own versions. A single job posting that doesn't comply can trigger a claim.

Labor law postings for remote workers

Federal, state, and local posters must be available to remote employees. Some states specifically require electronic delivery. "We have posters up at the office" doesn't cover a remote employee in another state.

Handbook addenda

A generic employee handbook written for one state won't cover the state-specific leave, sick time, and notice requirements in others. Applying an out-of-state policy consistently can create liability even if the original policy is fine.

Why this is an inflection point issue

Small companies rarely run into this at 5 employees. They run into it around the 15 to 50 range, when growth starts pulling in candidates from different states. One hire in Georgia. Two in California. Someone relocates to New York. Suddenly the company has employment obligations in four states, and nobody's tracking it.

The companies that handle this well either hire a dedicated HR leader early (expensive at this stage) or work with a fractional HR partner who knows what to watch for. The companies that handle it badly find out during an audit, a wage claim, or a state tax notice that they owed something six months ago.

What good looks like

Before you hire in a new state, somebody should be answering:

• Do we need to register with the state's labor department and tax authority?
• What are the specific wage, hour, and leave laws that apply?
• Are there pay transparency requirements that affect how we posted the role?
• Does our handbook need a state-specific addendum?
• How will we deliver required labor law notices to this remote employee?
• Who is tracking state-by-state compliance changes ongoing?

That's not a checklist most founders or COOs should be working through themselves. It's the kind of infrastructure question a good HR partner owns.

Where BloomHR fits

Ian Hall, who leads client-facing HR work at BloomHR, started his HR career as a department of one for a large multi-state employer. Multi-state compliance is not a side project for him. It's where his expertise is sharpest.

If you're expanding your hiring beyond your home state, or you've already hired remote employees and aren't confident about the compliance picture, this is exactly the kind of work Strategic HR Support was built for. We help you scope where you stand, close the gaps, and set up a system so the next hire in the next state isn't a scramble.

Learn more about Strategic HR Support → https://joinbloomhr.com/strategic-hr-support/