Skip to content

ACH return reason code

R03 return code: No Account/Unable to Locate Account

The account number passes the format checks but matches no account, or not the Receiver named.

What R03 means

R03 is the return reason code No Account/Unable to Locate Account. The account number passes the format checks but matches no account, or not the Receiver named.

It is sent by the RDFI as a return entry: the original entry goes back to the ODFI with an addenda record carrying R03, and the ODFI passes the return on to the Originator.

Typical causes

  • A digit of the account number was mistyped or transposed.
  • The account number belongs to another bank than the routing number names.
  • The account number exists but doesn’t match the Receiver named in the entry.

Return timeframe

Available to the ODFI by opening of business on the 2nd banking day after the settlement date of the original entry.

Banking days are the Federal Reserve’s business days: weekends and Fed holidays don’t count, so a holiday in the window pushes the deadline out by a day.

Worked example

For an entry that settled on Wednesday, November 25, 2026, the day before Thanksgiving: must be available to the ODFI by opening of business on Monday, November 30, 2026.

Try your own settlement date in the ACH date calculator

What the Originator can do next

  • Confirm the routing and account numbers with the Receiver before sending again.
  • Validate a new account before its first debit; for WEB debits the Rules make account validation part of the required fraud screening.
  • It counts toward the Originator’s administrative return rate (R02, R03 and R04), which Nacha reviews above 3% of debits.

How R03 appears in a NACHA file

A return is the original entry detail record (type 6) sent back with a return transaction code — 21 or 26 for a checking account, 31 or 36 for savings (21 and 31 return a credit, 26 and 36 a debit) — the original amount, and an addenda record of type 99 that carries the reason. The batch keeps the original entry’s SEC code.

Return addenda record (type 99) with R03
PositionsFieldIn an R03 return
1Record Type Code7 (addenda)
2–3Addenda Type Code99 (return)
4–6Return Reason CodeR03
7–21Original Entry Trace NumberTrace number of the entry being returned
22–27Date of DeathYYMMDD for R14 and R15; blank otherwise
28–35Original Receiving DFI IdentificationFirst 8 digits of the original entry’s RDFI routing number
36–79Addenda InformationFree text from the RDFI
80–94Trace NumberThe return entry’s own trace number

To read a return file record by record, open the file in NACHA Navigator, a free sister site that parses NACHA files in your browser without uploading them.

Look up R03 from code or an AI agent

The code table on this page is the one behind the REST API and the MCP server, so a script or an AI agent gets the same answer as JSON. No key and no account.

REST · GET · no key
curl -s 'https://payopskit.com/api/v1/codes/R03?set=ach-return'
MCP · tools/call · lookup_payment_code
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "lookup_payment_code",
    "arguments": {
      "code": "R03",
      "set": "ach-return"
    }
  }
}
Response (JSON)
{
  "code": "R03",
  "set": "ach-return",
  "found": true,
  "matches": [
    {
      "set": "ach-return",
      "code": "R03",
      "name": "No Account/Unable to Locate Account",
      "description": "The account number passes the format checks but matches no account, or not the Receiver named.",
      "details": {
        "category": "return",
        "timeframe": "Available to the ODFI by opening of business on the 2nd banking day after the settlement date of the original entry",
        "timeframeKind": "banking-days",
        "timeframeDays": 2,
        "timeframeFrom": "original-settlement",
        "account": "any",
        "accountNote": null,
        "writtenStatement": false,
        "initiatedBy": "RDFI",
        "note": null,
        "effectiveFrom": null,
        "upcomingChange": null,
        "caveat": null
      }
    }
  ]
}

The MCP server is at /mcp (Streamable HTTP, no key); the API and MCP docs show how to connect Claude, Cursor or VS Code.

The deadline for a settlement date: GET /api/v1/ach/return-deadline?settlement_date=2026-11-25&code=R03 or the MCP tool ach_return_deadline.

Source: Nacha Operating Rules, Appendix Four (Return Entries). The code’s title is the Rules’ own; the rest is this site’s plain-language summary. It is informational and not a substitute for the Rules, your ACH Operator’s schedule or your ODFI agreement.