ACH return codes

When this is used

The RDFI returns a debit because the Receiver's account does not have enough funds at the time of posting. This is the single most common ACH return. The Originator may reinitiate the same entry up to two times within 180 days of the original Settlement Date, and must label the resubmission as "RETRY PMT" in the Company Entry Description field.

When this is used

The RDFI returns the entry because the destination account no longer exists. The Originator must obtain new account information from the Receiver before any further entries are sent. Reinitiating against the closed account is not permitted; doing so would generate further returns and contribute to the ODFI's return rate threshold.

When this is used

The routing number and check digit are well-formed, but the RDFI cannot match the account number to an account holder. This typically reflects a data-entry error by the Receiver during enrollment, or a name mismatch where the account number belongs to a different person. The Originator must verify the account number and Receiver name (often by requesting a voided check) and submit a new entry with corrected data.

When this is used

The account number is malformed — wrong length, illegal characters, or fails the institution's internal check digit. This is a pure format error and almost always points back to a typo at enrollment. The Originator should obtain the correct account number, validate it (a voided check is the most reliable source), and resubmit as a new entry.

When this is used

The Originator routed what should have been a consumer-authorized debit (PPD, WEB, TEL) through a corporate SEC code (CCD, CTX) — either to bypass consumer dispute rights or by mistake. The consumer has 60 calendar days from settlement to dispute. The Originator is liable for any return fees and the entry must not be reinitiated under a corporate SEC code.

When this is used

Used when the ODFI itself wants an entry pulled back — typically after the Originator notifies them of fraud, error, or duplicate origination, but the standard reversal window has passed or a reversal is not appropriate. The RDFI must respond to the request within 2 banking days of receipt. The ODFI indemnifies the RDFI for accepting the return.

When this is used

Most often appears with recurring billing — subscription services, gym memberships, utilities. The customer canceled the underlying authorization (often verbally to the Originator), but the Originator continued to debit. Once R07 hits, the Originator must immediately stop all future debits against that account; further attempts violate NACHA rules and may trigger enforcement.

When this is used

The Receiver instructed their bank to block one specific upcoming debit — for example, because they dispute a single charge but still expect the recurring schedule to continue. The Originator should contact the customer to resolve the underlying issue. R08 is item-specific (unlike R07, which kills the whole authorization), so reinitiation may be possible after the customer agrees and the stop expires.

When this is used

The Receiver's ledger balance shows enough money, but a portion is on hold pending check collection or other settlement. Treated similarly to R01 — the Originator may reinitiate up to two times within 180 days of original Settlement, with "RETRY PMT" in the Company Entry Description.

When this is used

The consumer signs a Written Statement of Unauthorized Debit (WSUD) declaring they never gave the Originator permission to debit. Common in identity theft, account takeover, or where a free trial silently rolled into paid billing without proper authorization records. The Originator must immediately stop all debits, investigate, and retain authorization evidence in case of further dispute.

When this is used

Repurposed in the 2021 rules to handle "authorized but defective" disputes — separating real authorization-error scenarios from outright unauthorized claims under R10. Because the underlying authorization is still valid, the Originator may correct the error (fix the amount, fix the date) and resubmit a new entry within 60 days of the R11 Settlement Date without obtaining a new authorization.

When this is used

A bank merger or branch divestiture moved the account to a new institution with a different routing number. The Originator must obtain the Receiver's new routing number and account number and update any recurring schedules. Often paired with a Notification of Change (NOC) the Originator may have already received.

When this is used

Returned by the ACH Operator (not the RDFI) when the routing number does not belong to a participating ACH institution — typically a typo, a routing number that has been retired, or a routing number that belongs to a non-ACH institution. Originator must verify the routing number with the Receiver and resubmit.

When this is used

Common with Social Security and other federal benefit programs where a representative payee receives funds on behalf of a beneficiary. The beneficiary is still alive but needs a new representative. The Originator (typically a government agency) coordinates a replacement payee before resuming credits.

When this is used

Most often involves federal benefit credits (SSA, VA) continuing to a deceased beneficiary's account. The RDFI returns the entry; the Originator must reclaim funds and update the recipient record. For private-sector debits, this code surfaces when a sole account holder has died and the account is in estate processing.

