Skip to content

ACH return codes

An ACH return code is the reason a bank sent a debit back. Nacha defines R01 through R85. Most returns must arrive within 2 banking days of settlement, but an account holder can report a consumer debit as unauthorized for 60 days. Only R01 and R09 can be retried as is, at most twice. On Flint, every return reaches you as one normalized code, or as a bank return you never have to contest.
Verified against official documentationReviewed Send a correction (opens in a new tab)

Look up a return code

An R code such as R01, R03, or R16, with or without the R, or words from the reason such as closed or unauthorized.

Try

All 70 return codes are listed below.

Every ACH return code

The deadline is when the return must reach the originator's bank. “2 banking days” means by the opening of business on the second banking day after the debit settled; “60 calendar days” means the banking day after the sixtieth day. Numbers Nacha hasn't assigned, such as R48 and R54 to R60, are left out.

Returns from the account holder's bank

The codes behind almost every returned debit. The receiving bank (RDFI) sends them.

CodeMeaningDeadlineRetryOn Flint
R01Insufficient funds. The available balance doesn't cover the debit. The most common return.2 banking daysRetry up to twice
Up to two more times, within 180 days of the original settlement date.
insufficient_funds
After it succeeds: a bank_return Dispute, reason insufficient_funds
R02Account closed. A previously open account was closed by the account holder or the bank.2 banking daysFix, then retry
Only with new account details from the account holder.
bank_account_closed
R03No account or unable to locate account. The account number is well formed, but it doesn't match an open account or the name on the entry.2 banking daysFix, then retry
Only with new account details from the account holder.
payment_failed
R04Invalid account number structure. The account number fails the bank's format or check digit validation.2 banking daysFix, then retry
Only with new account details from the account holder.
payment_failed
R05Unauthorized debit to consumer account using corporate SEC code. A business-to-business entry (CCD or CTX) debited a consumer account the consumer didn't authorize.60 calendar days, with a signed statementNew authorization
Never without a new authorization from the account holder.
bank_debit_not_authorized
After it succeeds: a bank_return Dispute, reason debit_not_authorized
R06Returned per ODFI's request. The originator's bank asked for an erroneous or unauthorized entry back, and the receiving bank agreed.Agreed between the two banksFix, then retry
Only once whatever prompted the request is fixed.
payment_failed
R07Authorization revoked by customer. The consumer revoked the authorization they gave the originator.60 calendar days, with a signed statementNew authorization
Never without a new authorization from the account holder.
bank_debit_not_authorized
After it succeeds: a bank_return Dispute, reason debit_not_authorized
R08Payment stopped. The account holder placed a stop payment on this debit. It doesn't cancel a recurring authorization.2 banking daysNew authorization
Only after the account holder authorizes it again, following the return.
bank_debit_not_authorized
R09Uncollected funds. The ledger balance covers the debit, but the available balance doesn't, often because of a deposit still on hold.2 banking daysRetry up to twice
Up to two more times, within 180 days of the original settlement date.
insufficient_funds
After it succeeds: a bank_return Dispute, reason insufficient_funds
R10Customer advises originator unknown or not authorized. The account holder says they don't know the originator, have no relationship with it, or never authorized it to debit the account.60 calendar days for consumer accounts, with a signed statementNew authorization
Never without a new authorization from the account holder.
bank_debit_not_authorized
After it succeeds: a bank_return Dispute, reason debit_not_authorized
R11Customer advises entry not in accordance with the terms of the authorization. An authorization exists, but the debit broke its terms: the wrong amount, the wrong date, or another error.60 calendar days for consumer accounts, with a signed statementFix, then retry
Send a corrected debit within 60 days of the return's settlement date. That isn't a reinitiation.
bank_debit_not_authorized
After it succeeds: a bank_return Dispute, reason debit_not_authorized
R12Account sold to another DFI. The account moved to another financial institution.2 banking daysFix, then retry
Only with new account details from the account holder.
payment_failed
R14Representative payee deceased or unable to continue. The person receiving payments on the beneficiary's behalf died or can't continue in that role.2 banking daysDon't retry
Don't. Stop entries to this account.
payment_failed
R15Beneficiary or account holder deceased. The account holder or beneficiary died.2 banking daysDon't retry
Don't. Stop entries to this account.
payment_failed
R16Account frozen or entry returned per OFAC instruction. The bank or a legal action restricted the account, or OFAC told the bank to return the entry.2 banking daysFix, then retry
Only after the account holder confirms the account accepts debits again, or with a different account.
payment_failed
R17File record edit criteria. The bank can't process a field in the entry. Banks also use R17, marked QUESTIONABLE, for an entry with invalid account details they believe was sent under questionable circumstances.2 banking daysFix, then retry
Only after correcting the field the bank names in the return.
payment_failed
R20Non-transaction account. The account can't take this debit, such as a savings account that limits transfers.2 banking daysFix, then retry
Only to a different account.
bank_account_restricted
R21Invalid company identification. The company identification number on the entry isn't valid. Mostly used on CIE entries.2 banking daysFix, then retry
Only after correcting the identification number.
payment_failed
R22Invalid individual ID number. The account holder told their bank the ID number identifying them on the entry is wrong. Used on CIE and MTE entries.2 banking daysFix, then retry
Only after correcting the ID number.
payment_failed
R23Credit entry refused by receiver. The account holder refused a credit, such as a payment for the wrong amount or one they didn't authorize.2 banking days after the bank learns of the refusalDon't retry
Don't resend the credit. Settle the amount with the recipient first.
Doesn't apply to Flint debits
R24Duplicate entry. The entry matches another one in trace number, date, amount, and other data.2 banking daysDon't retry
Don't. Check whether the original posted, and whether a reversal already went out.
payment_failed
R29Corporate customer advises not authorized. A business account holder says it didn't authorize the debit.2 banking daysNew authorization
Never without a new authorization from the business.
bank_debit_not_authorized
After it succeeds: a bank_return Dispute, reason debit_not_authorized
R31Permissible return entry (CCD and CTX only). A business debit returned after the 2 banking day deadline, with the originator's bank's permission.Agreed between the two banksNew authorization
Only with a new authorization from the business.
bank_debit_not_authorized
R33Return of XCK entry. A destroyed check collected over ACH, returned at the bank's discretion.60 calendar daysNot a retry case
Check conversion only.
Doesn't apply to Flint debits
R37Source document presented for payment. The paper check behind an ARC, BOC, or POP entry was also presented, so the account would pay twice.60 calendar days, with a signed statementNot a retry case
Check conversion only.
Doesn't apply to Flint debits
R38Stop payment on source document. The check behind an ARC or BOC entry had a stop payment the bank missed when it cleared as ACH.60 calendar daysNot a retry case
Check conversion only.
Doesn't apply to Flint debits
R39Improper source document. The check used for an ARC, BOC, or POP entry was improper, or both the check and the entry posted.2 banking daysNot a retry case
Check conversion only.
Doesn't apply to Flint debits

