
Old Slip Insights · Retirement Plans
October 27, 2026
A 401(k) deposit problem often begins as a routine payroll exception: a rejected file, an absent approver, or a bank instruction that no longer works. For CFOs and HR leaders, preventing late employee contribution deposits requires a clear process that connects payroll, treasury, and the recordkeeper—and confirms that money actually reaches the plan.
Employee salary deferrals are not ordinary company funds once withheld from pay. Under Department of Labor rules, they generally must be deposited into the plan as soon as they can reasonably be separated from the employer’s general assets. The practical question is therefore not simply whether a deposit met an outside deadline, but whether the employer could reasonably have completed it sooner.
The fifteenth business day of the following month is generally an outer limit, not a safe harbor for holding employee contributions. A separate seven-business-day safe harbor generally applies to plans with fewer than 100 participants at the beginning of the plan year. Qualified ERISA counsel should confirm the applicable rules, including how they apply to participant loan repayments.
Employer matching and other employer contributions can follow different timing requirements. Keep those workflows distinct so an employer contribution schedule does not become the assumed deadline for employee deferrals. An internal target should reflect the company’s actual processing capabilities, not merely the latest date someone believes is permitted.
“Payroll handles it” is not a complete control. Payroll may calculate deductions and transmit a file, while treasury releases cash and the recordkeeper accepts and processes the submission. Each team can complete its assigned task without anyone confirming that the full transaction succeeded.
Name one internal process owner, even if an outside payroll provider performs most of the work. Document the handoffs and identify a trained backup for every approval or release step. A simple responsibility map should cover:
Create a deposit calendar that starts with each pay date and shows the expected file submission, funding, and confirmation steps. Include bank holidays, recordkeeper cutoffs, and the time needed to resolve a rejected submission. Set an escalation point early enough that a missed internal target receives attention before the delay grows. Internal targets should support timely deposits; they do not replace the legal standard.
The calendar should also capture bonus runs, off-cycle checks, correction payrolls, and payrolls for newly acquired entities. These are common places for an otherwise reliable process to break down because the regular automation may not apply. Before a payroll-system change or recordkeeper transition, test the contribution workflow and confirm who will monitor the first live cycles. Do not assume that an integration marketed as automatic removes the need for an internal completion check.
A successful file upload does not prove that contributions were deposited. Likewise, a bank debit alone may not establish that the recordkeeper accepted the contribution details or allocated the money correctly. The review should connect the payroll deduction, cash transfer, and recordkeeper confirmation, while distinguishing deposit timing from any later allocation issue.
For each payroll, retain a compact evidence package that allows someone outside the transaction to follow what happened. The reviewer should check:
When a deposit appears late, establish the facts promptly: the affected payroll, amounts withheld, relevant dates, and reason for the delay. Do not wait for the annual plan audit or assume that a later contribution automatically resolves the issue. Notify the internal process owner and involve the plan’s service providers and qualified ERISA counsel as appropriate.
Correction can involve more than depositing the withheld amount. Depending on the circumstances, lost earnings, excise taxes, reporting, or a formal correction program may need consideration. Counsel and qualified tax professionals should determine the appropriate treatment; an internal spreadsheet or vendor estimate should not substitute for that advice. Keep an exception log that records:
CFOs and HR leaders do not need every transaction detail at each committee meeting. They do need a consistent summary of whether deposits followed the established process, which exceptions occurred, and whether open items have been resolved. Report recurring issues separately from isolated events so a pattern of rejected files or missed approvals does not disappear inside routine administrative updates.
Periodically compare the written procedure with actual practice. Ask a backup employee to walk through the process, review a sample of completed payrolls, and verify that access rights and bank instructions remain current. Review controls again after staffing changes, acquisitions, or provider changes. An investment adviser can help keep the topic on the oversight agenda, but payroll execution and legal determinations should remain with the parties responsible for those functions.
Old Slip Capital, an independent, fee-based registered investment adviser established in New York in 1966, welcomes conversations with CFOs and HR leaders about retirement plan oversight. If deposit monitoring needs a clearer place in your review process, we would be glad to discuss how it fits within your broader plan governance.