Has your move to remote work inadvertently transformed your business into a multi-state compliance nightmare? The complex, ever-changing patchwork of state leave laws, payroll taxes, and pay transparency rules that now applies to distributed teams is one of the most underestimated operational risks in HR today.
At Lift HCM, we understand the constant stress and administrative burden that comes with managing a distributed workforce. With years of experience helping employers navigate the complexities of multi-state compliance, we are experts in building systematic, audit-ready HR operations that adapt to a shifting legal landscape.
This article walks you through the three critical layers of multi-state compliance: understanding your legal obligations, configuring your payroll and HR systems, and building the repeatable workflows that keep you compliant as your team and the law keep evolving. By the end, you'll have a clear strategy to keep your remote team compliant and mitigate the risk of costly penalties and lawsuits.
Table of Contents
2: Configuring Payroll, Time, Benefits, and Policies for Multiple States
Frequently Asked Questions: Multi-State Employment Compliance
Summary: Multi-State Employment Compliance for Remote Teams
If you have remote employees working in multiple states, you must follow the labor laws of each state where they physically work, not just your home state. That means separate payroll tax registrations, state-specific leave programs, minimum wage compliance, pay transparency rules, and electronic labor law posters for every state in your workforce's footprint. Getting this wrong is one of the most common and costly compliance mistakes for distributed teams.
The foundational rule of multi-state compliance is deceptively simple: employment law generally follows the employee, not the employer. The state where an employee physically performs their work is typically the state whose wage and hour, leave, posting, and tax rules apply, regardless of where your company is incorporated or headquartered.
A recent federal appellate case, Kuklenski v. Medtronic USA (8th Cir., April 2025), clarified that a Minnesota-based employer was not automatically subject to Minnesota discrimination law for a remote employee who stopped traveling to the state after February 2020; the court required “some degree of physical presence.” This underscores that multi-state compliance depends on where work is actually performed and whether that creates a real legal nexus.
For every worker on your team, you need to know:
This is not a one-time exercise. People move. Remote arrangements change. Build a process that flags employee location changes at the HR intake and during annual data audits, and routes them to your payroll and HR teams for configuration updates.
Your first compliance deliverable should be a living document: a table or dashboard that lists every state where you have employees and tracks:
The Most Common Mistake: Assuming HQ State Rules Apply Everywhere
Many growing companies configure payroll and policies once based on their home state and never update them as the team expands remotely. The result can be employees in other states paid below local minimum wage, missing PFML enrollment, on the wrong leave policy, or lacking required notices—gaps that state agencies and plaintiffs’ attorneys increasingly target.
Before layering on state rules, confirm your federal foundation is solid. These apply across your entire workforce once you hit the relevant thresholds:
State and local laws layer on top of these federal minimums, often with higher wages, broader leave rights, stricter anti-discrimination standards, or additional notice requirements. When state and federal rules conflict, the more protective rule for the employee generally applies.
Multi-state payroll is one of the highest-stakes areas of remote compliance. Getting it wrong can mean underpaid SUI contributions, incorrect income tax withholding, and exposure to penalties in states you may not even know you're registered in.
The core principle: Withhold income tax and contribute to SUI for the state where the employee's work is localized, generally where they work from home or perform services.
📌 Payroll System Tip: Configure each employee's payroll record with their primary work state (and city/county, if relevant). When an employee moves, update this before the next payroll run, not retroactively months later. Many HCM platforms allow location-based tax configuration at the employee level. Use it.
With a distributed remote team, you may have employees on the same project who are owed different minimum wages, overtime calculations, or break entitlements based purely on where they sit.
|
State / City |
2025-2026 Minimum Wage |
Notes |
|
Federal (FLSA) |
$7.25/hr |
Floor; most states exceed this |
|
Illinois |
$15.00/hr (state); $16.20/hr (Chicago, eff. July 1, 2026) |
Chicago adjusts July 1 annually via CPI |
|
California |
$16.90/hr (state); higher in many cities |
LA, SF, and others are higher; always apply the highest applicable rate |
|
New York (NYC/LI/Westchester) |
$17.00/hr; $16.00/hr (rest of state) |
Both effective Jan. 1, 2026; statewide indexes to inflation starting 2027 |
|
Washington |
$17.13/hr |
Highest statewide rate nationally; CPI-indexed annually |
|
Colorado |
$15.16/hr (state); $19.29/hr (Denver) |
CPI-adjusted; check annually |
|
Florida |
$14.00/hr (current); $15.00/hr (eff. Sept. 30, 2026) |
Final scheduled increase under Amendment 2; inflation-indexed from 2027 |
|
Texas, Tennessee, and others |
$7.25/hr |
Default to federal; no state minimum above federal |
For a full breakdown of every 2026 state and city rate, including tipped wage rates and mid-year increases, see our 2026 Minimum Wage Guide by State.
Always apply the highest applicable rate (state, county, or city) based on where the employee's work is performed. For overtime, most states follow the federal 40-hour weekly threshold, but California requires daily overtime (over 8 hours in a day), a critical difference for non-exempt employees.
State Paid Family and Medical Leave (PFML) programs are the fastest-growing compliance obligation for multi-state employers in 2025-2026. As of April 2026, 13 states plus D.C. have enacted mandatory PFML programs, and three launched new or expanded programs in 2026 alone.
Want to learn more about the Illinois Paid Leave Laws? We've got you covered! Check out: Illinois Paid Leave Laws: Payout Rules for Employers
|
State |
Program Status (as of Apr. 2026) |
Key Details |
|
California |
Active |
Up to 8 weeks PFL; employee contributions |
|
Colorado |
Active (expanded 2026) |
Up to 12 weeks FAMLI; added NICU Neonatal Care Leave Jan. 1, 2026 (up to 12 additional weeks, for up to 24 weeks total) |
|
Connecticut |
Active |
Up to 12 weeks; shared contributions |
|
Delaware |
Benefits began Jan. 1, 2026 |
State-administered via Delaware LaborFirst; applies to employers with 10+ employees (bonding) and 25+ (medical/caregiver) |
|
Illinois |
Paid Leave for All Workers Act |
40 hours/year; all employers; any reason; in effect since Jan. 2024 |
|
Maine |
Benefits begin May 1, 2026 |
Up to 12 weeks; contributions started Jan. 2025; applies to all private employers of any size |
|
Maryland |
Contributions begin Jan. 2027; benefits Jan. 2028 |
Delayed timeline; plan ahead now |
|
Massachusetts |
Active |
Up to 26 weeks combined; shared contributions |
|
Minnesota |
Benefits began Jan. 1, 2026 |
Up to 20 weeks combined; all employer sizes covered |
|
New Jersey |
Active |
Up to 12 weeks; employee contributions |
|
New York |
Active |
Up to 12 weeks PFL; employee contributions |
|
Oregon |
Active |
Up to 12 weeks; shared contributions |
|
Rhode Island |
Active (expanded 2026) |
Up to 8 weeks; expanded from 7 in 2025; now includes bone marrow, organ donation, and siblings as covered family members |
|
Washington |
Active |
Up to 12 weeks; shared contributions; expanded job restoration rights for employers of 25+ eff. Jan. 1, 2026 |
|
Washington D.C. |
Active |
Up to 12 weeks; employer-funded |
Several states require employers to reimburse employees for necessary business expenses incurred while working, and for remote workers, that includes home office costs like internet, phone, and equipment. California has the most robust rule: under Labor Code 2802, employers must reimburse all necessary expenditures regardless of company policy, and failure to do so exposes them to class action liability. Illinois (820 ILCS 115/), Massachusetts, Montana, Iowa, and a growing number of states have similar requirements. If you have remote employees in any of these states, a clearly written remote work expense policy that defines what is reimbursable, sets a submission process, and meets the strictest standard applicable in your workforce is not optional. It is a compliance requirement.
A single-state employee handbook doesn't work for a multi-state team. You have two options, and most growing employers end up using both:
Configure your HCM so that employees see (and must acknowledge) the policies and notices that apply to their location. Location-based policy routing is a standard feature in most modern HCM platforms and eliminates a major source of compliance risk.
Every state where you have employees requires that you display certain labor law posters. For remote employees, 'display' means electronic delivery, and several states explicitly require it.
Multi-state compliance is not a project you complete. It's an ongoing operational system. Employees move, states adopt new laws, and enforcement evolves. The employers who stay ahead of this are not necessarily those with the biggest legal budgets; they're the ones with the most systematic processes.
Compliance gaps almost always trace back to unclear ownership. Assign specific internal owners for each compliance domain and make accountability explicit. Meet at least quarterly as a compliance working group to review your remote footprint, flag upcoming law changes, and confirm that your HCM and payroll configurations match reality.
|
Compliance Domain |
Suggested Owner |
Frequency of Review |
|
Payroll tax registrations |
Payroll Manager / Controller |
At every new hire in a new state |
|
Wage and hour configuration |
Payroll + HR jointly |
Quarterly + at annual minimum wage changes |
|
State leave programs |
HR / Benefits Administrator |
Quarterly; at new PFML program launches |
|
Labor law posters and notices |
HR Compliance or Office Manager |
Annually + when laws change |
|
Pay transparency in postings |
HR / Talent Acquisition |
At each new requisition |
|
AI tool audit |
HR + IT/Legal |
Before deploying any new hiring tool |
|
EEO / harassment policies |
HR / Legal |
Annually + when new laws take effect |
|
New hire reporting |
HR / Payroll |
Within 20 days of each hire |
A strong HCM and payroll system can automate many of the heaviest multi-state compliance tasks: jurisdiction-based tax configuration, minimum wage updates, PFML contribution calculations, location-triggered policy routing, and digital notice delivery.
When evaluating or optimizing your platform, ask specifically:
Does it support multi-state payroll configurations at the employee level?
Does it automate minimum wage and SUI wage base updates by state?
Can it route different policies and notices to employees based on location?
Can it generate per-state compliance reports for audits?
With the right backbone in place, multi-state compliance becomes a manageable quarterly ritual, not a constant emergency.
Yes. Employment law generally follows the employee, not the employer. The state where your employee physically performs their work determines which wage, leave, tax withholding, and posting rules apply, regardless of where your company is headquartered or incorporated.
You can be held liable for compliance failures in the new state even if you didn't know about the move. This is why building a location-change notification process into your onboarding and annual data audits is critical. When an employee relocates, payroll configuration, leave enrollment, and applicable policies all need to update before the next pay run.
California, Illinois, Colorado, New York, and Washington consistently rank as the most complex, with overlapping obligations across PFML, minimum wage, pay transparency, expense reimbursement, and (in Illinois) AI hiring regulation. California's expense reimbursement law and daily overtime rule are particularly easy to miss for employers based elsewhere.
Yes, in most cases. You typically need to register for income tax withholding and state unemployment insurance (SUI) in every state where an employee works. You may also need to register for workers' compensation and enroll in state PFML programs. Most registrations must be completed before the employee's first payroll run in that state.
Almost certainly yes. Colorado, Illinois, New York, and Washington apply their pay transparency requirements based on where applicants are located, not just where the employer is based. If a remote role is open to applicants in those states, including the salary range in the posting is the safest approach regardless of where your company is headquartered.
New hire reporting is the federal requirement to report each new employee to the state directory within 20 days of hire, primarily for child support enforcement purposes. All employers must comply under federal law (PRWORA), and some states have shorter deadlines. You report to the state where the employee works. Rehires after a separation of more than 60 days also count as new hires for reporting purposes.
For remote employees, "displaying" required posters means electronic delivery. Maintain a digital notice portal (such as an intranet page or HCM document library) where all applicable federal, state, and local posters are kept current. Send new employees a link at onboarding, document the delivery, and re-notify employees whenever posters are updated.
Paid Family and Medical Leave (PFML) provides wage replacement for longer absences such as bonding with a new child, caring for a seriously ill family member, or the employee's own serious health condition, typically for weeks at a time. Paid sick leave covers shorter absences for the employee's own illness, preventive care, or in many states, family care needs. As of 2026, 13 states plus Washington D.C. jurisdictions have mandatory PFML programs and more than 20 states have paid sick leave laws. A state can have one, both, or neither.
At minimum once per year, ideally in Q4 before January law changes take effect. Your audit should include sampling payroll configurations and leave enrollments by state, verifying labor law poster versions, reviewing job postings for pay transparency compliance, confirming new hire reporting is current, and checking whether any employees have relocated without triggering a compliance update. Many employers also run a lighter mid-year check in June ahead of July 1 effective dates.
Multi-state employment law compliance is one of the most complex operational challenges for remote-first employers, but it's manageable when you treat it as a system rather than a one-time project. Map your footprint, configure your platforms to reflect reality, assign clear ownership, and build the monitoring habits that catch changes before they become penalties.
The states in your workforce's footprint are not standing still. New paid leave programs, pay transparency mandates, and AI regulation are rolling out on a near-continuous basis. The employers who build systematic compliance programs today will be far better positioned to absorb those changes and grow their remote teams with confidence.
If you have questions about how multi-state payroll or HR compliance affects your specific workforce, our team at Lift HCM works with small and mid-sized employers across industries to keep payroll accurate and compliant, no matter how many states your team spans.