Current-Year vs. Prior-Year ADP Testing: Which Method Should a Plan Use?

Current-year and prior-year ADP testing are alternative ways to establish the NHCE benchmark; the right method is the one authorized by the plan document and workable for the plan’s data and design.

Current-Year vs. Prior-Year ADP Testing: Which Method Should a Plan Use? matters because annual compliance work is only as reliable as the employee, payroll, ownership, and plan-document data behind it. This guide gives plan sponsors an operational way to understand the question, ask better questions of their administrator, and document decisions without treating a general article as individualized tax, legal, actuarial, investment, or compliance advice.

At a glance

Define the issue

IRS guidance permits ADP and ACP percentages for NHCEs to be based on current-year or prior-year contributions. The election is in the plan document and may be changed only in limited circumstances. [1]

For a sponsor, the practical definition starts with the plan document. It identifies the plan year, eligibility rules, compensation definition, contribution sources, and administrative elections that shape the calculation. A service provider can calculate from a file, but the sponsor remains responsible for supplying accurate operational facts and noticing when a file does not match the plan’s terms.

That distinction is especially important after a business change. A new payroll system, acquisition, owner change, merger, rehire population, or revised match formula can alter the information that should reach the annual review. The best time to resolve an ambiguity is when the underlying records are still easy to trace—not after a final report creates a surprise.

How the mechanism works

With a current-year method, the NHCE benchmark develops from the same year being tested. With a prior-year method, the benchmark uses the prior year’s NHCE contribution experience. Neither label tells a sponsor whether the plan will pass; participation patterns and the document matter. [1]

Think of the process as a chain: source records determine participant classification; classification and plan terms determine the testing population; payroll and account records provide amounts; and the resulting calculation informs a sponsor decision. A break at any link can make a result unreliable. That is why a documented input review is a control, not administrative busywork.

Compare the important inputs

The comparison is operational as much as mathematical. Current-year testing may demand more active monitoring as participation changes. Prior-year testing may make a benchmark available earlier, but it can diverge from current workforce behavior. [1]

Questions for the annual file review

Before approving a report, ask whether the census includes every person required by the document, whether late-year hires and terminated participants were handled consistently, and whether the compensation period matches the stated rule. Ask the administrator to identify assumptions rather than hiding them inside a calculation. A short written exception log makes it easier to distinguish a genuine design issue from a data-cleanup task.

Also separate information gathering from remedy selection. The right response to an incomplete roster is to complete and validate the roster; the right response to a failed calculation may involve a document-driven correction analysis. Conflating those steps can create unnecessary participant disruption and make the audit trail harder to explain later.

Implement a sponsor workflow

Start with the signed document and amendments, then ask the administrator which method was used historically, when the NHCE file becomes reliable, and what a permissible change would require. Do not switch a spreadsheet formula simply because a result is inconvenient. [1]

1. Assign ownership. Name a sponsor-side contact for HR, payroll, finance, ownership, and the recordkeeper file.
2. Freeze and reconcile inputs. Save the original extracts, compare them to the document, and log exceptions.
3. Review the result. Ask for the population, formulas, assumptions, and any adjustments—not just a pass/fail status.
4. Document the decision. Retain approvals, correction calculations, deposits or distributions, and participant communications where applicable.

Practical review table

Review and improve

Use quarterly trend reporting to test assumptions, but preserve the annual test as the formal result. Escalate acquisitions, ownership changes, eligibility changes, and new payroll systems because each can affect comparability. [1]

Use the post-cycle review to convert exceptions into controls. For example, an ownership-information gap can become a quarterly questionnaire; a contribution-code problem can become a payroll change-control test; and a late eligibility feed can become a checklist with a named deadline. Controls should be simple enough that the responsible team can actually perform and evidence them.

Close the loop with a short sponsor meeting after the administrator completes the work. Review what changed from the initial census, who approved each exception, and whether the result triggered a funding, distribution, notice, or design discussion. Store the final report alongside the source extracts and approval notes. That package gives next year’s team a starting point and helps prevent informal knowledge from disappearing when roles change.

For recurring issues, identify a leading indicator rather than waiting for an annual surprise. Examples include a monthly list of new owners and related entities, a payroll-code change report, an eligibility reconciliation, or a balance-adjustment queue. The measure should lead to a specific person reviewing a specific file by a specific date.

Editorial disclaimer: This article is educational and does not provide legal, tax, actuarial, investment, or compliance advice. Retirement plan outcomes depend on the plan document, facts, timing, and applicable law. Work with qualified plan, legal, tax, and payroll advisers before implementing a correction, contribution, or design change.

Planning resource

Testing Readiness

Takeaway

The practical takeaway: treat current year vs prior year ADP testing as a disciplined data-and-document process. Start with the governing terms, validate the population and amounts, preserve the calculation trail, and obtain professional review when facts or correction choices are uncertain.

Educational information only; not tax, legal, actuarial, investment, or compliance advice. Plan documents, current law, and qualified professional review control any decision.

References

• [1] Internal Revenue Service. Current-Year vs. Prior-Year ADP Testing supporting guidance. https://www.irs.gov/retirement-plans/401k-plan-fix-it-guide-the-plan-failed-the-401k-adp-and-acp-nondiscrimination-tests