What are ACH Return Codes?

ACH​‍​‌‍​‍‌ return codes are standardized code words starting with “R” that indicate the reason behind a particular Automated Clearing House (ACH) entry was returned. The indicators can show situations related to account balance levels, an account’s inactive status, identifying data accuracy, a payment hold, or an authorization outcome. SaaS businesses that accept ACH payments, the specific return code decides what action or solution will be next for these businesses.

It is the Originating Depository Financial Institution (ODFI) that makes the submission of the ACH entry to the bank at the instruction of the customer (Originator) through whom it is acting. The Receiving Depository Financial Institution (RDFI) is the one that receives the entry for the account of the Receiver. When a return situation arises, the RDFI sends out a Return Entry via the ACH network using the return reason code that best describes the reason for the return.

Many regular ACH return entries have to be processed before the ODFI can take the funds. The Return Entry should not be made available to the ODFI later than the Opening of a business on the second day of banking after the original entry’s Settlement Date.

In some cases, unauthorized consumer debits may be eligible for an extended Nacha return period. For such eligible returns, the Return Entry must generally be delivered to the ODFI no later than the opening of business on the calendar day of the settlement 60 days after the original Settlement Date.

In cases of lengthy consumer returns, a Written Statement of Unauthorized Debit (WSUD) is typically required for a consumer to report card theft or unauthorized use. It differs from Regulation E, which generally requires the consumer to notify their financial institution of the unauthorized transfer or other covered error within 60 days after the institution sends the first monthly statement showing the error.

R01 specifies circumstances where the Receiver’s account balance or cash reserve fell short of the debit transaction requirement. It should be noted here that an R01 return does not mean the account is invalid or closed. Based on the Nacha rules, a debit that results in an R01 return can be reinitiated twice on average if such a debit was deemed eligible for a return. Besides that, a permit reinitiation is an event that is to take place after 180 days of the Settlement Date of the original Entry.

The process for addressing an entry returned due to the Receiver not authorizing the Originator varies from the approach taken for an insufficient funds return regarding debit reinitiation. Depending on the return reason, a new debit may require a new authorization.

Different codes should trigger different workflows:

Uncompleted payment events are identified as card declines and ACH returns, with their Uncompleted payment events are identified as card declines and ACH returns, with their occurrence noted separately in the payment cycle. Messages signaling a card authorization decline are commonly transmitted as part of the authorization activity. The processing and settlement of a debit by banks can take place before an associated return is received. Due to this return-delayed model, recurrent billing systems must be capable of handling payment-status changes that occur even after settlement by incorporating return-code-sensitive strategies, not settled ACH payments as permanent.

The initiation of a return relates to either the receiving side’s non-acceptance of the debit or the fulfillment of a legal return criterion. A reversal is started by the sender to fix particular mistakes such as a repeated transaction, a wrong amount, a payment received by the wrong person, a debit carried out before the intended time, or a credit delayed beyond the intended delivery time.