State Tax Withholding for Remote Employees: State Taxes for Remote Workers and Hiring Out of State Employees

The default across the country is the physical presence rule: wages are sourced to the state where the work is actually performed. An engineer in Boise doing all their work from Boise creates Idaho wages, whether your company is in San Francisco, Austin or New York. Your own state of incorporation does not enter into it.

That gives you three practical obligations in the employee state, and you generally need all three before the first payroll run:

• A state withholding account with the revenue department, so you can remit the income tax you withhold. Most states let you register online in under an hour and issue an account number in a few days.
• A state unemployment insurance account with the labor or workforce agency, which sets your experience rate. New employers usually get an assigned new-employer rate for the first two to three years.
• Workers compensation coverage that is valid in that state. A policy written for one state does not automatically cover an employee sitting in another, and a handful of monopolistic states (Ohio, North Dakota, Washington and Wyoming) require you to buy the coverage from the state fund rather than a private carrier.

Nine states make the first item disappear entirely, because they impose no personal income tax on wages: Alaska, Florida, Nevada, New Hampshire, South Dakota, Tennessee, Texas, Washington and Wyoming. Washington still has a payroll obligation for its long-term care program and paid family leave, and New Hampshire and Washington both tax certain investment income rather than wages, so read "no income tax withholding on wages" rather than "no filings at all".

The remaining question is how much of the year a visit has to be before it triggers withholding somewhere new. There is no national threshold. Some states start at the first day worked in state, others use a day count (commonly 14 to 30 days) or a wage floor. If your remote team travels for offsites, that is the rule to look up before the trip, not after it.

A small group of states will not accept the physical presence answer. Under a convenience of the employer rule, a day your nonresident employee works from home is treated as a day worked in your state, unless the employee works remotely out of necessity for the employer rather than for their own convenience. The effect is that the employee can owe income tax to a state they never enter.

New York is the state that matters most here, and its rule is written down in detail in Technical Services Bureau memorandum TSB-M-06(5)I, published 15 May 2006 and still the operative guidance. We read it at the source. It is much more workable than its reputation suggests, because it defines an escape route: if the employee home office qualifies as a bona fide employer office, those days are genuinely out-of-state days.

The memorandum makes that a scoreable test. The home office qualifies if it meets the primary factor, or at least four of the six secondary factors and three of the ten other factors. That is worth knowing, because most write-ups on this topic stop at "New York has a convenience rule" and never mention that there is a defined way to satisfy it.

The states applying some version of the rule in 2026 are New York, Pennsylvania, Delaware and Nebraska, with Connecticut and New Jersey running a narrower reciprocal version that only bites when the employee lives in another convenience-rule state. Nebraska narrowed its rule in 2024 so that it applies only when the nonresident employee is physically present in Nebraska for more than seven days in the tax year. We verified the New York rule at the New York State Department of Taxation and Finance. The other five are widely reported by tax practitioners and payroll providers, and we could not locate an equivalent single primary memorandum for each, so confirm your own position with that state revenue department before you change a withholding setup.

The practical consequence for hiring: if you are a New York employer, a fully remote hire in another state is not automatically a clean break from New York withholding. Document the business reason for the remote arrangement, put it in the offer, and keep the evidence. If you are hiring into a convenience-rule state from elsewhere, none of this applies to you at all.

This is the part that catches people, and it is the most useful thing on this page. Income tax withholding and unemployment insurance are decided by two unrelated legal tests, so they do not have to agree.

Unemployment tax uses a four-step hierarchy that every state has adopted in near-identical statutory language, set out in US Department of Labor Unemployment Insurance Program Letter 20-04. You apply the steps in order and stop at the first one that answers:

1. Localization. Is the service performed entirely in one state, or is the out-of-state part merely incidental (temporary, transitory, or isolated transactions)? If so, all of the wages belong to that state.
2. Base of operations. If the service is not localized anywhere, is the employee base of operations in a state where some service is performed?
3. Place of direction and control. If there is no base of operations, which state is the work directed or controlled from, provided some service is performed there?
4. Residence. Failing all of the above, the employee state of residence, provided some service is performed there.

