money, profit, finance, business, return, yield, financial, cash, currency, investment, banking, wealth, coin, economy, success, loan, salary, rich, credit, payment, savings, save, deposit, growth, income. How ACH return codes decide your dispute window under Nacha rules
Photo by nattanan23 on Pixabay

Rules

How ACH return codes decide your dispute window under Nacha rules

ACH return codes and Nacha dispute windows: seven codes carry the 60-calendar-day return right, the rest only a few banking days. Here is how it works.

What to take away

  • Your return code decides the clock. On ACH return codes and Nacha dispute windows, the split is clean: seven codes — R05, R07, R10, R11, R51, R52 and R53 — carry the 60-calendar-day return right on a consumer debit, counted from settlement, not from the day you spot the charge. Every other code must go back within the short banking-day window.
  • R01 means insufficient funds, R05 means unauthorized debit, R10 means the customer says the debit was not authorized, and R11 means the customer says an authorized entry was in error.
  • A return code is not a ruling that you win. It is the receiving bank's reason for sending the entry back.
  • You never choose the code. Your bank selects it, and R05, R10 and R11 are not options on a form.
  • Regulation E runs a second clock on error claims that can stay open after the 60-day network window closes.

Where the 60-day window comes from

Nacha governs the ACH network, the batch system behind payroll, benefits, subscriptions and person-to-person payments between US accounts. Its rules set how long a receiving bank may hold an entry before returning it.

Article Three of the Nacha Operating Rules covers return timeframes, the section to cite for the 60-day figure.

For a consumer debit entry, the deadline depends on the return code. Two windows apply, and the code sorts the entry into one of them.

[figure 2]

60-Day Return Window Timeline

  1. Settlement date
    Entry settles between banks
  2. Day 58
    Call bank, little room left
  3. Day 60
    Return window closes at midnight
  4. Day 70
    Must handle as dispute, not return

Nacha amended its consumer debit return rules with an effective date in 2021, moving those entries from the two-business-day practice banks had applied to the current 60 calendar days.

Settlement date is the day the entry settles between the banks, not the day you noticed it. A charge from three weeks ago can still be returnable while one from four months ago cannot.

Which return codes get the 60-day window

For a consumer debit entry, the two windows look like this:

  • 60 calendar days from settlement:R05, R07, R10, R11, R51, R52 and R53 — the codes used when a consumer says a debit was unauthorized, the authorization was revoked, or an authorized entry was wrong. The receiving bank may return until midnight of day 60.
  • The short banking-day window:R01 and every other code, which must go back within a couple of banking days of settlement, in practice the two-business-day baseline banks applied before the rules changed.

The same 60 days generally applies to consumer credits, which matters when a payroll deposit lands and is later pulled back.

For an R05, R10 or R11 return on the extended clock, the rules require paperwork behind the claim: the receiving bank must obtain a Written Statement of Unauthorized Debit (WSUD) from the account holder. The written statement, not the phone call, is what supports the return.

Nacha publishes the full Return Reason Code list, and that published table is the source for the codes below. These are the ones a disputing reader actually meets.

R01, R05, R10 and R11 decoded — and the other codes you may meet

  • R01 insufficient funds.The account lacked available money when the entry posted, and no fraud claim is involved. Short window.
  • R05 unauthorized debit.The receiving bank returns a debit because the account holder said it was not authorized. Extended window.
  • R07 authorization revoked.The customer had authorized the debit and then took the authorization back before the entry posted. Extended window.
  • R10 customer advises not authorized.The same claim as R05, recorded in writing or on a call. Extended window.
  • R11 customer advises entry in error.The authorization existed, but the amount, date or duplicate posting was wrong. Extended window.
  • R51, R52 and R53.Check-conversion entries — an ineligible item, a stopped payment, or an item and its ACH entry presented twice. These sit on the extended window as well.
  • R02 closed account, R03 no account.The account was closed, or cannot be located, which is what an old subscription and a switched bank look like from the other side. Short window.
  • R08 payment stopped.The customer placed a stop payment on the entry. Short window.
  • R29 corporate customer advises not authorized.The business, not a consumer, says the debit was not authorized. Short window.
