‍

Introduction

For many employers, employee benefits compliance can feel like a moving target. Requirements around documentation, distribution, and administration are detailed, and often handled behind the scenes by brokers, carriers, or third-party administrators. That can create a false sense of security that everything is “taken care of.”

In reality, employers remain responsible for ensuring their benefit plans meet legal requirements under ERISA and the Internal Revenue Code. Missing or incomplete documentation can lead to administrative issues, penalties, or challenges during employee disputes.

This article outlines the core components of benefits plan documentation, including ERISA plan documents, Summary Plan Descriptions (SPDs), wrap documents, and cafeteria (POP) plans. It also highlights where employers should focus to reduce risk and maintain compliance.

Key Takeaways

• Most employers are subject to ERISA and must maintain written plan documents and SPDs for covered benefit plans
• SPDs are critical and often function as the controlling document in disputes
• Wrap documents can consolidate multiple plans, reduce Form 5500 filings, and fill documentation gaps
• Employers are responsible for maintaining, reviewing, and distributing compliant plan documents
• POP (cafeteria) plans are required to allow pre-tax benefit deductions
• Documentation must be updated and distributed according to specific timing and delivery rules

Understanding ERISA Coverage

Which Employers Are Subject to ERISA?

Most private-sector employers fall under ERISA requirements. Key exceptions include:

• Government entities (federal, state, local)
• Churches and certain affiliated organizations
• Some tribal employers

Even when exempt, maintaining formal plan documentation is still considered a best practice for consistency and clarity.

Which Benefit Plans Are Covered?

ERISA applies to most health and welfare benefits, including:

• Medical, dental, and vision plans
• Life and disability insurance
• Health FSAs and certain wellness programs

Some benefits are not subject to ERISA but may still require written documentation under other laws, such as:

• Cafeteria (POP) plans
• Dependent care FSAs
• Educational or adoption assistance programs

ERISA Plan Documents and SPDs

What Documentation Is Required?

ERISA requires two core documents for covered plans:

• Plan Document
  • The formal legal document governing how the plan operates
• Summary Plan Description (SPD)
  • A participant-facing document explaining benefits, eligibility, and rights

In many cases today, these documents are combined to avoid inconsistencies.

Why the SPD Matters

The SPD plays a central role in compliance and risk management:

• It must be distributed to participants
• It often governs in disputes if inconsistencies exist
• It defines eligibility, benefits, and administrative procedures

If the SPD conflicts with internal practices, employers may be required to follow what is written—not what was intended.

What Must Be Included in an SPD?

SPDs must include detailed information such as:

For all plans:

• Plan name, number, and sponsor details
• Plan administrator information
• Eligibility rules and benefits
• Claims and appeals procedures
• Amendment and termination provisions
• Statement of participant rights

Additional requirements for health plans:

• Cost-sharing details
• Coverage limits and exclusions
• Provider network rules
• COBRA rights
• Preventive care and prescription drug coverage

Employers relying on carrier certificates should confirm that all required elements are included, as these documents are often incomplete on their own.

Employer Responsibilities

Even when vendors assist, employers retain responsibility for compliance. Key obligations include:

• Ensuring all required documents exist
• Reviewing documents for accuracy and consistency
• Distributing materials within required timeframes
• Maintaining records of distribution
• Updating documents when plans change

Failing to follow plan terms or properly distribute documents can lead to fiduciary breaches and potential penalties.

What Is a Wrap Document?

Purpose of a Wrap Plan

A wrap document combines multiple benefit plans into a single ERISA plan. It serves three primary functions:

• Reduces Form 5500 filings
  • Multiple plans can be reported as one
• Fills documentation gaps
  • Adds required ERISA details missing from carrier documents
• Improves consistency
  • Aligns eligibility and administrative provisions across plans

How Wrap Documents Work

Without a wrap:

• Each benefit plan is treated separately
• Each may require its own Form 5500 filing

With a wrap:

• Plans are bundled into one ERISA plan
• Only one Form 5500 is required (if over 100 participants)

Limitations of Wrap Documents

Wrap documents can:

• Clarify or restrict eligibility
• Fill gaps in documentation

They generally cannot:

• Expand benefits beyond what carriers provide
• Override insurer-controlled provisions like claims processes or coverage

Common Wrap Document Considerations

• Not all plans must be included
• Non-ERISA plans can be included with proper disclaimers
• Employers may maintain more than one wrap (e.g., union vs. non-union plans)
• Wrap documents must be distributed like any other SPD

Updating and Distributing Plan Documents

When Updates Are Required

Plan documents must be updated when material changes occur. Employers can:

• Issue a revised SPD, or
• Provide a Summary of Material Modifications (SMM)

Timing Requirements

• New participants: within 90 days of coverage
• New plans: within 120 days of effective date
• Material changes:
  • Within 210 days after plan year end
  • Within 60 days if benefits are reduced

Electronic Distribution Rules

Employers may distribute documents electronically if:

• Employees have regular work-related computer access, or
• Employees provide consent

Paper copies must be provided upon request.

Cafeteria (POP) Plan Documents

Why POP Documents Matter

To offer pre-tax benefit deductions, employers must maintain a written Section 125 cafeteria plan (POP document).

Without it:

• Premiums and contributions must be taken after tax
• Tax advantages are lost for both employer and employees

What POP Documents Cover

POP documents define:

• Eligible benefits and participants
• Pre-tax deduction rules
• Mid-year election change events
• FSA and dependent care plan provisions
• Contribution limits and plan design choices

Key Distinction

• Wrap documents and POP documents serve different purposes
• Both are typically required for a compliant benefits structure

Additional Plan Documentation Requirements

Certain benefits require separate documentation:

• Health FSAs
  • ERISA plans with SPD requirements
• Dependent Care FSAs (DCAPs)
  • Not subject to ERISA, but must be in writing

These documents may be bundled or standalone, depending on plan structure.

Clarifications & Practical Context

• Employers often rely on vendor-generated “boilerplate” documents, which may not reflect actual plan operations
• Courts may not enforce provisions that were not properly communicated to employees
• Employees can formally request plan documents, and failure to respond within 30 days may result in penalties
• Electronic distribution rules are outdated and may not clearly address modern tools like mobile devices

Final Thoughts

Benefits documentation is often treated as a back-office task, but it plays a central role in compliance, administration, and risk management. Employers do not need to manage every detail themselves, but they do need to understand what is required, ensure documentation is accurate, and confirm that processes are aligned with what is written.

Taking time to review plan documents, confirm responsibilities with vendors, and address gaps can help prevent issues later.

‍

Disclaimer

This content is provided for general informational purposes only and is not intended as insurance advice. Coverage, terms, and availability can vary by carrier and state. For guidance specific to your situation, we recommend speaking with a licensed insurance professional.