ACH Chargebacks & Disputes: Rules, Time Frames, and How to Respond

When a customer disputes an electronic bank payment, merchants usually call the result an ACH chargeback. The ACH network technically calls it a return, but the effect is the same: the disputed money leaves your account. ACH disputes run on different rules, time frames, and remedies than credit card chargebacks, and merchants who treat the two the same get caught out. This guide covers who can dispute an ACH transaction and how long they have, the NACHA and Regulation E rules involved, the return codes you'll actually see, and how merchants can respond to — and lower — ACH disputes. If disputes are already straining your ACH payment processing, the prevention checklist below is a good place to start.

What Is an ACH Chargeback?

An ACH chargeback is the reversal of an ACH payment after a customer disputes it with their bank. The customer's bank returns the transaction through the ACH network — typically because the debit was unauthorized, duplicated, or processed for the wrong amount or date — and the funds are pulled back from the merchant's account.

Strictly speaking, the ACH network doesn't use the word "chargeback" at all; that's card-network vocabulary. What merchants experience as an ACH chargeback is a return entry, and the complaint behind it may be called an ACH dispute or an ACH claim. The labels matter less than the mechanics, which differ from card chargebacks in ways this guide covers section by section.

What Is an ACH Payment?

An ACH payment is an electronic funds transfer from one bank account to another through the Automated Clearing House (ACH) network — the system behind direct deposit, bill payments, recurring billing, and a growing share of e-commerce. ACH payments typically carry lower processing fees than credit card transactions, and bank accounts don't expire the way cards do, though transfers settle more slowly. And just like card payments, customers can dispute them.

ACH Chargebacks vs. Credit Card Chargebacks

ACH chargebacks are narrower than credit card chargebacks: they cover problems with the payment itself, not dissatisfaction with the product or service. They also follow different time limits and give merchants no formal representment process.

• Valid reasons. Card networks accept disputes over product and service issues — item not received, not as described, and so on. ACH disputes are generally limited to payment problems: unauthorized debits, incorrect amounts or dates, and duplicate entries.
• Dispute time limits. ACH windows split sharply by account type: roughly 60 calendar days for consumer accounts, effectively 2 banking days for business accounts. Details below.
• Merchant recourse. Card networks offer a formal representment and arbitration path for fighting a chargeback. The ACH network has no equivalent — merchants work through their bank (the ODFI) and directly with the customer instead.

The upside for merchants: because product complaints aren't valid grounds, banks are generally stricter about what counts as a legitimate ACH dispute than card networks are about chargebacks.

Can You Dispute an ACH Transaction?

Yes — you can dispute an ACH transaction, with conditions. Account holders can ask their bank to return an ACH debit that was unauthorized, processed for the wrong amount or date, or duplicated, and the window for doing so depends on the type of account.

• Consumer accounts get the strongest protection: generally about 60 calendar days to dispute an unauthorized debit, backed by NACHA rules and Regulation E.
• Business accounts get far less: under NACHA rules, an unauthorized corporate debit effectively must be returned within 2 banking days.

One important limit: dissatisfaction with goods or services is not valid grounds for an ACH return. A customer unhappy with a product needs to resolve it with the merchant directly — a bank can only reverse payment-level problems.

How to Dispute an ACH Transaction (Step by Step)

To dispute an ACH transaction, contact your bank, explain why the debit was unauthorized or incorrect, and complete the bank's dispute paperwork; the bank then files the return through the ACH network. Here is the process in order:

• Step 1 — Review the transaction. Confirm the debit really is unauthorized, duplicated, or incorrect. Check the statement descriptor against your subscriptions and agreements first — many "unauthorized" debits turn out to be unrecognized ones.
• Step 2 — Contact your bank promptly. The windows are strict: consumer accounts generally have about 60 calendar days, business accounts as little as 2 banking days.
• Step 3 — Sign the Written Statement of Unauthorized Debit. For unauthorized consumer debits, the bank will typically ask you to complete a WSUD, a signed statement affirming the entry wasn't authorized as it posted.
• Step 4 — The bank files the return. Your bank — the receiving depository financial institution, or RDFI — sends a return entry through the ACH network with the appropriate reason code, and the amount is charged back to the merchant.

What Happens on the Merchant's Side

