Item related to RCK Entry is Ineligible or RCK Entry is Improper
Category: Check conversion & RCK Initiated by: RDFI
Applies to (SEC scope)
RCK
camt.053 mapping
Not mapped
Reinitiation
No permitted reinitiation route on the sources reviewed
Nacha's definition
A RCK Entry considered to be ineligible or improper.
Verbatim from Nacha — ISO 20022 Guide to Mapping U.S. ACH Return Items and Notifications of Change, August 2023, Version 2.01 (Table 1, return reason codes) (return reason code table). Applies to: RCK.
How it appears in an ISO 20022 statement
Nacha's mapping guide marks this code as not currently supported or mapped for camt.053 (footnote 1): it applies to Standard Entry Class codes or flows the guide does not cover, so it has no published ISO 20022 reason-code mapping.
Return time frame
Nacha groups this code with the unauthorized debit return codes — R05, R07, R10, R29 and R51 — for its unauthorized entry return rate. The specific return time frame for this code is set in the Nacha Operating Rules and is not stated on the public Nacha pages used here.
Can the entry be reinitiated?
Nacha's risk-and-enforcement page never addresses R51 and reinitiation in the same sentence, but three things on it bear on the question. It sets the default: reinitiation is "the method permitted in the Rules by which a Returned Entry may be resubmitted", and Subsection 2.12.4 "implicitly prohibits the reinitiation of Entries outside of the express limited circumstances under which they are permitted under the Rules". It lists R51 by name among the return reason codes for unauthorized debit Entries. And it says that an entry returned as unauthorized cannot be re-initiated, because "an unauthorized debit cannot be remedied" and reinitiating one "would be considered an improper reinitiation practice". The one exemption the page gives — a debit is not a reinitiation if the Originator obtains a new authorization after the return — is written around authorization-based debits, and an RCK entry re-presents a cheque rather than debiting under an authorization, so it does not reach this case. None of the permitted circumstances named on that page covers an RCK item ruled ineligible or improper.
Treat further ACH presentment as closed until your ODFI confirms otherwise against the current Operating Rules, which are what govern.
Nacha counts this code toward an Originator's unauthorized entry return rate, whose threshold Nacha set at 0.5 percent. Each return under this code moves that ratio for your ODFI, independently of the money involved.
What an operator does next
The RCK re-presentment was ineligible or improper, so start with your RCK eligibility screening — that is what produced the return. On presenting the item again: nothing in the Nacha pages reviewed here gives you a permitted route, and the same page counts R51 as an unauthorized entry return and says an entry returned as unauthorized cannot be re-initiated. PaymentBrief's own position, not a Nacha ruling, is to treat further ACH presentment as closed until your ODFI confirms otherwise against the current Operating Rules.
PaymentBrief guidance, not Nacha text. Your ODFI's procedures and the current Nacha Operating Rules govern.
Where this comes up on PaymentBrief
Sources for this code
- Nacha — ISO 20022 Guide to Mapping U.S. ACH Return Items and Notifications of Change, August 2023, Version 2.01 (Table 1, return reason codes) — nacha-mapping-guide, retrieved 2026-09-06
- Nacha — rule page 'ACH Network Risk and Enforcement Topics' (unauthorized return rate threshold; reinitiation of entries) — nacha-rule-page, retrieved 2026-09-06