How to Reconcile Payroll to 401(k) Contributions

To reconcile payroll to 401(k) contributions is to prove that the employee deferrals, employer match, nonelective and safe-harbor amounts, and eligible compensation calculated on the payroll register agree with the amounts posted in the recordkeeper or TPA contribution report and settled into the plan trust statement. It is a payroll-side-to-plan-side tie-out, separate from payroll-to-general-ledger reconciliation and separate from the participant-data census that has to tie alongside it.

The control runs on a layered cadence. Each pay period gets its own operational reconcile before the contribution remittance is transmitted. Each quarter end aligns payroll-side wages with the Form 941 filing and with the contributions transmitted to the plan over the quarter. Year-end reconciles annual deferrals to W-2 Box 12 totals (code D for traditional pre-tax, code AA for Roth) and aggregates to W-3, which is the canonical tie-out the auditor will look at and the input that supports the contribution figures on Form 5500.

When the totals disagree, the cause is almost always one of four things. Pay codes the plan document excludes from compensation (most often bonuses, severance, fringe benefits, group-term life over $50,000, and equity vesting income) get included in the payroll system's default 401(k) eligible earnings, or the reverse. The plan document's compensation definition has drifted away from how the payroll system was set up. The employer match formula is being applied against the wrong base — usually full payroll-system gross instead of the narrower plan-document compensation. Or a post-payroll correction (a void, a reissue, a wage adjustment) updated the payroll register but never generated the matching contribution adjustment to the plan, or vice versa. Each of these has a distinct symptom on the report; the rest of this guide names them and walks through how to isolate which one you are looking at.

Two situations bring readers to this work, and the workflow serves both: chasing a mismatch already discovered (an audit finding, a year-end correction, a participant complaint about a missing deferral) and standing up the recurring per-cycle control that catches mismatches before they survive into year-end and force a corrective filing.

The amounts that have to tie between payroll and the plan

Before the documents are walked, it helps to be precise about what specifically must agree. The reconciliation is not one number against one number; it is several distinct contribution and compensation amounts, each of which can fail independently, each labeled differently in the payroll system, the plan document, and the recordkeeper report.

Per-period employee deferrals. Pre-tax (traditional) deferrals and Roth deferrals reconcile separately. They post to different sources on the recordkeeper side and are reported separately on the W-2 (code D for traditional, code AA for Roth), so a tie-out that nets them together can pass on the aggregate while masking a misallocation between the two. For participants age 50 and over, the catch-up portion is a third bucket. Catch-up amounts are tested against the catch-up limit, not the elective-deferral limit, so when a participant exceeds the elective-deferral limit during the year, eligible amounts may be recharacterized as catch-up. That recharacterization is a normal source of dollars moving between buckets between the payroll-side view (which sees an employee election and a payroll deduction) and the plan-side view (which classifies the contribution by source and limit).

Employer match. Three variables drive what the match should be. The match formula itself — dollar-for-dollar to a stated percentage of pay, a tiered formula like 100% on the first 3% and 50% on the next 2%, or a discretionary match. Whether the formula is funded per pay period or trued up annually, and the plan-document definition of compensation the formula is applied against. A plan that funds a per-period match and a plan that trues up annually will produce identical full-year totals but very different in-process numbers — so a mid-year reconciliation that compares per-period payroll-side match against an annual-true-up plan-side match will look broken even when nothing is wrong. This is one of the most frequent live sources of mid-year reconciliation noise, and recognizing it as a structural feature of the funding cadence rather than an exception is half the work.

Nonelective and safe-harbor contributions. Safe-harbor nonelective (typically 3% of eligible compensation), safe-harbor match (basic and enhanced formulas), and discretionary nonelective or profit-sharing contributions all post on their own cadence, frequently funded annually or quarterly rather than per pay period. Reconciling them mid-cycle, before the funding has happened, produces a phantom break that resolves itself when the contribution is made. The reconciliation either runs at a moment after the funding cycle, or it explicitly carries the unfunded amount forward as an in-process item.

Eligible compensation. This is the single biggest source of payroll-to-plan drift, and the one most often missed because both sides are nominally working from "compensation." The plan document defines compensation — typically Section 415 compensation, W-2 compensation, or a modified definition that excludes specified pay types — and that definition is the legally controlling base for every employer contribution and the denominator for every deferral percentage test. The payroll system's "gross pay" or default 401(k) eligible earnings code may not match. Reconciling means proving that the deferral percentage and the match formula were applied against the plan's compensation, not against whatever earnings code the payroll system happens to total. When eligible compensation reconciliation in a 401(k) plan fails systematically, the root cause is almost always that the payroll-side compensation code and the plan-document compensation definition have not been aligned since plan implementation.