ACH Operator rejects

The Federal Reserve or The Clearing House rejected the entry for its format, so it never reached the bank or settled.

CodeMeaningDeadlineRetryOn Flint
R13Invalid ACH routing number. The routing number isn't a valid ACH routing number.Rejected at processingFix, then retry
Only with a corrected routing number.
payment_failed
R18Improper effective entry date. The effective date is too far after the processing date.Rejected at processingFix, then retry
Send it again with a valid date.
payment_failed
R19Amount field error. The amount is non-numeric, zero where it can't be, or not zero where it must be.Rejected at processingFix, then retry
Send it again with a valid amount.
payment_failed
R25Addenda error. The addenda record indicator, type, sequence, or count is wrong.Rejected at processingFix, then retry
Send it again with valid addenda.
payment_failed
R26Mandatory field error. A mandatory field is missing or invalid.Rejected at processingFix, then retry
Send it again with the field corrected.
payment_failed
R27Trace number error. The original trace number is missing from a return's addenda, or an addenda trace number doesn't match its entry.Rejected at processingFix, then retry
Send it again with the right trace number.
payment_failed
R28Routing number check digit error. The routing number's check digit is invalid.Rejected at processingFix, then retry
Only with a corrected routing number.
payment_failed
R30RDFI not participant in check truncation program. The receiving bank doesn't take part in check truncation.Rejected at processingNot a retry case
Check truncation only.
Doesn't apply to Flint debits
R32RDFI non-settlement. The receiving bank can't settle the entry.Rejected at processingFix, then retry
Only once the bank can settle, or to a different account.
payment_failed
R34Limited participation DFI. A federal or state supervisor has limited the receiving bank's participation in ACH.Rejected at processingFix, then retry
Only to an account at a different bank.
payment_failed
R35Return of improper debit entry. Debits aren't allowed for this entry type or account, such as a CIE entry or a loan account.Rejected at processingFix, then retry
Only to an account that accepts debits.
payment_failed
R36Return of improper credit entry. Credits aren't allowed for this entry type, such as ARC, BOC, POP, RCK, TEL, or XCK.Rejected at processingNot a retry case
Credits only.
Doesn't apply to Flint debits

