Skip to content
Learn

ACH Return Code Explorer

Type a code or a word from the problem. Each entry says what the code means, what actually happened, and what operations should do next.

24 codes

R01

Insufficient funds

The available balance was not sufficient to cover the entry.

Action

Mostly a debit-side code. For an outbound payout program, check the entry type before reacting; funds availability is the issue, not the account.

R02

Account closed

A previously open account has been closed.

Action

Do not retry the same destination. Ask the recipient for a new account, then pay again.

R03

No account / unable to locate

The account number structure is valid, but it does not match any account at the receiving bank.

Action

Verify the account and routing details with the recipient; retry only after they are corrected.

R04

Invalid account number structure

The account number fails the format check.

Action

The destination was mis-entered. Correct it before another attempt.

R05

Unauthorized debit (corporate SEC code)

A debit to a consumer account used a corporate SEC code without authorization.

Action

Authorization and entry-class problem on debit programs; review how the entry was coded.

R06

Returned per ODFI request

The originating bank asked the receiving bank to return the entry.

Action

Usually follows your own recall request; reconcile the return against the original.

R07

Authorization revoked

The receiver had authorized the entry, then revoked that authorization.

Action

Stop originating against this authorization; obtain a new one before any further entries.

R08

Payment stopped

The receiver placed a stop payment on the entry.

Action

Contact the receiver before retrying; a stopped payment retried without resolution invites more returns.

R09

Uncollected funds

The balance was sufficient, but part of it was not yet collected.

Action

Debit-side timing issue; retrying after funds clear may succeed.

R10

Not authorized / originator not known

The consumer receiver advises the entry was not authorized or the originator is unknown.

Action

Treat as a dispute: stop origination and resolve authorization directly with the receiver.

R11

Entry not in accordance with authorization

An authorization exists, but the entry differs from its terms (amount, date, or account).

Action

Correct the entry to match the authorization; a corrected entry may be re-originated within the allowed window.

R12

Account sold to another DFI

The account was sold to another financial institution.

Action

Obtain the recipient’s new bank details; the old destination will not work.

R13

Invalid ACH routing number

The routing number is not a valid ACH participant.

Action

The routing number was mis-entered or the institution cannot receive ACH; verify with the recipient.

R14

Representative payee deceased

The person authorized to act for the account holder has died.

Action

Pause payouts to this destination and re-establish who should receive the money.

R15

Account holder deceased

The beneficiary or account holder has died.

Action

Stop origination; route the obligation through whoever lawfully stands in for the recipient.

R16

Account frozen

Funds are unavailable because the account is frozen, including by legal action or OFAC instruction.

Action

Do not retry. Escalate to compliance before doing anything else with this recipient.

R17

File record edit criteria

The entry failed the receiving bank’s edit criteria; some banks also use R17 to flag entries they believe are questionable.

Action

Review the entry details; if flagged as questionable, involve compliance rather than retrying.

R20

Non-transaction account

The account exists but does not accept transactions of this type.

Action

Ask the recipient for a transaction account (checking rather than certain savings products).

R21

Invalid company identification

The company identification on the entry is not valid for the receiver.

Action

Origination-setup issue; check the company ID your program sends.

R22

Invalid individual ID number

The individual ID on the entry does not match what the receiver expects.

Action

Verify the identification field against what the recipient’s bank expects.

R23

Credit entry refused by receiver

The recipient refused the credit, for example because the amount was unexpected.

Action

Talk to the recipient: confirm the amount and reason, then re-originate once they expect it.

R24

Duplicate entry

The receiving bank identified the entry as a duplicate of one already processed.

Action

Do not blindly retry. Confirm whether the obligation is already paid; fix the duplicate-protection gap that let two entries out.

R29

Corporate customer advises not authorized

The corporate receiver says the entry was not authorized.

Action

The business-account version of R10: stop origination and resolve authorization with the receiver.

R31

Permissible return

The receiving bank returned a corporate entry the ODFI agreed to take back outside the normal window.

Action

Follows a negotiated return; reconcile it against the original entry and the agreement.

Definitions follow Nacha’s standardized return reason codes, described here in plain language for payout programs. Your bank or processor’s rules govern specifics like return windows and re-origination; confirm with them before acting on an edge case. For the story around returns, read what happens when a payout fails and ACH return codes, explained.