How Nacha's ACH Return Rules Reopen a Month Your Reconciliation Software Closed

An ACH return is a debit sent back by the receiving depository financial institution (RDFI) to the originating one (ODFI) with a reason code, often after the payment looked collected. For a lender collecting loan payments by ACH debit, that return can land weeks after the month was reconciled and closed.

Here's what usually happens. The payment posts to the loan, the bank deposit matches, and the month closes clean. Then an R10 arrives 40 days later, and three teams each fix a different piece of it.

We'll walk through the return windows in Nacha's rules, where reconciliation tools stop and the four numbers we'd compute every week. We'll also cover what a returned loan payment has to undo, and when returns need their own ledger.

This is an operations guide, not legal advice.

Nacha's ACH Return Rules Keep a Collected Payment Provisional for About 60 Days

Under the Nacha Operating Rules, most ACH return entries come back within two banking days. Unauthorized returns on consumer accounts can come back about 60 days after settlement. So every ACH debit a lender collects stays provisional long after the bank statement says it cleared.

We treat that window as the single fact that should shape the whole reconciliation process. Volume makes it matter because Nacha reported 9.3 billion ACH payments worth $25.9 trillion in the second quarter of 2026 alone.

• The Two-Banking-Day Returns

Insufficient funds (R01), closed accounts (R02), missing accounts (R03) and invalid account numbers (R04) are standard returns. Plaid's guide to ACH return codes lists a two-banking-day ACH return time frame for each. The same guide gives R29 a two-day window too.

Nacha uses R29 for CCD and CTX entries to business accounts. Those are the Standard Entry Class codes for corporate debits.

Among the Nacha ACH return codes, these usually land before month-end work starts, so they rarely reopen a closed period. The exception is a debit that settles on the last banking day of the month.

• The Extended Unauthorized Returns

Unauthorized returns on consumer accounts are the long tail.

Nacha's rule on differentiating unauthorized return reasons sets a 60-day return timeframe for R11, which covers a debit for the wrong amount or the wrong date. The same page says these errors get the same Regulation E error resolution as unauthorized transfers.

Nacha's reversals rule page gives the exact extended deadline. The return must be available by the opening of business on the banking day after the 60th calendar day following settlement. The receiving bank also needs the customer's Written Statement of Unauthorized Debit.

Return group	Example codes	Return timeframe	Can it reopen a closed month?
Funding	R01, R09	2 banking days	Only for debits settled at month-end
Account data	R02, R03, R04	2 banking days	Only for debits settled at month-end
Corporate unauthorized	R29	2 banking days	Rarely
Consumer unauthorized	R05, R07, R10, R11	About 60 calendar days	Yes, often by one or two months

Why Reconciliation Software Closes the Month Before an ACH Return Arrives

Most reconciliation software matches the bank against the ledger as of a date. It closes the month correctly for the information it has. An ACH return that arrives later is new information about an old month.

• What Bank Reconciliation Gets Right

Bank reconciliation does its core job well. The deposit matches the batch, the batch matches the loan payments, and the difference is zero. We wouldn't change that.

Payment platforms go further. Modern Treasury's documentation on returns explains that a payment order can show as completed and still move to returned later. It recommends tracking an available balance separately from a settled balance.

• Where the Returned Loan Payment Falls Through

The trouble starts after the match. The loan servicing system already applied the payment, the borrower's delinquency status already improved, and the month's reports already went out.

When the ACH return lands, the bank side books it in the current month. The loan side has to reverse a payment from a prior month. Unless someone builds the link, nothing ties those two entries together by the original trace number, and ACH reconciliation turns into detective work.

Tool	What it does well	Where it stops for ACH returns
Bank reconciliation in the general ledger	Matches deposits and batches to the bank statement as of a date	Books the return in the month it arrives, not the month it came from
Payment platform (Modern Treasury)	Moves completed payments to returned and sends return webhooks with the code	Leaves the loan-level reversal and reporting policy to the lender
Bank ACH portal	Delivers return files and reason codes	Knows the bank's side of the entry, not the loan it paid
Loan servicing system	Applies and reverses payments on the loan	Return-rate and lag reporting by settlement month varies by vendor, so we'd check before assuming

