ACH Return Codes Explained: The Complete Guide for Finance Teams

July 11, 2025

•

5 min read

In This Article

Share this post

In high-volume banking environments, speed and accuracy go hand in hand. Financial institutions process thousands of ACH transactions every day, from payroll and vendor payouts to recurring debits and cross-institution settlements. When transactions fail, they trigger a chain of exceptions, delays, and compliance risks.

ACH return codes help identify the exact reason a transaction was rejected, whether it’s due to insufficient funds, incorrect account information, or unauthorized access. While useful, these codes can be difficult to interpret and manage, especially at scale.

For banks, credit unions, and fintech platforms, a clear understanding of these return codes is crucial for reducing manual investigation, accelerating resolution, and maintaining clean reconciliation records.

In this guide, we decode the full list of ACH return codes and explain what each one means, so your finance and ops teams can act faster and with full confidence.

What is ACH return Code?

‍

An ACH return code is essentially an error message. It specifies why a particular transaction or payment could not be completed or processed. These codes are governed by the National Automated Clearing House Association (NACHA).

Some common reasons businesses receive an ACH return code include insufficient account balances, unauthorized transactions, incorrect account details, and other errors. It’s essential to understand what each code represents and how to handle it, ensuring that business operations and customer trust are maintained.

ACH code categories:

All ACH return codes listed further in this blog fall into one of the following six categories, each representing a specific type of transaction failure:

1. Account-Related Errors

These return codes indicate issues with the recipient’s account, such as closure, freezing, or incorrect account details, that prevent the transaction from being completed.

2. Authorization & Permission Issues

These codes are triggered when a transaction lacks proper authorization or when the customer explicitly revokes or disputes permission.

3. Insufficient or Unavailable Funds

These codes reflect situations where the account exists but lack enough available funds to complete the transaction.

4. Data, Format & Processing Errors

These return codes are used when the transaction data is incomplete, improperly formatted, or fails NACHA processing standards.

5. Duplicate, Routing & Timing Errors

These codes point to operational issues such as duplicate transactions, misrouted returns, or entries submitted outside allowed timeframes.

6. International & Regulatory Restrictions (IAT Specific)

These codes are associated with international ACH transactions and reflect compliance, participation, or settlement issues specific to cross-border payments.

List of ACH Return Codes

Each ACH return code corresponds to a specific issue and provides guidance on how to resolve it. Below is a comprehensive table listing the most common ACH return codes, what they are and what they mean.

