Skip to content
ACH return R18

Improper Effective Entry Date

Category: Format & data Initiated by: RDFI

Applies to (SEC scope)

ALL

camt.053 mapping

DT01 — Invalid date

Reinitiation

Restricted — permitted only within the Rules’ limits

Nacha's definition

(1) The effective Entry date for a credit Entry is more than two Banking Days after the Banking Day of processing as established by the Originating ACH Operator; or (2) The Effective Entry Date for a debit Entry is more than one Banking Day after the processing date.

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 R18 to camt.053 reason code DT01 (Invalid date) — ISO definition: Invalid date (e.g., wrong or missing settlement date).

Return time frame

Nacha's public rule pages refer to the standard "two-day" return time frame for returns that are not extended (unauthorized) returns. The governing time limit for this code is set in the Nacha Operating Rules, which Nacha sells and which were not used here, so it is not restated.

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

Can the entry be reinitiated?

Nacha's reinitiation rule page allows reinitiation "to correct administrative errors", with fields other than Company Name, Company ID and Amount modified only to the extent necessary. A corrected resubmission of a returned debit is therefore treated as a reinitiation, within the Rules' limits and carrying RETRY PYMT. Nacha's reinitiation rule addresses returned debits; a returned credit falls outside it.

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

PaymentBrief guidance, not Nacha text

correct the field the RDFI identified, and code the resubmission correctly.

What an operator does next

The effective entry date is outside what the Rules allow relative to processing. Fix the date logic in your file generation.

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

Where this comes up on PaymentBrief

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

Related codes

← Back to the full ACH return-code lookup