Returned check entries (RCK)

For a bounced paper check collected again over ACH. They never apply to an online debit.

CodeMeaningDeadlineRetryOn Flint
R50State law affecting RCK acceptance. The bank's state, or its customer agreement, doesn't allow electronic presentment of the check.2 banking daysNot a retry case
Returned checks only.
Doesn't apply to Flint debits
R51Item related to RCK entry is ineligible or RCK entry is improper. The check was ineligible, the notice was missing, the signature wasn't genuine, the item was altered, or the amount was wrong.60 calendar days, with a signed statementNot a retry case
Returned checks only.
Doesn't apply to Flint debits
R52Stop payment on item related to RCK entry. The check behind the RCK entry has a stop payment.60 calendar daysNot a retry case
Returned checks only.
Doesn't apply to Flint debits
R53Item and RCK entry presented for payment. Both the check and the RCK entry for it were presented.60 calendar days, with a signed statementNot a retry case
Returned checks only.
Doesn't apply to Flint debits

Federal agency enrollment returns (ENR)

A federal agency refusing a direct deposit enrollment. They never apply to a payment.

CodeMeaningDeadlineRetryOn Flint
R40Return of ENR entry by federal government agency. The agency doesn't take part in automated enrollment.Set by the agencyNot a retry case
Correct the enrollment, or enroll another way.
Doesn't apply to Flint debits
R41Invalid transaction code. The enrollment's transaction code is invalid or inappropriate.Set by the agencyNot a retry case
Correct the enrollment, or enroll another way.
Doesn't apply to Flint debits
R42Routing number or check digit error. The enrollment's routing number or check digit is invalid.Set by the agencyNot a retry case
Correct the enrollment, or enroll another way.
Doesn't apply to Flint debits
R43Invalid DFI account number. The enrollment's account number is missing, too long, or has invalid characters.Set by the agencyNot a retry case
Correct the enrollment, or enroll another way.
Doesn't apply to Flint debits
R44Invalid individual ID number. The ID number doesn't match the agency's records.Set by the agencyNot a retry case
Correct the enrollment, or enroll another way.
Doesn't apply to Flint debits
R45Invalid individual or company name. The name doesn't match the agency's records.Set by the agencyNot a retry case
Correct the enrollment, or enroll another way.
Doesn't apply to Flint debits
R46Invalid representative payee indicator. The representative payee indicator is missing or doesn't match the agency's records.Set by the agencyNot a retry case
Correct the enrollment, or enroll another way.
Doesn't apply to Flint debits
R47Duplicate enrollment. The agency received the same enrollment more than once.Set by the agencyNot a retry case
Correct the enrollment, or enroll another way.
Doesn't apply to Flint debits

Dishonored returns

The originator's bank refusing a return as late, misrouted, or wrong. Sent within 5 banking days after the return settles.

CodeMeaningDeadlineRetryOn Flint
R61Misrouted return. The bank sending the return put the wrong routing number on it.5 banking days after the return settlesNot a retry case
Between the banks.
Handled between the banks
R62Return of erroneous or reversing debit. A reversal went wrong: the erroneous entry and its reversal were sent, and only one came back.5 banking days after the return settlesNot a retry case
Between the banks.
Handled between the banks
R67Duplicate return. The originator's bank received more than one return for the same entry.5 banking days after the return settlesNot a retry case
Between the banks.
Handled between the banks
R68Untimely return. The return came after the deadline the rules allow.5 banking days after the return settlesNot a retry case
Between the banks.
Handled between the banks
R69Field errors. One or more fields in the return are wrong, named by code in the addenda.5 banking days after the return settlesNot a retry case
Between the banks.
Handled between the banks
R70Permissible return entry not accepted or return not requested by ODFI. An R06 or R31 return the originator's bank never agreed to or requested.5 banking days after the return settlesNot a retry case
Between the banks.
Handled between the banks

Contested dishonored returns

The receiving bank disputing a dishonored return. Sent within 2 banking days after the dishonored return settles.

