10.6 ERISA, Benefits Compliance, and Integrated Documentation

What ERISA Governs

The Employee Retirement Income Security Act (ERISA) sets minimum standards for most voluntarily established retirement and welfare benefit plans in private industry. It does not require an employer to offer a plan; once a plan exists, ERISA governs how it is run. Note the carve-outs the exam tests: ERISA generally does not cover governmental plans or genuine church plans. For PHR purposes the focus is administrative discipline — plan documents, disclosures, fiduciary process, claims/appeals, and accurate records — not picking investments.

Key ERISA disclosure and reporting instruments:

Fiduciary Duties

An ERISA fiduciary is anyone with discretionary authority over plan management or assets. Fiduciaries must: act solely in the interest of participants and beneficiaries (duty of loyalty); act prudently (the prudent-expert standard); follow plan documents to the extent consistent with ERISA; diversify plan investments to minimize large losses; and pay only reasonable plan expenses. Breaches can create personal liability for the fiduciary — which is why HR routes questions about vendor fees, plan assets, or investment menus to the plan committee or fiduciary rather than answering informally.

Following the plan document is non-negotiable. When a manager promises eligibility the plan does not provide, or a recruiter misstates coverage, HR corrects the communication and supplies plan-based information. Making an off-plan exception "because the employee is valued" or "because the error is embarrassing" is the wrong answer — it can disqualify the plan and breach fiduciary duty.

COBRA, HIPAA, and Integrated Records

Benefits compliance extends beyond ERISA's core. The Consolidated Omnibus Budget Reconciliation Act (COBRA) lets covered employees and dependents continue group health coverage after a qualifying event — generally 18 months for termination or reduced hours, and up to 36 months for events like divorce or a dependent aging out (applies to employers with 20+ employees). HR must send the COBRA election notice within the required window (generally 14 days after being notified of a qualifying event). HIPAA privacy rules protect participants' protected health information held by the group health plan.

Worked Example

An employee goes on a leave of absence; the status change never reaches the medical-plan vendor, so the carrier shows the employee as terminated and denies a claim. The PHR-correct action is to reconcile the HRIS, payroll-deduction, and vendor eligibility records, correct the feed, document the resolution, and identify any other participants affected by the same broken feed — not to tell the employee the vendor "owns" the problem.

Benefits records intersect leave (continuation and deductions), payroll (final pay), and separation (COBRA, retirement distributions), so HR coordinates these systems so the employee record, payroll, and vendor data all agree.

Claims, Appeals, and Participant Protections

ERISA guarantees participants a fair claims-and-appeals process. When a benefit claim is denied, the plan must notify the participant in writing, state the specific reason and the plan provisions relied on, and explain how to appeal. The participant has a right to a full and fair review, including access to relevant documents. HR's job is not to decide the claim on its own judgment but to route it through the plan's procedure and preserve the correspondence. Telling an employee "the vendor said no, that's final" without surfacing appeal rights is a common wrong answer.

ERISA also protects participants from interference. Section 510 prohibits firing or disciplining an employee to prevent them from attaining a benefit (for example, terminating someone just before they vest in a pension). And while ERISA preempts most conflicting state laws for covered plans, HR should remember the carve-outs — governmental and church plans — and that fully insured plans may still feel state insurance regulation.

Coordinating Benefits Across the Employee Lifecycle

Because benefits data lives in multiple systems, the highest-value HR control is reconciliation. A leave of absence can change premium deductions, continuation status, and vendor feeds; a status change from full-time to part-time can trigger a COBRA qualifying event; and a separation cascades into final-pay coordination, 401(k) distribution paperwork, FSA run-out rules, and the COBRA election notice. HR should treat these as a connected workflow rather than isolated tickets.

• Keep benefit elections, notices, claims correspondence, and eligibility records organized and access-limited.
• Reconcile HRIS status changes against vendor eligibility files on a regular cadence, not just at year-end.
• Protect health and beneficiary information consistent with HIPAA; share only what an administrator needs.
• Route fiduciary questions — fees, plan assets, investment menus — to the plan committee, never answer them informally.
• Document every correction when plan data, payroll deductions, or vendor records are wrong, and identify others affected by the same error.

Benefits compliance is process-heavy because employees rely on accurate information at high-stakes moments — a hospitalization, a retirement, a layoff. HR's role is to administer consistently, follow plan documents over informal promises, monitor vendors, protect data, and escalate specialized questions, which is exactly the operational PHR standard.