ACH returns and notifications of change
How do we work ACH returns and notifications of change so the account is updated, the customer told and the originator notified inside the Nacha windows?
Treat each return and each notification of change as a case the rules classify. When the ACH file brings a return or a NOC, Callvu classifies it by reason code, applies the action the Nacha rules and the bank's policy set, updates the account or the standing instruction in the core, tells the customer where a notice is due, and sends the originator what the rules require, inside the window for that code.
In scopeSimpleCallvu moves: classify, write back
Last updated November 7, 2026.
The problem today
The return file is worked by hand, and the NOC that said the account number changed is applied three cycles late.
The morning ACH file carries returns (insufficient funds, account closed, unauthorized) and notifications of change (a corrected account number, a corrected routing number, a name). An operator reads each one, decides what to do, updates the core, and emails the originator or the customer. A NOC that is not applied within the rules' window produces the same return again next month, and a fee from the ODFI.
The Nacha Operating Rules set the reason codes, what each requires of the RDFI, and the windows: most returns within two banking days of settlement, consumer unauthorized returns within 60 days on a written statement, and NOC changes made by the originator within six banking days of receipt or before the next entry. The bank is both RDFI and, for its own originators, the party that must pass the NOC on.
Returns are also customer events: a returned preauthorized debit may be an overdraft, a closed-account return may be a customer who moved, and an unauthorized return is a dispute with its own clock.
How it runs
From the requestto the system of record.
A return or a notification of change arrives in the bank's incoming ACH file. Callvu picks it up with its reason code, the entry it relates to and the account.
- ACH operations
- Sees every item with its classification and action, and decides the cases the policy reserves in the Decision Desk.
- Customer
- Is told where a notice is due (a returned debit, a changed instruction) and confirms a change where the policy asks.
- Callvu
- Classifies by reason code, applies the action, updates the core, notifies the customer and the originator, and records.
Classify by reason code
The return code (R01 insufficient funds, R02 account closed, R03 no account, R10 unauthorized, R29 corporate not authorized, and the rest) or the change code (C01 account number, C02 routing number, C03 both, C05 transaction code, C06 and C07) sets the action, the window and who must be told.
Apply the action
A return is posted to the account with the fee the schedule discloses where one applies, and a returned preauthorized debit triggers the overdraft and notice rules. A NOC on an entry the bank originated is passed to the originating customer with the corrected data and the deadline; a NOC the bank receives as RDFI updates the record the rules require.
Notify and verify
The customer notice goes out where the rules or the policy require it, in the consented channel. A NOC that changes a standing instruction (a payroll or a bill payment) is confirmed with the customer where the policy asks before the next entry. An unauthorized return opens the dispute process with its clock.
Write back
The posting, the updated instruction, the notices and the originator communication are written to the core and the ACH system with the reason code and the window met, and the items the policy reserves (a repeated return, a high-value corporate return, a NOC on a critical payee) go to ACH operations in the Decision Desk.
Where it ends: Every return and NOC is applied inside its Nacha window, the account and the instructions in the core are right, the customer and the originator were told, and the reason codes and dates are on the record. The Decision Trace shows the code and the action; the Audit Trace shows every posting and notice.
Runtime enforcement
What is enforcedwhile the work runs.
The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.
The handoff
Between the front doorand the back office.
The front door
The incoming ACH file. The customer meets the process in a notice or a confirmation request.
The back office
ACH operations reviews only the reserved items; the core and the ACH system are updated by rule, and originators get NOCs on time.
The Decision Desk
- A repeated return, a high-value corporate return, or a NOC on a critical payee goes to ACH operations in the Decision Desk with the item and only the allowed outcomes.
Proof
In scope.Proof at scale, not one process at a time.
The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process. The results below are the industry's published proof; each claim code links to its record on agents.callvu.com.
Questions
What buyers ask next,answered plainly.
What does a NOC require?
The corrected data is passed to the originator within two banking days, and the originator must apply it within six banking days of receipt or before the next entry. Callvu tracks both.
What happens on an unauthorized return?
The return is filed inside the 60-day window on the consumer's written statement, and the dispute process opens with its Reg E clock.
Which items go to a person?
The ones the policy reserves: repeated returns, high-value corporate returns, and NOCs on critical payees.
Related processes
Bring this process, or the one that costs you most.
We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.