File Record Edit Criteria / Entry with Invalid Account Number Initiated Under Questionable Circumstances / Return of Improperly Initiated Reversal

Nacha's definition

(1) Field(s) cannot be processed by RDFI; (2) the Entry contains an invalid DFI Account Number (account closed / no account / unable to located account / invalid account number) and is believed by the RDFI to have been initiated under questionable circumstances; or (3) either the RDFI or the Receiver has identified a reversing Entry as one that was improperly initiated by the Originator or ODFI. If the Entry cannot be processed by the RDFI, the field(s) causing the error must be identified In the Addenda Information field of the Return. If the RDFI uses R17 to return an entry that contains an invalid DFI Account Number and believes that it was initiated under questionable circumstances, the RDFI must insert “QUESTIONABLE” within the first 12 positions of the Addenda Information field.

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: ALL.

How it appears in an ISO 20022 statement

Nacha's mapping guide maps R17 to camt.053 reason code NARR (Narrative) — ISO definition: Reason is provided as narrative information in the additional reason information. Nacha marks this ISO code as mapped to more than one Nacha return code, so the ISO code alone does not identify the Nacha reason; read the narrative or the original return record.

Return time frame

Nacha's R17 rule page states that RDFIs returning entries as R17 "QUESTIONABLE" must transmit the return under the standard 2-day return timeframe, and its reversals rule page gives R17 a 2-day return time frame when used for an improper Reversal on a non-consumer account or one the RDFI identifies itself. Its original use for field errors runs to the standard time frame in the Rules.

Source: Nacha — rule page 'Return for Questionable Transaction' (R17; effective 21 June 2019)

Can the entry be reinitiated?

Nacha's reinitiation rule governs resubmission of returned debit entries; it does not arise for this code. See the definition and the operator note for what the return means and who acts on it.

Source: Nacha — rule page 'ACH Network Risk and Enforcement Topics' (unauthorized return rate threshold; reinitiation of entries)

What an operator does next

Three different things share this code: a field error the RDFI cannot process, an entry with an invalid account number the RDFI believes was initiated under questionable circumstances (the RDFI must then write QUESTIONABLE in the addenda), or an improperly initiated reversal. Read the addenda before deciding what happened — a QUESTIONABLE R17 is a fraud signal, not a data error.

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 'Return for Questionable Transaction' (R17; effective 21 June 2019) — nacha-rule-page, 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
• Nacha — rule page 'ACH Network Rules: Reversals and Enforcement' (effective 30 June 2021) — nacha-rule-page, retrieved 2026-09-06
• US Treasury, Bureau of the Fiscal Service — Green Book, Chapter 4: Returns (return reason codes for federal ACH credits; dishonored return codes) — government-guide, retrieved 2026-09-06
• Federal Reserve Financial Services — FedGlobal ACH Payments Origination Manual, 3 August 2026 (return item code tables) — ach-operator-manual, retrieved 2026-09-06