Guide to Managing ACH Returns
Last updated: November 5, 2026
Overview
The following guide outlines what ACH Returns are, how they occur, how using Astra reduces the risk of returns (as well as the reduces the operational overhead), and the resources available to help track and manage ACH Returns in real-time.
What Are ACH Return Codes?
When an ACH transaction can’t be completed, the Receiving Depository Financial Institution (RDFI), which is the bank that holds the account being debited or credited, sends a return to the Originating Depository Financial Institution (ODFI). Each return includes an ACH return code: an “R” followed by two digits, such as R01, R04, or R10.
How Do ACH Return Codes Happen?
For the purposes of this guide, we’ll use the following example for context: A User opens a new bank account with a Neobank and attempts to fund this newly opened bank account via an ACH transfer.
Step 01: The User creates a request to move funds from their personal bank account (e.g. their Chase Personal Checking account) to their newly opened DDA account through the Neobank Application.
Step 02: The User had enough funds when they made the initial request. Later that day, before the ACH file was sent to the Federal Reserve, recurring bills drained their checking account. This means they do not have the required funds for the ACH, but the file was already sent to the Fed!
Step 03: Since the timeline for communication between the ODFI and RDFI via the NACHA network usually takes two banking days (sometimes more), the original request continues as is, and the funds are deposited into the User’s new bank account.
Step 04: Two banking days after settlement, Chase (the RDFI) returns the debit to the neobank’s bank (the ODFI) with return code R01 – Insufficient Funds. The neobank now has to recover funds it already credited, assuming the User hasn’t spent or withdrawn them yet.
ACH cutoff times and when to expect returns
Window | Fed deadline | Astra API cutoff | Settles |
|---|---|---|---|
Same Day 1 | 10:30 AM ET | 9:45 AM ET | 1:00 PM ET |
Same Day 2 | 2:45 PM ET | 1:45 PM ET | 5:00 PM ET |
Same Day 3 | 4:45 PM ET | 3:45 PM ET | 6:00 PM ET |
Next Day | 10:30 AM / 2:45 PM / 4:45 PM / 8:00 PM ET | 9:45 AM / 1:45 PM / 3:45 PM / 6:45 PM ET | 8:30 AM ET next business day |
When to expect returns
Administrative returns can arrive up to 2 banking days after the settlement date and typically post around 6:00 PM ET. For a transfer started on a Monday:
Route | Speed | Settles | Return window closes |
|---|---|---|---|
A2A | T+1 | Tue | Thu |
A2A | T+2 | Tue (debit), Wed (credit) | Thu |
A2A | T+4 | Tue (debit), Fri (credit) | Thu |
A2F | T+0 | Mon | Wed |
A2F | T+1 | Tue | Thu |
F2A | T+0 | Mon | Wed |
F2A | T+1 | Tue | Thu |
F2A | RTP/FedNow | Real time (under 30 min) | No ACH return window |
Partnering with Astra to Prevent Returns
By partnering with Astra, you gain more control over your ACH payments (and, therefore, your return rates).
Some of the benefits of Astra include:
Accelerated ACH that makes ACH payments happen faster and reduces the time from initial request to payout
Enhanced fraud detection to help flag payment requests that are unlikely to be honored by the customer’s bank
Automated balance checking to ensure the customer can cover a payment request
Automated updates on the transfer status via webhooks, so you get real-time information and don’t have to wait days or weeks to learn about a returned payment
Astra’s high resolution risk mitigation solution implements real-time dynamic settlement speed decisioning that optimizes for throughput, while reducing origination risk (return codes).
How Can You Track Return Codes?
Even for the most sophisticated programs, ACH Returns will happen. In the event an ACH Return occurs, you can utilize the following resources to track and manage them:
User Webhooks: for tracking User object status changes, such as from approved to suspended. This can occur when we receive R10 Return Codes.
GET User: this resource will return all details about the User object, including the status of the User and why their status change (e.g. if they were suspended)
Transfer Webhooks: for tracking Transfer object statuses changes, such as from processed to failed. This can occur when a User’s transfer fails because of a Return Codes.
GET Transfer: this resources will return all details about the Transfer object, including the status of the Transfer (e.g. failed) and the specific Return Code (e.g R01 - Insufficient Funds)
Transfer Segments resource: for tracking which specific leg of a Transfer object (the Debit or Credit) resulted in a return code. This can help team fold track positive or negative balances (more information below).
Guide to Routines, Transfers, and Webhooks: This articles outlines when webhooks are triggered in relation to status changes for Routines & Transfers. With ACH Transfers, a Transfer can have a status of
processed, which then transitions to a status offailed, if a Return Code is later received.Transaction and ACH Return Reports: via your Astra Dashboard DataHub, Astra provides a downloadable report for all transactions, and an ACH Return report, both of contain details on transfers that experienced a return code. Please note that the transactions report does not include the specific return code. The ACH Return report does contain additional details on each return.
The Ultimate Guide to ACH Return Codes: this blog post includes information about return codes, how they happen, and all the various kinds of return codes that can be issued.
Negative vs. Positive Balances
The following outlines how an ACH Return Code can result in a net zero, negative, or positive balance for your program:
Net Zero Balance: A Return can be received on the ACH debit before the ACH Credit is created. In this scenario, Astra cancels the ACH Credit and there is neither a positive nor negative balance. In other words, no funds were debited from the source account and no funds were credited to the destination account. This is most common on A2A T+4 transfers. Astra holds the credit until T+3 and cancels it if the debit return arrives before the credit is processed.
Negative Balance: A Return can be received on the ACH debit after the ACH Credit has been processed. In this scenario, there is a negative balance as the funds have been credited to the destination account, but the debit from the source account failed and the funds from the debit are absent. This is most likely on A2A T+1 and T+2 transfers, where the credit goes out before the debit’s return window closes.
Positive Balance: A Return can be received on the ACH Credit after the Transfer has been processed. This usually means the funds are returned to Astra because the account has been closed, is frozen, or has exceeded its allowable daily, weekly, or monthly depository limit. In this scenario, the User is missing their funds. Please contact Astra for further assistance.