When this is used

Triggered by court orders, IRS levies, garnishments, or OFAC sanctions hits at the RDFI level. The Originator cannot resolve this directly with the Receiver; the underlying legal or compliance hold must clear first. For OFAC-related R16s, the Originator should review their own sanctions screening and confirm whether the entry should have been originated at all.

When this is used

Two flavors. First: a hard format problem only the RDFI's posting system catches. Second: the RDFI's fraud team flags the entry as suspicious — for example, a high-dollar credit to a recently opened account that matches a money mule pattern. The addenda record will identify the offending field or carry "QUESTIONABLE" for fraud-related returns.

When this is used

The ACH Operator returns the file because the Originator scheduled it too far in the future. Almost always a file-construction issue in the Originator's system: clock drift, time-zone misconfiguration, or hard-coded dates. The Originator fixes the Effective Entry Date and resubmits.

When this is used

File-format violation caught at the ACH Operator. Prenotes must carry a $0.00 amount; any non-zero value triggers R19. Other R19s arise from non-numeric or malformed amount fields. The fix is always upstream in the file builder.

When this is used

The account exists and is in good standing, but is not eligible for the entry type. Most often hit when an Originator tries to debit a savings account that has exceeded the (now relaxed but still bank-policy-driven) Reg D transaction count, or when an entry is sent to a credit-only account such as a loan account. The Originator obtains a checking-account routing/account from the Receiver and resubmits.

When this is used

The Receiver's bank cannot recognize the Originator's Company ID, typically because the Receiver enrolled the Originator with a wrong identifier in their bill-pay system. Resolution requires the Receiver to correct the Company ID at their bank.

When this is used

A CIE/MTE-specific code where the Receiver disputes the customer-account identifier supplied by the Originator. Common in bill-pay scenarios where the customer entered the wrong account number with a biller. Originator must obtain the correct Individual ID from the Receiver.

When this is used

The recipient of a credit refuses to accept it. Examples include refunds to a closed business relationship, partial payments where full payment was required, or unsolicited credits the Receiver wants nothing to do with. Originator must coordinate with the Receiver before reattempting, or issue payment via another method.

When this is used

A file or batch was inadvertently transmitted twice. The RDFI returns the second instance. Before reinitiating anything, the Originator must reconcile carefully — if the Originator had already submitted a reversal, R24 plus the reversal could double-correct and create a new imbalance.

When this is used

Common with CTX entries where remittance addenda counts must align precisely. The fix lives in the file-construction logic — the Originator's payment platform needs to emit the correct addenda count and indicator.

When this is used

Catch-all for missing required fields — Receiver Name, Transaction Code, Identification Number, etc. The return addenda specifies which field. Always upstream in the file builder.

When this is used

A formatting problem in the Trace Number field — the unique identifier that ties an entry, return, and reversal together. Often surfaces when an Originator's system regenerates trace numbers between transmission and acknowledgement.

When this is used

Originator's enrollment data captured a typo in the routing number. The fix is always to obtain a verified routing number — a voided check is the most reliable artifact.

When this is used

The corporate-side equivalent of R10. Because corporate accounts have a much shorter dispute window (2 banking days from Settlement, not 60), R29 reflects active corporate cash management — usually a corporate treasury catching an unauthorized debit during daily reconciliation. Originator must stop further entries and resolve via business-to-business channels (the ACH Network does not provide dispute resolution here).

When this is used

Specific to ARC, BOC, POP, and RCK entries. The Originator converted a paper check to ACH, but the RDFI does not participate in the check-conversion program. Originator must process the original paper check via traditional check clearing instead.

When this is used

A late-return mechanism for corporate transactions. The corporate Receiver discovers an issue after the 2-banking-day window has closed and asks their RDFI to return; the RDFI contacts the ODFI; if the ODFI agrees, the entry is returned with R31. Voluntary on the ODFI's side — there is no obligation to accept.

When this is used

Rare. The RDFI itself cannot complete settlement — typically due to operational or financial-position issues at the institution. The Originator must coordinate with the ODFI to determine an alternate settlement path.

