ACH Payment Disputes, Return Reasons, and Merchant Actions

rétrofacturation?
Ce n'est plus votre problème.
Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000+ merchants.
En bref :
- An ACH dispute is a bank return, not a card chargeback: the receiving bank sends the debit back under a Nacha return reason code, so read the code before choosing a response.
- Yes, an ACH payment can be disputed: the route is a bank or provider return or inquiry procedure, and it should not be assumed to follow card representment rules.
- Build the authorization record first: the accepted mandate, debit identifiers, and return code decide the next step, and an invalid authorization should not be reused automatically.
- R11 is a terms mismatch: a wrong amount or date under a valid authorization calls for correcting the entry, not for treating the customer as a fraud suspect.
- Nacha fraud monitoring Phase 2: June 19, 2026 is the nominal date, and June 22, 2026 is the practical compliance date for remaining non-consumer originators, service providers, and RDFIs in the specified roles.
An ACH payment dispute concerns a bank-account payment handled through ACH rules and the provider’s available return or inquiry workflow. The merchant should identify the account type, return reason, authorization, and case controls before taking action.
It is not a card chargeback. The receiving bank returns the debit to the originating bank under a Nacha return reason code, and what a merchant can do next depends on the case type and the provider. Nacha is the organization that governs the ACH network. This guide covers the return codes merchants see, the clocks that apply, and the authorization record to build before responding.
{{cta}}
Qu'est-ce qu'un litige ACH ? Différence entre un rejet de prélèvement ACH et une contestation de paiement par carte bancaire
An ACH dispute happens when a bank customer, a business, or a receiving bank flags an ACH debit as unauthorized, inaccurate, or improperly processed. The receiving bank (the RDFI) does not “charge back” the transaction the way a card issuer would. Instead, it returns the entry to the originating bank (the ODFI) using a standardized Nacha return reason code, and the funds move back through the network. For the general idea of a reversed payment, see the payment reversal meaning explainer. A card chargeback, by contrast, is a separate contractual dispute process defined by the card networks (Visa, Mastercard, and similar); see our explainer on what is a chargeback for the full picture.
Pour les commerçants qui acceptent l'ACH comme moyen de paiement, que ce soit par l'intermédiaire d'un prestataire de services de paiement, d'un portail bancaire ou d'une plateforme de facturation, les différences concrètes sont les suivantes :
- A return code, not a case number. Every ACH return carries a two-character Nacha code (R05, R07, R10, R11, R29, and others) that states why the funds came back.
- The route depends on the case. A return and an authorization inquiry are handled differently, and the controls your provider displays for the case decide what you can submit, not card-network representment rules.
- Different clocks. The customer’s filing window, the receiving bank’s return deadline, and any provider evidence deadline are separate and should not be merged into one number.
- Evidence starts before the debit. The accepted mandate, timestamp, and IP address need to exist before the debit, not after the return.
How ACH Payments Work
The Automated Clearing House (ACH) is an electronic network for bank-to-bank transfers in the United States. It carries payroll, bill payments, and online purchases, which is why any merchant that debits customer bank accounts needs to understand returns.
« En 2025, le réseau ACH a traité 35,19 milliards de paiements pour un montant total de 93 000 milliards de dollars, soit une hausse de 4,9 % en volume et de 7,9 % en valeur par rapport à l’année précédente, ce qui représente une moyenne de 141 millions de transactions par jour. » Rapports sur le volume du réseau ACH de Nacha
Each ACH entry is identified by a three-letter code for the transaction type, and knowing the type tells you which authorization record to look for when a debit is questioned:
- PPD (Prearranged Payment and Deposits): Used for pre-authorized recurring payments such as subscription billing.
- TEL (Telephone-Initiated Entry): Également appelé « transaction par téléphone ».
- WEB (saisie via le Web): largement utilisé dans le commerce électronique.
Valid and Invalid Reasons for ACH Disputes
Return reasons under Nacha rules center on whether the debit was authorized, whether it matched the agreed terms, and whether it was processed properly. Common valid grounds include:
- Unauthorized Transaction: The debit was never authorized, or the authorization was canceled or revoked before a recurring debit was processed.
- Incorrect Amount or Date: The debit differs from the agreed amount or was processed earlier than agreed.
- Improper Processing: The debit was processed incorrectly, such as a duplicate payment.
Other complaints do not fit these grounds on their own. Buyer’s remorse, forgetting a recurring payment, or a delivery delay is not an ACH return reason, and product or service quality issues are best resolved directly with the customer. A return code records the reason given, not the customer’s intent, so do not assume friendly fraud from a claim alone.
The Impact of ACH Disputes on Businesses
ACH disputes can have significant consequences for merchants:
- Perte de revenus: des fonds peuvent être prélevés sur le compte du commerçant.
- Cash Flow Disruptions: Returns make cash flow harder to forecast.
- Additional Fees: Merchants may incur fees under their provider or bank terms.
- Atteinte à la réputation: un taux élevé de litiges peut nuire aux relations avec les banques et les clients.
- Difficultés opérationnelles: les banques peuvent imposer des limites de transaction ou retenir les fonds plus longtemps.
Software and other digital-goods sellers face a card-side version of these disputes as well; see digital goods chargebacks for that process.
Build an ACH Return and Authorization Record
When a debit is returned or questioned, the record you assemble decides what you can do next. Start by identifying whether the case is a return or an authorization inquiry, then match it to the table below. Name one case submission owner for each case, so a manual reply and an automated submission never go out for the same debit.
| Case or event | Required record | Operational action / Avoid this assumption |
|---|---|---|
| Authorization inquiry | Accepted mandate and debit identifiers | Operational action: Provide authorization through the displayed inquiry route Avoid this assumption: A sales receipt replaces the mandate |
| Return reports no authorization | Return reason, original mandate and account context | Operational action: Stop reuse of invalid authorization and follow provider instructions Avoid this assumption: A successful earlier debit authorizes every later debit |
| R11 terms mismatch | Agreed amount/ | Operational action: Investigate and correct the specific mismatch Avoid this assumption: An error under valid authorization proves customer fraud |
| Refund overlaps a return | Original debit, refund credit and return references | Operational action: Reconcile value movement before issuing more credit Avoid this assumption: An ACH refund cancels an independently initiated return |
R11 addresses an entry that does not follow an otherwise valid authorization, such as a wrong date or amount, so treat it as a terms mismatch. A return code is a reason classification, not independent proof of deliberate customer fraud, as Nacha’s guidance on differentiating unauthorized return reasons explains.
A refund can overlap with a return, so reconcile the original debit, the refund credit, and the return references before issuing more credit. The refund vs reversal difference matters here: a refund you initiate does not cancel a return the bank has already initiated on its own. For a broader look at where retained records come from and how they are joined, see chargeback evidence sources.
Keep the Clocks Separate
Several different clocks get mixed together in ACH guidance, and each applies to a different event:
- Customer filing: consumers generally have 60 days to report an unauthorized debit to their bank.
- Receiving-bank return: unauthorized debits to a business account must generally be returned within 2 banking days of settlement.
- Authorization inquiry: where your provider displays an inquiry, answer through that route with the accepted mandate and debit identifiers.
- Provider evidence deadline: follow the evidence_due_by value displayed on the case. Stripe’s ACH Direct Debit documentation describes a 60-calendar-day evidence window counted from dispute creation, which is not the customer’s filing window.
That same documentation also calls timely ACH disputes final in one section and describes a Counter dispute control in another. Because provider guidance can conflict, rely on the controls shown for your case rather than on a general rule.
Worked Example
Debit on the first of the month
Submitted on the third of the month
Preserve the accepted mandate, the actual debit, and the return code. Investigate the amount and date mismatch before treating the case as an unauthorized account or retrying the same instruction. This is the R11 pattern from the table above.
Steps for Merchants
- Identify the case type. Confirm whether it is a return with a reason code or an authorization inquiry, and whether the account is a consumer or business account.
- Pull the record. Gather the accepted mandate, the debit identifiers, and the return code.
- Check the provider controls. Use only the response options and due date the case displays.
- Contact the customer. Reach out directly to clarify the issue. If the complaint is valid, correct the entry or refund it, after checking whether a return is already in progress.
- Apply account updates. A notification of change tells you when account details such as a routing number have changed; update your records before the next debit.
- Review and prevent. Look for patterns in billing practices, transaction records, or authorization steps that produced the case.
Décider de relancer un paiement
An ACH return occurs when a payment fails to process or is reversed. Reasons include insufficient funds, a closed account, incorrect information, or an unauthorized transaction, and the bank sends a return code indicating which. Any fee depends on your provider and bank terms.
Use the following table to determine if you can retry a returned ACH Direct Debit payment:
Common ACH Return Reason Codes
| Code | Motif | Pourrais-tu réessayer ? |
|---|---|---|
| R01 | Fonds insuffisants | Oui. Nacha autorise jusqu'à deux tentatives de relance une fois que les fonds sont disponibles. |
| R02 | Compte fermé | Non. Commencez par récupérer les informations de compte mises à jour. |
| R03 | Aucun compte / impossible de trouver le compte | Non. Vérifiez les informations relatives au compte. |
| R04 | Numéro de compte invalide | Non. Commencez par corriger le numéro de compte. |
| R05 | Prélèvement non autorisé (compte de particulier) | No. Obtain new authorization |
| R07 | Authorization revoked by customer | No. Obtain new authorization |
| R08 | Paiement suspendu | Non. Contactez le client pour régler le problème. |
| R09 | Fonds non perçus | Oui. Réessayez une fois que les fonds auront été crédités. |
| R10 | Le client indique que cela n'est pas autorisé | No. New authorization required |
| R11 | Entry not in accordance with the terms of the authorization (wrong amount, early date, or similar error). A terms mismatch, not proof of customer fraud | Yes, if corrected. Fix the entry and resubmit; no new authorization is needed. Confirm the resubmission window with your provider or bank |
| R16 | Compte bloqué | Non |
| R29 | Les conseils aux entreprises ne sont pas autorisés | No. New authorization required |
| R51 | Entrée RCK (conversion de chèque) d'origine incorrecte | No. Confirm the underlying item and authorization |
Note: Repeatedly retrying transactions that cannot succeed may result in fines from Nacha and could lead to being blocked from sending new ACH transactions. Follow ACH network guidelines on retries.
ACH vs. rétrofacturation
ACH disputes and card chargebacks differ in their governing rules, in who sets the clocks, and in the response route. On the card side, merchants answer with compelling evidence, often organized in a chargeback response template. For the wider card-side picture, see our chargeback statistics report. For issuer and network routes on card payments, use our directory of card network and bank disputes.
| Aspect | Litige / retour ACH | Card chargeback |
|---|---|---|
| Règles applicables | Règles de fonctionnement de Nacha | Réseaux de cartes (Visa, Mastercard et autres) |
| Customer filing window | Set by Nacha rules and the customer’s bank, and differs by account type | Set by card network and issuer rules |
| Dispute reasons | Nacha return reason codes (R-codes) | Network reason codes, including product or service issues |
| Réponse du commerçant | Depends on the return or inquiry route and the controls the provider displays for the case | Representment with compelling evidence under network rules |
| Frais | Set by your provider and bank terms | Set by your acquirer or processor terms |
Merchants who accept both cards and ACH often pair this playbook with a chargeback alert service on the card side, since an early alert can stop a card dispute before it escalates.
Nouvelles règles de la Nacha que les commerçants doivent connaître en 2026
Nacha oversees the ACH network and its Operating Rules, and compliance is mandatory. It is also phasing in a fraud monitoring rule that reaches more ACH participants than banks.
- Phase 1 (effective March 20, 2026) requires ODFIs and any non-consumer originator, third-party service provider, or third-party sender that originated 6 million or more entries in 2023 to maintain risk-based processes for identifying fraudulent entries (Nacha, Risk Management Topics).
- Phase 2 is nominally effective June 19, 2026. Because that date is a federal holiday, Nacha gives Monday, June 22, 2026 as the practical effective and compliance date. It covers the remaining non-consumer originators, third-party service providers and senders, and RDFIs in the specified roles, and it requires risk-based processes with at least an annual review (Nacha, fraud monitoring Phase 2).
The rule does not require one particular vendor, and it does not make every ACH return a fraud case.
These expectations sit alongside Nacha’s WEB debit account validation rule, in force since March 2021, which requires originators to verify that an account number belongs to an open, ACH-eligible account before the first debit and after any account change. Together they are part of a broader shift toward proactive ecommerce fraud prevention.
Conseils en matière de conformité pour les entreprises
Pour rester en conformité, les commerçants doivent :
- Obtenir l'autorisation requise: obtenir un consentement explicite et vérifiable.
- Tenir des registres précis: conservez une documentation détaillée de vos transactions.
- Fournir des informations claires: indiquer clairement les conditions, les tarifs et les politiques.
- Assign One Case Owner: Give each return or inquiry a single case submission owner, whether the response is manual or automated.
- Stay Informed: Regularly update knowledge of Nacha rules.
{{cta}}
FAQ sur les litiges liés au système ACH et à l'rétrofacturation
Une contestation ACH correspond-elle à un rejet de prélèvement ?
No. An ACH dispute is processed as a return under the Nacha Operating Rules, using a return reason code such as R05, R07, R10, R11, or R29. A chargeback is a separate process run by the card networks, with representment rules specific to cards. The mechanics, timelines, and evidence a merchant can submit differ, so check the route your provider shows for the ACH case.
Can an ACH payment be disputed?
Yes. ACH payments have bank and provider dispute or return procedures. The available route depends on the payment and case type; it should not be assumed to follow card-network representment rules.
Qu'est-ce qu'un rejet de prélèvement ACH ?
An ACH chargeback is the everyday name for an ACH return or reversal: the customer’s bank pulls back an ACH debit under a Nacha reason code, most often because the debit was unauthorized (R05, R07, R10, R29). Unlike a card chargeback, it should not be assumed to follow card-network representment rules, and the route available depends on the case.
Qu'est-ce qu'une réclamation ACH ?
An ACH claim is a customer’s formal report to their bank that an ACH transaction was unauthorized, duplicated, or processed for the wrong amount or date. If the bank accepts the claim within the allowed window, it returns the debit to the merchant’s bank and the funds are reversed.
Dans quel délai faut-il contester une transaction ACH ?
Consumers generally have 60 days to report an unauthorized debit to their bank, and unauthorized debits to a business account must generally be returned within 2 banking days of settlement. A provider’s evidence deadline is a separate clock: use the evidence_due_by value shown on the case.
Can a merchant respond to an ACH dispute?
Sometimes. The available response depends on the return or inquiry type and the controls your provider displays. Use the displayed route and deadline, assemble the accepted mandate, debit identifiers, and return code, and resolve complaints directly with the customer where that is appropriate.
Can a merchant reuse an ACH mandate after a dispute?
Do not automatically reuse disputed or invalid authorization. Check the provider’s mandate state, resolve the issue with the customer, and collect new authorization where required before another debit.
Quels sont les codes de retour ACH les plus courants ?
The most common are R01 (insufficient funds), R02 (account closed), R05 and R10 (unauthorized consumer debit), R07 (authorization revoked), R11 (entry not in accordance with the authorization terms), and R29 (corporate customer advises not authorized). Insufficient-funds returns may be retried within Nacha’s reinitiation limits; R11 can be corrected and resubmitted without new authorization; the unauthorized-return codes require new authorization before another debit.
Protégez votre entreprise contre les retours ACH coûteux
Telling ACH returns apart from card chargebacks, and keeping an authorization record ready, helps merchants who accept bank debits limit operational disruption and revenue loss. Assign one case submission owner so manual and automated work never overlap.
For supported card-payment workflows, connect relevant evidence collection and response submission with Chargeflow Automation. Get started now.
Recover Chargebacks Without the Paperwork
Chargeflow Automation builds and submits evidence for the chargebacks that still arrive.

rétrofacturation?
Ce n'est plus votre problème.
Récupérez 4 fois plus d'rétrofacturation s et PRÉVENTION jusqu'à 90 % des messages entrants, grâce à l'IA et à un réseau mondial de 20 000 commerçants.














.avif)


