State Tax Reciprocity Agreements for Remote Employers

Ask most payroll teams how withholding works for an out-of-state employee, and the answer comes quickly: withhold where the work happens. That default holds as a starting point, but it is incomplete for a meaningful share of the workforce. Two structural exceptions override it, and many only encounter them during an audit or an unresolved employee complaint.

Withholding follows the work, until a state says otherwise

State income tax withholding starts as a work-location problem. An employee living in one state and working in another typically owes tax to the work state, and often to the home state as well, with a credit to prevent full double taxation. That is the default architecture, and it is what most systems are built for: look up the work address, apply that state's tables, and proceed.

Two exceptions complicate that default.

Reciprocity agreements are the first. Where they exist, a resident of State A working in State B is withheld only at home — no work-state withholding, no nonresident return. Reciprocity is not a national standard; it is a patchwork of specific state pairings, mostly among neighboring states with heavy commuter traffic. Pennsylvania anchors the largest network, with reciprocity covering New Jersey, Indiana, Maryland, Ohio, Virginia, and West Virginia. A Mid-Atlantic cluster links Maryland, D.C., Virginia, Pennsylvania, and West Virginia. A Midwest network ties together Illinois, Indiana, Iowa, Kentucky, Michigan, and Wisconsin. Notably absent: New York, New Jersey-to-New York specifically, Connecticut, Massachusetts, and California — states with some of the heaviest cross-border commuting in the country. There, the full dual-withholding-with-credit model still applies.

The convenience-of-the-employer rule is the second, and it does not add an exception to the work-location rule — it reverses the outcome entirely. Under a convenience rule, an employee who works remotely by choice rather than by employer requirement is sourced to the employer's state rather than their own. New York applies the strictest version. New Jersey enacted a reciprocal version in 2023: a New Jersey employer must apply New York's, Delaware's, or Nebraska's convenience rule to residents of those states, sourcing that compensation to New Jersey — retroactive to January 1, 2023. Connecticut takes a comparable approach: its convenience rule applies only when the nonresident's home state imposes an equivalent rule on Connecticut residents. As a result, whether the rule applies can depend on a second state's tax code — a lookup step most withholding logic was never built to perform.

The one fact both rules need is the one fact most systems don't have

Reciprocity and convenience rules both come down to a single input: where an employee is actually, physically working, day by day. That is the exact data point remote work has made hardest to verify. In March 2026, 22.6% of U.S. workers teleworked or worked from home for pay, a rate that has held between roughly 21.5% and 23% over the past year, per the Bureau of Labor Statistics. That is not a marginal population — it represents more than a fifth of the workforce every month, generating withholding decisions that depend on location data that often isn't fully verified.

The gap between employer confidence and reality is significant. SHRM has found that 28% of employees have worked outside their home state or country at some point since the pandemic began, but only about a third reported every one of those days to HR, even though most understood the tax implications. On top of that, the two exceptions compound quickly. Missing an applicable reciprocity agreement creates an unnecessary nonresident filing and refund process for an employee who should not have been withheld twice. Missing a convenience rule — or missing that it is conditional on a second state's law, as New Jersey's and Connecticut's now are — results in either remitting tax to a state with no legitimate claim to it, or under-withholding and leaving the employer exposed once the arrangement is audited.

Jurisdiction determination is the foundation, not a patch

The platforms that handle this well do not bolt reciprocity and convenience-rule checks onto a work-address lookup as an afterthought. They treat verified work location as the input to a rules engine that already accounts for every active reciprocity pairing, every convenience-rule state, and the conditional logic the newer reciprocal rules require — including checking a second state's law before determining whether a rule like New Jersey's applies at all.

That is one of the problems Symmetry Tax Engine is built to solve. Rather than an engineering team maintaining its own table of a dozen-plus reciprocity pairings and a handful of convenience-rule states — and revising that table every time a state changes its approach, as New Jersey and Connecticut both have in recent years — that logic lives in infrastructure built to track it, applied automatically at calculation time.

Why this matters to the people who never see the rules engine

The fallout from a wrong jurisdiction call rarely lands on the engineers who wrote the withholding logic. It lands on the payroll specialist explaining to a remote hire why they were taxed in a state they have never visited, or the finance team untangling a quarter's worth of filings that should never have existed. For compliance officers and payroll ops teams, the requirement isn't expertise in convenience-of-the-employer doctrine. It is a platform where that determination is made correctly every pay cycle, without anyone downstream left to absorb the error.

As the remote-work share of the workforce holds in the low-to-mid twenties with no sign of receding, accurate jurisdiction determination stops being an edge case. It becomes the foundation the rest of multi-state payroll accuracy depends on.