A returned mobile ACH payment means the bank rejected the transfer after it left your account

When you send money via mobile ACH—through your bank's app, a payment service, or a bill pay system—the receiving bank has a window to reject it. If they do, the money comes back to you, but not instantly. The return can take one to three business days, and your bank may charge you a fee for the rejected transaction. The most common reason is insufficient funds in the receiving account, but there are about a dozen other reasons a bank can send an ACH payment back.

The key difference between a returned ACH and a failed ACH is timing. A failed payment never leaves your account in the first place—your bank stops it before it goes out. A returned payment does leave, clears the receiving bank's initial checks, then gets sent back. That's why you see the money disappear from your account first, then reappear days later.

Key Takeaways

  • A returned ACH payment leaves your account, reaches the receiving bank, then gets sent back—a process that takes one to three business days.
  • The most common return reasons are insufficient funds, closed accounts, and mismatched account numbers or routing numbers.
  • Your bank may charge you a return fee, typically $5 to $15, even though the money is coming back to you.
  • If you sent the payment to the wrong account, contact your bank immediately; the receiving bank can refuse to return funds if the account holder requests it.
  • Repeated returns from the same recipient may trigger your bank to block future payments to that account or flag your account for review.

Why banks return ACH payments and what each reason means

The receiving bank assigns a return code when it sends an ACH back. These codes tell you why the payment was rejected. Insufficient funds (code R01) means the receiving account doesn't have enough money to cover the deposit—this is the most common return. Account closed (code R02) means the account no longer exists. Routing number mismatch (code R03) or account number mismatch (code R04) mean you entered the wrong numbers, and the receiving bank couldn't match them to any account.

Other common codes include account frozen (R07), which happens when the receiving bank has blocked the account due to fraud or legal hold; duplicate entry (code R10), which means the receiving bank thinks you already sent this exact payment; and authorization revoked (code R29), which means the account holder told their bank to reject payments from you. Less common returns include deceased account holder, account type mismatch (you sent to a savings account when the person gave you a checking account), and contact the customer (the bank needs more information before it can process the deposit).

How long it takes for the money to come back

Once the receiving bank decides to return the payment, it sends a return notice to your bank. Your bank then has one business day to credit the money back to your account. In practice, this means the full cycle—from when you send the payment to when it reappears in your account—usually takes two to four business days. If you sent the payment on a Friday, you might not see it back until Wednesday or Thursday of the following week.

Some banks are faster than others. A few large banks process returns same-day or next-day, but most follow the standard ACH timeline. If more than five business days have passed and the money hasn't returned, contact your bank with the payment confirmation number or transaction ID. The bank can trace the return and tell you where it's stuck.

Fees your bank may charge for a returned payment

Most banks charge a return fee when an ACH payment comes back to you, even though you're the one receiving the money back. These fees typically range from $5 to $15 per return, though some banks charge more. A few banks don't charge return fees, but they are the exception. The fee appears as a separate line item on your account, usually labeled "ACH return fee" or "returned item fee."

You can ask your bank to waive the fee, especially if it's your first return or if the return was caused by the receiving bank's error. Some banks will reverse one fee per year as a courtesy. If you use a payment app or third-party service rather than your bank directly, that service may also charge its own return fee on top of your bank's fee. Always check the terms before you send a large payment through an unfamiliar service.

What to do if your ACH payment is returned

First, check the return code your bank provides. If it's a mismatch (wrong account or routing number), contact the person or business you were trying to pay and get the correct information. Do not resend the payment until you've confirmed the details are right. If the return code is insufficient funds or account closed, contact the recipient to find out what happened and whether they can receive the payment another way.

If you sent the payment to what you believed was the correct account and it was returned for account closed or authorization revoked, do not resend it. The receiving bank is telling you the account is not available. Sending it again will only result in another return and another fee. If the recipient says they never received it and their account is open, ask them to contact their bank to find out why the return happened.

Keep the return confirmation from your bank. If the recipient claims they never got the money and you need to prove you sent it, the return notice shows the payment left your account and was rejected by their bank—not that you kept the money.

When repeated returns can trigger account review or restrictions

If the same ACH payment is returned multiple times—for example, you keep trying to send money to an account that keeps rejecting it—your bank may flag your account. Some banks will block future payments to that account number after two or three returns. Others may contact you to ask why you're repeatedly sending to an account that keeps rejecting the payment.

Repeated returns can also trigger your bank's fraud detection system. If your account shows a pattern of sending money that gets rejected, the bank may temporarily restrict your account or require you to verify the transaction before sending it. This is especially true if the returns are to different accounts or if the amounts are large. It's not a penalty, but it's a friction point designed to protect both you and the bank from fraud.

How to prevent ACH returns in the first place

Double-check the account number and routing number before you send any ACH payment. Many payment systems let you enter the information and review it before you confirm. Use that step. If you're paying a business, use the account details from their official website or invoice, not from an email. If you're paying a person, ask them to confirm the numbers by phone or in person if possible.

For recurring payments—like rent or loan payments—set them up once and verify the first payment goes through before you set up automatic future payments. If you're using a new payment service or app, send a small test payment first to confirm the account is correct. The small fee for a test payment is cheaper than the return fee and the delay of a rejected large payment.

If you're receiving ACH payments and want to avoid returns, make sure your account is open and in good standing. If your account is frozen or closed, inform anyone who might be sending you money. If you want to stop receiving payments from a specific person or business, contact your bank and ask them to set up a block rather than letting the payments return—this is faster and doesn't trigger return fees.

Frequently Asked Questions

Can the receiving bank keep my money if my ACH is returned?

No. If the ACH is returned, the receiving bank must send it back to your bank. However, if the receiving bank deposits the money into the account and the account holder then requests the bank not to return it, the bank may honor that request. This is rare but possible. Contact your bank immediately if you sent money to the wrong account—the faster you report it, the better your chances of recovery.

Will a returned ACH hurt my credit score?

No. A returned ACH payment does not appear on your credit report and does not affect your credit score. It only affects your bank account (through the fee) and the receiving bank's records. If the payment was for a bill you owe, however, the bill may still be considered late or unpaid, which could hurt your credit if you don't pay it another way.

What's the difference between a returned ACH and a bounced check?

Both result in the money coming back, but ACH returns are electronic and take one to three days, while bounced checks are paper-based and can take longer. ACH returns are assigned specific return codes that tell you why the payment failed. Bounced checks typically just say "insufficient funds." Both usually result in a fee from your bank.

Can I dispute an ACH return fee?

Yes. Contact your bank and ask them to review the fee. If the return was caused by an error on the receiving bank's side, or if it's your first return, many banks will waive it. If the return was clearly your mistake (you entered the wrong account number), the bank is less likely to waive it, but it doesn't hurt to ask.

How many times can an ACH payment be returned before my bank closes my account?

There's no set number. Most banks will tolerate a few returns, especially if they're spread out over time and for different reasons. However, if you have many returns in a short period, or if the pattern looks like fraud or money laundering, your bank may close your account without warning. Banks are required to report suspicious activity, and repeated failed transfers can trigger that threshold.