What Is an ACH Return?
An ACH return is an electronic payment that could not be completed and is sent back through the ACH network to the originator, along with a code explaining why. It functions like a bounced check but happens electronically, and it can occur on either a payment sent out or a payment received.
Why ACH Returns Happen
- Insufficient funds:
The receiving account did not have enough balance to cover the transaction.
- Invalid or closed account:
The account number is wrong, or the account no longer exists.
- Unauthorized transaction:
The account holder disputes that they authorized the debit.
- Incorrect routing information:
The routing number does not correspond to a valid financial institution.
- Stopped payment:
The account holder placed a stop on the specific transaction before it settled.
Common ACH Return Codes
- R01 : Insufficient funds. The most common return reason.
- R02 : Account closed.
- R03 : No account or unable to locate the account.
- R04 : Invalid account number, typically a data entry error.
- R07 : Authorization revoked by the customer.
- R10 : Customer advises the transaction was not authorized.
- R29 : Corporate customer advises not authorized.
Return codes are standardized by NACHA, so the same code means the same thing regardless of which bank sent it. This standardization is what makes it possible to build automated handling around specific codes rather than reading each rejection individually.
ACH Returns in Accounts Payable
When a supplier payment returns, the invoice it was meant to settle is still open, even though the payment appeared to have been sent successfully at the time. If the return is not caught and reconciled promptly, the supplier's records show a balance still due while the buyer's records may still show the invoice as paid, an inconsistency that only surfaces during the next supplier statement reconciliation, potentially weeks later.
EXAMPLE
A $12,400 ACH payment to a supplier returns three days later with code R02, account closed. The supplier had switched banks and the old account was closed, but the update was never communicated. Unless someone is monitoring for the return notification, the payment sits unresolved and the invoice remains functionally unpaid until the supplier follows up asking why they have not been paid.
The most common cause behind vendor-side ACH returns is stale banking details, exactly the same vulnerability addressed by verifying vendor bank changes independently, described in internal controls and supplier onboarding.
Resolving an ACH Return
- Identify the return reason.
The return code indicates whether the issue is with the account, authorization, or routing information.
- Contact the vendor.
Confirm current, correct banking details before attempting the payment again, verified through an independent channel rather than trusting an emailed update.
- Correct the payment record.
Update the vendor's banking information in the system to prevent the same return recurring.
- Reissue the payment.
Once corrected details are confirmed, resend the payment through ACH or an alternative method.
- Reconcile the original transaction.
Confirm the returned funds are accounted for and the invoice remains accurately reflected as unpaid until the reissued payment clears.
Preventing ACH Returns
- Verify new vendor banking details independently:
Confirm by phone to a known number before the first payment, not by replying to an email.
- Re-verify banking details on any change request:
A change to existing, previously validated details deserves the same independent confirmation as a new setup.
- Use account validation services:
Some banks offer pre-transaction validation that an account is open and able to receive funds, catching a closed account before the payment is even sent.
- Keep vendor records current:
Prompt updates when a vendor changes bank accounts, communicated and verified rather than assumed.
Frequently Asked Questions About ACH Return
1. What is an ACH return?
An ACH return is an electronic payment that could not be completed and is sent back through the network to the originator with a code explaining why, functioning like a bounced check but happening electronically.
2. What are common ACH return codes?
R01 for insufficient funds, R02 for a closed account, R03 for an account that cannot be located, R04 for an invalid account number, and R07 or R10 for authorization issues. Codes are standardized by NACHA across all banks.
3. Why do ACH payments to suppliers get returned?
Most commonly because the supplier's banking details are outdated, an account was closed or changed without the update being communicated and verified, or the routing information was entered incorrectly.
4. How do you resolve an ACH return?
Identify the return code and reason, contact the vendor to confirm current banking details through an independent channel, correct the payment record, reissue the payment, and reconcile the original returned transaction against the invoice it was meant to settle.
5. How can businesses prevent ACH returns?
Verify new vendor banking details independently before the first payment, re-verify on any change request rather than trusting an emailed update, use account validation services where available, and keep vendor banking records current.
6. What happens if an ACH return is not caught quickly?
The invoice it was meant to settle remains effectively unpaid, but internal records may still show it as paid, creating an inconsistency that only surfaces when the supplier follows up or during the next statement reconciliation.
