NOC — ACH Notification of Change codes
A Notification of Change (NOC) is how a US bank says "I posted your ACH payment, but your data is wrong — fix it for next time". It is not a rejection: the money moved. The zero-dollar COR entry carries a change code (C01 for a wrong account number, C02 for a wrong routing number…) together with the corrected value, and the Originator must apply it within six banking days or before the next entry to that account, whichever comes later.
NOC (ACH Notification of Change codes)
A Notification of Change (NOC) is how a US bank says "I posted your ACH payment, but your data is wrong — fix it for next time". It is not a rejection: the money moved. The zero-dollar COR entry carries a change code (C01 for a wrong account number, C02 for a wrong routing number…) together with the corrected value, and the Originator must apply it within six banking days or before the next entry to that account, whichever comes later.
Overview
A Notification of Change (NOC) is how a US bank says "I posted your ACH payment, but your data is wrong — fix it for next time". It is not a rejection: the money moved. The zero-dollar COR entry carries a change code (C01 for a wrong account number, C02 for a wrong routing number…) together with the corrected value, and the Originator must apply it within six banking days or before the next entry to that account, whichever comes later.
When it is used
Look a code up here when your bank sends back a NOC or COR file and you must know which field to correct in your payroll or billing system. Re-sending the payment after a NOC is the classic mistake — it would pay twice. The C61-C69 family is the reverse direction: your bank refusing a NOC it cannot act on.
The Nacha Operating Rules book is copyrighted and sold, and was not purchased. Every code here was checked against official sources that are free: the appendixes Nacha publishes itself, the US Treasury Green Book and the Federal Register. This is why the list has 19 codes and not the 22-odd you will find elsewhere: C04 was removed from the Rules in 2015, and C10, C11 and C12 — widely published by processors and bank PDFs — do not exist in the Rules at all (the table goes straight from C09 to C13; the likely confusion is with C63 below).
Download JSONChange codes — sent by the receiving bank (RDFI) (10)
| Code | Meaning |
|---|---|
| C01 | Incorrect DFI Account NumberThe account number is wrong or malformed. Correct the DFI Account Number held for this Receiver before the next entry — the payment itself went through. |
| C02 | Incorrect Routing NumberA once-valid routing number must change, typically after a bank merger or consolidation. Correct the Receiving DFI Identification and its check digit. |
| C03 | Incorrect Routing Number and Incorrect DFI Account NumberBoth the routing number and the account number must change — the usual outcome of a bank merger. Correct both fields together. |
| C05 | Incorrect Transaction CodeThe entry is being sent to the wrong type of account: it is coded checking when the account is savings, or the reverse. Correct the Transaction Code (2x = checking, 3x = savings). |
| C06 | Incorrect DFI Account Number and Incorrect Transaction CodeBoth the account number and the account type are wrong. Correct the DFI Account Number and the Transaction Code. |
| C07 | Incorrect Routing Number, Incorrect DFI Account Number, and Incorrect Transaction CodeAll three routing details are wrong. Correct the routing number, the account number and the transaction code. |
| C08 | Incorrect Receiving DFI Identification (IAT only)Applies to international (IAT) entries only: the receiving institution identifier is wrong. Correct the Receiving DFI Identification carried by the IAT entry. |
| C09 | Incorrect Individual Identification Number/Incorrect Receiver Identification NumberThe identifier the Originator uses for this Receiver (customer or member number) is wrong or has changed. Correct the Individual Identification Number. |
| C13 | Addenda Format ErrorThe entry itself was fine and was posted, but the addenda record was unusable — wrongly formatted or unclear. No corrected value is returned: reformat the addenda on your side. |
| C14 | Incorrect SEC Code for Outbound International PaymentSent by a Gateway, not by an RDFI: the payment leaves the United States and must therefore be classified IAT. Change the batch Standard Entry Class code to IAT for future entries. |
Refused NOC — sent back by the originating bank (ODFI) (9)
| Code | Meaning |
|---|---|
| C61 | Misrouted Notification of ChangeThe NOC reached the wrong ODFI. |
| C62 | Incorrect Trace NumberThe trace number in the NOC does not identify a real original entry. |
| C63 | Incorrect Company Identification NumberThe company identification in the NOC does not match the original entry. Note this is a REFUSAL of a NOC — not a change code asking to fix a company ID. |
| C64 | Incorrect Individual Identification Number/Identification NumberThe individual identification number in the NOC does not match the original entry. |
| C65 | Incorrectly Formatted Corrected DataThe corrected value the RDFI supplied is not formatted as the change code requires, so it cannot be applied. |
| C66 | Incorrect Discretionary DataThe discretionary data in the NOC does not match the original entry. |
| C67 | Routing Number Not from Original Entry Detail RecordThe routing number quoted by the NOC is not the one carried by the original entry. |
| C68 | DFI Account Number Not From Original Entry Detail RecordThe account number quoted by the NOC is not the one carried by the original entry. |
| C69 | Incorrect Transaction CodeThe transaction code quoted by the NOC is not the one carried by the original entry. |