Skip to main content

Hiring an Out-of-State Employee: The Payroll Tax Setup Playbook

· 10 min read
Mike Thrift
Mike Thrift
Marketing Manager

Your best candidate lives three states away. They don't want to move, and honestly, you don't care — they can do the job from their kitchen table. So you make the offer, they accept, and a week later you get a polite email from your payroll provider asking for your state unemployment account number for Colorado. You don't have one. You didn't know you needed one.

Welcome to multistate payroll. A single remote hire can quietly sign your company up for a half-dozen new tax accounts, filing cadences, and wage rules — and the tax agencies don't send a welcome packet. They send penalty notices.

2026-04-24-hiring-out-of-state-employee-payroll-tax-setup-playbook

This playbook walks through exactly what to set up before that new hire's first paycheck, the reciprocal-agreement loopholes that can save everyone paperwork, and the common mistakes that turn a $75,000 hire into a $78,000 hire after fines.

Why One Employee Changes Everything

For payroll purposes, the taxing state is almost always where the employee physically does the work, not where your company is incorporated, not where payroll is processed, and not where the paycheck gets deposited. The moment an employee sits down at a desk in a new state and performs services for you, several things become true at once:

  • You've established physical nexus in that state for employment tax purposes
  • You owe state income tax withholding in that state (with a few exceptions)
  • You owe state unemployment insurance (SUTA) contributions in that state
  • You likely need workers' compensation coverage that includes that state
  • You may owe local income taxes, paid leave premiums, or disability insurance

None of this triggers a federal filing. Your IRS situation barely changes — the same Form 941 covers federal income tax withholding, Social Security, and Medicare no matter where the employee lives. The complexity lives entirely at the state and local level, which is exactly why it catches so many small businesses off guard.

The Six-Step Setup Checklist

Do these in order, ideally before the employee's first day. None of them require an attorney for a straightforward remote hire, but all of them have deadlines, and a missed deadline usually means a penalty.

1. Register with the State's Department of Revenue

Every state that imposes an income tax also requires employers to register before withholding and remitting it. The application typically asks for your federal EIN, your legal entity information, an expected start date for withholding, and a contact for tax notices. Registration is usually free, and most states now accept online applications that return an account number within a day or two.

A handful of states have no state income tax: Alaska, Florida, Nevada, New Hampshire, South Dakota, Tennessee, Texas, Washington, and Wyoming. If your employee works exclusively in one of those, you can skip the income tax registration — but you'll still need the rest of this list.

2. Register for State Unemployment Insurance (SUTA)

This is a separate application from income tax withholding, often handled by a separate agency — typically a labor or workforce department. Every state, with no exceptions, requires SUTA registration for employers. Your initial tax rate will be the "new employer rate" for your industry, which can range from roughly 1% to over 6% depending on the state and the industry's historical claim experience.

Registering for SUTA in a new state also means you'll be filing quarterly wage reports in that state for as long as you employ anyone there.

3. Secure Workers' Compensation Coverage

Workers' compensation is mandated in every state except Texas (where it's technically optional, though most employers buy it anyway). If your current policy was written for employees in one or two states, it almost certainly doesn't extend automatically to a new state — call your insurer and add the state before day one. Some monopolistic states (Ohio, Washington, Wyoming, North Dakota) require coverage through a state fund, not a private carrier.

Skipping this step is how a minor injury becomes a lawsuit. The employee's state, not yours, governs the claim.

4. Check for Local Income Taxes

A growing number of cities and counties levy their own income taxes on top of state taxes. Notable examples include:

  • Pennsylvania local wage taxes (almost every municipality has one)
  • Ohio municipal income taxes (hundreds of jurisdictions, often collected through a central agency like RITA or CCA)
  • New York City and Yonkers surcharges
  • Kentucky occupational license taxes
  • Michigan city income taxes (Detroit, Grand Rapids, and others)
  • Indiana county-level income taxes

Ask the employee for their exact home address — down to the municipality — and cross-reference it with the state's Department of Revenue guidance. A new hire in Westmoreland County, PA will need a different local setup than one in Philadelphia.

5. Set Up State Disability and Paid Leave

Several states fund short-term disability or paid family leave through payroll contributions, split between employer and employee. As of 2026, the main ones to watch:

  • California: SDI and Paid Family Leave (employee-paid)
  • New Jersey: Temporary Disability and Family Leave (both)
  • New York: Disability and Paid Family Leave (mostly employee-paid)
  • Hawaii: Temporary Disability (shared)
  • Rhode Island: Temporary Disability (employee-paid)
  • Massachusetts, Connecticut, Oregon, Colorado, Washington: Paid Family and Medical Leave programs (various splits)

Miss one of these and you'll owe back contributions plus interest, and your employee will have gone without coverage they were legally entitled to.

6. Review the State's Wage and Hour Rules

Payroll tax is only half the compliance picture. The state where the employee works also sets:

  • Minimum wage (always pay the higher of federal, state, or local)
  • Overtime rules (some states require daily overtime, not just weekly)
  • Pay frequency (some states mandate at least biweekly or semimonthly pay)
  • Final paycheck timing (ranges from "immediately on termination" to "next regular payday")
  • Pay stub requirements (specific items must appear on every stub in many states)

