Hiring in a new state? Read this first

You found a great candidate. They live two states away and they'll work remote. You're thinking about the offer letter and the laptop.

The thing nobody tells you is that this one hire may have just made your company a taxpayer in a state you've never set foot in — and the obligations usually start with the first paycheck, not at some comfortable threshold down the road.

What one remote employee can trigger

Hiring someone in a state generally means dealing with some combination of the following. The specifics vary enormously by state, which is the whole problem:

• Payroll tax registration. You typically register with the state's revenue department to withhold and remit income tax on their wages.
• Unemployment insurance. A separate registration, separate agency, separate account, its own rate.
• Workers' compensation. Coverage requirements are state-specific, and your existing policy may simply not extend.
• New hire reporting. Most states require reporting new employees within a short window.
• Foreign qualification. Registering your entity to do business there — with an annual report and fee attached, forever.
• Income tax nexus. An employee in a state can create a filing obligation for the business, not just the employee.

That last one is the expensive surprise. Payroll registration is administrative. Nexus means the state may want a corporate return and a share of your income — and unwinding that later isn't free.

The assumptions that cause problems

"It's just one person"

Many state obligations aren't volume-based. One employee is frequently enough to trigger the full set. There's often no small-business exemption to hide behind.

"We'll sort it at year-end"

Withholding is a per-paycheck obligation. If you should have been withholding from January and you register in November, you haven't deferred the problem — you've created a compliance failure with penalties and interest, and you've done it to your employee's tax situation too.

"They're a contractor, so it doesn't apply"

Only if they're genuinely a contractor. Worker classification is determined by the actual relationship — control, integration, exclusivity — not by what the agreement says or what both parties prefer. States audit this aggressively because misclassification costs them unemployment and payroll tax revenue.

If someone works your hours, uses your systems, follows your direction, and has no other clients, calling them a contractor doesn't make them one. The penalties for getting this wrong include back taxes, interest, and potentially the employee's share too.

"Our payroll provider handles it"

They'll file in states where you're registered. They generally won't register you, won't tell you that you should be, and won't notice that your new hire in a new state means new obligations. The software does what you configure it to do.

"They moved and didn't mention it"

Extremely common now, and it's your problem the moment it happens. An employee who quietly relocates has changed your obligations without anyone filing anything. Worth asking about periodically — genuinely, not as a formality.

What to do before you make the offer

1. Find out where they'll actually work. Not where they're from. Where they'll physically be, most days.
2. Price the state before you price the salary. Registration, ongoing filings, extra accounting, possible foreign qualification fees. It's a real cost of that hire and it recurs.
3. Ask whether nexus follows. This is the question with the biggest range of outcomes, and the one most likely to be missed.
4. Register before the first payroll run. Not after. Registration can take weeks in some states — start early.
5. Write down which states you're in. Sounds trivial. It's the single most useful artifact you'll have when something changes.

The part that's genuinely reassuring

None of this is a reason not to hire the right person. Companies operate in fifty states routinely. The obligations are knowable, the process is mechanical, and once you're registered in a state the ongoing burden is mostly filings your provider handles.

It only becomes expensive when it's discovered late. Handled up front, a new state is paperwork and a modest annual cost. Handled at audit, it's back taxes, penalties, interest, and a conversation you'll remember.

The whole difference is a phone call before the offer instead of after.