Paid Family and Medical Leave Compliance Across Multiple States

A company that hires its first remote worker in a new state does not just gain an employee. It gains a set of contribution duties that follow the work itself. Washington and Oregon both apply what is called a localization test, the same test each state already uses to determine state unemployment insurance liability, and it means contributions follow wherever the employee actually does the job. A company headquartered outside Washington with a single remote employee logging in from Washington may owe Washington PFML contributions for that one hire. That single fact is why a PFML policy written once and filed away stops matching reality the moment the company's hiring map changes.

Every state with a paid family and medical leave program builds, funds, and administers it independently, so a company with employees in multiple states carries a separate compliance obligation in each jurisdiction where work is actually performed. Both Washington and Oregon apply a localization test that ties contribution duties to wherever the employee does the job, meaning a single remote hire in a new state can trigger registration, withholding, and reporting requirements there regardless of where the employer is headquartered. Federal FMLA and each state PFML program run concurrently rather than as alternatives, and employers must track both clocks simultaneously or risk extending an employee's total protected leave period beyond what was intended. Private-plan alternatives exist in states including Massachusetts, New York, New Jersey, Washington, Oregon, Colorado, Delaware, Minnesota, and Maine, but each requires state approval plus annual re-approval and benefit-equivalence checks, and a lapsed approval leaves the employer liable for contributions to the state fund on top of what it already paid into the private plan.

The failure is often invisible until the employee files a claim for benefits and the state agency goes looking for contribution records that don't exist, at which point the employer is on the hook for back contributions, interest, and penalties all at once. The gap between the hiring decision and the discovery of the error can run for years, since nothing forces an audit until a claim triggers one.

The Family and Medical Leave Act of 1993 guarantees up to twelve weeks of unpaid, job-protected leave, extending to 26 weeks for military caregiver leave, but it guarantees no pay during that leave. Every dollar of wage replacement an employee receives while out on leave comes from a state program, built, funded, and administered differently in each state that has one. Congress has not closed that gap. The bipartisan working group proposals circulating in Washington focus on grant funding to help states stand up their own programs, not on building one uniform federal standard that would let a multi-state employer apply a single policy everywhere. Until that changes, every new hire in a new state is, in effect, a new compliance jurisdiction.

How fast the PFML map is expanding in 2026

The map an employer has to track is not holding still. Thirteen states and Washington, D.C. now require paid family and medical leave, and 2026 alone brought several programs online while pushing others further down a legislated runway. That pace matters because it means the operational burden described elsewhere in this piece is not a fixed cost employers can absorb once and forget. It grows every year a new state joins the list.

Delaware's Family and Medical Leave Insurance Program began accepting employee claims for benefits on January 1, 2026, and employers there must post and distribute required notices at hire, when leave is requested, or as soon as the employer learns of a qualifying event. A July 30, 2025 amendment, House Substitute 1 for House Bill 128, removed the ability of Delaware employers to force workers to burn through accrued PTO before applying for benefits, though both sides can still agree voluntarily to a top-off arrangement. Minnesota's Paid Family and Medical Leave program also started paying benefits on January 1, 2026, and employers there now have to coordinate payroll withholding and reporting for every category of worker, including remote and seasonal staff. Washington's program, already running, expanded further on January 1, 2026, raising premium rates and tightening job-protection requirements. Employers there must adopt new contribution splits and keep health coverage active for any employee on protected PFML leave, joining Delaware and Minnesota among the states where new or expanded programs took effect or are actively paying benefits in 2026.

Two more states are on a defined but later schedule. Virginia became the first Southern state to enact a mandatory PFML program, signed into law on April 22, 2026, with contributions beginning April 1, 2028, and benefits following on December 1, 2028. Maryland's FAMLI program, already delayed once, now has contributions starting January 1, 2027, with benefits required no later than January 3, 2028.

Other states are expanding programs that already exist rather than launching new ones. Connecticut's paid sick leave law widens its coverage to employers with 11 or more employees starting January 1, 2026. New York City amended its Earned Safe and Sick Time Act through City Council action, adding new unpaid safe and sick leave banks and broadening the list of qualifying reasons for leave. Alongside the mandatory states, New Hampshire's Granite State Paid Family Leave, in place since January 2023 and underwritten by MetLife, and Vermont's VT-FMLI, covering state employees since July 2023 and the broader market since July 2024 and underwritten by The Hartford, maintain voluntary state-sponsored markets rather than mandates. None of these states are retreating from paid leave. The direction of travel across the country runs toward more states adopting either mandatory or voluntary programs, not fewer, and a growing list of additional states have already passed voluntary or private-insurance-based laws that have yet to take full effect.

