ACH Returns

An ACH return occurs when an ACH transaction is sent out but cannot be completed and is returned by the receiving financial institudion. For example, an ACH debit may be returned because the sender account has insufficient funds.

Merchant Responsibilities related to ACH Returns

The merchant should have processes in place to manage the following when processing ACH transactions:

• Review ACH returns regularly to identify the cause and prevent future returns
• Follow NACHA requirements when retrying returned transactions
• Monitor ACH return rates to remain below NACHA thresholds
• Review and respond to Notifications of Change (NOC)
• Respond to POA requests
• Request a WSUD where applicable

Review ACH Returns

ACH returns are available through the following reports:

• ACH Return File for file-based ACH
• Daily Exceptions Report for ACH API processing

Note: if you are using the ACH API, you may request the ACH Return File in addition to the Daily Exceptions Report by emailing [email protected].

Review the returns and the return reasons to root cause why the returns are occurring, and how they can be avoided in the future.

For more info on ACH Return/Reason Codes, refer to ACH Return Codes.

Retrying Transactions with Returns

Except forRCK entries, a returned ACH entry may be reinitiated only when:

1. The entry was returned for insufficient or uncollected funds. The original entry may be reinitiated a maximum of two times.
2. The entry was returned for stopped payment and the Receiver authorized re-initiation.
3. Corrective action was taken to resolve the reason for the return.

Monitor Return Rates

Merchants originating ACH debits must remain below NACHA return-rate thresholds.

• Unauthorized Return Rate: The percentage of debit entries returned because they were unauthorized
• Administrative Return Rate: The percentage of debit entries returned for administrative reasons
• Overall Return Rate: The percentage of all returned debit entries, regardless of reason, excluding RCK entries.

Return rates are measured over a rolling 60-day period. Calculate each rate by dividing the applicable number of returns by the total number of forward debit entries during the same period.

Merchants must remain below these thresholds to comply with NACHA requirements. Exceeding these thresholds may result in suspension of ACH processing. TabaPay may require a remediation plan to address excessive return rates.

Notification of Change (NOC) Process

A Notification of Change (NOC) notifies the ACH Originator that information submitted with an ACH entry is incorrect or outdated.

NOCs are included in the ACH Return File or Daily Exceptions Report (when using ACH API). Merchants must make the requested correction within six business days of receiving the NOC or before initiating the next ACH entry, whichever is later.

NOC codes begin with C. Refer to Notification of Change for code definitions.

Updating Customer Records

In most cases when you receive an NOC, your ACH transaction should still process as expected. It does NOT mean a failed transaction.

After receiving the NOC, update your customer's records to reflect the change to their account and ensure that future ACH transactions can be processed correctly.

Request for Proof of Authorization (POA)

A financial institution may request Proof of Authorization (POA) for an ACH debit. Merchants must maintain evidence that the Receiver authorized the debit and provide the requested documentation within the required timeframe.

Documentation may include:

• Original authorization
• Transaction date and time
• Customer and account information
• Additional evidence of authorization

If authorization cannot be provided, review the process used to collect and retain authorization before initiating ACH debits.

Written Statement of Unauthorized Debits (WSUD)

A Written Statement of Unauthorized Debit (WSUD) documents a Receiver's claim that an ACH debit was unauthorized. The Receiver's financial institution (RDFI) obtains the WSUD to support certain unauthorized ACH returns.

Unlike card chargebacks, ACH returns do not have a dispute or representment process. A merchant may request a copy of the WSUD associated with an unauthorized return when applicable.

When a copy of a WSUD is requested through the Originating Depository Financial Institution (ODFI), the RDFI must provide the copy within 10 banking days of receiving the request.

To request a WSUD, provide:

• Trace Number
• Settlement Date
• Receiver Name
• Amount of transaction
• Unauthorized Return Code

Contact TabaPay to initiate the WSUD report.