Employee Benefits
HR & Compliance
Technology
Wellness
PEO Solutions
If you're running payroll in Washington, fielding employee benefits questions, or trying to keep a multi-state workforce compliant, the Washington Cares Act probably isn't sitting in a neat bucket. It touches payroll, employee communication, exemption tracking, and benefits strategy all at once. That's why it tends to create more operational drag than a simple line item deduction would suggest.
For employers, the challenge isn't understanding that the program exists. It's building a repeatable process so payroll withholds correctly, exempt employees are handled correctly, and your team can answer the inevitable question: what does this mean for me?
Table of Contents
- What Is the Washington Cares Act
- Payroll Tax Mechanics for Employers
- Understanding Exemptions and Employee Opt-Outs
- Employer Responsibilities and Compliance Timeline
- Strategic Implications for Your Benefits Package
- A Step-by-Step WA Cares Compliance Checklist
What Is the Washington Cares Act
The Washington Cares Act created a state-run long-term care program for Washington workers. Washington's WA Cares Fund was enacted in 2019, signed by Governor Jay Inslee on May 13, 2019, financed by a 0.58% payroll tax on employee wages, and scheduled to begin paying benefits in July 2026. It provides a lifetime benefit of $36,500, adjusted for inflation, for eligible Washington residents age 18 and older who need long-term services and supports, according to the Center for Retirement Research at Boston College summary of WA Cares.
Why the program exists
At a practical level, the state is trying to solve two problems at once. First, workers often have no dedicated plan for long-term care. Second, when care needs arrive without funding, public systems often absorb more of the cost over time.
That makes employers part of the operating model, even though the benefit itself is public. Payroll teams collect the premium. HR teams answer questions. Benefits leaders decide whether the state program is enough on its own or whether employees need additional education around financial protection with long term care.
Practical rule: Treat WA Cares as both a payroll requirement and an employee financial wellness issue. If you treat it as payroll only, questions will spill into HR anyway.
What employees actually receive
Employees often hear "long-term care program" and assume broad coverage. That assumption creates confusion. WA Cares is better understood as a baseline public benefit, not a full replacement for every long-term care scenario an employee might face.
For employers, that's the useful framing. The program is intended to help with long-term services and supports, and it creates a state-administered layer of protection. It does not eliminate the need for employees to think carefully about future care planning, especially if they expect higher costs, want more flexibility, or already evaluate private coverage alongside public programs.
A clear employer message usually works best when it includes these points:
- State program: WA Cares is administered by Washington, not by an employer-sponsored carrier.
- Employee-funded premium: The money comes from employee payroll deductions rather than an employer match.
- Defined cap: The program has a fixed lifetime benefit ceiling rather than open-ended reimbursement.
- Workforce impact: Because payroll and eligibility administration run through the workplace, employers become the first stop for employee questions.
That last point matters more than many realize. Even when you aren't giving legal advice, employees will look to payroll, HR, and benefits for interpretation. A short internal explainer and manager talking points can prevent a lot of avoidable confusion.
Payroll Tax Mechanics for Employers
The payroll side of the Washington Cares Act is straightforward on paper and easy to mishandle in execution. WA Cares is funded by a 0.58% payroll premium on gross wages with no cap, collected from Washington employees and remitted by employers. Because the wage base is uncapped, a $100,000 wage base implies $580 per year in premium liability, while the maximum lifetime benefit remains fixed at $36,500, as outlined in this employer compliance overview from Sequoia.
How the deduction works
The key phrase is gross wages with no cap. Employers shouldn't think about this deduction the way they think about capped wage-based taxes. The WA Cares premium keeps applying as compensation rises.
That means your payroll system needs to answer a few basic questions correctly every pay cycle:
- Who is subject to withholding: Employees with Washington wages that fall under the program.
- What compensation is included: Gross wages used for the deduction calculation.
- How the amount is calculated: Multiply applicable wages by the premium rate.
- When to stop withholding: Only after a valid exemption or another valid status change has been processed.
A quick example helps. On a $100,000 wage base, the annual employee premium is $580 under the WA Cares rate in the Sequoia example above. Payroll teams don't need complicated formulas. They need clean configuration and reliable exception handling.
What employers are responsible for
Employers don't pay into the fund directly. Their role is administrative, but it isn't optional. You collect the employee premium through payroll and remit it to the state.
In practice, that means HR and payroll should coordinate on four items:
- Payroll coding: Set up the deduction correctly and test it before each relevant payroll cycle.
- Employee status handling: Know when a Washington work location or exemption status changes deduction treatment.
- Reporting discipline: Make sure payroll data and remittance records line up.
- Tax treatment alignment: Review how the deduction interacts with broader payroll practices and related questions, especially where teams also field questions about items like state disability insurance tax treatment.
If your payroll team has to manually correct WA Cares deductions often, the problem usually isn't the tax. It's employee classification, work location coding, or missing exemption workflow.
One operational mistake shows up repeatedly. Employers assume the deduction is "set and forget." It isn't. It's simple only if your employee data is current. A relocation, a payroll system migration, or an acquired entity can all create deduction errors fast.
Understanding Exemptions and Employee Opt-Outs
Many employers lose time, not because the concept is complicated, but because employees tend to bring partial information, old approval letters, or assumptions that HR can decide exemption status on the spot.
The employer's role is narrower than employees often think. Employers generally don't approve exemptions themselves. They respond to valid employee documentation, apply payroll changes correctly, and maintain records.
Private coverage exemptions
The most discussed exemption path has involved employees who previously secured qualifying private long-term care insurance and obtained exemption approval through the state's process. In day-to-day administration, the practical employer question is simple: has the employee provided the required written proof that supports stopping deductions?
If the answer is no, withholding usually shouldn't stop based on a verbal request alone. If the answer is yes, payroll needs a dated process for when deductions stop and a record of why.
A workable internal process looks like this:
- Require written documentation: Don't act on Slack messages, hallway conversations, or manager requests.
- Validate completeness: Check that the document clearly identifies an approved exemption or other qualifying status.
- Document the effective change: Record when payroll stopped withholding and who approved the change internally.
- Store the file consistently: Keep exemption records in the same secure system used for other payroll-sensitive documentation.
Employees may assume that buying a policy, moving, or changing personal circumstances automatically updates payroll. It doesn't. Payroll only changes when the employer has the right documentation and processes it correctly.
Other exemption categories employers may encounter
Some employees may fall into other exemption categories or special statuses. From an employer perspective, the exact legal basis matters less than process discipline. You need a repeatable way to identify when an employee may be exempt, collect the required proof, and update payroll only when the documentation supports it.
Common employer pain points include:
- Residency changes: A worker may live outside Washington while remaining on your payroll structure in a way that raises WA Cares questions.
- Military-related statuses: Employees and spouses may ask about military-linked exemption treatment.
- Temporary worker situations: Visa-related status can affect how employers think about payroll deductions and employee communication.
- Prior exemptions that need follow-up: Legacy files often create the most confusion during payroll transitions.
What doesn't work is letting each request get handled differently by a different administrator. That creates inconsistent outcomes and refund risk. A simple intake form, a standard checklist for reviewing documents, and one owner for final payroll instructions usually solve most of the friction.
A good rule for HR teams is to separate employee education from employer action. You can explain the process, direct employees to the appropriate state materials, and tell them what documentation payroll requires. You shouldn't improvise your own exemption standard.
Employer Responsibilities and Compliance Timeline
WA Cares compliance is easiest when employers treat it as a timeline with recurring checkpoints, not a one-time setup. The fund's latest actuarial valuation shows a $4.4 billion actuarial balance as of June 30, 2024, and a separate legislative report estimates about $70 million in Medicaid savings in 2027, rising to $360 million in 2050, according to the Washington actuarial valuation report. For employers, the takeaway isn't just public finance. It's that the system depends on consistent collection, reporting, and exemption handling.
What the timeline means in practice
The first employer responsibility is communication. Employees notice deductions fast. If your organization doesn't explain what the deduction is, who pays it, and where questions should go, payroll gets flooded with avoidable tickets.
The next responsibility is system setup. Payroll has to calculate the deduction accurately, tie it to the right employee population, and keep reporting records clean. If you use outside support for payroll or broader HR administration, this is one of the areas where teams often revisit whether a professional employer organization model fits their compliance operations.
After setup comes ongoing administration. That's the part many teams underestimate. WA Cares isn't hard because the formula is hard. It's hard because employee statuses change, exemptions arrive midstream, and reporting still has to match what payroll processed.
A practical internal timeline usually includes:
- Initial employee notice: Explain the deduction and direct employees to the right internal contact.
- Payroll activation: Confirm deduction logic and employee population before live payroll runs.
- Quarterly reporting rhythm: Reconcile what was withheld with what will be reported and remitted.
- Exemption intake review: Check whether any newly received documents require payroll changes.
- Annual policy review: Audit your own process, especially after payroll vendor or workforce changes.
Where employers usually get tripped up
Most compliance failures aren't dramatic. They're procedural. A deduction continues after an approved exemption was received. A newly hired Washington employee isn't coded correctly. An HRIS field doesn't sync to payroll. The result is the same. Manual cleanup.
The best WA Cares workflow is boring. The moment it depends on memory, inbox searches, or individual judgment calls, errors start showing up.
Keep records in one place. Define who can approve payroll changes. Reconcile every reporting cycle. Those habits matter more than any standalone memo or FAQ.
Strategic Implications for Your Benefits Package
WA Cares doesn't just create a deduction. It changes the benefits conversation, especially for employers competing for experienced talent or supporting a highly compensated population.
The strategic tension is easy to understand. The WA Cares benefit is capped at $36,500, while premiums remain 0.58% of gross wages with no cap. A $200,000 earner pays about $1,160 per year, which raises a real question about value for higher earners, as discussed in this Washington-focused legal explainer from Super Lawyers.
Why WA Cares changes benefits conversations
For lower and mid-wage employees, the state benefit may feel like a welcome floor of protection. For higher earners, the same program often prompts tougher questions. They may see the payroll deduction as mandatory participation in a benefit that won't align closely with what they'd want from a private long-term care solution.
That doesn't make WA Cares bad policy. It means employers should expect segmentation in employee reaction.
I've seen this dynamic play out in benefits meetings in a familiar way. One group asks, "What does this cover?" Another asks, "Can I supplement this?" A third asks, "Am I overpaying relative to the benefit?" Those are different questions, and they need different answers.
A smart employer response usually includes:
- Clear framing: Present WA Cares as a public baseline, not as a complete long-term care strategy for every employee.
- Audience-specific communication: New managers, hourly teams, executives, and multi-state employees often need different explanations.
- Voluntary benefit evaluation: Consider whether private long-term care coverage belongs in your broader menu.
- Recruiting alignment: Make sure candidates understand whether your company offers anything beyond the state framework.
Where private LTC and PEO support fit
Private long-term care coverage becomes a strategic discussion because WA Cares may not feel proportionate for every employee group. That's especially true when a highly compensated employee sees an uncapped payroll premium attached to a fixed state benefit.
That doesn't mean every employer should rush to add private LTC. In many cases, the better first move is to ask a few decision questions:
| Decision area | What to evaluate |
|---|---|
| Workforce profile | Do you employ a significant number of high earners or late-career professionals? |
| Recruiting pressure | Are candidates asking sophisticated questions about financial protection and long-term planning? |
| Benefits philosophy | Do you aim to offer a baseline package, or do you position benefits as a differentiator? |
| Admin capacity | Can your current team manage another education-heavy voluntary benefit well? |
A PEO or integrated HR support model can also become more attractive when your internal team is stretched. Not because WA Cares is impossible to manage, but because it adds one more state-specific process that touches payroll, onboarding, employee notices, and records. If you're already juggling leave administration, benefits enrollment, and multi-state tax coordination, WA Cares can be the issue that exposes a broader workflow problem.
A Step-by-Step WA Cares Compliance Checklist
Most employers don't need a legal memo. They need a checklist that survives turnover, payroll deadlines, and employee questions.
Start with a short training touchpoint for the people who process changes. Then use a written checklist that payroll, HR, and finance all understand. If you want a broader framework for adjacent obligations, this employee benefits compliance checklist is a useful companion resource.
Core checklist for HR and payroll teams
Identify covered employees. Review which workers should have WA Cares deductions based on how your organization tracks Washington employment status.
Audit payroll configuration. Confirm the deduction is set up for the correct wage base and employee population.
Test edge cases. Review new hires, transfers, off-cycle checks, bonuses, and employee moves that could affect deduction treatment.
Create a standard employee notice. Give employees a short explanation of what the deduction is, where it appears on pay statements, and who answers internal questions.
Build an exemption intake process. Decide where documents are submitted, who reviews them, and how payroll receives final instructions.
Store records in one system. Keep exemption documentation, payroll notes, and reporting support together rather than across inboxes and shared drives.
Reconcile before reporting. Compare withheld amounts to payroll records before each reporting cycle.
Assign ownership. One person should own payroll setup, another can support employee communications, but someone must be accountable for final compliance.
Review vendor workflows. If you use an HCM, payroll bureau, or outside HR platform, confirm where WA Cares logic lives and who updates it.
Train managers not to improvise. Managers shouldn't tell employees they're exempt or promise refunds. They should route questions to HR or payroll.
For teams that prefer a visual training aid, this short video can help reinforce the moving pieces:
Keep your WA Cares process simple enough that a new payroll administrator could follow it without tribal knowledge.
Simple tracking table
Use a working table like this in your internal compliance file.
| Task | Status (Not Started, In Progress, Complete) | Notes |
|---|---|---|
| Confirm covered employee groups | ||
| Validate payroll deduction setup | ||
| Draft employee communication | ||
| Create exemption intake workflow | ||
| Centralize records | ||
| Reconcile reporting process | ||
| Assign internal owners |
A good checklist does one thing well. It reduces reliance on memory. That's especially important with WA Cares because errors usually come from handoffs, not from misunderstanding the concept.
If your team needs help simplifying WA Cares payroll coordination, evaluating private benefit options, or comparing PEO and benefits administration models, Benely can help you build a cleaner process without adding more manual work.
