Returned Payroll Direct Deposits: Verify the Failure Before Reissuing Pay
Updated: 6 days ago
A payroll deposit can come back while the employee still needs wages and the employer still needs a bank refund. Those are two separate unfinished jobs. Paying again can restore the employee's pay, but an unnoticed provider retry can then send a second payment. Waiting for the refund can leave the wage problem unresolved.
Start with the particular payment instruction, not the payroll run's overall status. Establish which account failed, what amount remains undelivered and who can still send it. Then authorize one replacement route and follow both the employee payment and the employer's returned funds to their actual outcomes.
This guide is for U.S. employers and payroll teams handling an employee ACH credit that was rejected, returned or reported missing. It does not treat an employer funding-debit failure, tax-payment rejection or incorrect wage calculation as the same incident. The original Return and Reissue Ledger provides a copyable record for coordinating the attempts. Its fictional examples illustrate controls, not tested results from a payroll platform.
If failed-payment handling is part of a provider review, a free SelectSoftware Reviews consultation can help you identify services to evaluate. Ask each candidate who controls retries, which status evidence is available and how replacement payments are recorded.
Table of contents
Find the payment that actually failed
An employee's report is enough to open an investigation. It is not proof that the bank returned the deposit. Ask payroll's authorized provider or originating bank for the payment's current status, the amount, intended settlement date, trace or transaction reference and any return notification. Record the source and time of that answer so a later reviewer can distinguish today's confirmation from yesterday's estimate.
Match the answer to the actual employee credit. A company-bank debit may include wages for many employees, taxes or other amounts. Its appearance on a bank statement does not establish that one employee's receiving account was credited. Likewise, a completed payroll calculation or published pay statement is a record of the run, not a complete receiving-bank outcome.
Use precise status descriptions. A pending instruction may still arrive. A confirmed return identifies money that came back through the payment route. A reversal request describes an attempt to recover an earlier entry. A cancelled instruction needs confirmation of what was cancelled and whether transmission had already occurred. If the source cannot establish the status, record it as unknown instead of selecting the answer that makes replacement easiest.
Obtain the actual return code and the provider or bank's explanation. Do not diagnose from an employee's recollection of an account number or a search result for a similar code. Ask whether the reason concerns the account, routing information, receiving bank or another condition, and what must change before another payment can be attempted.
A notification asking for changed account information also needs classification. Intuit's Notice of Change guidance describes an employee still receiving pay when the bank found corrected information. An account-maintenance instruction, warning and returned credit are different records. Ask the provider whether the notice reports a failed payment, requests a change for future entries or requires some other action. Preserve the notification rather than reducing every message to “bank error.”
If money reached an unintended live account, describe that result accurately. It is not a routine closed-account return. Route the matter to the provider's recovery process and the appropriate internal incident owner. A profile edit does not retrieve the earlier payment, and an attempted recovery should not be described to the employee as completed.
A confirmed return, an unknown payment and a change notice need different questions. Match the notice to the actual credit before authorizing another attempt.
Identify who can still send money
Before creating a replacement, identify every operator and system that can act on this particular payment. The employer, provider support team, automatic retry process and accounts-payable team may each be able to initiate another instruction. One person should coordinate the incident and keep the current decision available to the other operators.
Ask the provider a narrow question: “Is any retry, replacement or recovery instruction already scheduled for this employee payment, and what action will trigger another attempt?” Record its answer and the related ticket or transaction reference. A generic statement that support is reviewing the account does not answer whether a payment is in flight.
Updating bank information can itself be a trigger. Gusto's public payroll-change guidance says that after a bank error, updating the employee's bank account causes a deposit retry. The same guidance directs employers to contact support when the account is known to be wrong but no bank error was received. That is a reason to confirm the actual incident and workflow before changing a profile, not an instruction to apply Gusto's behavior to every provider.
If the employer chooses a paper check or another permitted method, ask how an existing retry will be suppressed and what evidence establishes that result. Record the exact instruction being stopped. “We will not run another payroll” is inadequate when a provider can retry the original credit independently of a new payroll run.
Where the first payment's status remains uncertain and wages need urgent attention, escalate the competing risks explicitly. The wage-payment reviewer should establish the required timing and permitted method. The payment coordinator should establish what can still settle and what controls can limit a duplicate. An employer may need to authorize a replacement while recovery remains open; it should understand and record that exposure rather than assume the first instruction disappeared.
Nacha's public reversal explanation identifies duplicate entries, an incorrect receiver and an incorrect dollar amount as permitted reasons. If a duplicate replacement or a credit to the wrong receiver may qualify, ask the originating bank or provider about that route promptly. The page's five-banking-day explanation concerns availability to the receiving bank after the erroneous entry's settlement date. Confirm the applicable requirements and deadline for your case; eligibility does not guarantee recovery.
Keep an unresolved provider instruction on the incident record with an owner and next contact time. An unanswered support ticket should not silently become authority for two teams to pay. The useful handoff states who may execute the selected replacement and which other instruction must be confirmed before the case can close.
Choose the replacement amount at account level
Determine the amount of undelivered net pay from the actual payment instructions. Do not start by rerunning gross earnings. A payment-method failure can occur after the wage calculation, deductions and taxes were correctly recorded. Establish separately whether the payroll record itself needs a correction and how the named service records a replacement.
Split deposits make this distinction especially important. A paycheck may distribute net pay to two accounts while only one credit fails. The successfully delivered portion remains part of the employee's payment. Replacing the full paycheck can overpay the employee even if the returned portion is correctly identified elsewhere in the books.
For each allocation, record the intended amount, original reference and confirmed outcome. Mark amounts still pending separately from amounts confirmed delivered or returned. A screenshot showing the total net pay is not enough to decide which allocation needs replacement. Confirm whether the provider's notification concerns one credit or the whole payment distribution.
Use a simple obligation check: identify the net amount originally due, the amount confirmed delivered to the employee and any authorized replacement already delivered. The unresolved balance is not automatically a new earning. Pending instructions belong beside that calculation as possible future deliveries, not as completed payments or as zero exposure.
Suppose a fictional employee's net pay is $2,100: $1,500 to one account and $600 to another. The first deposit is confirmed delivered and the second is confirmed returned. With no other payment attempt scheduled, the undelivered amount is $600. A $2,100 replacement would add $1,500 beyond the originally intended employee payment.
Now change one fact: a $600 retry is already scheduled. The employee still has $600 undelivered today, but an additional $600 paper check introduces duplicate exposure unless that retry is controlled. The amount due and the number of possible payment attempts answer different questions. Keep both visible at release.
If the original net amount is itself wrong, open the calculation correction alongside the payment incident. Identify the approved corrected payroll result and its tax and deduction treatment with the responsible reviewer. Do not hide a wage adjustment inside a replacement-check amount that no longer matches the original net obligation.
Read a provider's repair route before changing records
The correct recordkeeping action depends on the named payroll product and the actual payment status. A provider may require a void and recreation, a manual payment entry, an account update, a support-assisted repair or another sequence. Verify that sequence before creating records that could change earnings, tax liabilities or the next export.
Intuit's public missing-direct-deposit instructions distinguish a deposit rejected because an account is closed or nonexistent from money delivered to a live wrong account. They also describe different check and direct-deposit replacement procedures for Intuit QuickBooks Workforce and QuickBooks Desktop Payroll. Those differences matter: a control objective can be common while the actual entries required to accomplish it differ.
Ask the provider to explain the effect of each proposed action. Does it affect only the employee payment, or does it void wages, reverse liabilities, change year-to-date amounts or create another funding debit? Will the payroll-to-accounting export carry an adjustment? What additional record is needed if a physical check was already issued outside the payroll system?
Preserve the original payment reference before following the repair procedure. Connect any void, cancellation, recreated paycheck or manual entry back to that original. If the provider changes transaction identifiers, record the old and new references rather than overwriting the only link to the failed credit.
A negative entry in a payroll report is not proof that cash has been recovered. Gusto's guidance describes a negative payroll entry appearing after reversal submission while bank recovery is still an attempt. Keep the provider's record adjustment and the bank result in separate parts of the ledger. One can precede the other.
Ask whether a return credit goes first to the provider or directly to the employer's bank account, and what report shows its allocation. Do not infer the route from the original company debit. If a credit covers several employees or includes fees, require enough detail to assign this incident's amount without netting unrelated differences together.
Public vendor documentation reviewed on October 13, 2026 supports these examples. It is not a claim that the employer or author has tested the platforms, that every account has the same functions or that support will use the same steps in every case. Use current instructions for the actual service and preserve the specific answer supporting the action.
The required repair route can influence your service choice. SelectSoftware Reviews offers a free consultation for discussing payroll options. Verify a named provider's actual return, replacement and export process before choosing it.
Keep one row for every payment attempt
Use the Return and Reissue Ledger for one employee, one pay obligation and its related attempts. Copy the case header once, then repeat the attempt record for each original credit, retry, paper check, replacement deposit or recovery request. A record of attempts prevents a newly issued payment from erasing the history of money that may still arrive.
Keep the file in the employer's approved system. Use employee and account references appropriate to authorized staff, with masked account identifiers where possible. Link to protected evidence instead of copying full bank details into a widely shared incident log. The ledger is a coordination tool, not a request for the employee's credentials.
Case header
Obligation: Identify the employee reference, payroll period, scheduled payday and net amount due. Record the payroll and payment identifiers separately.
Account allocations: List each intended account allocation, its amount and evidence of the original instruction. Distinguish allocations that succeeded, failed or remain unknown.
Required response: Record the wage-payment timing and method reviewer, applicable jurisdiction questions, urgency and the next employee update time. A bank estimate is not the wage deadline.
Coordinator and authority: Name the incident owner, replacement approver, authorized sender and finance reviewer. Identify the provider support contact or ticket.
Repeat for each attempt
Attempt identity: Record an original credit, retry, replacement or recovery request, with its amount, method and transaction reference. Name the party able to execute it.
Current status: Record the actual source, confirmed status and observation time. Use pending or unknown honestly; distinguish requested cancellation from confirmed cancellation.
Relationship: State which allocation this attempt replaces or recovers. If it is a retry of an earlier credit, identify that credit. Explain why the amount does not duplicate a delivered allocation.
Next action: State the authorized action, responsible operator and time for confirmation. Record which competing instruction must be stopped, checked or escalated.
Outcome evidence: Reference actual delivery, return, cancellation or other outcome evidence. Preserve the original notification and the provider's explanation of any changed status.
Record effect: Identify the associated payroll, company-bank and accounting entries, or the reviewer checking them. Mark effects that remain unverified.
Update the status of an attempt as evidence arrives, while retaining the earlier answer and its time in the supporting history. Do not delete a stopped retry from the ledger: its confirmed cancellation explains why a replacement was safe. A completed replacement should remain connected to any return credit that has not yet reached the employer.
Release a replacement with three checks
The approver should be able to answer three questions from the ledger without reconstructing the entire support conversation. These checks support an operational decision; they do not replace the wage-law review or the provider's required transaction procedure.
Check 1: Is this the supported undelivered amount? Match the proposed payment to the affected account allocation, confirmed delivered amounts and any earlier replacements. Identify a disputed calculation separately. If a credit remains pending, show that exposure rather than using the word returned without evidence.
Check 2: Who else can still pay it? Identify automatic retries, manual checks, provider support actions and other authorized senders. Record their confirmed outcomes or the unresolved duplicate risk. Bind approval to the particular replacement amount, destination, method and sender; a changed proposal needs the appropriate renewed approval.
Check 3: Can this route meet the payment requirement? Confirm the permitted method, the applicable wage timing, current provider cutoff or delivery estimate and the practical way the employee will receive funds. Escalate an unmet or uncertain legal requirement. A provider refund forecast should not become the default date on which the employee will finally be paid.
The Department of Labor's FLSA guidance states that wages the federal law requires are due on the regular payday for the covered period. State wage-payment and final-pay rules can add different requirements. Have the qualified reviewer establish the rule for the actual employee and circumstances. This guide does not give a nationwide number of days to wait after a rejected deposit.
Communicate the confirmed situation plainly. Explain the affected payment amount, the chosen replacement route, the expected receipt date or remaining uncertainty and the next contact time. Avoid asking the employee to repeatedly resend bank details through ordinary email. Verify changed payment instructions through the employer's approved bank-change process.
If an emergency payment was made before the normal payroll repair could be completed, add it to the ledger immediately and tell the other authorized senders. It must be accounted for in the employee-level obligation and in the later provider repair. A compassionate fast response can still create an avoidable duplicate if the second operator never learns about it.
Reconcile the return and employee payment separately
Give the employee-payment work and company-funds recovery different completion checks. The employee may have received an authorized replacement while the employer awaits a returned credit. Conversely, the employer may have its money back while the employee has not received a replacement. A single provider ticket marked closed does not resolve both outcomes.
For employee payment, connect the approved obligation, delivered allocations and replacement evidence. A check printed but not delivered is a different stage from an employee receiving it; a replacement ACH submission is a different stage from its confirmed outcome. Establish the evidence needed for the chosen payment channel and identify any outstanding check-clearing or confirmation work.
For company funds, match the return notification to the credit or provider balance and its amount. Trace any replacement disbursement separately. Keep fees and unresolved amounts in separate categories. Do not hide a missing return behind a larger credit from another incident or reduce the employee's replacement without the relevant authority.
Finance should review the payroll record and bank entries together. A return is not automatically a reduction of wage expense; the employee may still be owed exactly the original wages. A replacement is not automatically a second wage expense. The appropriate entries depend on the provider repair and the employer's accounting arrangement, so confirm the treatment rather than prescribing one universal journal.
The Department of Labor's recordkeeping guidance includes accurate wages paid, payment dates and the period covered among required records for covered nonexempt workers. Retain a payment trail that lets the responsible reviewer understand what actually happened. Keep the employer's full retention obligations and protected source records alongside the incident file.
Close the employee-payment issue when its defined evidence is present, then keep any unresolved company credit or reporting work assigned. Give that remaining work a next review date and escalation route. This allows the team to tell the employee truthfully that payment was restored without claiming the entire financial case has disappeared.
Use two incidents to test the ledger
In the split-deposit example, the original company cash outflow is $2,100. The employee received $1,500 and the receiving bank returned $600. The employer authorizes one $600 replacement after confirming no retry remains. When that replacement is delivered, the employee has received the intended $2,100 across the successful original allocation and replacement.
If the returned $600 reaches the company bank and the $600 replacement clears, the net company cash paid for those employee payments is $2,100: $2,100 out, $600 back and $600 out again. Any fee is separate. This arithmetic illustrates the cash trail; it does not determine the journal entries or say when a particular bank will post its credit.
For a second fictional incident, a $1,800 original credit has unknown status. An urgent $1,800 manual payment is authorized and delivered, with the unresolved original documented. A provider retry is then discovered. The coordinator requests cancellation and records whether the provider confirms it before another payment can settle. Until that result is known, the ledger shows potential duplicate exposure rather than an assumed zero balance.
If another $1,800 is ultimately delivered, the employee has received $3,600 against the intended $1,800 obligation. Open the appropriate overpayment decision and preserve both references. Do not make an automatic $1,800 deduction from a later paycheck simply to balance the incident. Recovery authority, communication and tax treatment are separate decisions.
The examples also show why a returned company credit is not a substitute for an employee-level check. In the first case, the return concerns only one allocation. In the second, a later return can change company cash without by itself establishing which employee payment remains valid. Follow each instruction to its own result.
The fictional employee-payment total and company cash total need different evidence. A returned company credit does not establish that the employee received replacement pay.
Repair the destination before the next payday
Restore the employee's current pay and fix the condition that would repeat the failure. Confirm the corrected bank instruction through the approved process, record who approved it and check which payroll output will actually use it. An employee profile can be correct while an imported allocation or a scheduled retry still uses the earlier destination.
For recurring failures, group incidents by the relevant cause and workflow. Separate closed accounts, invalid instructions, disputed destination changes, unsupported provider procedures and unresolved status reports. A count of returned deposits alone cannot tell the team which boundary failed or whether a repair prevented the next occurrence.
Verify the next relevant run's payment instruction and outcome. Assign that check to someone with access to the actual output and provider evidence, especially if a manual exception was used during the incident. Preserve the old references long enough to explain the earlier return while keeping sensitive account information appropriately protected.
The practical objective is one supported wage obligation, a visible history of payment attempts and a controlled route to the employee's missing amount. A disciplined return-and-reissue record lets payroll act promptly, finance trace cash accurately and the next operator see which instructions are still capable of moving money.
For a broader review of payroll support, an optional free consultation with SelectSoftware Reviews can help narrow provider options. Use your return-and-reissue requirements to ask for specific payment-status and repair evidence.
Explore the Decision Guides library.
See the Payroll Operations & Controls hub.
About the author
Ben Scott writes and maintains payroll decision guides for founders and operators. His work focuses on execution realities and how decisions hold up under growth, complexity, and controls and documentation pressure. He works hands-on in HR and leave-management roles that intersect with payroll-adjacent workflows such as benefits coordination, cutovers, and compliance-driven process controls.