When the return arrives, the merchant's bank — the originating depository financial institution, or ODFI — debits the merchant's account and passes along the return code. There is no built-in rebuttal window like card chargebacks provide; the return simply posts. What a merchant can do next is covered in the response section below.

ACH Dispute Time Frames: How Long Do You Have?

Consumers generally have about 60 calendar days to dispute an unauthorized ACH debit, while business accounts effectively have only 2 banking days under NACHA rules. Don't confuse these dispute windows with return settlement, which typically takes about 2–3 banking days once a return is filed.

• Consumer accounts: roughly 60 calendar days. NACHA's extended return window for unauthorized consumer entries — consistent with Regulation E's consumer protections — gives account holders about two months to catch and dispute an unauthorized debit.
• Business accounts: 2 banking days. Corporate entries must come back almost immediately, which is why businesses that pay or get debited by ACH should reconcile accounts daily. Miss the window and the bank generally can't return the entry, leaving the business to pursue the counterparty directly.
• Return settlement: about 2–3 banking days. Once a bank accepts a dispute and transmits the return, the money movement itself is quick. The often-repeated claim that ACH disputes "resolve in 2–3 business days" mixes these up — that figure describes how fast a filed return settles, not how long a customer has to dispute.

ACH Dispute Rules: NACHA and Regulation E

Two rulebooks govern ACH disputes: the NACHA Operating Rules, which bind every bank and originator on the network, and Regulation E, the federal rule protecting consumers in electronic funds transfers.

NACHA — the National Automated Clearing House Association — governs the ACH network. Its rules define return codes and return windows, and they require merchants, as originators, to obtain and retain proper authorization for every debit, use the correct entry codes, and honor revocations and stop payments. Merchants that ignore the rules or accumulate excessive returns face penalties and fines and can put their origination privileges at risk.

Regulation E gives consumers the right to dispute unauthorized electronic debits and requires banks to investigate those claims. It's the reason consumer windows are long and consumer claims are usually honored, while business accounts operate on the thinner protections of the NACHA rules alone.

Common ACH Return and Dispute Reason Codes

Every ACH return carries a reason code, and a handful of codes account for most of the disputes merchants see. Here are the ones to know and what to do when each arrives:

• R05 — Unauthorized debit to consumer account using corporate SEC code. A consumer account was debited with a corporate-type entry without authorization. Merchant action: verify you're using the correct SEC code for the account type, and obtain proper consumer authorization before billing again.
• R07 — Authorization revoked by customer. The customer previously authorized the debit but has since revoked that authorization. Merchant action: stop all future debits immediately and resolve the underlying issue before originating again.
• R08 — Payment stopped. The customer placed a stop payment order before the debit posted. Merchant action: contact the customer about the balance owed; don't re-originate without fresh authorization.
• R10 — Customer advises unauthorized. The account holder told their bank they never authorized the debit — the classic ACH "chargeback." Merchant action: pull your proof of authorization, request a copy of the Written Statement of Unauthorized Debit through your ODFI, and pursue the customer directly if the claim doesn't hold up.
• R11 — Entry not in accordance with the terms of the authorization. Authorization exists, but the debit didn't match it — wrong amount or wrong date, for example. Merchant action: correct the error; unlike an R10, an eligible R11 can generally be fixed and re-presented.
• R29 — Corporate customer advises not authorized. The business-account counterpart to R10, subject to the 2-banking-day window. Merchant action: contact the business and provide your authorization records.

These six aren't the whole rulebook — NACHA maintains dozens of return codes, most covering routine processing failures such as insufficient funds (R01) or closed accounts (R02) — but they're the codes that signal a dispute rather than a technical failure.

What Is an ACH Claim?

An ACH claim is the formal assertion a customer files with their bank that an ACH transaction was unauthorized, erroneous, or fraudulent. The claim starts the process, the dispute is the process itself, and the return is the mechanism the bank uses to send the money back.

In everyday use the terms blur — a customer "files a claim," "opens a dispute," or "charges back a payment" — and from the merchant's side all three arrive the same way: as a return entry with a reason code and a debit to the merchant account. For unauthorized consumer claims, the bank documents the claim with a signed Written Statement of Unauthorized Debit, which is the document a merchant can later request when evaluating whether a claim is legitimate.

ACH Fraud Claims: Who Is Liable and How Banks Investigate

