Handling Payroll for Multi-State Remote Employees in 2027

6/28/2026

Our post on multi-state withholding rules covers the legal question: which state gets the withholding, which gets the unemployment wages, and what nexus the employer created. Those rules are knowable.

This post is about the part that actually fails. The rules are not the problem — the maintenance is. Multi-state payroll breaks because nobody owns the process for adding a state, nobody learns when an employee moves, and nobody ever closes a state the employer has left.

Start With the Field That Causes Everything Else

The foundational operational error, and it is a data structure problem.

Payroll needs the employee's work location. Human resources systems capture a mailing address. These are different facts, and in most organizations they are stored in the same field.

The consequences: an employee who works from home in one state and receives mail at a family address in another is taxed wrong. An employee who moved and updated their address for benefits purposes has silently changed their tax situation with no payroll review. And an employee assigned to a headquarters cost center while working remotely is invisible in any report of where the workforce actually is.

The fix, and it is worth insisting on: a distinct, required work-location field, separate from the mailing address, with a defined change process rather than a self-service edit. Until that exists, every other control in this post is being applied to unreliable data.

The New-State Onboarding Runbook

Ten steps, in order, completed before the first payroll in a new jurisdiction. This is the deliverable a practitioner can hand a client.

1. Determine the obligations. Withholding, unemployment, local jurisdiction taxes, workers' compensation, and any state-mandated program — using the analysis in our rules post. Do not assume this state resembles the last one.
2. Register with each agency. Withholding and unemployment are separate registrations with separate agencies in most states, and local jurisdictions are separate again. Record for each: the account number, the deposit frequency, the filing frequency, the online portal credentials, and the agency contact. This record is the thing that makes the following years survivable.
3. Configure the payroll system — the state added, the unemployment rate entered, local codes applied, and the employee assigned to the correct work location.
4. Confirm workers' compensation coverage for that state. Coverage is state-specific and an employee in an uncovered state is an uninsured exposure, not a paperwork gap.
5. Enroll in state-mandated programs — paid family and medical leave, disability, and any state-facilitated retirement mandate — each with its own registration, contribution mechanics, and employee notice requirement.
6. Complete new hire reporting as that state requires.
7. Issue the state-required employee notices. Several states require specific notices at hire or on a change — wage notices, sick leave notices, and others — and this is the step employers most often omit entirely because nothing prompts it.
8. Address handbook applicability. State-specific requirements on leave, final pay, meal and rest periods, and pay frequency mean the existing handbook may not fit. A state supplement is the usual answer.
9. Verify the first payroll manually. Hand-compute one employee's withholding and employer taxes for the new state and compare it to the system. This is how a configuration error is caught in week one rather than in the third quarter.
10. Diary the filing deadlines, which differ from every other state's.

The Employee-Move Process

Where firms fail most often, because a move is an event nobody is required to report.

Require reporting before the move, in policy, with a stated reason — that the employer must register and configure payroll before the first pay period in the new state. Employees comply when told why.

Then build detection, because policy alone will not catch it. The triggers worth monitoring:

• An address change request of any kind, which should route to payroll rather than only to benefits
• A benefits change referencing a new location
• An expense report with travel from a new origin
• A manager mentioning it casually, which is how most moves are actually discovered
• Direct deposit changed to a bank in another state
• A device or network consistently connecting from a new location, where the organization has that visibility

Then handle the mid-year mechanics. As our rules post explains, the unemployment taxable wage base is applied per employee per state, so a mid-year move can restart it and produce a larger total obligation than either state alone. A mechanical calculation gets this wrong in one direction or the other, and it needs checking rather than assuming.

And raise the policy question the client has not considered: whether to permit moves at all. An employee relocating to a state the employer has no presence in creates registrations, filings, workers' compensation coverage, employment law obligations, and — per the rules post — potentially income and sales tax nexus for the business. Some employers permit moves only to an approved list of states for exactly this reason, and a client who has never thought about it should.

The State Exit Nobody Documents

The recurring annoyance that no checklist covers.

When the last employee in a state leaves, the employer's obligations do not end automatically. Without action:

Returns remain due, and an employer with no wages in a state still owes zero returns in many jurisdictions — generating notices, penalties, and eventually estimated assessments for filings nobody made.

Accounts stay open, accruing minimum assessments in some states.

The unemployment account remains active, and a former employee's claim can still be charged against it.

The registration remains, which can itself create a presumption of continued activity.

The exit runbook: file final returns and mark them final where the form provides for it; formally close or inactivate each account with each agency; cancel state-mandated program enrollments; confirm workers' compensation coverage is adjusted; retain the closure confirmations; and keep the state on the maintenance calendar for one more cycle to catch anything outstanding.

Firms that skip this receive correspondence for years, and the notices are addressed to an entity that no longer files — which means nobody reads them until an assessment arrives.

The Maintenance Calendar

Multi-state payroll is a recurring obligation, not a setup task.

Filing frequencies differ by state and differ within a state. Withholding may be monthly while unemployment is quarterly, and a state may change an employer's frequency based on volume. Each combination needs its own calendar entry.

Annual reconciliation returns, which several states require in addition to the periodic filings.

The unemployment experience rate, per state, per year — the item covered in our post on January payroll updates, and the most costly maintenance failure because an unentered rate runs all year.

Rate, wage base, and threshold changes, per state.