When this is used

XCK entries are originated when a paper check has been physically destroyed (typically in transit) and converted to ACH for collection. The RDFI may unilaterally return any XCK at its discretion within an extended 60-day window.

When this is used

Regulators have restricted the RDFI's ability to receive certain ACH entries. The Originator cannot resolve this directly — the underlying restriction must be lifted by the supervisor before resuming origination to that RDFI.

When this is used

The Originator sent a debit using an SEC code that does not allow debits — for example, an XCK debit attempted in a credit-only context, or a debit using a CIE code. Almost always a configuration issue in the Originator's payment platform.

When this is used

Mirror image of R35 on the credit side. Common when an Originator misuses a debit-only SEC code (such as RCK or POP) for a credit operation. Resolution is in the file-construction layer.

When this is used

Check-conversion mishap: the Originator converted a paper check to ACH (ARC, BOC, or POP), but the original check also entered the check clearing system — so the Receiver has been double-charged. R37 returns the ACH side. Originator must ensure the paper item is destroyed or marked clearly as non-negotiable after conversion.

When this is used

Receiver placed a stop payment on the original paper check before it was converted to ACH. The RDFI honors that stop and returns the ACH entry. Resolve directly with the Receiver to identify why the stop was placed.

When this is used

Examples of ineligible source documents include checks drawn on home equity lines of credit, demand drafts, third-party checks, and checks above eligibility thresholds. The Originator's check-conversion process needs tighter eligibility filtering at the point of capture.

When this is used

ENR (Automated Enrollment) entries are zero-dollar entries used by financial institutions to enroll customers for federal benefit payments. R40 indicates the agency could not process the enrollment — typically a data mismatch with agency records.

When this is used

Format-level error specific to ENR enrollments. Originator's enrollment system emitted a Transaction Code outside the permitted ENR set. Fix is in the enrollment file builder.

When this is used

ENR-specific format error. Same root cause as R28 but limited to enrollment entries. Fix the routing number with the customer and re-enroll.

When this is used

Account-number format error specific to ENR enrollments. Resolve by collecting a valid account number from the customer.

When this is used

Mismatch between the SSN/Tax ID on the enrollment and what the agency has on file for the beneficiary. Customer must verify their identification number before re-enrolling.

When this is used

Name mismatch on enrollment — common with name changes (marriage, legal name change) where the customer updated the agency but not the bank, or vice versa. The agency requires the legal-of-record name.

When this is used

Specific to enrollments for benefits paid via a representative payee. Must be reconciled with the agency before re-enrollment.

When this is used

The customer is already enrolled for direct deposit with the agency. No further enrollment is required; if the customer wants to change accounts, they must use the agency's change-of-account process rather than a new enrollment.

When this is used

This code number is a gap in currently assigned return reason codes and should not be used as an operational return reason.

When this is used

This code number is a gap in currently assigned return reason codes and should not be used as an operational return reason.

When this is used

A handful of states impose restrictions on how returned checks may be re-presented electronically. Originator must process the underlying paper check through the check clearing system instead.

When this is used

The Receiver is disputing the underlying check that was re-presented as RCK. Because the source document is being challenged, the dispute window is the consumer 60-day window. Originator must investigate the original check and any notice given to the customer.

When this is used

The Receiver placed a stop payment on the original paper check. RDFI honors the stop and returns the RCK. Originator should resolve directly with the Receiver before any further collection attempt.

When this is used

The double-presentment safeguard for RCK. The Receiver has been charged twice and the RDFI returns the ACH side. Originator must reconcile collection records to ensure they are not still pursuing the paper item.

When this is used

This code number is a gap in currently assigned return reason codes and should not be used as an operational return reason.

When this is used

This code number is a gap in currently assigned return reason codes and should not be used as an operational return reason.

When this is used

This code number is a gap in currently assigned return reason codes and should not be used as an operational return reason.

When this is used

This code number is a gap in currently assigned return reason codes and should not be used as an operational return reason.

When this is used

This code number is a gap in currently assigned return reason codes and should not be used as an operational return reason.

When this is used

