Why Payroll Definitions of Compensation Must Match the Plan Document
Why Payroll Definitions of Compensation Must Match the Plan Document: a practical guide for plan sponsors on pay codes, deferrals, employer match.
Payroll must use the plan’s definition of compensation—not a convenient proxy—because the included and excluded pay codes can drive deferrals, matching contributions, and testing inputs.
Why Payroll Definitions of Compensation Must Match the Plan Document is a practical guide for plan sponsors, HR teams, and finance teams that need a repeatable way to manage a 401(k) plan. The governing document is not a shelf document: it is the instruction set against which day-to-day administration should be evaluated. The IRS says operational errors should be corrected as soon as possible using a reasonable method that puts affected participants in the position they would have been in without the error.[1]
At a glance
- Core question: Can the sponsor show that daily administration follows the governing plan materials?
- Focus: Match a written rule to a system action, a responsible owner, and retained evidence.
- Reading path: Define the issue, compare possible gaps, then implement and review a control.
Define the control objective
A pay code can look routine yet be treated differently under the plan. Salary, bonus, overtime, commissions, paid leave, fringe items, and post-severance amounts may not be handled alike. The governing language and the plan’s actual administrative setup—not a payroll label alone—determine the review question. The control objective is simple: a reviewer should be able to trace a rule from the governing materials to an action in a system or workflow, and then to evidence that the action occurred. That trace makes issues visible before they become harder to reconstruct.
Use the word “document” broadly in the review. The signed plan, adoption agreement, amendments, service agreements that define handoffs, and relevant administrative procedures may each supply context. Still, the plan’s controlling terms should be identified by qualified counsel or the appropriate plan professional when language is unclear. A spreadsheet cannot resolve an ambiguous provision.
Compare the written rule with the operating record
| Question | Written-rule evidence | Operating evidence |
|---|---|---|
| Who is covered? | Eligibility and entry provision | Hire, hours, and enrollment records |
| How is money calculated? | Compensation and contribution terms | Payroll register and contribution file |
| How are benefits paid? | Vesting and distribution terms | Approval and transaction support |
This comparison is deliberately practical. For each row, ask whether the source is complete, who owns it, what period it covers, and whether exceptions have an explanation. The IRS 401(k) checklist emphasizes annual review of requirements for operating a 401(k) plan and points sponsors to resources for finding, fixing, and avoiding mistakes.[2]
A mismatch is a signal to investigate, not proof of a particular correction. Preserve the source records, determine the population and period involved, and avoid retroactively rewriting operational evidence. If a potential failure is confirmed, the remedy can depend on facts, plan language, and available correction programs.
Implement a sponsor-owned workflow
Inventory every pay code that may feed the plan. Map each code to included, excluded, conditional, or unresolved status under the plan terms, then test a sample against payroll configuration. Implementation should be proportionate to the plan’s complexity, but it should not rely solely on a provider’s general statement that a file was processed. The sponsor needs enough documentation to understand inputs, approvals, exceptions, and follow-up. The IRS describes the failure to follow plan terms as an operational problem and explains that correction principles focus on restoring affected participants appropriately.[1]
- Map data: identify payroll fields, owners, and timing.
- Compare gaps: compare provider mappings, controls, and exceptions.
- Test handoff: test the handoff before relying on production data.
- Reconcile: reconcile results and retain exception evidence.
Define → Compare → Implement → Review: retain evidence at each stage so a future reviewer can understand both the decision and the action.
Review cadence and escalation
| Review step | Practical output | Escalate when |
|---|---|---|
| Monthly or payroll-cycle review | Reconciliation and exception log | A variance lacks a documented cause |
| Quarterly control review | Owner certification and sample support | A control was skipped or changed |
| Annual plan review | Document inventory and compliance calendar | Terms, amendments, or operations do not align |
Keep the review focused on decisions that change participant outcomes: eligibility, compensation, elections, employer contributions, vesting, loans, distributions, remittances, and reporting. If an issue is found, document discovery date, affected period, population, preliminary impact, records reviewed, responsible parties, and next decision. The IRS notes that correction options can include self-correction when applicable or a Voluntary Correction Program submission when conditions warrant; eligibility and process depend on the facts.[1]
Build evidence that can be re-performed
Good administration creates an audit trail while the work is current. Save the version of the source report, the date it was obtained, the population used, the reviewer’s conclusion, and the follow-up for each exception. If a provider performs part of the workflow, retain the sponsor’s approval and reconciliation rather than treating a vendor report as the complete control. This approach also helps when personnel or systems change midyear.
Use a small exception register with a unique item number. Record the rule or control affected, the first affected date, participants or transactions potentially involved, temporary containment, owner, adviser escalation, and closure evidence. Review aging items at a committee or management meeting. A closed item should show why it was closed, not merely a status change.
Before changing a process, run a controlled comparison between the old and new output for a defined period. Confirm that the new system configuration, payroll mapping, or file layout still produces results consistent with plan terms. Update the matrix, checklist, and training materials at the same time. A documented change review prevents a well-intended operational improvement from creating an unobserved mismatch.
Takeaway
Payroll must use the plan’s definition of compensation—not a convenient proxy—because the included and excluded pay codes can drive deferrals, matching contributions, and testing inputs. The durable habit is not a once-a-year scramble. It is a short, recurring comparison of plan terms, data, transactions, and evidence—with timely escalation when the comparison does not hold.
Editorial disclaimer: This article is educational and is not tax, legal, actuarial, investment, audit, or compliance advice. Plan documents, facts, and correction options vary. Consult qualified ERISA counsel, tax advisers, auditors, and plan professionals before acting.
References
- [1] Internal Revenue Service, 401(k) plan fix-it guide: operations not based on plan document terms. https://www.irs.gov/retirement-plans/401k-plan-fix-it-guide-you-didnt-base-the-plan-operations-on-the-terms-of-the-plan-document
- [2] Internal Revenue Service, Publication 4531: 401(k) Plan Checklist. https://www.irs.gov/pub/irs-pdf/p4531.pdf