Why Did My Direct Deposit Get Rejected and Sent Back?
Payday came and went, and instead of the usual deposit hitting the account, there’s a notice that the transfer bounced back to wherever it came from. It’s an unsettling thing to see, especially when the delay lands during an already tight week before payday.
The short answer
Direct deposits usually get rejected because of a mismatch between the routing and account numbers on file, an account that’s been closed, or an account type that can’t accept the specific kind of deposit being sent. In most cases, the money doesn’t disappear, it returns to the sender, who then needs to reissue the payment once the correct information is confirmed. Fixing the underlying detail that caused the rejection is usually what resolves it going forward.
Common reasons a deposit bounces
A typo in either the routing number or account number is one of the most frequent causes, since even a single incorrect digit is enough for the system to reject the transfer. An account that’s been closed, whether recently or a while ago, will also reject an incoming deposit, since there’s no active account on the receiving end to accept it. Some account types have restrictions on what kinds of deposits they’ll accept, including certain high-yield savings accounts, and a deposit coded incorrectly by the sender can get flagged for that reason too. Occasionally, a hold or restriction placed on an account, sometimes tied to unusual activity, can also cause an otherwise valid deposit to bounce.
What happens to the money after a rejection
When a deposit is rejected, the funds are generally returned to the originating party, whether that’s an employer, a benefits agency, or another payer, rather than being lost. From there, the sender typically needs updated or corrected account information before reissuing the payment, which is why a rejected deposit often means a short delay rather than a permanent loss. The exact timeline for reissuing depends on the sender’s own payroll or payment processing schedule.
Steps to sort it out
- Confirm the account and routing numbers on file. Comparing what’s listed with the sender against a voided check or the bank’s own account details is the fastest way to catch a simple typo.
- Check whether the account is still open and active. An account that was closed, even briefly, will reject deposits until it’s reopened or replaced with updated information.
- Ask the sender directly what error code came back. Rejections usually come with a reason code that can point to the exact issue faster than guessing.
- Watch for a pattern if it keeps happening. A single rejection is usually a data entry issue, but repeated rejections from the same sender may point to a deeper mismatch that needs a more direct conversation with the bank.
When it’s something else entirely
Not every deposit issue is a routing or account problem. Sometimes what looks like a rejected deposit is actually a bank statement showing a payment that was never made in the first place, which points to a different kind of error worth investigating separately. It’s worth reading the specific notice carefully rather than assuming the cause before checking.
Worth remembering
A bounced direct deposit is disruptive, especially around a payday, but it’s usually a fixable, mechanical issue rather than a sign that the money is gone. Confirming account details, understanding that funds typically return to the sender, and following up quickly tend to resolve it faster than waiting to see if it corrects itself.