Don’t miss out on a safe harbor 401(k) for 2024! The deadline to sign up with Employee Fiduciary is September 16th.

Get started
Search for topics or resources

401(k) Document Retention Rules Made Simple

Eric Droblyen

August 13, 2024

Subscribe
Table Of Contents

Did you know that employers are required to retain detailed 401(k) documents, including testing results, transactions, and employee activity, for at least six years under the Employee Retirement Income Security Act of 1974 (ERISA)? If you're unaware, you're not alone. However, understanding and complying with these rules is crucial to avoid potential issues.

While the civil penalties for not retaining required 401(k) plan records are minor, missing records can significantly hinder an employer’s ability to defend plan operations or the accuracy of plan benefits if challenged by the IRS, DOL, or plan participants.

Below are some of the most common 401(k) plan records that must be retained to meet ERISA standards. I recommend employers use three files to organize this information: a file for the plan’s governing documents (a “Plan Document File”), a file for participant records (a “Participant File”), and a file for annual information (a “Annual File”). This simple file system should make accessing plan records easy if they are ever needed.

SH_LearnMore_ColoredBKGD

401(k) Document Retention Requirements

ERISA requires employers to retain certain documents and records in order to meet their fiduciary responsibilities. These requirements apply to both plan level and individual participant records. 

Section 107 of ERISA describes the retention requirements for records used to support plan filings. These records must be kept for at least six years after the filing date. Examples include:

Section 209 of ERISA describes the retention requirements for records used to determine participant benefits. These records must be kept “as long as a possibility exists that they might be relevant to determining the benefit entitlements of a participant or beneficiary,” which can mean indefinitely. Examples include:

    • Plan documents, and items related to the plan document
    • Records that determined employee eligibility, vesting, and benefits
  • Support and documentation for participant loans and distributions
  • Board or administrative committee minutes and resolutions

Plan Document File

This file is for records that govern the plan’s day-to-day operations. Superseded records should be archived for historical reference. Items to keep in the file include:

    • Plan Documents – adoption agreement, base document, IRS advisory letter, amendments, QDRO policy, and loan policy (if loans are allowed)
    • Summary Plan Description (SPD) – including any Summary of Material Modifications (SMMs) related to the SPD
    • Corporate Actions – resolutions, agendas, minutes, and documents distributed at meetings  
    • Service Agreements – Contracts that outline the services and fees of plan service providers
    • 408b-2 Fee Disclosure – Information a Covered Service Provider (CSP) must provide to employers for their fees to be considered “reasonable.”
    • Fidelity Bond – ERISA Section 412(a) requires every fiduciary of an employee benefit plan and every person who handles funds or other plan property be bonded.                  
                 

Participant File

This file is for records that document participant direction and distributions. Items to keep in this file include:

    • Payroll Records
    • Participant Deferral Election Forms
    • Investment Election Change Forms
    • Beneficiary Designation Forms
    • Distribution Request Forms (including any supporting documentation)
    • Loan Request Forms
    • Rollover Requests
    • QDRO Split Requests (with supporting documentation)

Annual File

This file is for records related to a plan year. A file should exist for each year the plan has been in existence. Items to keep in this file include:

Staying Out of Trouble is Easy!

A 401(k) plan, by its nature, generates large amounts of documentation and preserving much of it is required by ERSIA. Developing a filing system can make it easy for 401(k) sponsors to review, update, preserve, and dispose of documents.

These systems do not need to be complex. A simple system with three file types can do the trick. Ready access to plan documentation can mean the difference between a quick, cost-free settlement to a 401(k) dispute or a drawn-out, costly battle.

New call-to-action