Minimum wage changes, including local ordinances, which affect both pay and garnishment calculations.

New state programs taking effect, which arrive without notice to the employer.

Local jurisdiction changes, which are the least visible of all.

The Tracking Artifacts

Four documents that make this manageable. A firm advising a client should ask to see all four.

The work-location field, per above, populated and maintained.

A state matrix — one row per state, with the obligations, account numbers, rates, deposit and filing frequencies, portal credentials, agency contacts, and the employees currently there. This single document is the difference between a managed process and an annual scramble.

A travel-day log, for the employees where it matters. Not everyone — as the rules post explains, nonresident withholding thresholds vary and the exposure concentrates in high earners who travel. Track those people deliberately and accept that tracking everyone is not achievable.

A change log, recording every state added, every employee move, and every state closed, with dates. This is the audit trail.

What the Payroll Provider Does Not Do

The gap clients consistently misunderstand.

Providers file where they are registered and configured. They generally do not:

Determine your obligations. Whether an employee's situation creates a filing requirement in a state is the employer's determination, not the provider's.

Register for you in every case, and where they do, the employer usually still supplies the information and confirms the result.

Tell you an employee moved. They process what they are given.

Update the unemployment experience rate, which arrives by mail to the employer.

Handle local jurisdiction taxes reliably in every case, particularly obscure ones.

Manage the state programs, notices, or handbook obligations.

Close accounts when you exit a state.

A client who says "our provider handles multi-state" is describing the filing mechanics and not the compliance. The practitioner's contribution is knowing the difference and saying so.

Structured coverage is available through Multi-State Payroll Tax Compliance, the Certified Payroll Administrator and Certified Payroll Manager programs, the Payroll Boot Camp, the Payroll Operations Training and Certification Program, How to Have a Smooth Running Payroll Department, and the State Sick Pay Law Review.

The Cost Conversation

Worth having with a client before the next hire rather than after.

Each additional state carries a real ongoing cost: registrations, per-state filings, provider fees in some arrangements, workers' compensation coverage, state program contributions, notice compliance, and the internal time to maintain it. Plus the business-level obligations the employee may have created.

A client with employees in a dozen states should know what that costs annually, because the marginal cost of the thirteenth state is a decision input for a hiring manager who currently believes remote hiring is free.

Where Multi-State Payroll Breaks

• Work location stored as mailing address, corrupting everything downstream
• No registration before the first payroll in a new state
• Account numbers, frequencies, and credentials never recorded in one place
• Workers' compensation not extended to the new state
• State-required employee notices never issued
• The first payroll never hand-verified, so a configuration error runs for months
• Employee moves discovered late, from a benefits form or a casual remark
• The mid-year wage base handled mechanically and wrongly
• No policy on which states moves are permitted to
• A state exited and never closed, generating notices for years
• Filing frequencies assumed uniform across states or across tax types
• The experience rate not entered, running all year
• Travel days untracked for high earners where the exposure is material
• "Our provider handles it" accepted as a compliance answer
• The marginal cost of a new state never quantified for the client

The summary for a practitioner: insist on a work-location field separate from the mailing address, hand the client a ten-step runbook for adding a state and a matching one for leaving it, build detection for employee moves rather than relying on self-reporting, and be clear that the provider files where it is configured and determines nothing.

Frequently Asked Questions

What is the root cause of most multi-state payroll error?

Storing work location in the same field as mailing address. They are different facts, so an employee working from home in one state and receiving mail at a family address in another is taxed wrong, and an employee who updates their address for benefits has silently changed their tax situation with no payroll review. A distinct, required work-location field with a defined change process is the fix.

What must happen before the first payroll in a new state?

Determine the obligations; register separately with the withholding and unemployment agencies and any local jurisdiction, recording account numbers, deposit and filing frequencies, portal credentials, and contacts; configure the system and the rate; confirm workers' compensation coverage; enroll in state-mandated programs; complete new hire reporting; issue the state-required employee notices; address handbook applicability; hand-verify the first payroll; and diary that state's deadlines.

How should employee moves be detected?

By building detection rather than relying on policy alone. Route any address change to payroll rather than only to benefits, and watch for benefits changes referencing a new location, expense reports from a new origin, direct deposit changed to an out-of-state bank, and — the most common route — a manager mentioning it. Policy should also require reporting before the move, with the reason explained.

What happens if an employer stops having employees in a state but never closes the accounts?

Returns generally remain due — including zero returns in many jurisdictions — producing notices, penalties, and eventually estimated assessments. Accounts may accrue minimum assessments, the unemployment account remains chargeable for former employee claims, and the registration can support a presumption of continued activity. Final returns marked final, formal account closure, and retained confirmations are the exit runbook.

What does a payroll provider not handle?

Determining whether an employee's situation creates an obligation in a state; registering in every case; telling the employer an employee moved; entering the unemployment experience rate, which arrives by mail to the employer; local jurisdiction taxes in every case; state program enrollment, notices, and handbook obligations; and closing accounts on exit. Providers file where they are registered and configured.

Should a client restrict which states employees may move to?

It is worth considering. A move to a state where the employer has no presence creates registrations, filings, workers' compensation coverage, employment law obligations, and potentially income and sales tax nexus for the business. Some employers permit relocation only to an approved list for that reason, and a client who has never quantified the marginal cost of an additional state should before the next hire.