R15 | Beneficiary deceased
This code indicates the receiving institution returned the entry because records show the receiver/beneficiary is deceased.
What This Code Means
R15 is returned when the RDFI indicates that the receiver (often in contexts involving benefits, entitlements, or recurring payments) is recorded as deceased, making the posting of certain entries inappropriate or restricted. This return code is primarily administrative and compliance-driven. It does not communicate a funds issue or an account number formatting issue; it indicates the receiving institution has a status record that prevents posting under applicable policies. The presence of R15 does not necessarily mean every transaction type would be blocked universally, but it signals that the receiving institution is returning the entry based on the beneficiary status in its records. The return reflects a sensitive status condition rather than a technical processing failure.
Where Users Usually See This Code
- ACH credit returns related to benefits or structured payments
- Bank operational returns for accounts with restricted status
- Processor return files flagged as administrative/compliance outcomes
Why This Code Appears
- RDFI records indicate the receiver/beneficiary is deceased
- Account status was updated due to official reporting or internal compliance handling
- The entry type is restricted for posting under deceased beneficiary controls
- The receiving institution applied a status-based return rule
What Typically Happens Next
- The entry is returned through ACH with R15
- The originator’s systems mark the transaction as returned and typically stop automated continuation to the same receiver details
- The return may trigger additional internal review within the originator’s reconciliation processes
What This Code Is Not
- It is not insufficient funds (see R01/R09)
- It is not a closed account return (see R02), though both can occur in different contexts
- It is not an authorization dispute code (see R05/R07/R10)
Troubleshooting Checklist
- □ Record the return code and entry details for reconciliation and audit purposes
- □ Confirm whether your internal records require status review or additional verification processes
- □ Ensure automated retries do not proceed without appropriate internal checks
- □ Coordinate through official program, processor, or ODFI workflows for next handling steps
Notes And Edge Cases
Status-based returns can be influenced by how institutions update records and apply posting restrictions. Some entries may be returned even if the account remains open, depending on the institution’s compliance approach. The return code does not provide details on documentation or timing of the status update. In some cases, the beneficiary status may be associated with a specific payment program or posting rule rather than the account’s general ability to receive other credits. Because of the sensitive nature of this return, originators often treat repeat attempts cautiously.