State Paid Family Leave Deductions: The Setup Multi-State Employers Miss

A hotel group with properties in more than a dozen states sat down to check something routine. Which of their states fund paid family and medical leave through payroll contributions, and was the deduction set up correctly at each property?

The answer was worse than they expected. At most properties the deduction had never been added at all. At the one property where it existed, the employee contribution rate was set to zero percent, so it had been running for months withholding nothing. Their VP of HR summed it up in six words: nobody knew we ever had to add it.

A paid family leave deduction is the kind of obligation that doesn’t announce itself. There’s no invoice, no vendor chasing you, and no error message. The payroll runs fine. It just runs wrong.

Last updated: August 2026

Why this one gets missed

Start with a distinction that trips up a lot of people. The federal Family and Medical Leave Act provides unpaid, job-protected leave for eligible employees. It doesn’t create a payroll deduction. State paid family and medical leave programs are a separate thing entirely: a paid wage-replacement benefit, usually funded by payroll contributions from employees, employers, or both.

If you’ve been treating FMLA compliance as the whole picture, the funding side has probably never come up.

A growing list of states now runs a mandatory program, including California, New Jersey, New York, Rhode Island, Washington, Massachusetts, Connecticut, Oregon, Colorado, Delaware, Maine, Minnesota, and the District of Columbia. Maryland is the next one coming. Its FAMLI program has had its start date pushed back more than once, and payroll deductions there now begin January 1, 2027, with benefits following a year later. Effective dates, contribution rates, wage bases, and the split between employer and employee vary by state and get adjusted regularly. Several were enacted years before contributions actually began, which is exactly how a requirement slips past a payroll team that checked once and moved on.

Confirm your own obligations directly with each state agency. Don’t rely on a list, including this one.

The zero percent problem

A missing deduction code is at least findable. A deduction code that exists and does nothing is harder, because every audit checklist that asks “is it set up?” returns a yes.

That’s what the hotel group found. The code was there. It had the right name. The employee deduction amount was zero, there was no maximum configured, and the deduction type was set to recurring. It had been faithfully recurring nothing.

Checking for existence isn’t enough. You have to open the code and read the rate.

There’s a second version of this worth looking for. Some states cap contributions at an annual wage base, similar to Social Security. If the cap isn’t configured, high earners keep contributing past the ceiling and you owe them a refund. Nobody complains about that one either, until they do.

Per-entity configuration is where it actually breaks

Single-location employers rarely have this problem. Multi-entity operators have it constantly.

The reason is structural. In most payroll systems, deduction codes are configured per company code, not once across the organization. So a hotel group with three properties in the same state has to set the same deduction up three times. Add a fourth property and somebody has to remember.

Listen to how that team described working through it. Their first question was whether they really had to do this separately for every property. The answer was yes. Their remediation plan became: pull the list of states, map which properties belong to each state, check every company code one at a time, then mass-update employees using a report-builder export and a file upload.

That’s a multi-week project to fix something that should have been a setup step. And it’s the same reason the gap opened in the first place. Configuration that has to be repeated per entity gets done inconsistently by definition.

Whose contribution is it, exactly?

Funding models differ more than most employers expect, and getting the split wrong creates a different flavor of problem.

• Employee-funded. The full contribution comes out of employee wages. Miss it and you’ve under-withheld, which usually means the employer absorbs the shortfall.
• Employer-funded. The employer pays the whole contribution. Miss it and you owe back contributions plus whatever penalty the state applies.
• Shared. Both sides contribute at a set ratio, sometimes with the employer share waived below a headcount threshold.

Some states also permit an employer to opt out with an approved private plan providing equivalent or better benefits. New York shows how two layers stack on top of each other. The benefit is delivered through an insurance policy the employer carries, but it is funded by an employee payroll deduction the state resets every year. For 2026 that is 0.432% of gross wages, capped at $411.91 annually. Carrying the policy does not mean the deduction is handled, and employers who assume it does are the ones who find nothing was ever withheld.

Remote employees complicate this further. Coverage generally follows where the employee performs work, not where your headquarters sits. One remote hire in a covered state can create a registration and withholding obligation nobody planned for.

How to audit your own setup

Borrow the hotel group’s method. It’s sound, even if the circumstances that produced it weren’t.

1. Pull a list of every state where you have at least one employee working, including remote staff.
2. For each state, confirm with the state agency whether a paid leave program is active, who funds it, and at what rate.
3. Map every company code or entity to the states it operates in.
4. Open the deduction configuration in each entity. Confirm the code exists, the rate is not zero, and any wage cap is set.
5. Spot-check actual pay stubs. A configured code still needs to be assigned to employees.
6. Reconcile withheld amounts against what you remitted for the last four quarters.
7. Document who owns the check when you enter a new state.

That last step is the one that prevents a repeat. Expansion into a new state is the trigger event, and it usually gets handled by whoever is closest to the hire rather than whoever understands the filing calendar.

When nobody knew the requirement existed

There’s an organizational failure hiding underneath the technical one, and it deserves naming.

An HR leader at another hotel management company inherited a paid leave setup that had gone wrong, and watched her organization blame the payroll vendor for it. Her own read was more honest. Nobody internally had known or communicated the requirements in the first place, and the vendor could only configure what it was told to configure. She’s since focused on getting requirements to her provider proactively rather than reacting after something breaks.

Payroll providers calculate and remit. They generally aren’t your compliance department, and they don’t know you opened a location in Colorado unless you tell them. Worth confirming which of the two you’ve actually bought.

Making state deductions less fragile

The fix isn’t more diligence. It’s fewer places to be diligent.

Netchex handles state and local tax setup as part of payroll and tax, including registration guidance when you enter a new jurisdiction, and files and remits on your behalf. For hospitality operators and other multi-entity businesses, deduction configuration can be applied across company codes rather than rebuilt property by property, which removes the specific failure mode that produced the gap above.

Your HR team still owns knowing where your people work. That part doesn’t outsource. But once the system knows, the deduction shouldn’t depend on someone remembering to set it up eleven separate times.

Frequently Asked Questions

This guide reflects publicly available product information and independent reviewer data (G2, Capterra, Trustpilot, Yelp, Better Business Bureau, Reddit, Software Advice, GetApp) as of 2026. Feature availability and pricing may vary by plan. Contact each provider for current details.

Disclaimer: Any product roadmap or future plans provided herein are for informational purposes only. They do not represent a commitment to deliver any material, code, feature, or functionality. Plans may change without notification. The development, release and timing of any features or functionality described remain at the sole discretion of Netchex, its affiliates, and partners. Netchex does not give legal, tax, or accounting advice. You are responsible for ensuring your use of Netchex product meets your individual business and compliance requirements.

Print this page