Loan repayments, after-tax, and voluntary contributions. Where a plan supports them, loan repayments flow on the same remittance as deferrals and need to tie out against the participant's outstanding loan balance on the recordkeeper side. After-tax and voluntary contributions reconcile to their own sources. These are real reconciliation items but secondary in scope; the bulk of payroll-to-plan reconciliation effort sits with the four amounts above.

The source documents, in the order you reconcile them

The reconciliation is a four-document walk, and each handoff between documents is its own potential break point. A clean tie-out proves that the dollars survived all four.

1. The payroll register. Per-period employee deferrals (broken out by source — pre-tax, Roth, catch-up), employer contribution amounts as calculated by the payroll system, and the eligible compensation base for each participant. This is the originating record. Everything downstream is supposed to agree with it.

2. The contribution remittance file. The file actually transmitted to the recordkeeper for the cycle, in the recordkeeper's mandated layout. In a system that is working correctly, the remittance file is a one-to-one expression of the payroll register's contribution detail. In practice, file-build logic on the payroll provider's side or a custom transmittal step on the sponsor's side can drop participants, round amounts differently, or split a single deferral across multiple sources. Reconciling the remittance file against the payroll register before transmission catches problems while they are still cheap.

3. The recordkeeper or TPA contribution report. What the plan side received and posted, broken out by source: pre-tax, Roth, employer match, nonelective, safe harbor, loan repayments, after-tax. You tie the payroll register to the 401(k) recordkeeper report side by side, by source and by participant. A mismatch here means the remittance file did not load cleanly — sometimes a participant did not exist on the recordkeeper census, sometimes a source mapping was wrong, sometimes a contribution was rejected and rerouted to a holding account.

4. The plan trust or custodian statement. What actually settled into the trust. Trust-side amounts should agree with the recordkeeper contribution report once timing is normalized. Movements on the trust statement that do not correspond to contribution activity (mid-year fund transfers, corrective distributions, fee withdrawals) are not reconciliation breaks — they are non-contribution activity that has to be separated out before the comparison.

The most common operator mistake at this step is treating the timing offset between payroll posting and plan posting as a break. Funds withheld from a Friday paycheck do not appear on the trust statement that same day; they post over the next several business days as the contribution is transmitted, allocated by the recordkeeper, and settled in the trust. A reconciliation run mid-cycle will show the payroll side ahead of the plan side. That is in-process variance, not an exception. The reconciliation either waits for both sides to settle, or it explicitly carries the in-process amount forward as a reconciling item until it clears.

The regulatory line distinguishes in-process variance from a true exception. Under the 7-business-day safe harbor at 29 CFR 2510.3-102, retirement plans with fewer than 100 participants at the start of the plan year qualify for a safe harbor that treats employee contributions as deposited on time when they reach the plan no later than the 7th business day following the day the employer received or withheld the amount. Larger plans operate under the general rule that contributions must be deposited as soon as administratively feasible, with the same 7-business-day window cited frequently as the practical outer bound. A timing variance still inside the applicable window is in-process and not a reconciliation discrepancy; an amount sitting outside it is a late deposit, which is a separate fiduciary issue that surfaces on Form 5500 Schedule H and triggers its own correction process. The mechanics of setting an earliest-segregable date for the plan, comparing payroll dates to deposit dates, and unwinding a late deposit through VFCP are covered separately in the 401(k) deposit timing rules and late-deposit correction guide. Conflating the two — chasing every in-process variance as if it were a late deposit, or letting a late deposit hide inside what looks like routine variance — is one of the more avoidable failure modes.

The practical hurdle this step exposes is rarely the reconciliation logic itself; it is getting the four documents into one comparable view in the first place. The payroll register arrives as a PDF or Excel from the payroll provider. The remittance file is in the recordkeeper-mandated layout, often a fixed-width or pipe-delimited text file. The contribution report arrives as a recordkeeper PDF or a portal export with its own column conventions. The trust statement comes from the custodian on yet another schedule and format. Operators handling this manually spend much of their reconciliation cycle normalizing these documents before they can compare anything, and the larger the plan or the more frequent the cadence, the more this preparation work dominates. AI-powered payroll and recordkeeper document extraction is one approach to producing structured outputs from these source documents in a single comparable layout; the broader pattern is the same whether the conversion is done by hand, by a custom script, or by tooling that can extract payroll register data from PDF and the recordkeeper report alongside it. The tie-out cannot start until the four sources are in a form that lets them be compared by participant and by source.