When an ACH fraud claim is legitimate — an account really was debited without authorization — the consumer is generally made whole, and the loss lands on the originating side: the merchant absorbs the returned funds plus any related fees. Regulation E protects consumers who report unauthorized debits within the window; business accounts carry more of their own risk because of the short 2-banking-day return window.

The investigation runs through the customer's bank. The RDFI takes the claim, typically requires a signed Written Statement of Unauthorized Debit, reviews the transaction details against the claim, and — if it accepts the claim — returns the entry through the ACH network with the appropriate code, such as R10. For consumer accounts, Regulation E obligates the bank to investigate disputed transfers rather than simply reject them.

For merchants, the mirror-image problem is the false fraud claim: a customer disputing a debit they actually authorized. Practical recovery steps:

• Request a copy of the WSUD through your ODFI and compare it against your authorization records.
• Contact the customer with your evidence — many "fraud" claims are confusion over an unrecognized descriptor rather than malice.
• Re-present where the rules allow, such as a corrected R11 entry.
• For clear abuse, pursue the funds through direct invoicing, collections, or legal action.
• Watch your unauthorized return rate; excessive unauthorized returns invite NACHA penalties and scrutiny from your bank.

How Merchants Can Lower ACH Disputes

Merchants can lower ACH disputes significantly with disciplined authorization, validation, and billing practices. Most disputes trace back to a customer who didn't recognize a debit, wasn't expecting the amount or date, or couldn't reach the merchant fast enough to fix a problem — and all three are preventable.

• Keep airtight authorization records. Retain proof of authorization for every debit — signed forms, recorded phone authorizations, logged online consents — so you can answer any unauthorized claim with documents.
• Validate accounts before you debit. Use account validation or prenotes to confirm account details before the first live transaction; this cuts administrative returns and reduces declines caused by bad account data.
• Use a recognizable statement descriptor. Make sure the name on the customer's bank statement matches the name they bought from — unrecognized descriptors are a leading driver of "unauthorized" claims.
• Set expectations for recurring billing. Disclose amounts, dates, and frequency clearly, and notify customers before any change in amount.
• Handle refunds and cancellations fast. A prompt refund costs far less than a dispute; make cancellation easy and honor it immediately.
• Apply deliberate retry logic to insufficient-funds returns. NSF returns can generally be re-presented, but uncontrolled retries frustrate customers and inflate return rates — space retries sensibly and communicate before re-debiting.
• Layer in fraud prevention. Anti-fraud screening, multi-factor authentication, tokenization, and encryption reduce genuinely unauthorized transactions and protect stored account data.
• Monitor activity and act early. Watch for suspicious transactions and treat the first sign of a dispute as urgent — early customer contact resolves many issues before a return is ever filed.

The right processor makes much of this easier to put into practice. If disputes and unauthorized returns are a recurring drag on your business, PayKings' ACH payment processing is built with high-risk merchants — the businesses most likely to face elevated dispute volume — in mind.

How to Respond to an ACH Dispute as a Merchant

There's no formal rebuttal process through the ACH network the way card networks allow, but the common claim that merchants "can't contest" ACH returns overstates things. ACH dispute resolution for merchants runs through your bank and the customer, and you have several practical avenues:

• Work through your ODFI. Your bank is your interface to the ACH network — it can pass documentation along, interpret return codes, and advise whether a return qualifies for re-presentment.
• Request the Written Statement of Unauthorized Debit. For unauthorized-entry returns such as R05, R07, and R10, ask your ODFI to obtain a copy of the customer's signed WSUD and check it against your authorization records.
• Re-present eligible returns. Some returns can be corrected and re-originated under NACHA rules — a wrong-amount R11 can be fixed and re-presented, and insufficient-funds returns can be retried.
• Resolve directly with the customer. Often the fastest path: share your evidence, fix genuine errors, refund where warranted, and pursue false claims through direct contact, collections, or legal action if necessary.

Build the evidence file before you need it. A strong response package includes:

• Proof of authorization — the signed form, recorded call, or logged online consent, with date and terms
• Transaction records — amount, date, entry type, and the statement descriptor the customer saw
• Delivery or service records showing the customer received what they paid for
• Communication logs — emails, support tickets, and call notes
• Refund and cancellation history for the account

Disputes strain banking relationships as much as cash flow, so documentation protects more than any single transaction. And if your current provider treats every return as your problem alone, it may be time to look at high-risk merchant solutions built for businesses that live with elevated dispute volume.