What to Do When a Direct Deposit Fails

A failed direct deposit is one of the most stressful payroll moments a small employer faces, and it almost always shows up as a returned payment or an employee who never received their net pay. One closed bank account, one wrong routing number, or one rejected transfer can turn a clean payday into a follow up call and a second payment. The good news is that most failed deposits follow the same small set of causes, which means a few steady habits handle them cleanly and keep the records straight.

This guide walks through what to do when a direct deposit fails, from the way you confirm the return to the reissue that puts the net pay back in the right hands. If you are newer to the deposit side of payroll, it helps to start with our guide on how direct deposit works for small business payroll before you dig into the failure steps. For a fuller look at the broader correction process, see our guide on how to handle payroll corrections after payday.

What It Means When a Direct Deposit Fails

A direct deposit fails when the receiving bank rejects the transfer instead of posting it to the employee account. The net pay leaves your payroll bank account, but the receiving bank sends it back, which means the employee never received the money even though the payroll run shows it as paid. The return can take a day or two to show up, which is why a failed deposit often surfaces after payday instead of during it.

The failure can run in a few directions. The bank may return the full net pay because the account is closed or the routing number is wrong. The bank may reject the transfer because the name on the account does not match the name on the deposit. Either way, the fix is the same, which is confirming the return, reissuing the net pay, and recording the correction so the records stay accurate and easy to trace.

Common Causes of a Failed Direct Deposit

Most failed deposits come from a small set of causes. Knowing them helps you find the return fast and fix the right thing instead of the symptom.

• A closed or changed bank account. An employee closes or switches a bank account and the old detail is still on file, so the receiving bank returns the transfer and the net pay never posts.
• A wrong routing number. A routing number is entered one digit off, so the transfer goes to the wrong bank or the wrong branch and the receiving bank rejects it.
• A wrong account number. An account number is keyed in wrong, so the transfer lands on an account that does not belong to the employee or does not exist, and the bank returns it.
• A name mismatch. The name on the bank account does not match the name on the direct deposit, so the receiving bank rejects the transfer to protect the account holder.
• A rejected transfer. The receiving bank rejects the transfer for its own reason, such as a hold or a fraud check, so the net pay comes back even when the detail is right.

Each of these causes shares one root, which is a gap between the bank detail on file and the real account. For a fuller look at the errors that show up alongside a failed deposit, see our guide on what to do when payroll is processed incorrectly.

How a Failed Deposit Shows Up in the Records

A failed deposit is a second transaction, not an edit to the first one. The original entry stays in the payroll register so the run stays traceable, and the return is recorded beside it when the net pay comes back. The reissue is then recorded as a third entry when the net pay goes out again to the right account. The three rows together show what was paid, what came back, and what was reissued.

The correction also lands in the books. The returned net pay hits the cash account when the bank puts it back. The reissued net pay hits the cash account again when the second transfer clears. When each entry is journaled the same day it happens, the payroll register and the books stay tied together, and the month end close starts from numbers that already agree.

How to Handle a Failed Direct Deposit

Even with clean runs, a failed deposit can still slip through, which is why the steps matter. Confirm the return with your payroll bank or payroll platform first, which shows the reason the transfer was rejected. Get the correct bank detail from the employee, and reissue the net pay as a second direct deposit or a paper check.

Record the return and the reissue as second and third transactions so the original entry stays intact. Tell the employee what changed and why, and keep the original entry, the return notice, the correction, and a short note about the cause with the payroll records. A failed deposit handled this way keeps the run traceable, keeps the books tied to the register, and stops the same wrong detail from reaching the next payday.

Example: A Cafe Catches a Closed Account Return

Consider a small cafe with hourly employees paid biweekly. Two days after payday, a server notices their check never hit their bank account. The owner checks the payroll platform and finds the direct deposit was returned because the server closed their old bank account and opened a new one, but the old detail was still on file.

The owner confirms the return with the payroll platform, collects the new bank detail from the server, and reissues the net pay as a second direct deposit. The owner records the return and the reissue as second and third transactions, tells the server about the timeline for the reissued payment, keeps the original entry, the return notice, the correction, and a short note about the closed account with the payroll records, and updates the bank detail on file. The example shows how a closed account return turns into a clean correction when you confirm the return and reissue the same day.

Example: A Shop Catches a Wrong Routing Number

Take a small retail shop with a mix of hourly and salaried staff paid semimonthly. The day after payday, the owner notices a returned direct deposit in the payroll bank account. The owner checks the return notice and finds a new hire entered their routing number one digit off, so the transfer went to the wrong bank and was rejected.

The owner confirms the return, asks the new hire for the correct routing number, and reissues the net pay as a second direct deposit. The owner records the return and the reissue as second and third transactions, tells the new hire about the reissued payment, keeps the original entry, the return notice, the correction, and a short note about the wrong routing number with the payroll records, and rechecks the bank detail before the next run. The example shows how a wrong routing number is caught after payday and corrected with a clean second transaction.

How to Prevent the Next Failed Deposit

A correction is cleaner when the next run does not repeat the same failure. The habits below keep the bank detail on file and the real account from drifting apart.

• Confirm bank details with each employee before the first direct deposit run, including the routing number and the account number.
• Collect updated bank detail when an employee opens or closes an account, and update the file the same day.
• Recheck the routing number and the account number before each run so a wrong digit is caught before the transfer goes out.
• Watch for returns from closed accounts, and reissue the net pay the same day a return shows up so the employee is not left waiting.
• Reconcile the payroll bank account after every run, and review each return with the team so the cause does not reach the next payday.

Failed Direct Deposit Checklist

Use this checklist after each failed deposit so the fix lands in clean records and the same failure does not reach the next run. Work through it in order so the correction stays traceable and the books stay tied to the register.

Getting Started

A failed direct deposit is manageable, and the management is cleaner when you confirm the return, reissue the net pay, and record the correction the same day. Work through the steps above, and your next failed deposit lands in clean records instead of a second mistake.