Skip to content
ACH return R03

No Account / Unable to Locate Account

Category: Account & routing Initiated by: RDFI

Read reinitiation conditions and source →

Applies to (SEC scope)

ALL, EXCEPT ARC, BOC, POP

camt.053 mapping

BE01 — Inconsistent with End Customer

Nacha's definition

Account number structure is valid and it passes the check digit validation, but the account number does not correspond to the individual identified in the Entry, or the account number designated is not an existing account i.e., not an open account.

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 ARC, BOC, POP.

Reinitiation conditions

Nacha's reinitiation rule page says the rule "will allow reinitiations to correct administrative errors", with fields other than Company Name, Company ID and Amount modified only to the extent necessary to correct an error — so Nacha's page treats a resubmission with corrected account details as a reinitiation — within the Rules' limits and carrying the RETRY PYMT description — unless the Originator obtains a new authorization after the return, in which case Nacha does not treat the debit as a reinitiation.

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

PaymentBrief guidance, not Nacha text

get the corrected details from the Receiver, and decide deliberately whether you are reinitiating or originating a freshly authorized entry.

How it appears in an ISO 20022 statement

Nacha's mapping guide maps R03 to camt.053 reason code BE01 (Inconsistent with End Customer) — ISO definition: Identification of end customer is not consistent with associated account number

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 current Nacha Operating Rules and your ODFI determine the applicable deadline for this code; a general public two-day reference is not a substitute for that code-specific requirement.

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

What an operator does next

The account number has a valid structure, but the account is not located or does not correspond to the identified Receiver. Verify both account and Receiver details through a trusted channel before any new entry. The code alone does not prove a typo; apply the applicable validation and reinitiation requirements with the ODFI.

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

Closed, unlocated or malformed?

These codes identify different account problems. A valid format is not proof that an account exists or belongs to the Receiver.

PaymentBrief comparison of the definitions above. Repair is not automatic retry permission: check the reinitiation conditions and your ODFI’s procedures before a new entry.

Where this comes up on PaymentBrief

Public-source reference. Quoted definitions and rule statements are attributed to the public documents linked on this page; PaymentBrief's operator guidance is labelled separately. This reference does not reproduce the complete Nacha Operating Rules. The current rules and your ODFI's procedures govern. A gap in a cited public document does not establish that the rules permit an action or that no other rule applies.

Sources for this code

Related codes

← Back to the ACH return-code lookup