Insufficient funds
The available balance was not sufficient to cover the entry.
Mostly a debit-side code. For an outbound payout program, check the entry type before reacting; funds availability is the issue, not the account.
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
The available balance was not sufficient to cover the entry.
Mostly a debit-side code. For an outbound payout program, check the entry type before reacting; funds availability is the issue, not the account.
A previously open account has been closed.
Do not retry the same destination. Ask the recipient for a new account, then pay again.
The account number structure is valid, but it does not match any account at the receiving bank.
Verify the account and routing details with the recipient; retry only after they are corrected.
The account number fails the format check.
The destination was mis-entered. Correct it before another attempt.
A debit to a consumer account used a corporate SEC code without authorization.
Authorization and entry-class problem on debit programs; review how the entry was coded.
The originating bank asked the receiving bank to return the entry.
Usually follows your own recall request; reconcile the return against the original.
The receiver had authorized the entry, then revoked that authorization.
Stop originating against this authorization; obtain a new one before any further entries.
The receiver placed a stop payment on the entry.
Contact the receiver before retrying; a stopped payment retried without resolution invites more returns.
The balance was sufficient, but part of it was not yet collected.
Debit-side timing issue; retrying after funds clear may succeed.
The consumer receiver advises the entry was not authorized or the originator is unknown.
Treat as a dispute: stop origination and resolve authorization directly with the receiver.
An authorization exists, but the entry differs from its terms (amount, date, or account).
Correct the entry to match the authorization; a corrected entry may be re-originated within the allowed window.
The account was sold to another financial institution.
Obtain the recipient’s new bank details; the old destination will not work.
The routing number is not a valid ACH participant.
The routing number was mis-entered or the institution cannot receive ACH; verify with the recipient.
The person authorized to act for the account holder has died.
Pause payouts to this destination and re-establish who should receive the money.
The beneficiary or account holder has died.
Stop origination; route the obligation through whoever lawfully stands in for the recipient.
Funds are unavailable because the account is frozen, including by legal action or OFAC instruction.
Do not retry. Escalate to compliance before doing anything else with this recipient.
The entry failed the receiving bank’s edit criteria; some banks also use R17 to flag entries they believe are questionable.
Review the entry details; if flagged as questionable, involve compliance rather than retrying.
The account exists but does not accept transactions of this type.
Ask the recipient for a transaction account (checking rather than certain savings products).
The company identification on the entry is not valid for the receiver.
Origination-setup issue; check the company ID your program sends.
The individual ID on the entry does not match what the receiver expects.
Verify the identification field against what the recipient’s bank expects.
The recipient refused the credit, for example because the amount was unexpected.
Talk to the recipient: confirm the amount and reason, then re-originate once they expect it.
The receiving bank identified the entry as a duplicate of one already processed.
Do not blindly retry. Confirm whether the obligation is already paid; fix the duplicate-protection gap that let two entries out.
The corporate receiver says the entry was not authorized.
The business-account version of R10: stop origination and resolve authorization with the receiver.
The receiving bank returned a corporate entry the ODFI agreed to take back outside the normal window.
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.