EACA vs. QACA vs. Basic Automatic Enrollment: A Sponsor’s Decision Guide
Compare EACA, QACA, and basic automatic enrollment for a 401(k) plan. Learn the operational choices, notices, testing effects, and review steps for sponsors.
EACA vs. QACA vs. Basic Automatic Enrollment: A Sponsor’s Decision Guide is best handled as a documented plan-design and operations decision—not as a one-time payroll setting.
For a plan sponsor, automatic enrollment can look simple until an exception, a data transfer, or a participant question exposes a gap between the plan document and day-to-day administration. This guide gives HR, payroll, finance, and the plan’s service providers a shared way to frame the decision. It is educational information, not individualized tax, legal, actuarial, investment, or compliance advice.
At a glance
- Core question: What does the plan require?
- Control point: Which system owns the data?
- Reading path: define, compare, implement, then review.
Define automatic enrollment
Basic automatic enrollment is a plan feature; an EACA adds a statutory framework that can include a permissible withdrawal feature and a longer correction window in certain circumstances; a QACA is a safe-harbor design with required contribution, vesting, notice, and automatic-enrollment conditions. [1] The practical point is to separate the rule from the workflow. A rule answers what the plan may or must do. A workflow answers who supplies data, who approves a change, which system records it, and how the sponsor proves the action occurred. Treating those as separate workstreams makes errors easier to find.
A useful starting file contains the signed plan document and amendments, adoption agreement if applicable, service agreements, payroll configuration notes, prior-year testing or administration reports, and current participant materials. These records should agree on eligibility, compensation, contribution sources, elections, and timing. If they do not, pause before changing payroll or communicating a conclusion.
Compare the sponsor choices
The sponsor’s decision is usually about whether the sponsor needs testing relief, can fund the required contribution, and can administer defaults and notices consistently. Compare each option against three lenses: document fit, operational capacity, and participant impact. Document fit asks whether the amendment and notices support the approach. Operational capacity asks whether payroll, HRIS, and recordkeeping can exchange accurate data. Participant impact asks whether the explanation, opt-out or election experience, and correction process are understandable.
| Lens | Question to ask | Evidence to retain |
|---|---|---|
| Plan terms | Is the feature and its timing authorized? | Document and amendment review |
| Data | Can the required population be identified? | Validated census or payroll report |
| Operations | Who handles exceptions and corrections? | Owner map and test results |
Do not let a vendor screen label substitute for a document review. IRS materials repeatedly emphasize operating the plan under its terms and using correct employee, compensation, ownership, and contribution information. [2] A change that looks administratively convenient can create a mismatch if the systems or notices were not updated at the same time.
Implement a controlled workflow
Document the default percentage, escalation schedule, opt-out path, investment default process, payroll code, and annual notice owner before launch. Start with a written implementation brief: scope, effective date, data fields, responsible parties, test cases, participant communication, and escalation contacts. Ask the recordkeeper and payroll vendor to confirm their file specifications in writing. A short parallel run can identify mapping defects before they affect live contributions or testing.
Use a four-part control: first, compare the plan document with the configuration; second, reconcile payroll totals and participant-level data to the recordkeeper file; third, have a separate reviewer inspect exceptions; fourth, retain a dated record of approvals and corrections. This does not replace professional advice, but it creates a practical audit trail and reduces reliance on oral handoffs.
Review results and exceptions
Reconcile payroll-to-recordkeeper files after each cycle; sample opt-outs and default changes; retain notice evidence; then ask counsel or the TPA to review amendments before each plan year. The Department of Labor’s guide explains that retirement-plan disclosures and reporting requirements are separate but related administrative duties, and it directs readers to current agency resources for complete requirements. [3] Calendar a review after significant workforce, payroll, ownership, vendor, or plan-document changes rather than waiting for an annual deadline.
- Know terms: identify governing terms, eligibility, and participant facts.
- Compare choices: compare available choices, costs, and consequences.
- Guide action: guide the next action without replacing required advice.
- Confirm: confirm records, notices, and unresolved questions.
Decision flow: Define → Compare → Implement → Review.
Practical review table
| Review item | Owner | Question |
|---|---|---|
| Document alignment | Plan sponsor and counsel/TPA | Does operation match written terms? |
| Data reconciliation | Payroll and recordkeeper | Do totals and participant sources agree? |
| Exceptions | Named compliance owner | Was each exception resolved and documented? |
| Communications | HR | Were participants given clear, timely information? |
Takeaway
Make automatic enrollment a repeatable control cycle. Define the plan rule, compare feasible operating choices, implement with tested data, and review evidence after each cycle. When facts involve tax treatment, ERISA duties, correction programs, ownership attribution, or document interpretation, obtain advice from qualified tax, ERISA, payroll, and plan-administration professionals before acting.
Common pitfalls to prevent
One frequent failure is treating a report as the source of truth when the underlying payroll, HRIS, ownership, or plan-document inputs changed. Another is solving a participant-facing question informally without recording the decision, then discovering that a later file uses a different rule. Prevent both by naming the authoritative source for each field, setting a cutoff date for the review, and preserving the version sent to each service provider. Build an exception log that identifies the person affected, the issue, the evidence reviewed, the decision maker, the correction date, and any participant communication. The log is not a substitute for a formal correction process; it is a way to make escalation visible early.
Also avoid copying a calendar, dollar limit, or rule summary from an old communication into a new plan year. Use current official materials and the plan’s own documents to confirm requirements. If the sponsor changes payroll providers, acquires an entity, changes ownership, amends eligibility, or adds a contribution source, repeat the design-to-configuration comparison instead of assuming existing controls still fit.
Escalation checklist
Escalate promptly when a file omits employees, a contribution source does not reconcile, an ownership relationship is uncertain, an election cannot be implemented as written, or a notice and system configuration conflict. Bring the plan document, amendment history, relevant census or payroll extracts, vendor reports, and a timeline to the TPA or counsel. A short fact package produces a better review than a broad request to “check compliance.” Close the loop only after the owner confirms the action taken, the evidence retained, and the next review date.
References
- [1] https://www.irs.gov/publications/p560
- [2] https://www.irs.gov/retirement-plans/401k-plan-fix-it-guide-the-plan-failed-the-401k-adp-and-acp-nondiscrimination-tests
- [3] https://www.dol.gov/agencies/ebsa/about-ebsa/our-activities/resource-center/publications/reporting-and-disclosure-guide-for-employee-benefit-plans