When Must 401(k) Deferrals Be Deposited? A Practical Timing Guide
Practical guidance for when must 401(k) deferrals be deposited? a practical timing guide, including controls, records, and review steps.
401(k) deferrals should be deposited as soon as they can be segregated from the employer’s general assets, using a documented process that is faster than treating the outside maximum as a routine target.
Deposit timing is a process-control issue, not just a calendar reminder. Payroll close, bank approvals, file transmission, and trust confirmation all affect the actual date. A sponsor that measures those steps can set a repeatable standard and spot drift before it becomes a late-deposit problem.
At a glance
- Core question: Does the recorded operation match the plan’s written terms?
- Best evidence: Dated source reports, not a reconstructed summary.
- Reading path: Define the rule, compare records, then document action.
Define the operating question
The IRS fix-it guide says Department of Labor rules require deferrals to be deposited as soon as the employer can segregate them from general assets and states that the fifteenth business day of the following month is a maximum, not a safe harbor.[1] The practical benchmark depends on the employer’s demonstrated ability to complete the process and on any stricter plan-document term.
Before reviewing individual transactions, write the question in a way that can be tested: which people, pay periods, contribution source, and plan provisions are in scope? Use source-system extracts with an “as of” date and preserve the version of the plan materials used. That discipline separates a defensible finding from a report that merely looks complete.
Compare records before drawing a conclusion
The payroll date is when withholding arises; the deposit date is when the money reaches the plan trust. The gap between them is the control interval. A recurring three-day pattern may be evidence of the employer’s capability, while an occasional disruption needs documentation and remediation rather than an assumption that the broader outside limit applies.
| Record set | What to test | Useful outcome |
|---|---|---|
| Plan materials | Rule, formula, eligibility, and timing | Control standard |
| Payroll and HR data | Dates, pay, status, and withholding | Expected result |
| Trust or recordkeeper data | Funding and allocation | Confirmed variance |
Use a variance log that records the participant or payroll population, source records, initial explanation, owner, due date, and disposition. Do not silently overwrite a difference to make totals agree. A documented “not an error” conclusion is valuable because it shows why the reviewer rejected the exception.
Make the comparison reproducible. Save the original extract names, filters, report dates, and calculation version, then have another reviewer rerun a small sample from the same evidence. This is especially important when a payroll code, job classification, or plan amendment changes during the review period. A control is more reliable when it can explain both a matched item and an exception. Where information is incomplete, label the item as pending rather than guessing an effective date or contribution source. The resulting file gives the sponsor a practical audit trail and a clearer handoff if outside counsel or a plan specialist needs to evaluate a potential correction.
Implement a controlled response
Once a variance is confirmed, contain the issue first. Stop the faulty configuration or manual process, preserve the records, and identify whether additional payrolls or populations use the same rule. Then use a consistent case file: facts, governing terms, analysis, professional advice, corrective amounts if applicable, approvals, funding evidence, participant communications, and prevention steps. The right sequence depends on the plan and facts, so administrators should involve ERISA counsel, a qualified TPA, or other appropriate advisers before selecting a correction method.
- Map every step from payroll finalization through bank release, file acceptance, and trust confirmation.
- Identify the earliest consistently achievable deposit date for each payroll cycle and document the evidence.
- Set an internal due date before that demonstrated date, with a backup approver for absences.
- Reconcile each payroll register to the trust receipt and flag any deposit that misses the internal standard.
- Investigate delays immediately; preserve dates, reason, participant impact, and corrective action.
Assign one owner for the case, but do not make that person the only reviewer. Payroll can validate source data, HR can validate employment events, and the recordkeeper can validate posting. The plan administrator should retain the final decision trail. This division makes it easier to distinguish a data correction from a plan-operation correction and reduces the risk that a fix in one system is never reflected in another.
Review the control, not only the case
Review timing reports monthly and after payroll changes, bank changes, holidays, or staffing turnover. If the plan document states a timing commitment, test against that commitment as well. The DOL’s small-business responsibilities materials also emphasize fiduciary and operational responsibilities, making retained evidence and timely follow-up important.[2]
Decision flow
- Set scope: define the requirement, scope, timing, and decision owner.
- Check evidence: check documents, reports, controls, and open exceptions.
- Assign action: assign the approved action, deadline, and accountable owner.
- Revisit: revisit evidence, changes, and unresolved exposure.
Move forward only when the evidence supports the prior step; retain the record of each decision.
Practical review table
| Review point | Evidence to retain | Escalate when |
|---|---|---|
| Population | Dated HR and eligibility extracts | People appear in one system but not another |
| Calculation or election | Plan terms and calculation detail | Expected and actual results differ |
| Funding or posting | Bank, trust, and allocation confirmations | Timing or allocation cannot be explained |
| Prevention | Test result and owner sign-off | The root cause remains active |
Planning resource
Takeaway
The strongest operating practice is a short, repeatable reconciliation tied to the plan document, with dated evidence and an exception path that stays open until both the participant impact and root cause are addressed. That approach turns a difficult review into a manageable routine.[1][2]
Close the review by asking whether the control would detect the same failure next month. If the answer depends on a person remembering a special step, convert that step into an owned report, a documented approval, or a system validation. Retain both the original exception and the proof of the changed process. Periodic samples should confirm that the control is operating in practice, not merely written into a procedure.
Editorial disclaimer: This article is general educational information, not legal, tax, investment, actuarial, or compliance advice. Plan documents, facts, and current guidance can change the result; consult qualified advisers before acting.
References
- [1] https://www.irs.gov/retirement-plans/401k-plan-fix-it-guide-you-have-not-timely-deposited-employee-elective-deferrals
- [2] https://www.dol.gov/agencies/ebsa/employers-and-advisers/small-business-owners/understanding-your-responsibilities