These aren't tax issues per se, but they land in the same inbox when they go wrong.

The Reciprocal Agreement Shortcut

Sixteen states plus D.C. maintain income tax reciprocity agreements that let cross-border commuters pay income tax only to their home state. If the pairing applies, your employee fills out a nonresidency certificate, you skip withholding for the work state, and you withhold for their home state instead. Fewer accounts, fewer filings, less friction.

Concentrated in the Mid-Atlantic and Midwest, the most common reciprocal pairs include:

  • Kentucky with Illinois, Indiana, Michigan, Ohio, Virginia, West Virginia, and Wisconsin
  • Michigan with Illinois, Indiana, Kentucky, Minnesota, Ohio, and Wisconsin
  • Maryland with Pennsylvania, Virginia, West Virginia, and D.C.
  • Pennsylvania with Indiana, Maryland, New Jersey, Ohio, Virginia, and West Virginia
  • Wisconsin with Illinois, Indiana, Kentucky, and Michigan
  • Virginia with D.C., Kentucky, Maryland, Pennsylvania, and West Virginia

Reciprocity is strictly pair-specific. Living in a state that participates in some agreements doesn't help unless the specific home-work combination is listed. And reciprocity only affects income tax withholding — SUTA is still owed to the state where the employee physically works.

The "certificate of nonresidency" paperwork varies by state: Pennsylvania uses Form REV-419, Ohio uses Form IT-4NR, Michigan uses Form MI-W4. Get it signed before the first paycheck and keep it in your records.

The "Convenience of the Employer" Landmine

A handful of states — most famously New York, and also Delaware, Nebraska, Pennsylvania (in limited cases), and formerly Connecticut — apply a rule known as "convenience of the employer." If your company is based in New York and your employee works remotely from, say, New Jersey, New York claims the right to tax their wages as if they were still sitting in the New York office unless the remote work is required by the employer for a legitimate business necessity.

This often creates double taxation: the employee's home state also taxes the wages because the work is physically performed there. Most home states offer a credit for taxes paid to the other state, but the credit is often capped below what's owed, and the employer is stuck withholding for both states in the meantime.

If you're based in one of these states and hiring remote workers who will live elsewhere, document the business reason for the remote arrangement in writing — ideally a formal remote work agreement that states the position is designated remote by the employer. That documentation can be the difference between a $200 filing adjustment and a five-figure audit exposure.

When Multistate Gets Even More Complex

A few scenarios turn an already-tricky situation into something worth calling an accountant about:

  • Employees who split time across states. A sales rep who lives in Connecticut, visits clients in New York two days a week, and works from home otherwise probably owes taxes in both states — proportional to days worked in each.
  • Traveling employees. Many states have "mobile workforce" thresholds (often 30 days or $10,000 in wages earned in the state) below which withholding isn't required, but thresholds vary widely.
  • Employees who move mid-year. Prorate withholding based on the move date. Both states get filings for that year.
  • Executives and highly compensated employees. Some states apply day-count rules that scoop up wages the employee never actually earned in the state.

None of these eliminate your obligations elsewhere. They add to them.

Why Bookkeeping Matters Here

Multistate payroll generates a paper trail that grows faster than most small-business owners expect: quarterly wage reports per state, unemployment filings per state, reconciliations between W-2s and state tax returns, and copies of every nonresidency certificate. When a notice arrives two years later asking why Q3 2025 wages were reported to Colorado for one employee but Q4 wages weren't, you'll want records that answer the question in under an hour.

Tracking payroll taxes by state from the beginning — rather than trying to reconstruct them when an audit notice arrives — is one of those disciplines that costs almost nothing up front and saves you real money when something goes sideways. Keep your payroll register, state-by-state tax filings, and nonresidency forms all in one organized place, and label every transaction in your books with the state it relates to.

Timeline: What to Do and When

  • Before the offer letter: Confirm the employee's work location (including whether they might move), and estimate the all-in employer tax burden for that state so your compensation budget is accurate.
  • Between offer acceptance and start date: Register for state income tax withholding, SUTA, and any applicable local taxes. Expand workers' comp coverage. Collect state W-4 equivalents and any reciprocity forms.
  • First paycheck: Withhold correctly from day one — refunding over-withheld amounts later is annoying; under-withholding triggers penalties.
  • Each quarter: File state wage reports and remit SUTA on each state's cadence. Most are due the last day of the month following quarter-end.
  • Year-end: Issue W-2s that report wages to each state separately. Reconcile state withholding totals. File annual unemployment reconciliations where required.

Keep Your Financial Records Audit-Ready from Day One

Multistate payroll generates a steady drumbeat of filings, deadlines, and reconciliations — and when a state agency eventually has a question, the business with organized records closes the loop in a week instead of a month. Beancount.io offers plain-text accounting that gives you complete transparency and version control over every transaction, so you can tag payroll entries by state, reconcile against filings, and hand over clean records to your CPA or an auditor with zero scrambling. Get started for free and see why developers and finance teams are switching to plain-text accounting.