The return file lands mid-morning, and one line changes the entire close. A church that showed a cleared loan payment yesterday now sits $14,750 short, the general ledger cash balance is overstated, and the investor distribution scheduled for the 15th still has to go out. Nobody stole anything. The money didn't arrive, and your bank has a three-character code explaining why.
Most funds treat that moment as a receivables chore. It isn't. A returned ACH payment is a measurable network event with a hard deadline attached, and the code on the return determines what you're allowed to do next. Treat every one as insufficient funds and you'll retry accounts that must not be retried, miss windows that close in two banking days, and erode the authorization file your compliance position rests on.
What follows is the working playbook: what each code means, how long you have, which ratio Nacha watches, and how to book the reversal so your auditors nod instead of asking questions.
What a Returned ACH Payment Is and Why It Matters
A returned ACH payment is an entry your bank originated that the receiving bank sends back through the network with a standardized Nacha reason code. It isn't a reversal you initiated, and it isn't a reject the operator catches before settlement.

Say your fund drafts $14,750 against a church construction loan on the 5th. The batch settles, the treasurer's report shows the payment received, and you move on. On the morning of the 7th, the bank's return file shows that entry coming back with R01. Cash is overstated by the exact amount you believed you had, the loan balance needs the payment put back, and nobody at the church has called you yet.
The path that produced it runs through four parties. Your bank, the originating depository financial institution (ODFI), submitted the debit. The ACH operator routed it to the church's bank, the receiving depository financial institution (RDFI), which could post it or send it back. It sent it back, tagged with a reason code that tells you what happened and how long the window stayed open.
The ledger effects nobody enjoys
Four moves follow from one returned entry, and skipping any of them creates a reconciliation break you'll chase for a month:
- Reinstate the receivable. Put the loan or note balance back exactly where it was before settlement, not netted against a fee.
- Reverse the cash entry. Take the debit off the bank account in the period it settled, with a traceable reference to the return.
- Keep interest accruing. A returned payment doesn't stop the borrower's interest clock unless your note terms say otherwise.
- Carry the investor obligation. The distribution you promised still comes due whether or not the church paid.
Volume explains why this deserves a process rather than a hero. Federal Reserve statistics show ACH volume rising from about 23.9 billion payments in 2015 to 52.42 billion in 2024 (Federal Reserve ACH top-line data). Multiply any plausible return rate across numbers that size and the absolute exception count is large. For a CEF, return handling is a financial-control function, not a back-office nuisance.
ACH Return Codes and What to Do First
Nacha assigns every return a three-digit reason code, and the payer's bank chooses it. That code, not the dollar amount, decides what you may do next. Read the table in two passes: first the meaning and the deadline, then the action you take before you leave the office today.
| Code | What it means | Typical cause at a CEF | Return deadline | First action |
|---|---|---|---|---|
| R01 | Insufficient funds | Loan draft hits before the church's weekly offerings clear | 2 banking days after settlement | Contact the payer, then retry on a verified date |
| R02 | Account closed | Church or investor switched banks without telling you | 2nd banking day by opening of business | Stop retries and get replacement account details |
| R03 | No account or unable to locate | Typo in the account number or a closed-and-reopened account | 2nd banking day by opening of business | Re-verify details with the payer before any re-debit |
| R04 | Invalid account number structure | Transposed digits or wrong account type captured at onboarding | 2nd banking day by opening of business | Correct the number and run a verification entry |
| R05 | Unauthorized debit to a consumer account filed with a corporate SEC code | Loan drafted from a personal account under a company-entry code | 60 calendar days with a Written Statement of Unauthorized Debit | Suspend retries and review the authorization file |
| R07 | Authorization revoked by the customer | Payer cancelled the recurring draft with their bank | 60 calendar days with a WSUD | Stop future debits and obtain a fresh authorization |
| R08 | Payment stopped by the receiver | Payer flagged the debit as disputed at their bank | 2 banking days | Call the payer to learn why before re-attempting |
| R09 | Uncollected funds | Business account had the balance but it was not yet collected | 2 banking days | Retry after confirming cleared funds |
| R10 | Customer advises the originator is unknown or not authorized | Borrower or investor does not recognize the debit | 60 calendar days with a WSUD | Halt debits immediately and escalate to compliance |
| R11 | Entry not in accordance with the authorization | Amount or date differs from the signed mandate | 60 calendar days with a WSUD | Compare the entry to the authorization and correct the setup |
| R16 | Account frozen | Payer's account restricted by their bank or a legal hold | 2 banking days | Hold retries and await the payer's resolution |
| R20 | Non-transaction account | Debit drawn on a savings or restricted-purpose account | 2nd banking day by opening of business | Collect a transaction-capable account number |
| R23 | Credit entry refused by the receiver | Investor's bank rejects a distribution credit | 2 banking days | Contact the investor and correct the credit details |
| R24 | Improper duplicate entry | Same debit sent twice in one processing cycle | 2 banking days | Confirm the duplicate and cancel the second entry |
| R29 | Corporate customer advises not authorized | Business account holder disputes the debit | 2 banking days | Review the corporate authorization and escalate |
| R51 | Improper or ineligible item | Check-conversion entry lacks required notice or source document | Set by Nacha's check-conversion rules; confirm before re-presenting | Review the source document and notice file before any re-presentment |
Three families worth memorizing
Sort the codes and the table collapses into four decisions. Cash-availability returns (R01, R09) usually resolve with better timing, not with paperwork. Account-and-data returns (R02, R03, R04, R16, R20) mean the details are wrong, so no re-debit happens until the record is corrected. Authorization returns (R05, R07, R10, R11, R29) mean the mandate itself is in question, and everything stops until you hold the signed document. The operational codes (R08, R23, R24) are one-off events you fix by phone.
Five codes carry weight beyond the individual payment. Nacha's unauthorized-return calculation draws on R05, R07, R10, R29 and R51, so each one you record is also a data point in a ratio your ODFI reports.
Two patterns show up in CEF portfolios more than any other. R01 on drafts dated the 5th or 10th happens when the debit hits before Sunday offerings and monthly tithe remittances clear. R02 and R03 cluster after a church refinances its building loan at another bank and forgets to tell you the old account closed.
One more distinction saves grief. When the error was yours, not the payer's, the ACH reversal rules govern a different process with a much narrower window. Confusing a reversal with a return is how funds create disputes they cannot win.
Return-Rate Thresholds and What Crossing Them Triggers
A fund can show the board a tolerable stack of bounced drafts and still be the originator Nacha wants to talk to. The ratio uses a denominator you control: originated debit entries for the relevant population and period. Three rates sit on that volume, and they do not trigger the same response.
| Measure | Threshold | What it counts | If the rate is exceeded |
|---|---|---|---|
| Unauthorized debit return rate | 0.5% (Nacha unauthorized return rate guidance) | R05, R07, R10, R29 and R51 debits returned over the trailing 60 days or two calendar months, divided by originated debit volume | Escalate the same day. Suspend further debits on that file. Nacha oversight and corrective action can follow. |
| Administrative return rate | A separate ceiling, well above the unauthorized limit | Returns for account or data errors such as R02, R03 and R04 | Correct the record. Do not retry until validation, onboarding capture and payer notice are fixed. |
| Overall debit return rate | The widest of the three | All debit returns for any reason, excluding check-conversion (RCK) entries | Retry only after timing, underwriting or payer cash-flow fit changes. A same-day re-debit just feeds the rate. |
The tight rate is the one that ends the argument
You can stay inside a workable overall return rate and still breach the unauthorized limit. One defective authorization file throws off a cluster of R10s. The all-in total never flags them. Nacha treats these thresholds as network-quality and compliance controls, not as a collections report. A rate above the unauthorized level can bring oversight and a corrective-action plan.
Read the code, then pick the control. Do not run one wait-and-retry rule across the file.
R05, R07, R10, R29 and R51 are the numerator of the unauthorized rate for that trailing 60 days or two calendar months. Decision: suspend and escalate to compliance the day the return posts. Do not re-present. Each of those returns stays in the ratio your ODFI reports until it ages out of the window.
R02, R03 and R04 load the administrative rate. Decision: correct. No new debit against that account until the account number, name and status match what the bank will accept. Another attempt on the bad record is another administrative return.
R01 and R09 load the overall debit rate. Decision: retry only after the draft date matches when the congregation's cash is in the account, or after underwriting says the payment fits. Drafting early, then re-drafting on the same cycle, is how a cash-timing miss becomes a rate breach.
Alarm before the unauthorized limit, not at it
Each month, compute all three rates and split them by originator, SEC code, account type and settlement period. Set the internal alert under the unauthorized limit so the board sees the climb while you can still suspend, correct or stop a retry. A fund that first learns its unauthorized rate at that limit has already handed the trailing window to its ODFI.
The board question to ask every quarter: what is our unauthorized return rate for the trailing 60 days, which originators drive it, and what did we suspend, correct or stop retrying?
How to Respond When a Payment Comes Back
Speed matters less than sequence. The return window depends on the reason and the account type, and getting the order wrong is how funds miss a deadline they had 60 days to meet. Standard administrative returns such as R02, R03 and R04 generally must be made available to your ODFI by the opening of business on the second banking day after settlement. Unauthorized consumer claims, including R07, R10 and R11, can generally be returned within 60 calendar days of settlement and require a Written Statement of Unauthorized Debit (WSUD) (Nacha reversals and enforcement rules).
Seven steps, in this order:
- Log the return the same day. Capture the reason code, settlement date, trace number, amount, SEC code and payer identity in one exception log with a named owner. A return that exists only in an email thread is not audit evidence.
- Post the reversal properly. Reinstate the loan receivable or note balance, reverse the cash entry against the original settlement, and leave a visible trail. Never net a return against a fee or a later payment to make the account look current.
- Classify the code. Assign it to its family, because the family sets the move: timing, data correction, authorization review, or a one-off operational fix.
- Apply the table's first action. No re-debit of an account with bad data, and no debit at all on an authorization return until the signed mandate is in front of you.
- Respect re-presentment limits. An R01 or R09 item can be reinitiated no more than two times within 180 days. An unauthorized debit cannot be re-presented at all until authorization is re-verified, and automatic retry logic that ignores this will manufacture a second violation out of the first one.
- Call the payer and write down what you heard. Document the conversation, confirm the replacement date, and apply late fees or waivers consistently under the note agreement. A waiver granted to one church and charged to another is a board-level fairness problem, not a clerical one.
- Schedule the replacement and track it through settlement. The case stays open until the funds post, not until the promise is made.
When the return itself looks wrong
Store settlement date, SEC code, return code, receipt timestamp, WSUD status and a banking-day calendar in a deadline queue that flags each case at defined checkpoints. If a reason code appears incorrect, or the amount doesn't match your record, raise it with your ODFI before the window closes. A return you challenge late is a loss you booked voluntarily.
The follow-up discipline around all of this matters as much as the code handling. Teams that keep collections moving use firm past-due follow-up messages stating the amount, the new date and the consequence in plain language, and a CEF should hold the same standard with a borrower church: specific, dated, documented.
What Returns Look Like in Practice
Three scenarios cover most of what a fund handles.
The timing return, resolved cleanly. The $14,750 construction draft settles on the 5th and returns R01 on the 7th because the church's pledge receipts don't settle until the 8th. Treasury calls the church treasurer that morning, reinstates the receivable the same day, and confirms the retry for the 14th. The note carries a $75 late fee, which the fund waives once under the agreement's grace terms and documents in the relationship file. The lesson: an R01 is a cash-flow conversation, and handled early it costs nothing but a phone call.
The authorization failure nobody saw coming. A $25,000 investor purchase debit returns R10 thirty-eight days after settlement. That triggers the WSUD process, and pulling the authorization file reveals the mandate was never signed after an online onboarding change six months earlier. Compliance suspends all debits to that account, obtains a fresh signed authorization, and adds a signature-confirmation step to onboarding. The lesson: the 60-day window works against you as easily as for you, because a defect from last quarter surfaces today.
The return request that outlives the return window
The hardest case isn't the failed payment. It's the request that arrives months after a $9,200 entry settled, when your originating bank asks the payer's bank to return it. Under a Nacha rule change effective April 1, 2025, the receiving institution must advise the status of a return request within 10 banking days (Nacha rule and operations updates). The request may be accepted, rejected, or still under review, and no money yet does not mean the request failed.
Practical rule: a missing deposit is not a failed request. Track the request's age against the 10-banking-day response date before you tell the board anything.
Track that request the way you track a receivable: open date, response due date, exposure amount, owner and status. When the funds arrive, reconcile them against the original receivable, the general ledger, the borrower's balance and any replacement payment already collected, so you don't double-count. And understand the limit of your authority. Resolution is partly a bank-to-bank workflow, so you cannot unilaterally reverse an entry once the ordinary deadlines have passed. Assign ownership across treasury, loan servicing, compliance and the bank relationship, and keep the authorization plus all correspondence on file.
Reducing Returns Before They Happen
Prevention is cheaper than exception handling, and most of it happens before the first debit. Adopt this checklist this month, whatever system you run.
- Verify every new account before the first debit. Use a prenote or micro-entry. The rules are specific and they apply to small test amounts: an unauthorized micro-entry debit on a consumer account can return as R10 within 60 days when accompanied by a Written Statement of Unauthorized Debit; an unauthorized debit on a non-consumer account can return as R29 within two banking days; and an unauthorized micro-entry credit can return as R23 (Nacha micro-entry rules). A one-cent verification transaction waives no authorization discipline.
- Keep an authorization file that matches reality. Each mandate should carry its SEC code, amount range, frequency and start date, re-papered whenever terms change, including when a church changes banks. If the file can't answer "what did they authorize, on what account, starting when," it isn't a file.
- Time recurring debits to church cash flow. Draft after the pledge Sundays and monthly tithe remittances settle, not the business day before. Moving a recurring debit date by three days is a legitimate operational fix, not a concession.
- Reconcile returns to the subledger daily. Borrower and investor balances should never carry a stale payment overnight. Pair that habit with a disciplined ACH cash management routine so cash position, returns and forecasts update from one source.
- Review the exception log at month end. Put the three return-rate trends in front of the board or audit committee alongside the delinquency report. Repeat codes are the signal; single events are noise.