Triage tree: why a payroll-to-plan tie-out fails

When a reconciliation breaks, the first job is to identify which of the recurring failure modes you are looking at. Each one has a distinctive symptom on the report and a defined place to look on each side to confirm.

Excluded pay codes. The most common single source of payroll-side under-deferral. Bonuses, severance, commissions, fringe benefits, taxable group-term life over $50,000, equity vesting income, expense reimbursements miscoded as wages, and imputed income all sit on the line between included and excluded depending on the plan-document compensation definition. The payroll system's default 401(k) eligible code rarely matches the plan's definition exactly. The symptom is a participant whose deferral percentage looks correct against gross pay but understates against eligible plan compensation, or whose match comes in light on a payroll cycle that contained a bonus or other irregular pay. Confirm by recalculating both the deferral and the match for the cycle in question against the plan's compensation definition; if the recalculated figure agrees with the recordkeeper-side amount, the payroll-side compensation code is including pay the plan excludes (or vice versa).

Compensation-definition drift. Adjacent to excluded pay codes but a distinct failure mode. Drift happens when the payroll system's compensation code was set up correctly at plan implementation but has not been kept in sync with plan amendments, with new earnings codes added to the payroll system since, or with a change in the plan's compensation election. The symptom is a tie-out that reconciled cleanly through prior years and breaks this year with no obvious change in payroll process. Confirm by pulling the current plan-document compensation definition and reconciling it against the active mapping of payroll earnings codes to "401(k) eligible compensation"; expect to find that one or more new earnings codes were added without a corresponding decision about whether they should be included.

Missing or duplicated payroll cycles. Off-cycle bonus runs, supplemental payrolls, severance payouts, and final-pay runs for terminated employees frequently get omitted from the contribution remittance — sometimes because the off-cycle run does not flow through the same automated transmittal as regular payrolls, sometimes because a manual decision was made not to defer on a one-time payment. The reverse also happens: in correction scenarios, a cycle gets transmitted twice. The symptom is a clean per-cycle reconciliation that fails on the period total. Confirm by reconciling the count of payroll cycles in the period to the count of remittances received on the recordkeeper side, and resolving any cycles that exist on one side and not the other.

Post-payroll corrections reflected on only one side. A void, a reissue, or a wage adjustment processed after the original cycle's remittance often updates the payroll register and the year-to-date W-2 totals without generating a corresponding contribution adjustment to the plan, or vice versa. The symptom is a year-to-date payroll number that no longer reconciles to the plan year-to-date even though every individual cycle reconciled at the time. Confirm by listing every correction processed since the last clean reconciliation and tracing each one through to the plan side; the unreconciled corrections will be the difference.

Employer-formula errors against the wrong base. The match formula itself is correct, but it is being applied to the wrong compensation. The most common version: the formula runs against payroll-system gross pay including bonuses when the plan defines compensation to exclude bonuses, producing systematic match overpayment that compounds across cycles. The symptom is an employer-side amount that ties internally within the payroll system but exceeds the recordkeeper-recalculated match by a stable percentage — the percentage being roughly the share of pay made up of excluded items. Confirm by recalculating the match for a small sample of participants using the plan-document formula and the plan-document compensation definition and comparing against both the payroll-side and recordkeeper-side amounts.

Mid-year plan amendments. A change to the match formula, eligibility, compensation definition, or safe-harbor election effective mid-year. The symptom is a tie-out that reconciles cleanly through one date and then breaks consistently afterward. Confirm by checking the amendment effective date against the cycles where the break begins; the failure pattern usually means that either the payroll-side reconciliation logic or the recordkeeper-side calculation engine was not updated to reflect the amendment on the effective date.

Terminations and final-pay catch-up. Final pay for a terminated participant typically includes accrued vacation, severance, or a bonus, and sometimes a final scheduled deferral the participant elected. The deferral and match logic on these final-pay items is often where edge cases live: amounts the plan excludes for terminated participants get deferred against, or a final deferral the participant elected gets missed because the payroll system flagged the participant as terminated before the final cycle ran. The symptom is a participant-level break confined to terminated employees in the period. Confirm by reconciling the termination roster against the contribution detail for each terminated participant's final pay period.

