Table of Contents
When You Accidentally Send the Same Payment Twice
ACH payments make it easy to send money directly to a customer, vendor, or employee—but even with automation, mistakes can happen. One of the more frustrating errors is when the same payment gets submitted more than once.
When that happens, you’ll likely see ACH Return Code R24, which indicates a duplicate entry. It’s not a fraud flag, and it doesn’t mean the account is closed or the customer is disputing the charge—it just means the system caught a repeated transaction and blocked it.
Let’s take a closer look at what R24 – Duplicate Entry means, what causes it, and how to fix the issue quickly and prevent it from happening again.
What Does ACH Return Code R24 Mean?
ACH Return Code R24 stands for:
“Duplicate Entry.”
Here’s the official NACHA definition:
R24 – Duplicate Entry: The ACH transaction appears to be a duplicate of an entry that has already been processed. It may have the same trace number, date, dollar amount, and other identifying information.
In simple terms: the transaction you submitted was flagged because it looked identical to another payment that had already been sent.
What Causes a Duplicate Entry?
There are several common reasons this can happen:
A payment file was submitted twice by mistake
The same transaction was included in multiple batches
An automated system retried a payment too quickly
The trace number or transaction ID was reused in error
A software bug or user error caused an entry to be duplicated
These situations can happen in any kind of ACH transaction—whether you’re sending payroll, paying suppliers, issuing refunds, or collecting recurring payments.
How to Handle ACH Return Code R24
The good news: a duplicate entry is easy to fix once you spot it. Here’s how to handle it:
1. Check Your Payment History
Compare the returned transaction to recent ACH entries you’ve submitted. Look for duplicate dollar amounts, trace numbers, and timestamps.
2. Identify Why the Duplicate Occurred
Was a file uploaded twice? Did an automated system send the same entry after a timeout? Did someone hit “submit” more than once?
Understanding the root cause helps you prevent repeat issues.
3. Confirm That the Original Payment Was Accepted
Make sure the first entry went through and wasn’t rejected for another reason. If the original payment failed and this “duplicate” is actually valid, talk to your processor before resubmitting.
4. Do Not Resubmit the Duplicate
Once the return is confirmed as a true duplicate, do not try to push it through again. If you still need to send funds, create a new entry with a unique trace number and timestamp.
How to Prevent R24 Returns in the Future
Here are a few best practices to help you avoid R24 errors:
Implement batch file controls to prevent duplicate file submissions
Use unique trace numbers and identifiers for every transaction
Check payment reports before resubmitting failed or delayed payments
Use payment systems that detect and flag duplicates automatically
Train your team on proper file handling, especially when reprocessing transactions
Taking a few extra steps during submission can save time and prevent headaches later.
Get ACH Processing With Durango
ACH Return Code R24—“Duplicate Entry”—means your payment was flagged because it was too similar to one you already sent. While it’s not a serious issue, it can cause confusion for your customer or vendor if not addressed promptly.
At Durango Merchant Services, we help businesses avoid common ACH pitfalls like duplicate entries by providing tools, training, and payment systems that are designed to minimize returns—especially in high-risk or high-volume environments.