ACH Return Code	Description	Details	Solution	Type
R01	Insufficient Funds	Transaction cannot be completed because the receiver’s account has insufficient funds.	Retry the transaction.	Account-Related
R02	Account Closed	Receiver’s account is closed.	Contact the customers and request details for a different account.	Account-Related
R03	No Account / Unable to Locate Account	The provided account number doesn’t match any existing account.	Contact the customer and re-confirm the details. If there are changes, submit a new payment with revised details.	Account-Related
R04	Invalid Account Number	The account number has been incorrectly or improperly provided.	Contact the customer and get the correct number.	Account-Related
R05	Unauthorized Debit to Consumer Account	A debit entry has been initiated without proper authorization.	Contact the customer to resolve any issues.	Authorization-Issues
R06	Returned per ODFI’s Request	The ODFI has requested the RDFI to return the transaction.	Contact the ODFI.	Other
R07	Authorization Revoked by Customer	The receiver has revoked authorization for the transaction.	Suspend any scheduled recurring transactions and contact the customer to confirm why authorization was revoked.	Authorization-Issues
R08	Payment Stopped	The receiver has requested a stop payment on the transaction.	Contact the customer to solve any problems.	Authorization-Issues
R09	Uncollected Funds	The receiver’s account contains funds that aren’t available yet.	Retry the transaction.	Account-Related
R10	Customer Advises Not Authorized	The receiver claims the transaction was not correctly authorized.	Suspend recurring payments and contact the customer to resolve any problems.	Authorization-Issues
R11	Check Truncation Entry Return	The RDFI determines the transaction is not eligible for check truncation.	Correct any incorrect information (like date, amount, etc.).	Data-Format
R12	Branch Sold to Another DFI	The branch holding the account has been sold to a different financial institution.	Find the new account information and routing number. After correcting the information, update and resubmit the payment via an NOC.	Data-Format
R13	Invalid ACH Routing Number	The ACH routing number provided is invalid or incorrect.	Resubmit the ACH payment with the correct number, or contact the payment processor for assistance.	Data-Format
R14	Representative Payee Deceased	The representative payee is deceased or not able to carry out their duties.	Immediately contact the payer to determine how they want to proceed.	Account-Related
R15	Beneficiary or Account Holder Deceased	The account beneficiary or holder is deceased.	Contact the concerned parties to determine how to proceed.	Account-Related
R16	Account Frozen	The receiver’s account is frozen because of legal or other reasons.	To resolve this issue, you will need to contact your customer, request an alternate bank account or payment method, or dispute it through the ODFI.	Account-Related
R17	File Record Edit Criteria	The transaction contains incorrect data or formatting.	Identify which fields have errors, correct entry errors, and then initiate any further entries.	Data-Format
R18	Improper Effective Entry Date	The entry has an invalid or incorrect effective entry date.	Contact customer support at the relevant financial institution for help.	Data-Format
R19	Amount Field Error	Incorrect values or formats have been entered in the amount field.	Modify the information in the amount field.	Data-Format
R20	Non-Transaction Account	The account isn’t authorized for ACH transactions.	Contact the consumer and ask them to pay via an alternate account without restrictions.	Account-Related
R21	Invalid Company Identification	The company identification number (CIN) provided is incorrect or invalid.	Contact your customer and request them to try the payment again, or use an alternate payment method or bank account.	Data-Format
R22	Invalid Individual ID Number	The individual’s identification number provided was invalid or incorrect.	Contact your customer and discuss retrying the transaction, an alternate payment method, or alternate bank account.	Data-Format
R23	Credit Entry Refused by Receiver	The receiver has refused the credit entry due to an incorrect payment amount, transaction code, or other reasons.	Contact the vendor regarding processing.	Authorization & Permission Issues
R24	Duplicate Entry	The RDFI received a duplicate entry.	First, verify if the entry was actually duplicated. If yes then treat it the same as a return. You can also request the RDFI for a return.	Duplicate, Routing & Timing Errors
R25	Addenda Error	Incorrect or improperly formatted addenda record was provided.	Determine the reason for the error. If it is missing or out of sequence, simply reformat the addenda. If the value exceeds the threshold, change it to be within the threshold, and if the number sequence is invalid, change the sequence number to one.	Data-Format
R26	Mandatory Field Error	A mandatory field has an incorrect or wrongly formatted value.	If caused by a typo, simply correct the typo. If the data matches what the customer provided, contact the customer for clarification, or ask for an alternate account for payment.	Data-Format
R27	Trace Number Error	An incorrect or wrongly formatted trace number was provided.	Identify where the problem occurred and rectify it accordingly.	Data-Format
R28	Routing Number Check Digit Error	The check digit for the routing number is wrong.	In case of an error, redo the entry and try reprocessing the payment. If this fails, contact the customer to verify the provided information.	Data-Format
R29	Corporate Customer Advises Not Authorized	A corporate receiver states the transaction was not properly authorized.	First, halt any recurring payments from that bank account. Next, contact the customer to determine what caused this dispute or cancellation, or ask for an alternative payment method.	Authorization & Permission Issues
R30	RDFI Not Participant in Check Truncation Program	The RDFI doesn’t participate in the check truncation program.	Request the customer for an alternate form of payment. You can also get in touch with your financial institution for support.	Data-Format
R31	Permissible Return Entry (CCD and CTX only)	The corporate receiver authorized a return of an entry.	Contact your customer immediately to obtain authorization for another bank account.	Data-Format
R32	RDFI Non-Settlement	The RDFI is unable to settle the transaction.	Determine the circumstances. You can also contact your customer and ask for another bank account or payment method.	Duplicate, Routing & Timing Errors
R33	Return of XCK Entry	The RDFI is returning a destroyed check entry.	Typically your financial institution must resolve this issue. However, merchants can contact their customers and request an alternate mode of payment and inform them of delays.	Data-Format
R34	Limited Participation DFI	The Receiving Depository Financial Institution (RDFI) has restricted involvement in the ACH network, preventing the transaction from being completed.	Contact the RDFI directly for further steps and information.	Data-Format
R35	Return of Improper Debit Entry	According to NACHA rules, the transaction is an improper debit entry.	This cannot be solved by the merchant, and must be done by the concerned financial institutions.	Data-Format
R36	Return of Improper Credit Entry	According to NACHA rules, the transaction is an improper credit entry.	The associated financial institutions must resolve this.	Data-Format
R37	Source Document Presented for Payment	The transaction’s source document was presented for payment.	The receiver can request for immediate credit from the RDFI.	Data-Format
R38	Stop Payment on Source Document	A stop payment request was made for the original document used in the transaction.	An RDFI using return code R38 must submit the return by the ACH operator’s deadline to ensure the ODFI receives it within 60 banking days of settlement.	Data-Format
R39	Improper Source Document	The source document for the transaction is invalid or incorrect.	The customer and merchant must allow their banks to address the issue.	Data-Format
R40	Return of ENR Entry	The automated enrollment entry is being returned.	This code can’t be resolved at the merchant level.	Data-Format
R41	Invalid Transaction Code	The transaction code provided is invalid or incorrect.	Immediately inform the concerned government agency about the returned ENR.	Data-Format
R42	Routing Number / Account Number Mismatch	The provided DFI account number is invalid or incorrect.	Simply inform the other party about the return, allowing them to correct any incorrect information. You can also contact your bank for further support.	Data-Format
R43	Invalid DFI Account Number	The provided DFI account number is invalid.	This ACH return code can’t be corrected at the merchant level and is handled by the concerned government agency or bank.	Data-Format
R44	Invalid Individual Identifier	The individual identifier provided is invalid or incorrect.	Contact the other transaction party to inform them of the return, and request them to verify their details to those mentioned in the ACH transactions.	Data-Format
R45	Invalid Individual Name	The incorrect or invalid individual name was provided.	Contact the customer to redo the transaction. Alternate payment methods can also be requested.	Data-Format
R46	Invalid Representative Payee Indicator	The representative payee indicator provided is invalid or incorrect.	Contact the concerned government agency to rectify the problem.	Data-Format
R47	Duplicate Enrollment	The RDFI received a duplicate for the same transaction.	Contact the RDFI and request to speak with the ACH operations group department. Provide the agent with the code number and formal definition.	Data-Format
R50	State Law Affecting RCK Acceptance	State law prevents the RDFI from accepting RCK entries.	Verify that you’ve entered the right routing number for the other party. Contact the customer, their bank, or your financial institution to discuss potential payment options that comply with state laws.	Data-Format
R51	Item is Ineligible, Notice Not Provided	The item doesn’t qualify for RCK processing because the required notice wasn’t given.	To resolve ACH return code R51, first identify the reason for the return; if it’s unclear, contact your ACH processor or the RDFI for help.	Data-Format
R52	Stop Payment on Item	The receiver placed a stop payment request on the transaction item.	This ACH return code requires waiting, but you can ask the customer why they requested the stop payment.	Data-Format
R53	Item and ACH Entry Presented for Payment	The original item and the ACH entry were both submitted for payment.	Submit a written request and statement to the RDFI within 15 days, confirming that both the RCK entry and the original item were presented for payment; if the issue continues, contact the RDFI for further assistance.	Data-Format
R61	Misrouted Return	The RDFI returns the entry because it was misrouted.	ACH return code R61 occurs when the RDFI enters incorrect information (like a wrong routing or account number) causing the transfer to be misrouted.	Data-Format
R62	Incorrect Trace Number	The trace number entered is either incorrect or not in the proper format.	To resolve ACH return code R62, follow NACHA’s reversal rules.	Data-Format
R63	Incorrect Dollar Amount	The dollar amount entered is either wrong or not properly formatted.	Contact the RDFI’s ACH operations team and explain that the return amount doesn’t match the original transaction.	Data-Format
R64	Incorrect Individual Identification	The individual ID entered is either incorrect or formatted improperly.	Contact the RDFI, explain the mismatch, and request a reversal so they can reissue the return with the right ID.	Data-Format
R65	Incorrect Transaction Code	The transaction code entered is either incorrect or not properly formatted.	Contact the RDFI’s ACH operator, provide the transaction details, and request a return reversal.	Data-Format
R66	Incorrect Company Identification	The company ID entered is either incorrect or not properly formatted.	Contact the RDFI’s ACH team and explain that the company ID on the return doesn’t match the original transaction. After the return gets reversed, submit a new one with the correct company ID.	Duplicate, Routing & Timing Errors
R67	Duplicate Return	The RDFI received a second return entry for a transaction that was already returned.	Contact the RDFI operations group. Explain the situation to the agent and request reversal or cancellation of the duplicate returns.	Duplicate, Routing & Timing Errors
R68	Untimely Return	The return entry was submitted past the allowed deadline.	Contact the RDFI’s operations team, explain that the return was late, and request a reversal. After it’s reversed, submit a new return within the correct time frame to proceed with processing.	Duplicate, Routing & Timing Errors
R69	Multiple Errors	The entry has several errors, preventing it from being processed.	Reach out to RDFI’s ACH operations team, share the details, and request that they update the return with the correct code and reinitiate it.	Duplicate, Routing & Timing Errors
R70	Permissible Return Entry Not Accepted	The RDFI either declined a valid return entry or failed to give the required notice.	Contact the RDFI, explain the situation, and request that they dishonor the return so it can be corrected.	Duplicate, Routing & Timing Errors
R71	Misrouted Dishonored Return	The dishonored return was sent to the wrong financial institution.	Contact the ODFI that initiated the original transaction, explain the issue, and ask their ACH team to correct the routing number on the dishonored return.	Duplicate, Routing & Timing Errors
R72	Untimely Dishonored Return	The dishonored return was submitted past the allowed deadline.	Contact the concerned ACH operations team from the right ODFI. Remind them of the five-day deadline for dishonoring a return, so they can correct the issue and help resume normal ACH processing.	Duplicate, Routing & Timing Errors
R73	Timely Original Return	The RDFI received the original return entry within the required timeframe.	Reach out to RDFI and request the reason for the delay.	Duplicate, Routing & Timing Errors
R74	Corrected Return		Wait this one out. If some time passes and the code repeats, contact the RDFI and follow the same steps as for code R69.	Duplicate, Routing & Timing Errors
R75	Return Not a Duplicate	The return entry is confirmed to be unique and not a repeat of a previous return.	Contact the RDFI’s ACH operations team, share the transaction details, and ask them to review and correct the issue on their end.	Duplicate, Routing & Timing Errors
R76	No Errors Found	The return entry was reviewed and found to be error-free.	To resolve ACH return code R76, contact the RDFI’s ACH department, share the return code and transaction details, and ask for an update.	Duplicate, Routing & Timing Errors
R77	Non-Acceptance of R62 Dishonored Return	The RDFI does not process dishonored return entries for code R62.	Contact the RDFI’s ACH department to determine which of the two possible reasons applies. If it’s an RDFI issue, you may need to wait for them to fix it; if it involves the recipient, follow up with them directly. Once resolved, ACH payments can continue as usual.	Duplicate, Routing & Timing Errors
R78	Non-Acceptance of R68 Dishonored Return	The RDFI does not accept dishonored return entries for ACH return code R68.	For ACH return code R78, the originating bank needs to update the name or address details and resubmit the payment. In some cases, the receiving bank can also request extra documentation to verify the account holder’s identity.	Duplicate, Routing & Timing Errors
R79	Incorrect Data in Return Entry	The RDFI included incorrect information in the return entry.	First, contact the receiver to confirm they accept ACH payments and verify the information provided. If there’s an error, correct it and resend the credit entry.	International & Regulatory Restrictions (IAT Specific)
R80	IAT Entry	An International ACH Transaction (IAT) entry has been recognized.	Review the codes for accuracy and notify the payer (they may be able to identify and correct the issue). Once the correct codes are entered, the payment can be successfully processed.	International & Regulatory Restrictions (IAT Specific)
R81	Non-Participant in IAT Program	The RDFI is not enrolled in that International ACH Transaction (IAT) program.	Contact your RDFI’s operations team and inform them of the code.	International & Regulatory Restrictions (IAT Specific)
R82	Invalid Foreign Receiving DFI Identification	The foreign receiving bank’s identification number is either incorrect or invalid.	Simply check that the reference number on the IAT matches the one from the customer. If not, resend the payment with the correct reference number to continue processing.	International & Regulatory Restrictions (IAT Specific)
R83	Foreign Receiving DFI Unable to Settle	The foreign receiving financial institution is unable to complete the transaction settlement.	Contact the relevant ODFI for support.	Duplicate, Routing & Timing Errors
R84	Entry Not Processed by Gateway	The transaction was not processed by the gateway operator.	Contact your bank’s ACH operations team and give them the error and transaction details so they can liaise with the RDFI on your behalf.	International & Regulatory Restrictions (IAT Specific)
R85	Incorrectly Coded Outbound International Payment	The ODFI incorrectly coded the outgoing international payment.	Simply notify your ODFI about the SEC code error on the international ACH transaction. Contact them by phone or in person with the transaction details, and they will resend the payment using the correct IAT SEC code. Once done, ACH return code R85 will be resolved, allowing you to continue processing ACH payments.	Data-Format

