News & Information | Electronic Merchant Systems

Understanding Returned Mobile ACH Payments and How to Prevent Them

Written by Blagoja Jovanovski | Aug 15, 2024 9:02:35 PM

 

ACH payments are one of the most affordable payment methods for business owners. By accepting ACH transactions from customers, your business can significantly reduce its payment processing costs. This affordability has led to the ACH network being one of the nation's most popular payment platforms, with more than 8.3 billion ACH payments being transacted in the second quarter of 2024. However, ACH payments aren't without their downsides. One drawback to consider is the cost and inconvenience of returned payments. 

An ACH return code is generated when the ACH network returns a payment. The return code signifies the reason for the payment failure. For example, it may indicate there were insufficient funds or that the account number doesn't exist. Regardless, business owners must understand mobile ACH return codes and their impacts.

This guide explores returned ACH payments, what causes ACH returns, how long ACH returns take, a full list of ACH return codes, and other related topics. Read ahead to learn about ACH returns and how they may impact your business!

What is a Returned Mobile ACH Payment?

A returned mobile ACH payment occurs when a mobile ACH transfer fails. It's similar to a bounced check. In many cases, ACH returns occur because the sender has insufficient funds or provides incorrect details during the transfer process. Returned mobile ACH payments cause headaches for business owners. If a business has already provided a product or service, returned ACH payments may result in lost revenue and cash flow issues. Likewise, fees may be applicable if an ACH return occurs.

So, how do ACH returns work? Let's explore the step-by-step process:

  • Step 1: An ACH transfer fails, so the receiver's bank (RDFI) sends a return code to the originator's bank (ODFI). The return code corresponds to a specific reason the payment failed, such as insufficient funds within the originator's account.
  • Step 2: The ODFI informs the payment originator (sender) that the transaction has failed. Any money sent during the transaction returns to the originator's bank account. Based on the return code, the originator may choose to take action to resolve the issue. For example, in the case of insufficient funds, they may transfer money into their bank account; in the case of an incorrect account number, they may update the recipient's payment details.
  • Step 3: In some cases, the payment originator must pay a fee to the ODFI because of the failed payment. 
  • Step 4: Once the issue is resolved, the originator may choose to initiate the payment again.

ACH return vs. ACH reversal

It's critical to distinguish between ACH returns and reversals. With ACH returns, the payment fails — any money transferred to the receiving account automatically returns to the sender's account. This is similar to a bounced check or a failed credit card payment. On the other hand, an ACH reversal involves a request to cancel an already-completed payment. It's more similar to a refund than a failed payment. To complete an ACH refund (or payment reversal), the request must be initiated within five banking days of the transaction date.

How Does an ACH Transaction Work?

ACH transactions, also known as Automated Clearing House transactions, are bank-to-bank transfers facilitated by the National Automated Clearing House Association (NACHA). There are two types of ACH payments: ACH deposits and ACH credits. Let's explore a step-by-step guide for how ACH transactions work:

  • Step 1: The payment originator uses their bank or a third-party money transfer service to set up a payment. This includes providing information, such as the payment amount and the recipient's bank details. In the case of a customer paying a business, this step may also include the business sending the customer an invoice or bill with ACH payment instructions before the originator initiates the payment. 
  • Step 2: Once the originator authorizes the payment, its bank (ODFI) debits its bank account and sends the ACH files to an ACH operator. 
  • Step 3: After the ODFI sends the files to the ACH operator, the ACH operator forwards the files to the receiver's bank (RDFI).
  • Step 4: The receiver's bank (RDFI) processes the payment, and if everything is correct, the funds are deposited into the recipient's bank account.
  • Step 5: However, if the ACH payment is unsuccessful due to insufficient funds, incorrect payment details, or any other reason, the money is sent back to the recipient's bank account, and a return code is generated to indicate why the payment failed.

So, what is an example of an ACH payment? If a business allows customers to set up direct deposits for recurring bills, such as utilities, this is usually done using an ACH payment. Bank-to-bank transfers help utility businesses reduce payment processing costs at scale.

ACH transfers first began operating in 1972. The ACH network is now one of the most integral components of the money transfer sector in the United States—it is responsible for more than $76 trillion worth of transactions annually. While traditional ACH payments take multiple business days to settle, a new Same Day ACH product allows individuals and businesses to conduct same-day transfers using the network.

What Causes ACH Returns?

