R01
Insufficient funds
ReturnThe 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.
ACH Return Code Lookup
Type a code, like R01, R17, R20, R23 or C02, or a word from the problem. Each entry says what the code means in plain English, what actually happened, what operations should do next, and whether it is a return or a Notification of Change.
32 codes
R02
Account closed
ReturnA 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
ReturnThe 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
ReturnThe account number fails the format check.
Action
The destination was mis-entered. Correct it before another attempt.
R05
Unauthorized debit (corporate SEC code)
ReturnA 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
ReturnThe 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
ReturnThe 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
ReturnThe 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
ReturnThe 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
ReturnThe 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
ReturnAn 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
ReturnThe 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
ReturnThe 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
ReturnThe 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
ReturnThe beneficiary or account holder has died.
Action
Stop origination; route the obligation through whoever lawfully stands in for the recipient.
R16
Account frozen
ReturnFunds 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
ReturnThe 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
ReturnThe 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
ReturnThe 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
ReturnThe 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
ReturnThe 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
ReturnThe 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
ReturnThe 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
ReturnThe 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.
R33
Return of XCK entry
ReturnA destroyed-check (XCK) entry was returned by the receiving bank.
Action
Rare in payout programs; handle the underlying item outside ACH.
C01
Incorrect account number
Notification of ChangeThe payment posted, but the account number should be corrected.
Action
Update the recipient record with the corrected account number before the next payout.
C02
Incorrect routing number
Notification of ChangeThe payment posted, but the routing number should be corrected, often after a bank merger.
Action
Update the routing number on file; future entries sent to the old number risk returns.
C03
Incorrect routing and account number
Notification of ChangeBoth the routing number and the account number should be corrected.
Action
Update both fields on the recipient record before the next payout.
C05
Incorrect transaction code
Notification of ChangeThe entry posted, but it was coded to the wrong account type, such as checking instead of savings.
Action
Correct the transaction code so the next entry posts to the right account type.
C06
Incorrect account number and transaction code
Notification of ChangeThe account number and the transaction code both need correction.
Action
Update the account number and the account type together before the next payout.
C07
Incorrect routing, account number and transaction code
Notification of ChangeAll three identifying fields need correction.
Action
Refresh the recipient’s full bank details; treat it like a re-entry of the destination.
C09
Incorrect individual ID number
Notification of ChangeThe individual identification number on the entry should be corrected.
Action
Correct the ID field your program sends for this recipient.
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 the complete ACH return code list.