ACH return codes
Every ACH return code from R01 to R85, in plain English. Search by code or by words.
Showing all 70 codes.
Filters
ACH return codes, from achforms.com/ach-return-codes/. Last reviewed October 4, 2026. Every code is listed, whatever was searched or filtered on the screen.
| Code | Meaning | Time frame | Returned by |
|---|---|---|---|
| R01 | Insufficient Funds The account did not have enough available money to cover the payment. Can be sent again: R01 | 2 banking days | Receiving bank (RDFI) |
| R02 | Account Closed The bank account was open before, but it has now been closed by the customer or by the bank. After a fix or new permission: R02 | 2 banking days | Receiving bank (RDFI) |
| R03 | No Account/Unable to Locate Account The account number looks valid, but it does not match the name on the payment or is not an open account at that bank. After a fix or new permission: R03 | 2 banking days | Receiving bank (RDFI) |
| R04 | Invalid Account Number Structure The account number is not in a valid format for that bank. It has the wrong number of digits or fails the bank's own check. After a fix or new permission: R04 | 2 banking days | Receiving bank (RDFI) |
| R05 | Unauthorized Corporate-Coded Debit to a Consumer Account A business-type debit (coded CCD or CTX) was sent to a consumer account, and the consumer says they did not authorize it. Cannot be sent again: R05 Unauthorized-type | 60 calendar days | Receiving bank (RDFI) |
| R06 | Returned per ODFI's Request The sender's bank asked the receiving bank to send the payment back, and the receiving bank agreed. After a fix or new permission: R06 | Agreed between the banks | Receiving bank (RDFI) |
| R07 | Authorization Revoked by Customer The customer had authorized the payments, then cancelled that authorization and told their bank. Cannot be sent again: R07 Unauthorized-type | 60 calendar days | Receiving bank (RDFI) |
| R08 | Payment Stopped The account holder told their bank to stop this payment. After a fix or new permission: R08 | 2 banking days | Receiving bank (RDFI) |
| R09 | Uncollected Funds The account balance looks high enough, but part of the money is not yet available to spend, for example because a deposit is still on hold. Can be sent again: R09 | 2 banking days | Receiving bank (RDFI) |
| R10 | Originator Not Known or Not Authorized The customer told their bank that they do not know the business, or never authorized it to take money from the account. Cannot be sent again: R10 Unauthorized-type | 60 calendar days | Receiving bank (RDFI) |
| R11 | Entry Not in Accordance with the Terms of the Authorization The customer agrees that they authorized payments to this business, but says this payment did not match what they agreed to, for example the amount was wrong or it came too early. After a fix or new permission: R11 Unauthorized-type | 60 calendar days | Receiving bank (RDFI) |
| R12 | Account Sold to Another DFI The account was moved to a different bank because the bank or branch was sold. After a fix or new permission: R12 | 2 banking days | Receiving bank (RDFI) |
| R13 | Invalid ACH Routing Number The routing number on the payment is not a valid ACH routing number, so the ACH Operator rejected it before it reached a bank. After a fix or new permission: R13 | Next file delivery | ACH Operator |
| R14 | Representative Payee Deceased or Unable to Continue The person who received payments on behalf of someone else (a representative payee) has died or can no longer act. The person the payments are for is still living. After a fix or new permission: R14 | 2 banking days | Receiving bank (RDFI) |
| R15 | Beneficiary or Account Holder Deceased The person entitled to the payment, or the account holder, has died. Cannot be sent again: R15 | 2 banking days | Receiving bank (RDFI) |
| R16 | Account Frozen or Returned per OFAC Instruction The bank has restricted the account, by its own decision or because of a legal order, or the US Treasury's sanctions office (OFAC) told the bank to return the payment. After a fix or new permission: R16 | 2 banking days | Receiving bank (RDFI) |
| R17 | File Record Edit Criteria or Questionable Entry The receiving bank could not process some of the details in the payment, or it suspects the payment is fraudulent, or a reversal was sent improperly. After a fix or new permission: R17 | 2 banking days | Receiving bank (RDFI) |
| R18 | Improper Effective Entry Date The effective date on the payment was too far in the future: more than two banking days ahead for a credit, or more than one for a debit. After a fix or new permission: R18 | Next file delivery | ACH Operator |
| R19 | Amount Field Error The amount on the payment is not valid: it is not a number, it is zero when it should not be (or not zero on a zero-dollar entry such as a prenote), or it is over $25,000 on a converted check. After a fix or new permission: R19 | Next file delivery | ACH Operator |
| R20 | Non-Transaction Account The account is a type that does not allow this kind of payment, such as some savings or loan accounts. After a fix or new permission: R20 | 2 banking days | Receiving bank (RDFI) |
| R21 | Invalid Company Identification On a customer-initiated bill payment (a CIE entry), the company identification number is not valid. After a fix or new permission: R21 | 2 banking days | Receiving bank (RDFI) |
| R22 | Invalid Individual ID Number On a customer-initiated bill payment (a CIE or MTE entry), the number that identifies the customer's account with the biller is not correct. After a fix or new permission: R22 | 2 banking days | Receiving bank (RDFI) |
| R23 | Credit Entry Refused by Receiver The person or business the money was sent to refused the deposit, so their bank sent it back. After a fix or new permission: R23 | 2 banking days after the refusal | Receiving bank (RDFI) |
| R24 | Duplicate Entry The receiving bank believes this payment is a copy of one it already received: the trace number, date, amount or other details match. After a fix or new permission: R24 | 2 banking days | Receiving bank (RDFI) |
| R25 | Addenda Error The addenda (extra information) records attached to the payment are wrong: a bad indicator, type code or sequence number, or too many records. After a fix or new permission: R25 | Next file delivery | ACH Operator |
| R26 | Mandatory Field Error A field that must be filled in is missing or contains invalid data. After a fix or new permission: R26 | Next file delivery | ACH Operator |
| R27 | Trace Number Error The trace number is wrong: it is missing from the addenda record of a return or Notification of Change, or it does not match the trace number of the entry it belongs to. After a fix or new permission: R27 | Next file delivery | ACH Operator |
| R28 | Routing Number Check Digit Error The last digit of the routing number, the check digit, does not match the first eight digits. After a fix or new permission: R28 | Next file delivery | ACH Operator |
| R29 | Corporate Customer Advises Not Authorized A business told its bank that it did not authorize this debit from its business account. Cannot be sent again: R29 Unauthorized-type | 2 banking days | Receiving bank (RDFI) |
| R30 | RDFI Not Participant in Check Truncation Program The receiving bank does not take part in a check truncation program. Cannot be sent again: R30 | Next file delivery | ACH Operator |
| R31 | Permissible Return Entry A business payment (coded CCD or CTX) was returned after the normal two-day deadline, because the sender's bank agreed to take it back. After a fix or new permission: R31 | Agreed between the banks | Receiving bank (RDFI) |
| R32 | RDFI Non-Settlement The receiving bank was not able to settle the payment. Ask your bank: R32 | Next file delivery | ACH Operator |
| R33 | Return of XCK Entry A destroyed-check entry (XCK) was returned. The receiving bank may return these at its own discretion. After a fix or new permission: R33 | 60 calendar days | Receiving bank (RDFI) |
| R34 | Limited Participation DFI A federal or state regulator has limited the receiving bank's participation in the ACH network. After a fix or new permission: R34 | Next file delivery | ACH Operator |
| R35 | Return of Improper Debit Entry A debit was sent where debits are not allowed: as a CIE bill payment or to a loan account. After a fix or new permission: R35 | Next file delivery | ACH Operator |
| R36 | Return of Improper Credit Entry A credit was sent with a payment code that only allows debits (ARC, BOC, POP, RCK, TEL or XCK). After a fix or new permission: R36 | Next file delivery | ACH Operator |
| R37 | Source Document Presented for Payment A check was converted to an ACH payment (ARC, BOC or POP), and the paper check was also presented for payment. Cannot be sent again: R37 | 60 calendar days | Receiving bank (RDFI) |
| R38 | Stop Payment on Source Document The customer had placed a stop payment on the check that was converted to an ACH payment (ARC or BOC). After a fix or new permission: R38 | 60 calendar days | Receiving bank (RDFI) |
| R39 | Improper Source Document The check used for a converted payment (ARC, BOC or POP) was not eligible for conversion, or both the check and the ACH payment were paid. Cannot be sent again: R39 | 2 banking days | Receiving bank (RDFI) |
| R40 | Return of ENR Entry by Federal Government Agency A federal agency returned an automated enrollment (ENR) entry. The agency does not take part in the automated enrollment program. | Not stated | Federal government agency |
| R41 | Invalid Transaction Code (ENR) In an automated enrollment (ENR) entry sent to a federal agency, the transaction code is not valid. | Not stated | Federal government agency |
| R42 | Routing Number/Check Digit Error (ENR) In an automated enrollment (ENR) entry sent to a federal agency, the routing number or its check digit is not valid. | Not stated | Federal government agency |
| R43 | Invalid DFI Account Number (ENR) In an automated enrollment (ENR) entry sent to a federal agency, the account number is missing, longer than 17 characters, or has invalid characters. | Not stated | Federal government agency |
| R44 | Invalid Individual ID Number (ENR) In an automated enrollment (ENR) entry sent to a federal agency, the ID number (such as a Social Security number) does not match the agency's records. | Not stated | Federal government agency |
| R45 | Invalid Individual Name/Company Name (ENR) In an automated enrollment (ENR) entry sent to a federal agency, the name does not match the agency's records. | Not stated | Federal government agency |
| R46 | Invalid Representative Payee Indicator (ENR) In an automated enrollment (ENR) entry sent to a federal agency, the representative payee indicator is missing or does not match the agency's records. | Not stated | Federal government agency |
| R47 | Duplicate Enrollment (ENR) A federal agency returned an automated enrollment (ENR) entry because the same enrollment was already sent. | Not stated | Federal government agency |
| R50 | State Law Affecting RCK Acceptance A re-presented check (RCK) entry was returned because of state law: the state has not adopted the rules that allow checks to be presented electronically, or it requires canceled checks to be returned to the customer. Cannot be sent again: R50 | 2 banking days | Receiving bank (RDFI) |
| R51 | RCK Entry Ineligible or Improper A re-presented check (RCK) entry was not eligible or not proper. For example, the customer was not told about the policy, the signature was not genuine, the check was altered, or the amount was read wrongly. Cannot be sent again: R51 Unauthorized-type | 60 calendar days | Receiving bank (RDFI) |
| R52 | Stop Payment on Item Related to RCK Entry The customer had placed a stop payment on the check behind a re-presented check (RCK) entry. After a fix or new permission: R52 | 60 calendar days | Receiving bank (RDFI) |
| R53 | Item and RCK Entry Presented for Payment Both the re-presented check (RCK) entry and the original paper check were presented for payment. Cannot be sent again: R53 | 60 calendar days | Receiving bank (RDFI) |
| R61 | Misrouted Return The originating bank is refusing a return because the receiving bank put the wrong routing number on it. | 5 banking days | Originating bank (ODFI) |
| R62 | Return of Erroneous or Reversing Debit The originating bank is refusing a return because a reversal went wrong: either an erroneous debit was returned while the correcting credit was kept, or an erroneous credit was kept while the correcting debit was returned. The receiver ended up with money by mistake. | 5 banking days | Originating bank (ODFI) |
| R67 | Duplicate Return The originating bank received more than one return for the same payment and is refusing the extra one. | 5 banking days | Originating bank (ODFI) |
| R68 | Untimely Return The originating bank is refusing a return because it arrived after the deadline in the Nacha rules. | 5 banking days | Originating bank (ODFI) |
| R69 | Field Error(s) The originating bank is refusing a return because one or more fields on it are wrong. It lists which ones with the numbers 01 to 07: account number, original trace number, amount, individual ID number, transaction code, company ID, or effective entry date. | 5 banking days | Originating bank (ODFI) |
| R70 | Permissible Return Entry Not Accepted The originating bank is refusing a return that the receiving bank marked as agreed or requested (R06 or R31), because the originating bank did not agree to it or ask for it. | 5 banking days | Originating bank (ODFI) |
| R71 | Misrouted Dishonored Return The receiving bank is contesting a dishonored return because the originating bank put the wrong routing number on it. | 2 banking days | Receiving bank (RDFI) |
| R72 | Untimely Dishonored Return The receiving bank is contesting a dishonored return because it was sent late, more than five banking days after the return settled. | 2 banking days | Receiving bank (RDFI) |
| R73 | Timely Original Return The receiving bank states that its original return was sent on time. It uses this code to contest a dishonor coded R68. | 2 banking days | Receiving bank (RDFI) |
| R74 | Corrected Return The receiving bank is sending a corrected return, after its first return was dishonored with R69 for wrong or missing information. | 2 banking days | Receiving bank (RDFI) |
| R75 | Return Not a Duplicate The receiving bank states that its return was not a duplicate. It uses this code to contest a dishonor coded R67. | 2 banking days | Receiving bank (RDFI) |
| R76 | No Errors Found The receiving bank states that its return did not contain the errors the originating bank reported. It uses this code to contest a dishonor coded R69. | 2 banking days | Receiving bank (RDFI) |
| R77 | Non-Acceptance of R62 Dishonored Return The receiving bank does not accept an R62 dishonored return, because it returned both the erroneous payment and the reversal, or because the money cannot be recovered from the account holder. | 2 banking days | Receiving bank (RDFI) |
| R80 | IAT Entry Coding Error An international ACH payment (IAT) has a coding error, such as an invalid country code, currency code, foreign exchange indicator or transaction type code. Ask your bank: R80 | 2 banking days | Gateway |
| R81 | Non-Participant in IAT Program An international ACH payment (IAT) was returned because the gateway has no agreement to send international payments for this bank or customer. Ask your bank: R81 | 2 banking days | Gateway |
| R82 | Invalid Foreign Receiving DFI Identification In an international ACH payment (IAT), the number that identifies the foreign bank is not valid. Ask your bank: R82 | 2 banking days | Gateway |
| R83 | Foreign Receiving DFI Unable to Settle An international ACH payment (IAT) was returned because of a settlement problem in the foreign payment system. Ask your bank: R83 | 2 banking days | Gateway |
| R84 | Entry Not Processed by Gateway The gateway did not process an international ACH payment (IAT). Processing it would expose the gateway to too much risk, or the foreign payment system cannot handle this kind of payment. Ask your bank: R84 | 2 banking days | Gateway |
| R85 | Incorrectly Coded Outbound International Payment A payment going abroad was sent with a domestic payment code instead of the international code (IAT), so it lacks the details needed for sanctions screening. After a fix or new permission: R85 | 2 banking days | Gateway |
No code matches. Check the spelling, or clear the search to see every code.
Free. No signup. Every code is checked against the sources listed at the bottom of its page.
How to use the ACH return codes list
- Find the code. Your bank statement, payment report or software shows a code such as R01 or R10. Type it in the search box.
- Or search by words. Type what you know, such as “closed account” or “not authorized”.
- Open the code’s page. It says what the code means, who sent it, how long they had, and what to do next.
- Check the details. If the code points to a wrong number, test it in the routing number checker. If your bank sent you a return file, open it in the ACH file viewer to see the code next to each payment. Have a 15-digit trace number? The ACH trace number lookup shows what it means.
How ACH returns work
An ACH payment passes from the sender’s bank, through an ACH Operator, to the receiving bank. If the receiving bank cannot or should not complete the payment, it sends a return with a reason code. The return travels back the same way, and the money goes back with it.
Three kinds of sender use return codes:
| Who sends it | Codes | What it means |
|---|---|---|
| The receiving bank | Most codes, such as R01 to R12, R14 to R17, R20 to R24, R29, R31 | A problem with the account, the funds or the authorization |
| The ACH Operator | R13, R18, R19, R25 to R28, R30, R32, R34 to R36 | The entry was rejected while the file was being processed, before it reached a bank |
| The sender’s own bank | R61 to R70 | It is refusing a return it received (a dishonored return) |
Codes R71 to R77 are the receiving bank’s reply to a dishonored return. Codes R80 to R85 are for international payments. Codes R40 to R47 are used by federal agencies for direct deposit enrollments.
If your bank passes returns to you as a NACHA file, each returned payment has one extra line. It holds the return code and the trace number of the original payment. See what a return file looks like, with a made-up example.
Return time frames: two days or sixty
| Kind of return | Deadline | Examples |
|---|---|---|
| Standard returns | 2 banking days after the payment settles | R01, R02, R03, R04, R08, R09, R29 |
| Unauthorized consumer debits | 60 calendar days after the payment settles | R05, R07, R10, R11 |
| By agreement between the banks | No fixed deadline | R06, R31 |
For the 60-day codes, the bank first gets a signed Written Statement of Unauthorized Debit from its customer. It must then send the return within six banking days of finishing its review.
A business payment (CCD or CTX) taken from a business account does not get 60 days. If it was not authorized, it is returned as R29. For a business account, the bank must return it by the opening of business on the second banking day after settlement. After that the business needs the sending bank to agree to take it back (R31).
Sending a returned payment again
Nacha rules allow a returned payment to be sent again only in three cases:
- Not enough money (R01 or R09). Up to two more tries, within 180 days of the original payment, for the same amount, labeled RETRY PYMT.
- Stopped payment (R08). Only if the account holder authorizes it again after the return.
- You fixed the problem. For example, you corrected a wrong account number. A new payment to the right account after R03 or R04 does not count as a retry at all.
A payment returned as unauthorized may not be sent again. Adding a fee to the retried amount, or splitting it into smaller payments, is also not allowed.
Return rates Nacha watches
Nacha watches how often a business’s debits come back.
| Measure | Level | Codes counted |
|---|---|---|
| Unauthorized returns | 0.5% | R05, R07, R10, R11, R29, R51 |
| Administrative returns | 3% | R02, R03, R04 |
| All returns | 15% | Every debit return, except re-presented checks |
Use the calculator at the end of this page to work out your own rate.
Going over 0.5% for unauthorized returns means your bank must report you and can be made to act. The 3% and 15% levels start a review. Going over them is not a rule violation by itself. A clear, signed ACH authorization form and correct bank details help you stay under all three. To check a customer’s account before the first debit, see ACH account verification.
Return fees
A return can cost money twice. The account holder’s bank may charge a returned item fee, and the business may charge a returned payment fee. A business may collect its fee by ACH only if it told the customer in advance that the fee could be collected electronically, and how much it is. State law can limit the amount. Read ACH return fees.
Numbers that are not used
There is no return code for R48, R49, R54 to R60, R63 to R66, R78 or R79. They do not appear in any code list we checked. A new code, R90, comes into use on March 17, 2028 for sanctions returns.
Work out your return rate
Count your debit payments and your returns for the last 60 days, or for the last two calendar months. The calculator divides each kind of return by the debit payments you sent in that time.
Check "All returned debits". It should also count the returns in the two boxes above, except re-presented check (RCK) entries.
| Measure | Your rate | Result |
|---|---|---|
| Unauthorized returns | ||
| Administrative returns | ||
| All returns |
Going over 0.5% for unauthorized returns means your bank must report you and can be made to act. The 3% and 15% levels start a review. Going over them is not a rule violation by itself.
The rate is your returns divided by the debit payments you sent in the same period. Nacha's rules also allow a second way to count, based on the files the returned payments were sent in. Nothing you type is saved or sent.
Questions and answers
What is an ACH return?
An ACH return is a payment that the receiving bank sends back instead of completing. The bank attaches a return reason code, such as R01 for insufficient funds, so the sender knows why. The money goes back to where it came from.
What happens when an ACH payment is returned?
The payment is undone. If you were collecting money, the amount is taken back out of your account and your bank or payment software shows the return code. If you were paying a bill, the bill is still unpaid, and the business or your bank may charge a returned payment fee. Look up the code to see whether the payment can be sent again.
Why would an ACH payment be returned?
Common reasons include not enough money in the account (R01), a closed account (R02), a wrong account number (R03 or R04), a stopped payment (R08), and a payment the account holder says they did not authorize (R10).
How long can an ACH payment be returned?
Most returns must be sent within two banking days of the payment settling. A consumer who did not authorize a debit has longer. The bank can return it for up to 60 calendar days. For a business account, the bank must return it by the opening of business on the second banking day after settlement.
What does "returned mobile ACH payment" mean on my statement?
It means a payment you made from a bank account through a mobile app was sent back by that bank, so the payment did not go through. Some statement lines add "CONA". Capital One uses CONA as the short name for its bank, Capital One, National Association. Common causes are a low balance or a wrong account number. Ask the card issuer or your bank which return code it received, then look it up here. See returned mobile ACH payment for the usual causes and what to do.
Which ACH return codes are "unauthorized" returns?
Nacha counts R05, R07, R10, R11, R29 and R51 as unauthorized returns. A business that collects payments must keep these below 0.5% of its debits. To see them, tick Only "not authorized" codes in the filters above the table.
Can I download or print the ACH return codes list?
Yes. Use "Download the list (CSV)" to open it in Excel, or "Print this list" and choose "Save as PDF" in your browser.
Are ACH return codes the same as check return codes or wire codes like AC01?
No. ACH return codes start with R and come from the Nacha Operating Rules. Returned paper checks have their own reason codes. AC01 belongs to the ISO 20022 standard used by other payment systems. A code that starts with C, such as C01, is an ACH Notification of Change, not a return.
Sources
- ACH Network Risk and Enforcement Topics (return rate levels, reinitiation), Nacha
- Differentiating Unauthorized Return Reasons (R10 and R11), Nacha
- Risk Management Topics, effective October 1, 2024 (R06, R17, written statements), Nacha
- New Return Reason Code for Sanctions Compliance Obligations (R90, 2028), Nacha
- Green Book: A Guide to Federal Government ACH Payments, US Treasury, Bureau of the Fiscal Service
- 2024 ACH Quick Reference Guide, EPCOR
- 12 CFR 1005.3(b)(3), fees for returned payments (Regulation E), Consumer Financial Protection Bureau
- Swap dealer disclosures (uses "CONA" as the short name for Capital One, National Association), Capital One
General information, not legal or financial advice. Rules change and banks set their own requirements. Check with your bank before you act. ACH Forms is not affiliated with Nacha.