R06 | Returned per ODFI request
This code indicates the entry was returned at the request of the originating depository financial institution.
What This Code Means
R06 is used when an entry is returned because the ODFI requested that the RDFI return it. This is not a receiver-initiated dispute code like unauthorized debit, and it is not necessarily a funds or account validation issue. Instead, it reflects an origin-side request to reverse or return an entry through approved ACH return mechanisms. The reason for the ODFI’s request can vary and may relate to operational handling, duplicate processing concerns, or other administrative conditions. The code itself does not disclose the underlying reason; it identifies the return as ODFI-requested.
Where Users Usually See This Code
- ACH returns in bank-to-bank operational reports
- Processor dashboards where an origin-side return request was initiated
- Reconciliation records showing administrative returns
Why This Code Appears
- ODFI initiated a request to return an entry
- An origin-side processing issue triggered a return workflow
- Duplicate or erroneous origination was identified and addressed through return channels
- Administrative handling required the entry to be returned
What Typically Happens Next
- The entry is returned with code R06
- The originator’s records reflect the item as returned per ODFI request
- Follow-on handling is typically internal to the originator/ODFI workflow
What This Code Is Not
- It is not a receiver dispute (see R05/R07/R10)
- It is not an insufficient funds condition (see R01/R09)
- It is not an invalid account number outcome (see R04)
Troubleshooting Checklist
- □ Review internal origination and exception logs associated with the entry
- □ Confirm whether the return aligns with an intentional origin-side action
- □ Document the return reason internally, since the code itself is non-specific
- □ Reconcile funds movement and status updates across systems
Notes And Edge Cases
Because R06 communicates a category rather than a specific defect, it can appear in varied scenarios depending on the ODFI’s operational practices. Some originators may see R06 in the context of correcting internal posting issues, while others may rarely encounter it. In multi-party processing chains (originator → processor → ODFI), the initiating reason may be recorded in upstream logs but not visible in the return code alone.