Four Numbers We'd Compute From Your Own ACH Return Files Every Week

We'd compute four numbers every week from the ACH origination files and return files a lender already receives. Three are the ACH return rate measures in the Nacha Operating Rules. The fourth shows how long each month stays open.

Say you service about 20,000 ACH loan payments a month, so roughly 40,000 debits fall in any 60-day window. This hypothetical example shows how each number reads.

1. Unauthorized Return Rate

This is debit returns coded R05, R07, R10, R11, R29 or R51 divided by debit entries, over the preceding 60 days or two calendar months. Nacha's ACH Network Risk and Enforcement Topics set the threshold at 0.5%, and the R11 rule added R11 to the same rate.

Nacha allows two denominators, either the debits in the original files that produced the returns, or all debits originated in the same period. We pick one and never switch, so the trend stays honest.

In our hypothetical book, 150 unauthorized returns against 40,000 debits is 0.375%. That is under the threshold, but only 50 returns away from it. If it keeps climbing, the authorization and monitoring controls in our Nacha fraud monitoring guide are where we'd look next.

2. Administrative Return Rate

This is debit returns coded R02, R03 or R04 divided by debit entries over the same window. Nacha sets a return rate level of 3.0% here, and exceeding it can start a preliminary inquiry rather than an automatic violation.

At 400 administrative returns, our hypothetical rate is 1.0%. Modern Treasury notes that some bank partners set this limit anywhere from 1.0% to 3.0%, so we'd ask the bank for its own number.

3. Overall Return Rate

This is all debit returns, excluding RCK (re-presented check) entries, divided by debit entries over the window. Nacha's return rate level is 15.0%.

At 1,800 total returns, our hypothetical rate is 4.5%. Most of that is usually insufficient funds, which is a collections signal more than a compliance one.

4. Return Lag by Original Settlement Month

This is the share of one month's settled debits that came back, measured at day 2, day 10, day 30 and day 60 after settlement. It is the number most lenders never compute, and it is the one that tells finance how long a month stays open.

In our example, March settles 20,000 debits. By day 10, 850 are back. By day 60, another 50 have arrived, mostly R10 and R11. Those 50 returns are the ones that reopen March.

Number	Return codes	Nacha level	Window	What a bad reading means
Unauthorized return rate	R05, R07, R10, R11, R29, R51	0.5% threshold	60 days or two calendar months	Authorization or fraud controls are weak
Administrative return rate	R02, R03, R04	3.0% level	60 days or two calendar months	Account data at onboarding is bad
Overall return rate	All debit returns except RCK	15.0% level	60 days or two calendar months	Funding and collections risk is rising
Return lag by settlement month	All	None	Day 2 to day 60	Month-end numbers will move after close

Pro tip: Store the original trace number and settlement date on every return record. Without both, none of these four numbers can be computed by settlement month.

What a Returned Loan Payment Has to Undo in Your Servicing Records

A returned loan payment has to undo four things, in order, and each one belongs to a different owner. When an ACH return arrives, we'd work through them against the original payment, not as a new negative payment.

These steps assume a servicing system that keeps a full payment history, which we cover in what a loan servicing system actually has to do.

1. Reverse the Payment Application

Reverse the original payment on the loan, including the split between principal, interest and escrow. The reversal should reference the original trace number, so the loan history shows one payment and one return.

2. Reassess Fees and Delinquency Status

Recompute the borrower's due status and any late fee as of the original due date. Which fees apply depends on the note and applicable law, so we'd have compliance own the fee rules and the system apply them.

3. Decide on Reinitiation Under Nacha's Rules

Nacha's risk and enforcement rule requires a reinitiated entry to keep the same Company Name, Company ID and Amount, with "RETRY PYMT" in the Company Entry Description. An entry returned as unauthorized cannot be reinitiated without a new authorization obtained after the return.

Plaid's guide summarizes the limit on re-presenting R01 and R09 returns as two attempts after the original return. For R11, Nacha lets the originator correct the error and send a new entry within 60 days of the return's settlement date.

4. Adjust Anything Already Remitted

If the servicer already remitted the payment to an investor or a trust, the return creates a receivable or an advance. We'd record it the same day, because it is the entry most often missed at the next remittance.

