An ACH Notification of Change is a message from a recipient’s bank telling you that something in the account details you used, usually the account number, routing number, or transaction type, needs to be corrected before you send the next payment. The payment itself still went through. The receiving bank posted the funds to the right account, flagged the mismatch, and sent the correction back to you through the ACH network. Under Nacha Operating Rules, you then have six banking days to update your records, or until you send the next payment to that recipient, whichever comes later.
How an NOC Differs From a Return
This is the distinction that trips up most people seeing their first NOC. An NOC means the payment was applied. The recipient got the money. The bank is simply asking you to clean up your file so future transactions carry the right details.
A return is the opposite. The transaction could not be applied, the funds come back to you, your bank charges a fee, and the recipient is left unpaid. NOCs themselves cost nothing. Ignoring them, though, is how NOCs turn into returns on the next payment cycle.
What the Change Codes Mean
Every NOC carries a change code that tells you exactly what to fix. Nacha assigns the codes. In practice, C01 through C07 cover almost everything a payroll or accounts payable team will see.
Account and Routing Codes
- C01: the account number is wrong or incorrectly formatted. The receiving bank identified the correct account and is giving you the right number to use.
- C02: the routing number has changed. This often follows a bank merger, rebrand, or routing infrastructure update.
- C03: both the routing number and account number need correcting. Common when a recipient has switched banks entirely.
Name and ID Codes
- C04: the individual or company name doesn’t match bank records. Banks aren’t required to verify names, so this one is relatively rare, but it shows up after legal name changes or corporate rebranding.
- C09: the individual identification number is incorrect, typically an employee ID or other internal identifier your organization attached to the transaction.
Transaction Type and Combined Codes
- C05: the transaction code is wrong. You sent the payment as checking when the account is actually savings, or the reverse.
- C06: both the account number and the transaction code need updating. A recipient may have closed a checking account and moved to savings at the same bank.
- C07: the routing number, account number, and transaction code all need changing. Essentially a full rebuild of the recipient’s banking details in your system.
Codes past C07 exist for international entries (the C6x series) and micro-entries, but most originators rarely encounter them.
Where the Corrected Data Lives
An NOC arrives as a structured record. The field you care about most is the Corrected Data field, which holds the first 29 characters of the addenda information and contains the actual values the receiving bank wants you to use going forward. You pull the replacement account number, routing number, or transaction code straight from that field and update your records. No phone call to the recipient required.
The record also includes the Original Entry Trace Number, a 15-digit identifier that pinpoints which transaction triggered the NOC (the last seven digits match the entry detail sequence number in your batch file), and the Original RDFI Identification, which is the routing number of the bank that flagged the discrepancy. Most modern payroll and payment platforms import these corrections automatically. Smaller operations on older systems may need to key them in by hand.
How Long You Have to Act
Nacha requires you to update your records within six banking days of receiving the NOC, or before the next payment to that recipient, whichever comes later. That last phrase matters. If you pay a vendor monthly and the NOC lands right after the last payment, you effectively have nearly a month to make the change. If you run weekly payroll, six banking days might fall right before your next run, and you need to move quickly.
The clock starts when the NOC reaches you, not when the receiving bank generates it. There’s usually a one- or two-day lag as it travels through the ACH Operator and your bank, so the real window from the original transaction to your deadline often runs eight or nine calendar days.
The Single-Entry Exception
If the payment that triggered the NOC was a one-time transaction and you have no plans to pay that recipient again, Nacha gives you discretion on whether to act on the correction at all. The exception applies regardless of payment type: payroll, vendor payment, consumer debit, or anything else.
Use the exception cautiously. If a payment you thought was one-time turns into a second transaction months later, running the stale data through will likely bounce back as a return. When there’s any chance of a repeat, make the update.
What Happens If You Ignore an NOC
The first consequence is predictable. The next payment you send with the uncorrected data gets returned. Your bank charges a fee for each returned ACH transaction, and your recipient doesn’t get paid on time.
Beyond per-transaction fees, repeated failure to act on NOCs can trigger Nacha’s enforcement process. Nacha classifies rules violations into tiers. For the most serious violations (Class 3), sanctions can reach up to $500,000 per occurrence, along with a directive to your bank to suspend you as an Originator entirely.1Nacha. ACH Network Rules – Reversals and Enforcement That outcome is reserved for egregious or systemic problems, but lower-tier actions still involve fines and compliance audits.
The practical fix is simple. Automate NOC processing if your platform supports it. If it doesn’t, have someone review NOC reports from your bank at least weekly and enter the corrections before the next payment run. The minute it takes to update a record costs far less than chasing a returned payment and explaining the delay.