Distributed teams turn payroll into a jurisdiction puzzle. A hire in one state, a move to another, and a week of client work in a third can each trigger withholding, unemployment insurance, or paid-leave obligations you did not model at offer stage. The surprise arrives as a penalty notice, a worker complaint, or an employee whose net pay shifts without explanation.
Growing SMBs often treat address changes as HRIS hygiene—update the field, move on. Payroll compliance requires sequencing: address change → payroll review → employee confirmation → HRIS update. Manager approval alone is not enough; managers rarely know whether your company has nexus for unemployment in the destination state.
#Gate every move before payroll changes
Relocation should start with a form, not a Slack message. The form captures effective date, residential address, work location pattern (fully remote, hybrid days in office, temporary travel), and whether the move is permanent or exploratory.
That submission triggers an automatic payroll ticket. HR ops validates employment type and start date; payroll validates withholding, unemployment, and any local taxes. Only after payroll approves does HRIS update—and the employee receives written confirmation of tax impact before the move is treated as final.
Tip. Block "confirmed" status in the relocation workflow until payroll sign-off. If your HRIS allows address edits without workflow, disable self-service address change for W-2 employees or route edits through the same ticket.
#Maintain a living nexus matrix
Compensation and HR ops should co-own a nexus cheat sheet: one row per state where you have employees or active recruiting, columns for income tax withholding registration, unemployment account, paid family leave overlay, city or county taxes, and last review date.
Review the matrix quarterly and after every headcount plan. New hires, office closures, and fully remote expansions each change exposure. Pair the matrix with your remote work policy refresh so policy language matches payroll reality—if policy allows work-from-anywhere but payroll is registered in only three states, you have a gap to close or a policy to narrow.
Document who owns registration renewals and rate notices. Unemployment rate changes often arrive by mail to an old registered agent address; missed updates compound silently until an audit.
#Withholding versus unemployment: different triggers
Employees conflate "payroll takes the right tax" with "we are compliant everywhere." Withholding follows where work is performed and where the employee lives, depending on state rules and reciprocity agreements. Unemployment follows where the employee performs services for the employer's benefit—often the work state, not merely the mailing address.
A remote employee who moves from State A to State B may require new State B withholding immediately while unemployment remains in State A until you analyze whether services are performed in B. Payroll vendors automate much of this, but automation assumes correct work-location codes in the HRIS—garbage in, penalty out.
Train recruiters and managers: "They can work from there" is a policy question and a payroll question. Recruiting should not promise location flexibility without a payroll pre-check for common destination states.
#Communicate tax impact before confirmation
Employees experience net pay changes as betrayal when nobody warned them. Before confirming a move, provide a plain-language summary: expected withholding change, any new local taxes, paid-leave deductions if applicable, and whether the company will adjust gross pay for cost-of-living (if that is your philosophy—consistency matters more than the direction of adjustment).
If payroll cannot estimate until the first run in the new jurisdiction, say so and commit to a follow-up date after the first paycheck. Silence reads as incompetence or concealment.
Keep a template email approved by counsel—tax language is sensitive. Store confirmations in the employee file alongside the approved relocation form.
Tip. For multi-state travelers, define a temporary assignment threshold in policy (e.g., more than twenty working days in another state triggers review). Ad hoc travel without tracking is how nexus accretes unnoticed.
#New hires: jurisdiction at offer, not at start
Offer letters should name primary work state and remote-work expectations. Background checks, I-9 worksite rules, and workers' compensation classifications often hinge on the same facts payroll needs.
If a candidate wants to relocate within the first ninety days, treat it as a new payroll review—not an informal address tweak. Starting in one state and moving before registrations complete is a common SMB failure mode.
Align with labor compliance for SMBs checklists: headcount-indexed obligations change when you cross state thresholds for paid leave, pay transparency, or predictive scheduling—payroll nexus and labor law nexus are related but not identical.
#What breaks distributed payroll—and how to fix it
HRIS address updated first. Payroll runs in the wrong state; employee owes at year-end. Fix: workflow order enforced by system or checklist; payroll approval gate.
Manager-only approval. Manager does not know unemployment rules. Fix: payroll ticket mandatory; manager approval is input, not authorization.
Stale matrix. You hired in four new states since last review. Fix: quarterly calendar hold with compensation + payroll + legal; update matrix before recruiting expands.
Vendor set-and-forget. Payroll provider flags unregistered state; nobody acts. Fix: assign owner to vendor alerts; SLA to register or restrict hiring.
Employee self-service drift. Digital nomads update address without ticket. Fix: disable or intercept self-service; communicate why.
#Operational checklist for relocations
- Relocation form submitted with effective date and work pattern
- Payroll ticket opened automatically from form submission
- Nexus matrix consulted; new state registration initiated if required
- Employee tax impact summary sent before final confirmation
- Payroll approval recorded; HRIS update follows approval
- Workers' compensation and paid-leave overlays verified
- Manager notified of any policy constraints (office days, travel limits)
- Confirmation stored in employee file with approver names and dates
#Integrate nexus review into headcount planning
When finance models new hires by region, payroll should see the plan before offers go out. A cluster of five hires in an unregistered state is cheaper to register proactively than to remediate under audit pressure.
Executives often ask for "hire anywhere" as a talent strategy; payroll and legal translate that into a registered anywhere list or a narrower approved-state list. Publish the approved list to recruiting so sourcers do not pipeline candidates you cannot employ compliantly on the desired timeline.
Treat nexus maintenance as infrastructure, not a one-time project. States change reciprocity rules, paid-leave programs expand, and city taxes appear. The living matrix is how SMBs avoid enterprise-scale surprises without enterprise-scale headcount.
#Related guides
Sources
- Internal Revenue Service. State Links
- American Payroll Association. Payroll Compliance
This article is operational education only, not legal advice. Work with qualified counsel for compliance, compensation, and termination decisions in your jurisdiction.