image

ACH Return Codes: — What They Are and How to Fix Them!

In the realm of electronic payments, the Automated Clearing House (ACH) network plays a pivotal role in facilitating transactions between banks and financial institutions across the United States. However, not all transactions proceed smoothly. Occasionally, payments are returned, accompanied by specific codes that indicate the reason for the return. These are known as ACH return codes.

Understanding these codes is crucial for businesses to maintain efficient payment processes, ensure compliance, and foster trust with customers.

What Are ACH Return Codes?

ACH return codes are standardized alphanumeric codes used to indicate why an ACH payment was returned or rejected. Each code begins with the letter ‘R’ followed by a two-digit number (e.g., R01, R02). These codes are established and maintained by the National Automated Clearing House Association (NACHA) and are used by financial institutions to communicate the specific reason for a transaction’s failure.

For instance, if a customer’s bank account lacks sufficient funds to cover a transaction, the return code R01 (Insufficient Funds) is used. These codes help businesses quickly identify issues and take appropriate corrective actions.

How Do ACH Return Codes Work?

When an ACH transaction fails, the Receiving Depository Financial Institution (RDFI) assigns an appropriate return code and sends it back to the Originating Depository Financial Institution (ODFI). The ODFI then communicates this information to the business that initiated the transaction.

Each return code is associated with specific rules and timeframes for resolution. For example, some codes require action within two banking days, while others allow up to 60 calendar days. Understanding these timeframes is essential to ensure timely responses and maintain compliance with NACHA regulations.

Common ACH Return Codes: –

ACH return codes help banks and businesses understand why a transaction failed. Here’s a complete list of the most common (and uncommon) ACH return codes with explanations:

CodeDescriptionReason
R01Insufficient FundsNot enough balance to cover the debit.
R02Account ClosedAccount closed by customer or bank.
R03No Account/Unable to Locate AccountAccount number not found at receiving bank.
R04Invalid Account NumberAccount number fails validation or is incorrectly formatted.
R05Unauthorized Debit to Consumer Account Using Corporate SEC CodeBusiness debit sent to a personal account without consent.
R06Returned per ODFI’s RequestEntry returned at originating bank’s request.
R07Authorization Revoked by CustomerCustomer withdrew authorization for the debit.
R08Payment StoppedStop payment order issued by customer.
R09Uncollected FundsFunds held or not yet available.
R10Customer Advises Not AuthorizedCustomer claims transaction was unauthorized.
R11Entry Not in Accordance with TermsAuthorized, but amount/date wrong.
R12Account Sold to Another DFIAccount moved to a different bank.
R13Invalid ACH Routing NumberRouting number doesn’t pass validation.
R14Representative Payee DeceasedAuthorized payee is deceased.
R15Account Holder DeceasedPrimary account holder is deceased.
R16Account FrozenAccount restricted due to legal or compliance issues.
R17File Record/Edit ErrorFile or formatting error detected.
R18Improper Effective DateInvalid or incorrect effective date.
R19Amount Field ErrorError in transaction amount field.
R20Non-Transaction AccountAccount not authorized for ACH payments.
R21Invalid Company IdentificationInvalid originator company ID.
R22Invalid Individual ID NumberInvalid customer ID number.
R23Credit Entry Refused by ReceiverReceiver refused to accept credit.
R24Duplicate EntrySame transaction submitted twice.
R25Addenda ErrorIssue in the addenda record.
R26Mandatory Field ErrorRequired field missing or incorrect.
R27Trace Number ErrorIssue with the trace number format.
R28Routing Number Check Digit ErrorCheck digit in routing number is wrong.
R29Corporate Customer Advises Not AuthorizedBusiness disputes unauthorized debit.
R30RDFI Not in Check Truncation ProgramReceiver not part of Check 21 system.
R31Permissible Return EntryReturn allowed by agreement between banks.
R32RDFI Non-SettlementReceiving bank unable to settle.
R33Return of XCK EntryCheck conversion entry returned.
R34Limited Participation DFIReceiving bank limited in ACH capabilities.
R35Return of Improper Debit EntryEntry not submitted properly.
R36Return of Improper Credit EntryCredit entry formatted incorrectly.
R37Source Document Presented for PaymentCheck was also cashed outside ACH.
R38Stop Payment on Source DocumentStop payment issued on original check.
R39Improper Source DocumentCheck used not eligible for conversion.
R40ENR Return by Government AgencyGovernment agency rejects enrollment.
R41Invalid Transaction CodeTransaction code doesn’t match account type.
R42Routing Number/Check Digit ErrorInvalid routing/check digit combo.
R43Invalid DFI Account NumberReceiving bank doesn’t recognize account number.
R44Invalid Individual ID NumberID number not in correct format.
R45Invalid Individual/Company NameName doesn’t match bank records.
R46Invalid Representative Payee IndicatorPayee indicator incorrectly flagged.
R47Duplicate EnrollmentEnrollment already exists.
R50State Law Prevents RCK EntryState law prohibits check conversion.
R51RCK Entry Not EligibleCheck not eligible for conversion.
R52Stop Payment on RCK EntryStop payment on check before ACH.
R53Item and RCK Entry PresentedBoth check and ACH submitted.
R61Misrouted ReturnReturn sent to wrong bank.
R62Incorrectly Formatted ReversalReversal entry contains errors.
R67Duplicate ReturnReturn submitted more than once.
R68Untimely ReturnReturn submitted after deadline.
R69Field ErrorGeneral formatting or content issue.
R70Permissible Return Not AcceptedReceiving bank refused valid return.
R71Misrouted Dishonored ReturnDishonored return sent to wrong place.
R72Untimely Dishonored ReturnDishonored return too late.
R73Timely Original ReturnOriginal return was on time.
R74Corrected ReturnReturn corrected and resubmitted.
R75Return Not a DuplicateReturn claimed as duplicate was not.
R76No Errors FoundNo issue with reported return.
R77Non-Acceptance of R62Reversal not accepted by bank.
R80IAT Coding ErrorInternational ACH transaction has coding error.
R81Non-Participant in IAT ProgramReceiving bank doesn’t support IAT.
R82Invalid Foreign RDFI IDForeign bank identifier invalid.
R83Foreign RDFI Unable to SettleForeign bank can’t complete transaction.
R84Entry Not Processed by GatewayGateway failed to process ACH.
R85Incorrectly Coded International PaymentInvalid coding in international ACH.

