ACH return
DEFINITION
An ACH return is a rejected or reversed bank transfer sent back through the Automated Clearing House network with a standardized return code explaining why the payment could not be completed.
TABLE OF CONTENTS
RELATED TERMS
An ACH return is a rejected or reversed transaction sent over the Automated Clearing House (ACH) network, meaning a bank transfer that could not be completed or was later reversed after initial processing. Instead of settling normally, the receiving bank sends the payment back through the network with a standardized return code that explains why.
ACH returns can happen for many reasons, from a simple data entry error to insufficient funds in the payer's account to an unauthorized or disputed debit. Because ACH is a batch-based network rather than a real-time one, returns do not happen instantly. A payment can appear to succeed for a day or more before a return is generated, unlike a card decline that typically happens at the moment of authorization. For a subscription business collecting recurring payments by bank transfer, a platform such as Recurly can help detect ACH returns as they come back from the network and route the account into a recovery or dunning flow. Recurly runs a dedicated retry process for ACH and other direct debit methods, separate from the retry logic used for cards, and only retries returns caused by insufficient funds. Under NACHA and related direct debit rules, a return can be retried at most twice.
Why ACH return matters for subscription businesses
ACH payments are increasingly common for recurring billing because they usually carry lower processing costs than cards, but that cost advantage comes with a tradeoff: returns surface later and are harder to predict than card declines. A subscription business that accepts ACH needs a clear process for catching returns, understanding why they happened, and deciding whether and how to retry the payment or reach out to the customer.
Unmanaged ACH returns create real risk. A merchant that keeps billing an account that consistently returns for insufficient funds can face increased scrutiny from its bank or payment processor, and an unauthorized-debit return signals that the customer never approved the payment, which needs a different response than a simple retry. Understanding the return code behind each ACH return is central to handling it correctly and avoiding involuntary churn.
How ACH return works
Every ACH return carries a standardized return code, typically in the R-series (for example, codes for insufficient funds, invalid account number, or a customer-authorized revocation), which the originating bank and merchant use to determine next steps.
A business submits an ACH debit to collect payment from a customer's bank account.
The transaction enters the ACH network and is routed to the customer's receiving bank.
The receiving bank attempts to process the debit against the account.
If the debit cannot be completed, the receiving bank generates a return with a specific reason code and sends it back through the network.
The originating bank relays the return and its code to the merchant, usually within a window defined by ACH network rules rather than instantly.
The merchant reviews the return code and decides whether to retry the payment, contact the customer, or stop collection attempts, particularly for reasons tied to unauthorized transactions.
Return timelines vary by reason. Standard returns for issues like insufficient funds generally arrive faster than returns related to unauthorized debits, which can have a longer window under ACH network rules.
How to use ACH return data
Sorting returns by reason code leads to better outcomes than treating them as a single bucket:
Route insufficient-funds returns into a retry or dunning sequence, since a later attempt may succeed once funds are available.
Treat invalid account or routing number returns as a data problem, and prompt the customer to update their payment details rather than retrying blindly.
Flag unauthorized-debit returns for immediate review, since these indicate the customer disputes the charge and repeated attempts can create compliance risk.
Monitor return rates over time by reason code, since a rising rate of unauthorized returns can draw attention from a payment processor or bank.
Cap retry attempts per invoice so that repeatedly returned payments do not keep cycling indefinitely.
ACH return vs chargeback
An ACH return and a card chargeback both represent a payment that ultimately failed to settle in the merchant's favor, but they work differently. An ACH return happens within the bank transfer network itself, generated by the receiving bank based on a standardized reason code, and it can occur for routine reasons like insufficient funds as well as disputes. A chargeback is specific to card networks and is initiated by the cardholder's bank in response to a customer dispute, following a formal process that can include evidence submission by the merchant. ACH returns are generally faster and cheaper to resolve than chargebacks, but an unauthorized-debit return functions much like a dispute and deserves the same attention.
Benefits and examples
Faster diagnosis of failed payments, since standardized return codes tell a merchant exactly why a payment failed and support a more targeted recovery approach than a generic "payment failed" message.
Reduced involuntary churn, since retrying returns tied to temporary issues like insufficient funds at the right time can recover revenue that would otherwise be lost.
Better compliance posture, since watching for and responding quickly to unauthorized-debit returns helps a merchant stay within ACH network rules and avoid return-rate thresholds that processors monitor.
Example scenario: a customer's monthly subscription payment is submitted by ACH. Two days later, it returns with a code indicating insufficient funds. The merchant's billing system automatically schedules a retry for later in the week, when the customer's paycheck is expected to have cleared, and the retry succeeds without the customer needing to intervene.
Frequently asked questions
How long does it take to get an ACH return? It depends on the reason. Routine returns like insufficient funds typically come back within a few business days, while returns related to unauthorized transactions can take longer under ACH network rules.
What is an ACH return code? It is a standardized code, often in the R-series, that a receiving bank attaches to a returned transaction to explain why it could not be completed, such as insufficient funds, a closed account, or a revoked authorization.
Can a returned ACH payment be retried? Yes, in many cases, particularly for reasons like insufficient funds. However, some return reasons, especially those indicating the customer never authorized the debit, generally should not be retried without first resolving the underlying authorization issue.
Does an ACH return affect my ability to keep accepting ACH payments? A high rate of returns, especially unauthorized-debit returns, can draw scrutiny from a payment processor or bank and may affect a merchant's ability to continue processing ACH transactions.
