R11 | Check truncation entry returned
This code indicates the RDFI returned an ACH entry identified as a check truncation-related item that could not be processed as presented.
What This Code Means
R11 is an ACH return reason code used for entries associated with check truncation processing that the receiving institution cannot accept or post. In practical terms, it indicates the RDFI determined that the entry’s context or attributes do not meet the requirements for settlement under the check truncation framework or related handling rules. This is an administrative return category rather than a funds-availability result like insufficient funds. It also differs from account status returns such as closed or invalid accounts, because the issue is tied to entry type or processing eligibility. The code signals that the item was not processed as a valid payable entry under the relevant check truncation handling category.
Where Users Usually See This Code
- Bank or processor return files for specialized ACH entry types
- Back-office reconciliation reports for returned items
- Operational exception dashboards for ACH administrative returns
Why This Code Appears
- Entry type or classification is not acceptable for the receiving bank’s check truncation handling
- The entry was routed or coded in a way the RDFI cannot process under truncation rules
- An administrative mismatch exists between the entry’s details and the receiving bank’s allowed processing paths
- The receiving bank’s systems flagged the item as ineligible or improperly formatted for truncation-related settlement
What Typically Happens Next
- The entry is returned through the ACH network with return reason R11
- The originator and ODFI receive the return and mark the item as failed/returned
- The return is logged as an administrative/processing eligibility outcome rather than a funds dispute
What This Code Is Not
- It is not an insufficient funds determination (see R01/R09)
- It is not an invalid account number outcome (see R04)
- It is not an authorization dispute (see R05/R07/R10)
Troubleshooting Checklist
- □ Review the entry class, identifiers, and origination metadata associated with the returned item
- □ Confirm whether the entry type aligns with the intended processing method and destination
- □ Record the return as an administrative eligibility outcome for audit and reconciliation
- □ Consult your payment processor or ODFI for clarification on how this entry type is supported
Notes And Edge Cases
Administrative return codes can reflect institution-specific processing capabilities and how entry types are interpreted in the RDFI’s systems. Similar entries may post successfully at one institution and return at another if eligibility rules differ. In multi-step processing chains, the visible return code may not reveal the precise internal validation rule that triggered the return, so upstream origination metadata often holds the most useful context. Timing around system updates or routing table changes can also influence whether a given entry is accepted.