Simplify ACH Returns and Reconciliation with Osfin.ai

Simply knowing what each return code means is not enough to manage ACH returns at scale. You have to be able to act on them quickly, reconcile transactions accurately, and prevent repeated failures. For banking and finance teams dealing with thousands of entries daily, manual handling of return codes leads to delays, errors, and compliance risk.

That’s where automation becomes essential. With Osfin.ai, reconciliation workflows are built to handle complex ACH logic, exceptions, and return codes with unmatched accuracy. The platform automatically tags exceptions with the correct return reason and routes them to the appropriate team for resolution. From parsing diverse file formats to mapping data across payment gateways, banks, and ERPs, Osfin lets your teams resolve breaks without navigating multiple spreadsheets.

Osfin.ai is purpose-built for banking and fintech teams handling large-scale ACH transaction reconciliation. The platform parses return files and automatically maps return codes (R01–R85), identifies failed entries, flags repeat offenders, and links each item back to the originating transaction across your ERP, core banking, or processor feeds. With AI-driven matching logic, Osfin handles ACH, SWIFT, ISO 20022, and custom API formats with precision.

Osfin’s 100% accurate, high-speed engine matches up to 30 million records in 15 minutes, with real-time exception tagging, auto-routing, and duplicate detection built in. Its no-code rule builder lets finance teams create custom ACH return handling workflows to risk teams.