This code number is a gap in currently assigned return reason codes and should not be used as an operational return reason.

When this is used

This code number is a gap in currently assigned return reason codes and should not be used as an operational return reason.

When this is used

A dishonor code used by the original ODFI to push back at the RDFI when a return arrives at the wrong institution because of a routing-number error in the return itself. The RDFI must correct the routing number and resubmit the return.

When this is used

Used in the rare case where an Originator reverses a credit but the Receiver insists the original credit was correct. Most often surfaces in payroll context — the Originator tries to claw back a paycheck, and the employee disputes the reversal.

When this is used

This code number is a gap in currently assigned return reason codes and should not be used as an operational return reason.

When this is used

This code number is a gap in currently assigned return reason codes and should not be used as an operational return reason.

When this is used

This code number is a gap in currently assigned return reason codes and should not be used as an operational return reason.

When this is used

This code number is a gap in currently assigned return reason codes and should not be used as an operational return reason.

When this is used

Operational duplicate at the RDFI: the same return was transmitted twice. ODFI dishonors the duplicate so the original entry is not double-credited back.

When this is used

Most common dishonor code in practice. The RDFI sent a return after its allowed window — for example, an R01 sent more than 2 banking days after Settlement. ODFI dishonors and the funds remain with the Originator.

When this is used

The return itself was malformed — wrong amount, wrong original-entry-trace-number, or other format errors. ODFI dishonors and the RDFI must resubmit a corrected return.

When this is used

The reverse of R31. The RDFI sent what it claimed was a permissible late return, but the ODFI never agreed. The ODFI dishonors with R70.

When this is used

Contested-return code used by the RDFI when a dishonor arrives at the wrong institution. Mirrors R61 but in the dishonor → contest direction.

When this is used

The RDFI contests an R68 / dishonor that itself arrived outside the dishonor window (typically beyond 5 banking days from the original return).

When this is used

Direct response to R68. The RDFI provides evidence that the original return met the time-frame rule, asking the ODFI to accept the original return after all.

When this is used

The clean follow-up to R69. The RDFI fixes the field-level errors and resends the return labeled R74 so the ODFI can identify it as the corrected version.

When this is used

Contests R67 by demonstrating the second return is for a different original entry, not a duplicate of an earlier return.

When this is used

The RDFI reviewed the original return after receiving an R69 dishonor and determined the return was in fact valid. R76 sends it back to the ODFI for acceptance.

When this is used

The narrow contested-return path tied to reversal disputes. RDFI maintains that the Receiver's original credit was authorized and the Originator's reversal was improper.

When this is used

This code number is a gap in currently assigned return reason codes and should not be used as an operational return reason.

When this is used

This code number is a gap in currently assigned return reason codes and should not be used as an operational return reason.

When this is used

IAT entries carry an extensive set of mandatory addenda and OFAC-related fields. R80 catches structural problems before settlement. Originator's IAT formatting logic must be reviewed.

When this is used

Some U.S. financial institutions opt out of receiving IAT entries entirely. Originator must use a different payment rail (wire) to deliver the cross-border payment, or have the Receiver provide an account at an IAT-capable institution.

When this is used

The foreign bank identifier (typically a SWIFT BIC or local clearing code) does not resolve. Originator must verify the foreign bank reference through their correspondent or SWIFT directory before resubmitting.

When this is used

The foreign bank exists and is reachable, but cannot complete settlement — for example, due to local cut-off times, currency restrictions, or a temporary settlement issue at the foreign institution. Originator may need to resend later or use an alternate correspondent.

When this is used

The Gateway Operator (the bridge between the U.S. ACH network and foreign systems) declined to process the entry — typically due to OFAC screening hits, sanctions hits at the gateway, or operational restrictions. Originator must investigate whether the entry should have been originated at all.

When this is used

The Originator sent what should have been an IAT entry under a domestic SEC code (such as PPD or CCD). Because the entry crosses a U.S. border, it requires the IAT format and OFAC-related addenda. The Originator must reformat as IAT and resubmit. This is a key compliance code — improperly coded cross-border payments expose the Originator to BSA and OFAC violations.