Table of Contents
Why Timing Matters in Dishonor Returns
The ACH system runs on precision—and not just in the numbers and account info. Timing is a huge part of how transactions, returns, and even disputes are managed. When a dishonored return (basically a rejection of a return) isn’t sent back within the strict window allowed, it’s flagged with ACH Return Code R72.
Let’s break down exactly what happens when a dishonored return misses the deadline, and what you can do if it shows up in your system.
R72 Explained: What It Means in Simple Terms
ACH Return Code R72 stands for:
“Untimely Dishonored Return.”
In official NACHA language:
R72 – Untimely Dishonored Return: The dishonored return entry was not sent within the time limits specified in the ACH rules.
Or, to put it plainly:
The bank tried to reject a return, but they took too long.
ACH rules are strict about deadlines, and when those are missed, the dishonored return isn’t allowed to proceed. The system rejects it to keep everything moving efficiently.
How a Dishonor Return Normally Works
When a bank receives a return it disagrees with—maybe they think the return reason code is wrong—they can send a dishonor return to push back. But there’s a catch:
Dishonor returns must typically be submitted within 5 banking days after the RDFI receives the original return.
If that 5-day window passes and they still try to dishonor the return? R72 gets triggered.
Common Causes of an R72 ACH Return
Wondering why this might happen? A few common reasons include:
Internal delays at the bank in reviewing or processing returns
Confusion over return timelines or misunderstandings about when the clock starts ticking
System outages or other technical issues that slow down processing
Manual errors where returns sit too long in someone’s queue before being handled
Whatever the cause, if the dishonor isn’t sent in time, it’s not valid—and the R72 code makes sure the system enforces that rule.
If You See an R72: Here’s What to Do
Getting an R72 response? Here’s how you should handle it:
Step 1: Double-Check the Timing
Look at the original return settlement date and when the dishonor was submitted. If more than five banking days passed, the dishonor is definitely too late.
Step 2: Confirm the Status of the Original Return
The original return likely still stands. Since the dishonor failed, the original returned transaction is considered final.
Step 3: Communicate With Your ACH Provider
Loop in your payment processor or bank if needed to make sure no further action is necessary—and to understand if any customer communication is needed based on the situation.
Step 4: Keep Good Records
Document the original transaction, the dishonored return attempt, the R72 code, and any internal actions taken.
Tips to Keep R72 Errors From Slowing You Down
While you can’t always control what other banks do, you can stay ahead of the curve by:
Responding quickly to any return disputes
Monitoring returns and dishonor notices daily
Working with an ACH provider that tracks return deadlines
Training your team on how return timing works
Automating alerts for return and dishonor submission windows wherever possible
Staying sharp on timing saves you a lot of headaches down the road.
Get ACH Payment Processing with Durango merchant Services
ACH Return Code R72—“Untimely Dishonored Return”—is a reminder that in the world of ACH, even a good reason isn’t good enough if the clock runs out. When banks miss their window to challenge a return, they lose the right to push back.
At Durango Merchant Services, we help businesses keep their ACH operations clean, compliant, and quick-moving. From setting up payment processes to troubleshooting returns like R72, we make sure your ACH program is built for success.