Two things follow from the hierarchy that matter to an employer with a distributed team. First, an employee wages are never split between states for unemployment purposes. All of them go to one state. Income tax withholding, by contrast, can be apportioned across states day by day. Second, the localization test is decided by where the work is actually done, not where the employer sits. The program letter carries an example that reads as though it were written for remote hiring: a New York employee moves to Florida for family reasons, the employer agrees to let her telecommute, all assignments and work products travel over the internet, and the DOL conclusion is that her services are localized in Florida and subject to Florida law.

Put the two rules side by side and you get a genuine divergence. A New York employer whose employee moves to Florida pays unemployment tax to Florida, because the service is localized there. But if that employee works from home for their own convenience rather than the employer necessity, New York can still treat those days as New York workdays for income tax. Same wages, same person, two different states collecting. That is not an error in your payroll setup, it is what the two tests actually say.

The program letter also flags the fix when work is genuinely split between states: employers can elect to cover all of an individual service in one state under the Interstate Reciprocal Coverage Arrangement. It is worth asking your payroll provider about if you have staff who genuinely work across a state line every week.

Reciprocity is the one piece of good news in multi-state payroll. Where two states have an agreement, an employee who lives in one and works in the other pays income tax only to their home state, and you withhold only for the home state. No second withholding, no nonresident return.

Sixteen states plus the District of Columbia have active agreements in 2026, spread across roughly 30 state pairs. Pennsylvania has the widest set, and its Department of Revenue lists them directly in the Personal Income Tax Guide.

Three warnings, because reciprocity is narrower than it sounds. It is opt-in: nothing happens until the employee files the work state exemption certificate with your payroll team, and if they never file it you are legally withholding for the wrong state. It does not cover unemployment tax, which still follows the DOL hierarchy above. And it does not cover local taxes, so Pennsylvania local earned income tax, Ohio municipal tax and the Maryland county piggyback tax survive the agreement intact.

Note also what reciprocity is for. It was built for commuters who cross a state line to get to work. A fully remote employee who lives and works in the same state does not need it at all, because there is only one state involved. The Pennsylvania guide is the source for the Pennsylvania row above; the other rows follow the exemption certificates each state publishes, and the 16-states-plus-DC count is a widely reported figure from payroll compilations rather than a single government list.

Most of the cost of a new state is time, not money. The registrations are cheap; the annual compliance is what accumulates.

The sequence that keeps you out of trouble is short. Ask the candidate which state they will actually work from, and get it in writing in the offer letter, because that one answer drives everything else. Register for withholding and unemployment in that state before the first pay date. Confirm the workers compensation policy extends there. Check whether the state or the city imposes its own paid leave, paid family leave or retirement mandate, because several now do and they are easy to miss. Then add a light annual check that nobody has quietly moved: an employee relocating without telling payroll is the single most common way employers end up filing in a state they did not know about.

One more piece of arithmetic worth having in mind before you decide how wide to cast the net. Registering in a state is inexpensive, but the ongoing cost of employing anyone anywhere is not, and the payroll tax component is the same in every state at the federal level: 6.2% Social Security on the first $184,500 of 2026 wages, capped at $11,439.00 per employee, 1.45% Medicare with no cap, and 0.6% federal unemployment on the first $7,000 after the full state credit. State unemployment sits on top and typically runs 0.5% to 5.4% on a state-specific wage base. The full build-up is on our page covering the cost of hiring an employee.

For most companies, no. The registration burden per state is a few hours and a few hundred dollars, and it is a fixed cost that does not scale with the number of employees you eventually put in that state. Constraining a search to five states to avoid ten hours of paperwork is usually the more expensive decision, because it shrinks the candidate pool at exactly the point where the pool determines the quality of the hire.

There are three situations where it genuinely does change the answer. If you are a New York, Pennsylvania, Delaware or Nebraska employer, the convenience rule complicates the tax position of remote staff and is worth structuring deliberately. If you are hiring a single part-time or short-term role, the setup cost can exceed the value of widening the search. And if you expect to place one person in a state and then nobody else for years, the recurring registered agent and annual report cost is real, if small.

Everywhere else, the better filter is the one candidates can see. Say in the job posting which states you can employ in, and applicants outside them will self-select out before you spend a screening call finding out. Boards where the listing shows location eligibility and salary up front do that filtering automatically, which is most of what a remote-focused job board is actually buying you. If you want the full comparison of what a listing costs across the major channels, we keep a current one on what it costs to post a job, and if you are weighing a recruiter instead, the fee structures are broken down on recruiter fees.