Pro tip: Route R10 and R11 to different queues. R10 means no authorization, while R11 means an authorized payment went out wrong, and Nacha lets you correct an R11 without new authorization.

How to Keep Month-End Accurate Without Reopening Every Close

We keep month-end accurate by closing cash on schedule and reporting ACH return activity against the original settlement month in a separate view. The close stays on time, and nobody pretends a month is final when it isn't.

• Close Cash, Not Collections

Close the bank reconciliation as usual. Report collections for the last 60 days as provisional, with an expected return amount based on the return lag number from your own history.

• Report Returns Against the Month They Came From

Keep a monthly schedule that restates each prior month's net collections as returns arrive. Finance sees the cash month. Operations and investors see what each month actually collected once its window closed.

View	Books the ACH return in	Who uses it	Final after
Cash view	The month the return arrives	Accounting close	The close date
Settlement month view	The month the debit settled	Operations, credit, investors	About 60 days after month-end

When a Spreadsheet Works and When ACH Returns Need Their Own Ledger

A spreadsheet is enough for ACH returns when volume is low and one bank handles all origination. A dedicated returns ledger pays off once volume, banks or loan products multiply and the four numbers take hours to rebuild.

• Stay on a Spreadsheet

A few thousand debits a month through one bank is spreadsheet territory in our view. Export the origination and return files, join on trace number and compute the four numbers weekly.

• Use Your Payment Platform's Return Data

If a payment platform already originates the debits, start with its return records and webhooks. It gives the code, the trace and the original payment, which covers most of the join.

• Build a Returns Ledger

When several banks, several products or investor remittances are involved, we'd build a small returns ledger. It links each return to its original debit, loan, settlement month and remittance, and it drives the reversal workflow.

It sits beside the servicing system and the general ledger rather than replacing either. Our engineers have worked embedded inside the team at Valon on a mortgage servicing platform.

Situation	Our default	Why
One bank, a few thousand debits a month	Spreadsheet	The join on trace number takes minutes
Debits originate through a payment platform	Platform return data plus a monthly report	Most fields already exist
Several banks, products or investor remittances	Returns ledger	Only a linked record answers all four numbers
Unauthorized rate trending toward 0.5%	Fix authorization first	A ledger measures the problem, it doesn't cure it

Run Last Month's ACH Returns Against the Month They Came From

This week we'd pull every ACH return from the last 90 days and tag each one with its original settlement month. That single column shows how long your months really stay open.

Then compute the three Nacha rates with one fixed denominator and the lag curve for each month. Your reconciliation software will keep closing cash correctly.

What it needs beside it is a record that ties each return to its loan and its month. That is the kind of layer Better Software builds with operators who own the process.

Frequently Asked Questions

Are Nacha rules mandatory?

For banks and businesses that use the ACH Network, yes. Wikipedia's ACH Network entry notes that participants are bound by Nacha's rules. Businesses originate debits through a bank, so we read that bank agreement closely, because it sets how every ACH return and fee reaches you.

Who pays for returned ACH charges?

Usually the originator. Plaid's guide puts typical processor fees at $2 to $5 per ACH return, and Nacha's Unauthorized Entry Fee also applies to unauthorized returns. We ask our bank for its fee schedule, because it decides which of those costs reach us.

What is the difference between an ACH return and an ACH reversal?

An ACH return is sent by the receiving bank. A reversal is sent by the originator to correct its own error, such as a duplicate, wrong amount or wrong date. We rely on Nacha's reversals rule, which requires a reversal to reach the receiving bank within five banking days of settlement.

Why does an ACH take 2 to 3 days?

Standard ACH settles next day, and the receiving bank then has a short window to send an ACH return, per Wikipedia's ACH Network entry. Same Day ACH speeds settlement, and Nacha says its dollar limit rises to $10 million in 2027. We still wait for the return window.

What is the difference between ACH and Nacha?

ACH is the network that moves the payments. Nacha is the nonprofit that writes its rules, while the Federal Reserve's FedACH and The Clearing House's EPN operate it, per Wikipedia. We deal with Nacha through our bank, which handles every ACH return and rule change first.