Build a Return Routine That Survives an Audit
An auditor asks who posted the reversal, who called the church, and who approved the retry. If those answers live in someone's inbox, the routine will not survive the visit. Name one owner per step, in writing.
Treasury owns cash posting and reversals. Loan servicing owns payer contact, retries, and replacement schedules. Compliance owns authorization files and every WSUD case. The controller owns ledger tie-out, the rate calculations, and board reporting. The bank relationship belongs to whoever can escalate a disputed return before the deadline lapses.
Do four things this week. Pull recent returns and compute the return rates. Adopt the code-to-action table as standing operating procedure, printed and posted where servicing works. Open a deadline queue on a banking-day calendar so a holiday cannot shorten the week without someone noticing. Then extend the audit discipline you already apply elsewhere. Use these key trust account audit checks as a model for evidence retention, and design the close around a documented bank reconciliation process.
Tooling deserves a straight answer. A disciplined spreadsheet handles low volume. When loan drafts, investor notes, the general ledger, and cash must stay tied every day, manual re-keying is the risk. CEFCore is one option to weigh. Its Cash & ACH module generates ACH/NACHA files for upload to the bank and tracks real-time cash position across all accounts. Transactions above configurable thresholds require approval from a second authorized user before execution. Cash management keeps forecasting, daily position reports, transaction history, and audit trails together. Fee handling covers waivers and exceptions, and subledger reconciliation supports the monthly close. Judge any system by whether it stores the fields your response procedure needs and produces a trail auditors can follow without a meeting.
Visit CEFCore to see how cash and ACH operations, fee waivers, and subledger reconciliation fit your fund.
Fewer returned payments means steadier funding for church building loans and more predictable distributions to the investors who make that lending possible. That is the mission case. It is the same case as good controls.