CodeMeaningDeadlineRetryOn Flint
R71Misrouted dishonored return. The dishonored return carried the wrong routing number.2 banking days after the dishonored return settlesNot a retry case
Between the banks.
Handled between the banks
R72Untimely dishonored return. The dishonored return came after its deadline.2 banking days after the dishonored return settlesNot a retry case
Between the banks.
Handled between the banks
R73Timely original return. The receiving bank certifies its original return was on time.2 banking days after the dishonored return settlesNot a retry case
Between the banks.
Handled between the banks
R74Corrected return. The receiving bank corrects a return dishonored for field errors.2 banking days after the dishonored return settlesNot a retry case
Between the banks.
Handled between the banks
R75Return is not a duplicate. The original return wasn't a duplicate, contesting an R67.2 banking days after the dishonored return settlesNot a retry case
Between the banks.
Handled between the banks
R76No errors found. The original return had no errors, contesting an R69.2 banking days after the dishonored return settlesNot a retry case
Between the banks.
Handled between the banks
R77Non-acceptance of R62 dishonored return. The receiving bank can't recover the funds for an R62, or returned both entries.2 banking days after the dishonored return settlesNot a retry case
Between the banks.
Handled between the banks

International (IAT) gateway returns

A gateway returning an outbound international entry. Flint's bank debits are domestic.

CodeMeaningDeadlineRetryOn Flint
R80IAT entry coding error. A country, bank, currency, or transaction type code on the IAT entry is invalid.2 banking daysFix, then retry
Only after correcting the entry, recoded as IAT for R85.
Doesn't apply to Flint debits
R81Non-participant in IAT program. The gateway has no agreement to send IAT entries for this originator's bank.2 banking daysFix, then retry
Only after correcting the entry, recoded as IAT for R85.
Doesn't apply to Flint debits
R82Invalid foreign receiving DFI identification. The foreign bank's identifier is invalid.2 banking daysFix, then retry
Only after correcting the entry, recoded as IAT for R85.
Doesn't apply to Flint debits
R83Foreign receiving DFI unable to settle. Settlement failed in the foreign payment system.2 banking daysFix, then retry
Only after correcting the entry, recoded as IAT for R85.
Doesn't apply to Flint debits
R84Entry not processed by gateway operator. The gateway declined it as too risky, or the foreign system can't process it.2 banking daysFix, then retry
Only after correcting the entry, recoded as IAT for R85.
Doesn't apply to Flint debits
R85Incorrectly coded outbound international payment. An international payment was sent with a domestic SEC code instead of IAT, so it lacks the data OFAC screening needs.2 banking daysFix, then retry
Only after correcting the entry, recoded as IAT for R85.
Doesn't apply to Flint debits

Return deadlines

  • 2 banking days covers nearly every return: insufficient funds, closed or missing accounts, stop payments, frozen accounts, and business accounts disputing a debit (R29).
  • 60 calendar days covers unauthorized consumer returns, R05, R07, R10, and R11, for which the account holder first signs a Written Statement of Unauthorized Debit at their bank. Check conversion codes R33, R37, R38, and R51 to R53 share the window.
  • Late returns outside these windows happen only by agreement: R06 when the originator's bank asks for an entry back, and R31 when it agrees to take a late business return.

The 60-day window is why an ACH payment can come back weeks after it settled and after you shipped. Settlement means the debit cleared, not that the money is yours for good.

When you can retry a returned debit

Nacha calls a retry a reinitiation, and allows it in three cases only, within 180 days of the original settlement date:

  • R01 and R09: at most two more attempts after the original return, three presentments in all. Space them toward the account holder's payday.
  • R08: only after the account holder authorizes the debit again, following the return. Authorization collected in advance doesn't count.
  • Any other return: only after you fix what caused it, such as new account details after R02, R03, or R04.

A reinitiated debit keeps the original company name, company ID, and amount, and carries RETRY PYMT in the company entry description. Changing the amount to get around the rule counts as an improper reinitiation. A debit returned as unauthorized can't be retried at all; only a new authorization from the account holder, obtained after the return, starts a new debit. R11 is the exception: the authorization stands, so a corrected debit sent within 60 days of the return is allowed.

Return rate limits

Nacha measures each originator's debit returns over the last 60 days or two calendar months. Crossing a limit can start a Nacha inquiry into the originator and its bank.

RateLimitCodes counted
Unauthorized returns0.5 percentR05, R07, R10, R11, R29, R51
Administrative returns3.0 percentR02, R03, R04
All returns15.0 percentEvery returned debit, except RCK entries

ACH returns on Flint