Plan-side timing differences that look like breaks but are not. Recordkeeper posting calendars, mid-year fund transfers between investment options, corrective distributions for failed nondiscrimination testing, and excess-deferral refunds processed by the recordkeeper all produce trust-statement movements that have no payroll-side counterpart. The symptom is a trust-side number that does not tie to the contribution report even though contributions themselves reconciled cleanly. Confirm by separating contribution activity from non-contribution activity on the trust statement before attempting the comparison; almost all of the apparent break will sit in the non-contribution column.

These eight cover the bulk of payroll-to-plan reconciliation failures. They are deliberately narrow to the contribution tie-out itself. If the underlying issue is broader payroll-to-general-ledger reconciliation — payroll-side wages, taxes, and accruals against the GL accounts — that is a separate control with its own scope and its own failure modes; the payroll-to-general-ledger reconciliation process covers it on its own terms.

The calendar that drives when each tie-out matters

The reconciliation runs on overlapping cadences, each tied to a different downstream consequence. Knowing which version of the tie-out runs when, and what window closes if a break survives past it, is what separates an audit-ready control from a year-end fire drill.

Per-pay-period operational reconcile. The first-line control. Each cycle's payroll register is reconciled to its contribution remittance file before the remittance is transmitted, and then to the recordkeeper contribution report once the contribution has posted. Catching breaks at this cadence is the cheapest place to fix them — the correction runs through the next cycle's remittance, the participant impact is small, and the dollars stay inside the same plan year and usually the same quarter. Per-cycle reconciliation is also where the recurring control shape gets built; the year-end tie-out and the audit are easier when there is a documented sign-off for each cycle behind them.

Quarterly with Form 941. At quarter end, payroll-side wages and FICA reconcile to the 941 filing. The same payroll-side compensation total feeds the contributions transmitted to the plan over the quarter, so a quarterly tie-out aligns the payroll-tax view and the plan-contribution view at a cadence short enough to remediate without filing a corrective 941 or a corrective contribution. A break that surfaces at quarter end and gets resolved before the next quarter is a contained problem; the same break at year-end is a corrective-filing problem.

Year-end against W-2 Box 12 and W-3. Annual deferrals reconcile to W-2 Box 12 code D (traditional pre-tax 401(k) deferrals) and code AA (Roth 401(k) deferrals), participant by participant. Aggregated W-3 totals should agree with annual contribution totals on the recordkeeper side. This is the canonical year-end tie-out — the one most commonly examined when the plan is audited, the one that supports the contribution figures reported on Form 5500, and the one that has to be clean before W-2s go out to participants. A break discovered after W-2 issuance forces a W-2c, which is visible to the participant and to the IRS.

March 15 corrective distribution deadline for excess deferrals. Where the year-end reconciliation surfaces a participant who exceeded the elective-deferral limit (across all plans the participant contributed to that year, which the plan sponsor often will not see without participant notification), the corrective distribution must be processed by March 15 of the following year to avoid double taxation on the excess — taxed in the year deferred and again in the year distributed. A reconciliation that does not surface excess deferrals before March 15 forces the participant into the worse tax outcome. This is one of the harder cases for the per-cycle control to catch, because the excess often arises from contributions to another employer's plan the sponsor has no visibility into, but the year-end reconciliation surfaces it in time only if it runs early enough to act on.

Form 5500 and the audit window for large plans. Plans with 100 or more eligible participants at the start of the plan year are large plans for Form 5500 purposes and require an independent audit performed by an Employee Benefit Plan auditor. The audit examines, among other things, whether participant contributions reconcile to the records — meaning the payroll-to-plan reconciliation moves from internal control to documented evidence the auditor will sample, recalculate, and test. Plans approaching the 100-eligible-participant threshold are well served treating their reconciliation cadence and documentation as if the audit applies one year before it does, because building per-cycle sign-off retroactively is harder than building it forward. The payroll to 401(k) audit reconciliation that the auditor will run is essentially the same control walked in this guide — the difference is that the sponsor's worksheets, the payroll register, and the recordkeeper report all have to be available, internally consistent, and produced to a sample of participants the auditor selects.

The contribution reconciliation is one of three jobs that hit at year-end. The audit-package contents the auditor will request — plan document, adoption agreement, prior-year 5500, fidelity bond, recordkeeper SOC 1 report, and the rest — sit in the 401(k) audit package checklist for employers. The participant-data census tie-out (eligibility, compensation, hire and termination dates, hours of service) runs alongside contributions and is its own discipline; the employee benefit plan census reconciliation covers what has to tie there. Contribution reconciliation, audit package, and census tie-out are three separate workstreams that all converge on the same Form 5500 and the same auditor; treating them as a single undifferentiated year-end project is what produces the fire drill.