ACH returns occur for various reasons, from the sender having insufficient funds in their account to the customer rescinding authorization. When an ACH return occurs, your business will receive an ACH return code corresponding to the reason for the return. For example, if you receive an ACH return code R04, it means an invalid account number was provided for the transaction.

Unfortunately, while some ACH codes are straightforward, others are vague. For example, R07 indicates that the customer revoked authorization but doesn't indicate the reason the authorization was revoked. To find out more, the merchant must contact the customer or the originator's bank. 

How long does an ACH Return Take?

In most cases, ACH returns settle within two days. This means the payment originator should receive the funds back into their account within 48 hours of the RDFI sending the return code to the ODFI. However, if it is a customer-initiated code, such as R07 (customer revokes authorization), then it may take up to 60 days to resolve. 

While two days may not sound like a long time, it can create numerous problems for businesses accepting ACH payments. This means it may take multiple days for the customer to fix the ACH issue and re-attempt the payment. If your business is dependent on quick payments and reliable cash flow, ACH returns may cause massive headaches!

What Happens if ACH Payments are Returned?

If ACH payments are returned, the payment originator should receive a refund within 48 hours (unless it's a customer-initiated return, in which case it may take up to 60 days). Likewise, the originator may have to pay an ACH return fee.

From a business's perspective, ACH payments create various issues. Not only do failed ACH payments result in cash flow issues for businesses, but the National Automated Clearing House Association (NACHA), which manages the ACH network, has strict guidelines for how many ACH returns are acceptable for businesses. It assesses ACH returns on a rolling basis for the preceding 60 days. Let's explore the ACH return limits below:

  • Overall Returns: Must remain below 15% of transactions
  • Administrative Returns (R02, R03, and R04): Must remain below 3% of transactions
  • Unauthorized Returns (R05, R07, R10, R29, and R51): Must remain below .5% of transactions.

Not adhering to the above ACH return rate thresholds may result in enforcement proceedings and fines. 

What is an ACH Return Fee?

ACH return fees are charges associated with failed ACH payments. To cover the costs of processing ACH returns, many payment providers issue fees to payment originators if they're at fault for failed ACH payments. ACH return charges vary depending on the payment provider and circumstances.

ACH Return Codes List

Understanding ACH return codes makes it easier to manage returned payments within your business. While return codes don't provide a detailed analysis of why a payment is returned, they ensure you understand the basic premise of the return. The most common ACH return codes are "customer-initiated return codes and bank-initiated return codes." However, there are also some lesser-known return codes. Let's explore a full list of ACH codes:

Customer-initiated Return Codes

Let's explore the primary customer-initiated return codes:

  • R05: Unauthorized consumer debit using corporate SEC code
  • R07: Authorization revoked by customer
  • R10: Customer advises unauthorized, improper, ineligible, or party of an incomplete transaction
  • R11: Check truncation entry return
  • R29: Corporate customer advises not authorized

Bank-initiated ACH Return Codes

Let's explore the primary bank-initiated return codes:

  • R01: Insufficient funds
  • R02: Account closed
  • R03: Unable to locate account or no account
  • R04: Invalid account number
  • R06: Returned due to ODFI's request
  • R08: Payment stopped
  • R09: Uncollected funds
  • R13: Invalid ACH routing number
  • R17: File record edit criteria
  • R20: Non-transaction account
  • R23: Credit entry refused by the receiver

Less Common ACH Return Codes

Let's explore other types of ACH return codes:

  • R12: Branch sold to another DFI
  • R14: Representative payee deceased or unable to continue in that capacity 
  • R15: Beneficiary or account holder deceased
  • R16: Account frozen/entry returned per OFAC instruction
  • R18: Improper effective entry date
  • R19: Amount field error
  • R21: Invalid company identification
  • R22: Invalid individual ID number
  • R24: Duplicate entry
  • R25: Addenda error
  • R26: Mandatory field error
  • R27: Trace number error
  • R28: Routing number check digit error
  • R30: RDFI not a participant in check truncation program
  • R31: Permissible return entry
  • R32: RDFI non-settlement t
  • R33: Return of XCK entry
  • R34: Limited participation DFI
  • R35: Return of improper debit entry
  • R36: Return of improper credit entry
  • R37: Source document presented for payment
  • R38: Stop payment on source document
  • R39: Improper source document or source document presented for payment 
  • R40: Return of ENR entry by Federal Government Agency
  • R41: Invalid transaction code
  • R42: Routing number or check digit error
  • R43: Invalid DFI account number
  • R44: Invalid individual ID number or identification number
  • R45: Invalid individual name or company name
  • R46: Invalid representative payee indicator
  • R47: Duplicate enrollment
  • R50: State law affecting RCK acceptance
  • R51: Item related to RCK entry is ineligible or RCK entry is improper
  • R52: Stop payment on item related to RCK entry
  • R53: Item and RCK entry presented for payment
  • R61: Misrouted return
  • R62: Return of erroneous or reversing debit
  • R63: Incorrect dollar amount
  • R64: Incorrect individual identification
  • R65: Incorrect transaction code
  • R66: Incorrect company identification
  • R67: Duplicate return 
  • R68: Untimely return
  • R69: Field error(s)
  • R70: Permissible return entry not accepted or return not requested by ODFI
  • R71: Misrouted dishonored return 
  • R72: Untimely dishonored return
  • R73: Timely original return
  • R74: Corrected return
  • R75: Return not a duplicate
  • R76: No errors found
  • R77: Non-acceptance of R62 dishonored return
  • R80: IAT entry coding errors
  • R81: Non-participant in IAT program
  • R82: Invalid foreign receiving DFI identification
  • R83: Foreign receiving DFI unable to settle
  • R84: Entry not processed by gateway
  • R85: Incorrectly coded outbound international payment 

What to Do if a Payment is Returned?

If a customer sends your business a payment and it's returned, it's best to contact the customer directly to find a way to correct the issue. In some cases, it may be due to a minor technical issue, such as the customer using the incorrect account number for your commercial bank account. Regardless, speaking with the customer before re-attempting payment is the best way to avoid further issues, as an additional failed ACH payment may result in more delays and fees.

However, if the reason for the returned ACH payment is that the customer revoked authorization, the issue may be a bit more complicated. You'll need to determine if the transaction was legitimate and whether you want to dispute the ACH return.

Can Returned ACH Payments Be Disputed?

Most returned ACH payments are not eligible for dispute. For example, if an ACH return occurs because a bank account doesn't exist, your business cannot dispute it. However, if a customer claims a transaction is unauthorized, your business can dispute the return if you believe the customer is incorrect. 

This is very similar to chargeback fraud, where customers attempt to file chargebacks for goods or services they have already received. Make sure to protect your business from all types of payment disputes by having strong controls in place to avoid fraudulent ACH returns.

How to Prevent Returned ACH Payment and Reduce Your Risks?

If your business uses ACH billing, preventing returned payments is essential to protecting your bottom line. Not only do ACH returns result in cash flow issues, but they can also lead to fines from NACHA (or, in some cases, loss of access to ACH payments). As previously discussed, you must keep ACH returns below the 15% threshold (and lower thresholds for specific types of ACH payments, such as administrative returns and customer-initiated returns).

So, how do you reduce your risk? Let's find out:

Confirm all details

Whether your business is sending or receiving an ACH payment, it's critical to confirm all details before initiating a payment. This is the simplest way to avoid unnecessary ACH payment returns.

Don't immediately fulfill orders

As ACH payments take longer to settle, they create an opportunity for fraudsters. If a customer says they initiated a payment, don't take their word for it — wait for the payment to clear. If a customer wants to pay with ACH, make sure they know it takes longer for your business to fulfill the order.

Communicate with customers

Next, always communicate with your customer if there are any issues. If there's an issue with a payment, it's better to resolve the problem before re-attempting a transfer.

Use a high-quality merchant service provider

Lastly, partner with a high-quality merchant service provider to avoid ACH payment returns. A merchant service provider will provide advice and resources to help reduce your returned ACH payments. Likewise, they'll have access to alternative payment methods so your business can benefit from better payment solutions. Never underestimate the power of choosing the right merchant account provider!

Final Thoughts on Returned ACH Payments

Now that your business understands ACH returns, how they work, and the ACH codes that correspond to various payment issues, it's time to protect your business from ACH return fees. Always use responsible ACH practices within your business to ensure you don't pay excessive ACH return fees or experience cash flow issues due to rejected ACH payments.

It's essential to choose a reputable merchant service provider if you want to protect your business from disputed payments. Whether it's ACH returns, chargebacks, or any other type of disputed payment, a security-focused merchant service provider is an excellent resource!

ACH Return FAQs