Skip to main content

How ACH Returns are handled & fees

What happens when an ACH payment is returned, what it costs you, and how to prevent it.

ACH payments don't decline in real time the way credit cards do. An ACH payment can look successful for days and then come back as a return, because the customer's bank rejects the transfer.

This article explains what happens to the money, what it costs, and how to stop returns from happening in the first place.

📌 Note: An ACH return is not the same as an ACH dispute.

  • A return means the transfer could not be completed.

  • A dispute means the customer is contesting a payment that did complete.

For disputes, chargebacks, and refunds, see Handling Disputes in Method Pay.


Why ACH returns happen after the fact

There is no real-time authorization on ACH. When a payment is submitted, the funds status is unknown until the receiving bank responds.

Return type

Typical cause

When it arrives

Administrative

Insufficient funds,
Closed account,
Wrong account, or
Wrong routing number

2–3 business days

Authorization-related

Customer revoked authorization, or says the debit wasn't authorized

Up to 60 calendar days

Dispute-related

Customer formally contests the payment through their bank

Up to 90 days after processing

Every return carries a reason code from R01 to R85. For the full code list and what each one means, see ACH rejection codes.

The most common ones:

Code

Meaning

What to do

R01

Insufficient funds

Contact the customer, retry once funded

R02

Account closed

Collect new bank details before retrying

R03

No bank account /
unable to locate

Account or routing number doesn't match the bank's records. Collect the correct details.

R04

Invalid account number

Correct the details and resubmit

R07

Authorization revoked

Do not retry without new authorization

R08

Payment stopped

Contact the customer

R10

Customer says not authorized

Do not retry without new authorization

📌 Note: ACH returns cannot be disputed. Unlike a card chargeback, there is no evidence submission process — the return is an automated decision made by the customer's bank.


What happens to the money

Standard ACH payments deposit on T+4: four business days after processing. Where the return lands relative to that deposit determines what you see.

If the payment is returned before it deposits

  • The payment status changes to Returned

  • The funds are never deposited to you

  • You are still billed the original ACH transaction fee and the return fee

If the payment is returned after it deposits

  • The payment stays in Succeeded status

  • The return amount plus the return fee are deducted from your next deposit

Because administrative returns usually arrive within 2–3 business days and standard ACH deposits on T+4, most returns land before the deposit.

📌 Note: ACH payments cannot be refunded within T+4 of processing. This is deliberate. It prevents you from refunding a payment that may still come back as a return. Attempting a refund inside that window returns the reason code IN_ACH_RETURN_WINDOW.


How fees are handled

Two fees apply to a returned ACH payment, and they stack.

Fee

Amount

Refunded on a return?

Original ACH transaction fee

1% + $0.30

No

ACH return fee

$20.00

Not applicable. This is the charge itself

The original processing fee is not returned to you when the payment fails. The work of submitting the transaction was already done, so that fee stands. The $20 return fee is then applied on top.

Worked example: a $45 ACH payment that returns

Event

Amount

Detail

Payment processed

$45.00

Transaction fee $0.75 → Net to merchant $44.25

Payment returned

–$45.00

Funds reversed

Return fee applied

–$20.00

Flat fee, shown as Net to merchant ($65.00) on the return record

Net effect on you

–$20.75

$20.00 return fee + $0.75 original transaction fee

You'll see both records in the Method Pay transaction list: the original payment marked Returned / Has ACH Return, and a linked ACH Return record showing the reason code and the return fee.

📌 Note: The return fee is flat. A returned $45 payment and a returned $45,000 payment both carry the same $20 fee, so on small-value ACH payments, a single return can cost close to half the transaction value.

For current fee details, see the Method Pay Payment Processing Agreement.

Accounting impact

Returns do not automatically create or amend accounting records in QuickBooks. The original Receive Payment record remains and the invoice balance is reduced, but the offsetting entries need to be applied manually.

Contact your Method Pay support contact for guidance on the entries.


Preventing returns with Validated ACH

Most ACH returns are avoidable, because most of them are caused by bad bank account data — not by customers who can't pay.

Validated ACH replaces manual entry of account and routing numbers with a real-time bank login. Your customer authenticates directly into their online banking through Plaid inside the payment component, and the account is confirmed as active and belonging to them before the payment is submitted.

How it works

  1. Your customer selects ACH and is prompted to connect their bank.

  2. They log in to their online banking through Plaid.

  3. The account is collected and validated in real time.

  4. The payment proceeds as a standard ACH payment.

What it prevents

Return code

Prevented by Validated ACH?

R02 - Account closed

✅ Yes

R03 - No account / unable to locate

✅ Yes

R04 - Invalid account number

✅ Yes

R13 - Invalid routing number

✅ Yes

R01 - Insufficient funds

⚠️ Only with the optional balance check

R07 / R10 - Authorization disputes

❌ No

Balance-Checked Validated ACH

An optional add-on performs a real-time balance check before the payment is submitted. If the account doesn't hold enough, the payment declines immediately instead of returning days later.

📌 Note: A balance check reduces insufficient-funds returns but does not eliminate them. Unlike a card authorization, ACH does not place a hold on the funds — the money can still leave the account before the transfer settles.

Why it's worth it for recurring and stored payments

When a customer pays by ACH, their bank details are saved and tokenized for future payments. That's convenient, but bank accounts change. Customers switch banks, close accounts, and open new ones, and there is no automatic updater service for bank accounts the way there is for cards.

Validating the account at the point of connection means the details on file are confirmed correct, and a validated payment method can be reused for recurring payments without paying a new validation fee each time.

The trade-off

Validated ACH carries an additional per-validation fee. Weighed against a $20 return fee plus the lost transaction fee, plus the time spent chasing the customer for corrected bank details and re-collecting the payment, it pays for itself quickly for most businesses, particularly those running recurring ACH or a high volume of low-value ACH payments.


Turning on Validated ACH

Validated ACH and Balance-Checked Validated ACH are not enabled by default. Both require platform-level enablement and carry billing fees.

To enable either, or to get current pricing, contact your Platform Success Manager or your Method Pay support contact.


Reducing returns without Validated ACH

If Validated ACH isn't enabled yet, these help:

Action

What it prevents

Confirm account and routing numbers verbally or in writing before the first payment

R03, R04, R13

Keep signed ACH authorizations on file and up to date

R07, R10

Re-confirm bank details with recurring ACH customers annually

R02, R12

Watch for repeat returns from the same customer and move them to card

R01

Reconcile your Method Pay transaction list regularly

Catches patterns before they compound

Did this answer your question?