Understanding these codes enables businesses to identify issues promptly and take corrective measures to prevent future occurrences.

Why Am I Receiving an ACH Return?

Several factors can lead to ACH returns:

  1. Insufficient Funds: The customer’s account doesn’t have enough money to cover the transaction.
  2. Incorrect Account Information: Errors in account numbers or routing numbers can cause returns.
  3. Closed Accounts: Transactions attempted on closed accounts will be returned.
  4. Unauthorized Transactions: If a customer disputes a transaction or claims it was unauthorized, it may be returned.
  5. Duplicate Transactions: Submitting the same transaction multiple times can result in returns.

Identifying the root cause of each return is essential for implementing effective solutions and maintaining customer trust.

How to Fix and Prevent ACH Return Codes: –

To minimize ACH returns, businesses should consider the following strategies:

  1. Verify Customer Information: Ensure that all account and routing numbers are accurate before initiating transactions.
  2. Obtain Proper Authorization: Secure explicit authorization from customers for each transaction to prevent disputes.
  3. Monitor Transactions: Regularly review transaction reports to identify and address issues promptly.
  4. Educate Customers: Inform customers about the importance of maintaining sufficient funds and notifying the business of any account changes.
  5. Implement Fraud Detection Tools: Utilize advanced tools to detect and prevent fraudulent transactions.

By adopting these practices, businesses can reduce the incidence of ACH returns and enhance the efficiency of their payment processes.

Recent Trends and Updates in ACH Processing: –

Recently, NACHA has updated several ACH return codes to reflect changes in transaction behavior:

  • R11 now addresses payment errors, such as wrong amount/date
  • Increased adoption of AI-powered ACH fraud detection tools
  • More businesses are using eCheck and ACH API integrations

With digital payment processing evolving rapidly, staying informed of changes is crucial for compliance and performance.

Conclusion: –

ACH return codes are integral to understanding and managing electronic payment failures. By comprehending the reasons behind these codes and implementing proactive measures, businesses can minimize disruptions, maintain compliance, and foster positive relationships with customers. Staying updated with the latest industry standards and leveraging advanced payment solutions will position businesses for success in the evolving financial landscape.

author avatar
Tisa Stone Senior Content Writer
Tisa Stone is a Senior Content Writer at eCheckplan, specializing in payment processing, fintech, and merchant services.

Comments are closed.

Say goodbye to high fees

Switch To eCheckplan For Simple
Secure Processing. 🚀

Start Now!

Payments made easy, the way they should be.