Flint is a payments API with orders, tax, and subscriptions built in, and ACH debit is a payment option on the same orders, PaymentIntents, and invoices you use for cards. You never parse an R code:

  • One code per return. A debit the bank rejects before the payment succeeds sets last_payment_error.code to insufficient_funds, bank_account_closed, bank_account_not_found, bank_debit_not_authorized, bank_account_restricted, or bank_debit_limit_exceeded, the same field a card decline uses. Anything else arrives as payment_failed, never as a raw processor string.
  • Nothing ships early. The payment stays processing until the bank settles or rejects the debit, and the order isn't paid until then. Flint Checkout tells the buyer the payment is processing instead of sending them to your success page.
  • Late returns are labeled. A return after the payment succeeded arrives as a Dispute with case_type bank_return, already lost and marked not contestable, so it never sits in an evidence queue beside your card chargebacks. A paid invoice reopens and sends invoice.reopened.
  • No double refunds. Flint handles a refund and a bank return one at a time, so the same money can't go back twice. After a full return, a refund fails with reason payment_disputed.
  • No accidental reinitiations. Every Flint bank debit is one-time, with the buyer present, and Flint doesn't save bank accounts. It never re-debits a returned account on its own, so it can't break the reinitiation rule for you.

A PaymentIntent whose debit came back R02, trimmed to the fields that matter:

JSON
{
  "data": {
    "payment_intent_id": "pi_1kmn0aExample",
    "status": "requires_payment_method",
    "payment_options": ["card", "ach_debit"],
    "last_payment_error": {
      "code": "bank_account_closed",
      "message": "The bank account is closed. Ask the customer to use a different payment method.",
      "failed_at": "2026-11-12T15:02:44Z",
      "remediation": {
        "retry": "none",
        "next_steps": "Ask the customer to use a different payment method."
      }
    }
  }
}

The same failure arrives on the payment_intent.payment_failed webhook. A return after success arrives on dispute.created:

JSON
{
  "data": {
    "dispute_id": "du_1kmn0aExample",
    "case_type": "bank_return",
    "payment_option": "ach_debit",
    "reason": "debit_not_authorized",
    "status": "lost",
    "amount_money": {"amount": 183600, "currency": "USD"},
    "can_respond_with_evidence": false,
    "is_action_required": false,
    "evidence_due_at": null,
    "response_unavailable_reason": "bank_return_not_contestable"
  }
}

Your handling is one switch, whichever R code sits behind the code:

TypeScript
// Every R code reaches you as one of these. Unknown codes fall to default,
// because Flint can add values.
function nextStep(code: string): "new_account" | "authorize" | "try_later" | "other_method" {
  switch (code) {
    case "bank_account_closed":     // R02
    case "bank_account_not_found":
    case "bank_account_restricted": // R20
      return "new_account";
    case "bank_debit_not_authorized": // R05, R07, R08, R10, R11, R29, R31
      return "authorize";
    case "insufficient_funds": // R01, R09
      return "try_later";
    default: // payment_failed and anything new
      return "other_method";
  }
}

Test each return

In a sandbox, pay with routing number 110000000 and one of these account numbers:

Account numberReturn it stands in forWhat Flint reports
000222222227Insufficient funds (R01)insufficient_funds
000111111113Account closed (R02)bank_account_closed
000111111116No account foundbank_account_not_found
000333333335Not authorized, such as R10bank_debit_not_authorized
000555555559A return after settlementSucceeds, then a bank_return Dispute

Questions, answered

What is an ACH return code?

A return code is the reason a bank sent an ACH entry back. Nacha, which writes the ACH rules, defines codes R01 through R85. The account holder's bank uses most of them; the rest belong to the ACH Operator, federal agencies, and international gateways.

What does return code R03 mean?

R03 means no account, or unable to locate account: the account number is well formed but doesn't match an open account or the name on the entry. It must arrive within 2 banking days. Ask the account holder for correct details before debiting again. On Flint it arrives as payment_failed.

How long does a bank have to return an ACH debit?

Most returns must reach the originator's bank by the opening of business on the second banking day after settlement. Unauthorized returns on consumer accounts, R05, R07, R10, and R11, can come up to 60 calendar days after settlement, backed by the account holder's signed statement.

Can I retry a returned ACH debit?

Only for R01 and R09, and at most two more times within 180 days of the original settlement. After R08 you need the account holder's new authorization. After an unauthorized return (R05, R07, R10, R29) you need a new authorization. Any other return can be resent only after you fix its cause.

Which ACH return codes count against Nacha's return rate limits?

Unauthorized returns, R05, R07, R10, R11, R29, and R51, count toward the 0.5 percent unauthorized return rate. R02, R03, and R04 count toward the 3.0 percent administrative return level. Every returned debit counts toward the 15.0 percent overall level.

Sources

Every code, deadline, and retry rule comes from these pages, checked on November 17, 2026.