1. LandOffer
  2. Blog
  3. All articles
  4. 401(k) Contributions Left Your Paycheck but Not Your Account: Trace the Deposit

Pay & Benefits

401(k) Contributions Left Your Paycheck but Not Your Account: Trace the Deposit

A fictional employee reconciles three paydays with pretax and Roth postings, asks the plan administrator to trace unmatched amounts, and tracks a partial resolution without assuming timely funding.

10 min readLandOffer team

If your paystub shows a 401(k) deduction but your retirement account does not show the contribution, build a transaction-level reconciliation and ask the plan administrator to trace it. Match each payday and employee contribution type to the plan’s receipt and posting records. A payroll deduction, a transmitted file, money received by the plan, and a contribution allocated to your account are different pieces of evidence. An absent dashboard entry does not show whether funding, allocation, or the displayed view caused the mismatch.

This LandOffer.ai guide uses current federal primary guidance checked October 27, 2026, for a private-sector, ERISA-covered 401(k). It does not determine whether your employer violated a deadline or calculate a personal remedy. All people, amounts, records, and replies below are fictional. The two completed examples show how to ask a precise question and track an incomplete answer; no payroll, retirement account, government complaint, or investment transaction was accessed or changed.

An employee compares three pay statements with a retirement contribution ledger

Start with employee contributions, not the account balance

Start with contribution transactions rather than the account’s total value. Investment changes, fees, distributions, and employer contributions can all affect that figure. Look for contribution transactions and their source labels instead. A $300 difference in market value does not establish that a $300 payroll deduction is missing, and a rising balance does not prove every payroll contribution arrived.

Download the relevant pay statements and the plan’s transaction detail for an overlapping period. Include a few transactions before the first questionable payday so you can see how your own records label and group contributions. Check whether the website is filtering to one contribution source, one account, or a limited date range. Preserve what the view actually shows rather than rewriting an empty row as “employer never sent it.”

Keep employee pretax deferrals and designated Roth contributions separate. Likewise, do not combine them with an employer match or a loan repayment simply because they appear on the same statement. The IRS explicitly distinguishes the timing rules for employee elective deferrals from those for employer contributions. A match scheduled under plan terms does not explain away a missing employee deduction. This article traces the employee amounts; it does not assess the employer’s matching formula or annual contribution limit.

The Department of Labor’s participant guide recommends reviewing contribution information and contacting the plan administrator or HR about suspected errors. Find the administrator identified in your Summary Plan Description, rather than assuming the recordkeeper’s customer-service representative controls employer payroll funding. The recordkeeper may help identify what it received and posted; payroll can explain deductions and remittance records. Your request should connect those records through the administrator.

Worked reconciliation: three paydays, two unresolved amounts

Nora works for the fictional Cedar Vale Analytics and participates in its assumed ERISA-covered 401(k). On October 27, she reviews three biweekly pay statements and an employee-contribution transaction export covering September 1 through October 27. Her account balance is deliberately excluded. No investment return or lost-earnings calculation is attempted.

Each paystub lists $240 as employee pretax deferral and $60 as employee Roth deferral. Nora labels her own rows P1, P2, and P3; these are reconciliation identifiers, not payroll batch numbers. The transaction export has separate pretax and Roth source columns. She checks both, so a Roth-only filter cannot explain her particular table.

Reconciliation row and payday Paystub employee deduction Employee amounts visible in the plan export by October 27 Unmatched amount and current status
P1 — September 18, 2026 Pretax $240; Roth $60; total $300 September 23: pretax $240 and Roth $60 $0; amounts matched, receipt date and timeliness not established by posting alone
P2 — October 2, 2026 Pretax $240; Roth $60; total $300 October 7: pretax $240; no matching Roth transaction found $60 Roth; needs trace, not yet classified as unfunded
P3 — October 16, 2026 Pretax $240; Roth $60; total $300 No matching employee transaction found in either source $300; both sources need trace
Selected-period totals Pretax $720; Roth $180; total $900 Pretax $480; Roth $60; total $540 $360 unmatched: pretax $240 plus Roth $120

Use the $360 gap to request a trace; these selected records do not establish a final loss. Nora has not yet established the plan’s actual receipt dates, whether a rejected participant allocation exists, whether another transaction identifier applies, or whether the export is complete. She records those as questions rather than choosing an explanation that sounds likely.

P1 is useful comparison evidence: its employee amounts are visible as separate sources. It does not prove that a five-calendar-day posting interval is the employer’s lawful deposit schedule. P2 also shows why “the October 2 payroll posted” is an incomplete answer. Only $240 of its $300 employee deduction appears in Nora’s export. A batch-level reassurance must still account for the missing $60 Roth line.

For each row, Nora saves the original paystub, the dated export, and a cropped view showing the selected sources and date range. She creates a redacted copy for the inquiry, retaining the dates, deduction codes, and amounts. Full originals remain in her own secure records. She does not attach a Social Security number, password, full bank details, or unrelated coworker information to ordinary email.

Ask for the trace, with evidence for each stage

An explanation such as “payroll processed it” needs a precise follow-up: processed which amount, for which payday, and at which stage? Request the remittance reference, date funds reached the plan, allocation status, and participant posting information where available. If the parties use different identifiers, ask the administrator to map them. These are investigation questions, not an assertion that every plan exposes identical fields to participants.

Nora’s completed request is addressed to the plan administrator through the employer’s verified benefits channel. The subject and attachments make the scope clear without circulating sensitive identifiers:

Subject: Trace employee 401(k) deductions for October 2 and October 16 paydays

Hello Plan Administrator,

My three selected pay statements show $900 in employee 401(k) deductions: $720 pretax and $180 Roth. The plan export I downloaded on October 27 shows $540 attributable to these paydays: $480 pretax and $60 Roth. My attached reconciliation identifies $360 not yet matched in that export.

For P2, October 2, I can match the $240 pretax amount but not the $60 Roth amount. For P3, October 16, I cannot match either the $240 pretax or $60 Roth amount. Please confirm whether each amount was received by the plan, including the receipt date, remittance reference, and current allocation or rejection status. If a transaction uses a different source label or date, please identify it so I can reconcile the records.

If an employee contribution was deposited late or not deposited, please identify the person responsible for the correction, the proposed timing, and how any required earnings correction will be determined and documented. I am not calculating that correction from the account’s market movement.

Please acknowledge receipt and provide a status update by October 30, or identify the person handling the trace and the next update date. This is my requested follow-up date, not a statement of a statutory response deadline.

Attached: redacted pay statements P1–P3; employee-source transaction export dated October 27; three-row reconciliation. I can provide additional identifying information through an approved secure channel if needed.

Thank you, Nora

This message identifies the discrepancy, requests evidence, and leaves room for a recordkeeping explanation. The request describes the discrepancy without alleging theft. It also avoids asking payroll to return the deduction as ordinary wages or to take another deduction to “make up” the gap. Those proposals would raise separate plan and tax questions; the current task is to trace the original withheld amounts.

Track the reply without closing the case too early

Separate what a reply reports from what the attached records establish. In the fictional case, payroll responds on October 28 that it found a source-code rejection affecting P2’s $60 Roth allocation and is investigating P3’s remittance. Payroll does not supply a plan receipt date for either unresolved item. Nora records this as a reported explanation, not independently verified funding evidence.

Case update Evidence received in the fictional record Disposition and next check
October 27 request Reconciliation and redacted source documents prepared Administrator asked to coordinate the trace; $360 unmatched
October 28 payroll reply Reports P2 source-code rejection; says P3 under investigation Request rejection reference, actual funding status, and responsible correction owner; gap remains $360
October 29 plan export A new $60 Roth transaction is visible and identified by the administrator as P2 P2 principal matched; ask for receipt/correction explanation; P3 $300 remains unmatched
October 30 requested update Administrator says P3 status and any earnings review will be addressed November 2 Record the promised update date; no proof of P3 deposit and no completed earnings determination

At this checkpoint, the remaining unmatched principal is $300, not $360. Nora preserves both versions of the reconciliation so the reduction is explainable. She does not replace the original P2 entry with a backdated “everything was fine” note. A later posting can resolve an amount mismatch while leaving the question of late-deposit correction open.

The example deliberately stops with a partial resolution. No November 2 reply is invented, and no recovered earnings are assumed. A new promised date becomes a follow-up item with a named contact; it is not proof that funding occurred. If another paycheck arrives during the investigation, add a new row without losing the unresolved older payrolls.

A contribution trace record keeps an unresolved payroll sheet separate from matched records

Understand timing without turning an outer limit into permission

The IRS’s current fix-it guide says employee elective deferrals must reach the plan trust as soon as the employer can deposit them. It describes the fifteenth business day of the following month as an outside limit, explicitly not a safe harbor. An employer may need to deposit earlier. Do not interpret that date as permission to hold every employee deduction until then, or as a reason you must wait before asking questions.

DOL’s employee-contributions fact sheet also describes a seven-business-day safe harbor for plans with fewer than 100 participants. That is a particular small-plan rule, not a universal seven-day deadline based on the number of employees you happen to know. Your plan’s status, its terms, and the actual ability to separate contributions matter. Nora has not established those facts, so this article does not calculate a legal due date for any row.

A recordkeeper’s visible posting date is also not automatically the date funds reached the plan trust. Ask for the relevant dates and their definitions. A payroll file sent on time does not, by itself, establish timely funding; an allocation error can be a different problem from money never transmitted. Ask how the funds reached the trust and how those funds were allocated to your contribution sources.

For late employee deferrals, the IRS discusses depositing missed amounts and associated lost earnings and reviewing the process that caused the failure. Its correction guidance addresses plan officials, not a participant’s do-it-yourself interest calculation. Ask what correction applies and how it was determined. Do not substitute a stock-market estimate, a fixed interest percentage, or an unrelated account gain for the plan’s correction analysis.

Get help when records remain missing or answers do not resolve them

Keep a dated contact log, copies of replies, the Summary Plan Description, and your changing reconciliation. If the administrator cannot identify the funds, repeated update dates pass without evidence, or the issue is continuing across payrolls, contact an EBSA Benefits Advisor through the official Ask EBSA site or 1-866-444-3272. You can seek help with understanding the issue; an employer’s proposed follow-up date does not require you to wait before doing so.

Explain what your records show, what the administrator reported, and what remains unknown. A request for assistance is distinct from an adjudicated violation, a formal benefit claim under plan procedures, or a guaranteed recovery. If a formal claim or appeal becomes relevant, obtain the applicable procedure and deadline rather than treating your informal payroll email as automatically satisfying it.

Use the completed reconciliation and request above to start a bounded trace. Match each amount to evidence before closing it; keep unanswered correction questions on the follow-up record. LandOffer.ai publishes this workplace guide; the plan administrator and appropriate benefits professionals remain the sources for your actual plan records and case-specific next steps.

Sources and Further Reading