You get 170+ pre-built connectors, real-time dashboards, audit-ready logs, and transaction-level matching across ledgers, payment files, and bank statements. With Osfin, security is never an afterthought as 256-bit SSL encryption, role-based access, 2FA, and full SOC 2 / PCI DSS compliance are included. You also get audit-ready logs, timestamped records, and a responsive expert support team to assist with onboarding and ongoing reconciliation.

Ready to eliminate reconciliation delays and errors from ACH returns? Book your demo with Osfin.ai today

FAQs on ACH Return Codes

1. How do ACH return codes impact payment processing?

ACH return codes delay the completion of payments and often require manual intervention. They interrupt cash flow, trigger exceptions in reconciliation, and can impact settlement timelines across payroll, vendor payouts, and customer transactions.

2. Can ACH return codes lead to compliance issues if not handled properly?

Yes. Unresolved return codes can result in inaccurate records, repeated failures, and missed deadlines, leading to audit issues and regulatory breaches, especially under NACHA rules. Proper tracking and resolution are necessary for risk-free compliance.

3. Are ACH return codes the same for domestic and international payments?

Not always. International ACH transactions (IATs) involve additional codes specific to cross-border rules, foreign financial institutions, and currency settlement standards. These return codes are categorized separately and must meet different regulatory requirements.

4. What’s the typical turnaround time for resolving a returned ACH transaction?

ACH return issues are usually resolved within 2–5 business days, depending on the code, institution policies, and customer response. Timely action is needed to avoid repeat errors and downstream processing delays.