ACH return R75

Return Not a Duplicate

Category: Contested dishonored return (RDFI) Initiated by: RDFI

Applies to (SEC scope)

ALL, EXCEPT IAT

camt.053 mapping

Not mapped

Reinitiation

Not applicable to this code

Nacha's definition

The Return Entry was not a duplicate of an Entry previously returned by the RDFI.

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, EXCEPT IAT.

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

Dishonored and contested dishonored returns are exchanged between the ODFI and RDFI under their own time frames in the Nacha Operating Rules. Nacha's mapping guide notes they must be sent in Nacha file format rather than through camt.053. The time frames are not stated in the public sources used here.

Source: 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)

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

The RDFI contests an R67 dishonor: its return was not a duplicate. Operators encounter these only through their ODFI's exception handling; the practical question is which entry finally stands.

PaymentBrief guidance, not Nacha text. Your ODFI's procedures and the current Nacha Operating Rules govern.

Where this comes up on PaymentBrief

Direct debit explained: ACH, SEPA, Bacs and eGIRO

Where ACH debit returns sit in the mandate and collection lifecycle, and how the return-rate thresholds bear on your ODFI relationship.

Confidence: high. Status: verified. The Nacha Operating Rules govern. Nacha sells them and they were not used here; every statement above is taken from a public Nacha document or a public US Treasury or Federal Reserve document, named per statement. Where those documents are silent, this card says so of those documents — it is not a claim about everything Nacha has published.

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

Related codes

R71

Misrouted Dishonored Return

R72

Untimely Dishonored Return

R73

Timely Original Return

R74

Corrected Return

← Back to the full ACH return-code lookup