Table of Contents
When a Return Entry Gets Sent Twice
The ACH network is built for speed and accuracy, but even in a highly automated system, mistakes can happen. One of the more straightforward errors is when a return entry gets sent more than once, leading to confusion for all parties involved.
That’s when you’ll see ACH Return Code R67.
Let’s walk through what R67 – Duplicate Return means, why it happens, and how to handle it so you can get your payments back on track.
What Does ACH Return Code R67 Mean?
ACH Return Code R67 stands for:
“Duplicate Return.”
Here’s NACHA’s official definition:
R67 – Duplicate Return: The return entry appears to be a duplicate of one that was previously submitted for the same original transaction.
In plain language: the same transaction was returned twice, and the system flagged the second one as a duplicate.
Why Would an R67 ACH Return Happen?
There are several reasons you might encounter an R67 return:
Clerical errors during manual return processing
System glitches causing the same return file to be sent twice
Miscommunication between teams or departments processing ACH returns
Banking system delays that lead someone to think the return didn’t go through the first time, so they send it again
Duplicate returns cause confusion because the system isn’t built to handle two returns for the same payment—only one is valid.
How to Handle ACH Return Code R67
Here’s what to do if you receive an R67 return:
1. Review the Original Return
Look at the transaction records to confirm that the return was already submitted and processed once.
2. Verify the Duplicate
Compare the duplicate return to the original. Check the trace number, dollar amount, and transaction information to ensure they match.
3. Communicate With Your ACH Processor or Bank
Let your ACH provider or bank know that a duplicate was flagged. They may automatically disregard the second return, but it’s good practice to confirm that no extra actions are needed.
4. Monitor Your Records
Make sure your internal systems reflect only one return for the transaction. Update your customer payment history and reconciliation logs as needed.
How to Avoid R67 ACH Returns in the Future
Here’s how you can help prevent duplicate return issues:
Double-check your return submissions to avoid sending the same file more than once
Wait for confirmation from your ACH processor before re-attempting a return
Use ACH software that tracks returns automatically and flags duplicates before submission
Train your accounting and payment teams to recognize return processing steps clearly
Keep good internal logs showing when and how each return was submitted
A little extra attention can save a lot of unnecessary confusion.
Get ACH Payment Processing with Durango merchant Services
ACH Return Code R67—“Duplicate Return”—means the same payment was returned more than once, and the duplicate was rejected. While it’s not a major compliance problem, it’s still something that needs to be managed carefully to keep your payment records clean and accurate.
At Durango Merchant Services, we help businesses manage every aspect of their ACH processes—including returns—so you can avoid errors, stay organized, and keep your cash flow steady.