What are the most common payroll and HR compliance mistakes when managing employees across multiple state PFML programs?

Most of the liability employers face under PFML law doesn't come from not knowing the rules exist. It comes from a short list of operational errors that recur across companies, each with its own distinct way of generating exposure. The first is treating a remote hire as though the rules that govern the company's headquarters apply to that employee too. A Texas-headquartered company with a remote worker based in Washington may owe Washington PFML contributions under RCW 50A.10.025, because both Washington and Oregon apply the same localization test used for unemployment insurance to decide which state's rules govern the work. The mistake often goes unnoticed for a long stretch, since nothing forces the issue until the employee files a benefit claim that the state agency cannot match to any contribution record, at which point back contributions, interest, and penalties land on the employer all together.

The second mistake is failing to designate FMLA leave at the same time an employee goes out on state PFML. When HR treats the PFML claim as a stand-alone benefit and never issues the FMLA designation notice, the employee's 12-week FMLA entitlement is never charged. The FMLA clock never actually starts running. The employee can then take additional unpaid FMLA leave on top of the paid state benefit they already used, and the employer ends up owing weeks of job-protected leave it believed it had already accounted for.

The third mistake involves the private-plan opt-out that several states allow in place of the state fund. Massachusetts, New York, New Jersey, Washington, Oregon, Colorado, Delaware, Minnesota, and Maine all let employers use a private plan instead of the state program, but only with state approval, and that approval comes with annual re-approval, financial-soundness reviews, and benefit-equivalence checks. If that approval lapses, or gets denied after the fact, the employer owes contributions to the state fund on top of what it already paid into the private plan, effectively paying twice for the same coverage.

The fourth mistake sits in how employers handle taxes when they voluntarily cover the employee's share of the PFML premium. Law § 195(3).

The fifth mistake is mishandling how PTO interacts with PFML benefits. DOL Opinion Letter FMLA2025-01-A reinforces that once an employee is receiving state paid leave payments, neither the employer nor the employee can unilaterally require PTO to run at the same time. Both sides have to agree, though they remain free to agree voluntarily to a top-off. A company that applies a single "exhaust PTO first" policy across a workforce spread over several states is very likely violating the law in at least one of those states, since the rules on this point are not uniform from state to state.

How federal FMLA and state PFML interact in practice

Federal FMLA and state PFML are not two versions of the same protection that an employer can choose between. They run at the same time, and how they interact determines who is actually eligible to take leave, how long that leave can last, and what the employer is required to track on each separate axis.

FMLA sets a federal minimum that applies to employers with 50 or more employees on payroll during at least 20 workweeks in the current or preceding calendar year, counted at the worksite level within a defined radius, and no state law can reduce the protection FMLA provides, even though states remain free to add to it. To actually qualify for FMLA leave, an employee needs 12 months of employment with that employer, which does not have to be consecutive, a minimum number of hours worked over the preceding 12 months, and a work location where the employer has at least 50 employees within 75 miles. For a company with staff spread across many states, that count has to be done location by location rather than as one company-wide tally. A direct consequence follows from that structure: an employee working out of a small satellite office may not qualify for FMLA at all, even if the company employs thousands of people nationwide, while that same employee can still be fully covered by their state's PFML program based purely on where they work.

Where FMLA does apply, it carries its own job restoration guarantee. The employer must return the employee to the same job or an equivalent one, with equivalent pay, benefits, and working conditions, and group health coverage has to stay in place on the same terms it would have if the employee had kept working the whole time.

Intermittent leave is where this coordination gets hardest to manage. Every intermittent absence has to be counted against the employee's 12-week annual FMLA entitlement, adjusted proportionally for the employee's normal schedule, and tracked in whatever increment the employer already uses for other leave types, usually one hour. An employee managing a single chronic condition can generate hundreds of separate deductions against that entitlement over the course of a year, each one requiring its own accurate tracking.

The consequence of getting the coordination wrong runs directly back to the fourth mistake described above. When HR treats PFML and FMLA as separate "buckets" instead of one concurrent clock, the FMLA clock never starts, and the employee retains the right to take additional unpaid FMLA leave afterward, doubling the effective leave period at the employer's expense. Colorado adds a further wrinkle to this picture through its own FAMLI program, which layers state-specific coordination requirements on top of the federal baseline and requires separate attention from any employer running a workforce in that state.