R18 - Improper Effective Entry Date
The Effective Entry Date on the entry is not usable: a credit dated too far in the future, or a debit dated before the file was processed. The ACH Operator/RDFI cannot settle on the date given.
R18 - Improper Effective Entry Date
The Effective Entry Date on the entry is not usable: a credit dated too far in the future, or a debit dated before the file was processed. The ACH Operator/RDFI cannot settle on the date given. This rejection is recoverable: correct the cause and the same payment can be resubmitted.
What this code means
The Effective Entry Date on the entry is not usable: a credit dated too far in the future, or a debit dated before the file was processed. The ACH Operator/RDFI cannot settle on the date given.
Typical causes
- Effective entry date set in the past (stale file)
- Credit dated beyond the maximum permitted lead time
- Timezone / cut-off miscalculation in the originating system
What to do
Fix the Effective Entry Date and re-send. Not a reinitiation.
What it looks like in an ACH return
The return arrives as an Addenda Record (type 99), 94 characters wide. The return reason code sits in positions 4-6.
799R18091000010000001 09100001 091000019000001Tools for this code
Decode a real status report, or check a payment file before you send it — all in your browser, nothing uploaded.
Related codes
Source: Nacha ISO 20022 mapping guide + Federal Reserve ACH Return Reason Report + US Treasury Green Book · Last verified: 2026-07-13
Checked against: nacha.org · frbservices.org