CodeMeaningWhat it signals
R01Insufficient fundsBalance problem, not fraud
R05Unauthorized debitNo valid authorization
R10Customer advises not authorizedDocumented claim of no authorization
R11Customer advises entry in errorAuthorization existed, entry was wrong

Only the receiving bank applies the code. Describe what happened, and the bank decides whether the facts support R05, R10 or an error investigation. Duplicate postings and slow reversals are traced in pending payments and reversals.

Example: crediting after the return window closes

Suppose a subscription debits your checking account on 3 March and settles the same day. Day 60 falls in early May.

You notice the charge in June, around day 95. The bank cannot return it as R05 or R10, so it opens an error investigation and credits the amount, reversible if the charge proves authorized.

Call on day 58 and the path is shorter: the bank returns the entry without a full investigation or a provisional credit.

Filing the dispute with your own bank

Nacha does not take consumer complaints. You file with the bank or credit union that holds the account, which acts as the receiving bank.

  1. Call the number on your statement and dispute the ACH debit.
  2. Ask for the actual return code in writing.
  3. If the bank is weighing an R05, R10 or R11 return, expect to sign a written statement of unauthorized debit.
  4. Send a written error notice to the address in your account agreement.
  5. Record the case number and the name of the person you spoke to.
  6. Check the account daily until the credit posts.

[figure 4]

How to File an ACH Dispute

  1. Call bank, ask for return code and settlement date
  2. Follow up in writing via secure message or letter
  3. State plainly if debit was unauthorized or in error
  4. Ask for provisional credit and case number
  5. Keep copies of everything you send and receive

If the bank will not act, escalate. A complaint with the CFPB is the usual next step, and you can also complain to the bank's prudential regulator: the OCC for national banks, the Federal Reserve for state member banks and bank holding companies, the FDIC for state nonmember banks, and the NCUA for federal credit unions. Money sent to the wrong person is covered in wrong recipients and scam transfers.

Re-presentment after a return

A returned entry is often not the end. The originating bank may correct the problem and re-present it under the rules. Re-presentment is limited, and each attempt can be returned again, so watch for a second debit after you thought the matter closed.

A re-presentment does not extend your Regulation E right to an investigation. If the entry reappears and was never authorized, report it again.

Regulation E sits on top of the Nacha clock

Regulation E governs consumer electronic fund transfers and applies alongside the network rules. The official text sits at 12 CFR Part 1005.

The Nacha deadline is between banks. The Regulation E clock is your own right to an error investigation, and it can outlast the return window.

The error-resolution side of Regulation E sits at 12 CFR 1005.11. Notify the bank of a claimed error and it has to investigate; you keep that right when you report the problem within 60 days after it sends the statement showing the transfer. That clock is the one to watch in an ACH dispute, because it can outlast the network's return window.

Regulation E limits what you can lose on a card, code or other access device that is lost or stolen: report the loss within two business days of learning about it and your liability is capped at $50. Wait longer and the cap can rise to $500. Past 60 days from the statement, liability can become unlimited. The tiers sit in 12 CFR 1005.6.

A bank that can still return an entry may do that instead of opening an investigation, because a return is faster. Once the window closes, your Regulation E claim is the remaining route. Frozen accounts during a claim are covered in account freezes and partner-bank confusion.

Common questions

How long do I have to dispute an ACH debit?
Two clocks run. Nacha's return window is 60 calendar days from settlement, and only for the extended codes — R05, R07, R10, R11, R51, R52 and R53. Your Regulation E right to an error investigation is separate: report an unauthorized transfer within 60 days of the statement and the bank must investigate it, while the liability tiers for a lost or stolen access device start at two business days and $50.
Does an R05 mean I win the dispute?
No. It means the receiving bank sent the debit back as unauthorized. The originating bank can contest the return, and a re-presentment can follow.
Can I ask my bank to use R10 instead of R05?
No. The bank selects the code from the facts you give it. R05, R10 and R11 are not customer choices on a form.
Can I dispute an ACH credit that was pulled back?
Yes, if the entry was wrong or duplicated. Contact your bank quickly, because the credit side generally carries the same 60-day window from settlement.

More in Rules

Latest from Guides Desk