Retired ACH Notification of Change code
C04 NOC code (retired): Incorrect Individual Name/Receiving Company Name
C04 is a retired change code: RDFIs no longer send it. Removed from the Nacha Rules by the amendment "Removal of Change Code C04", effective March 20, 2015: an RDFI would have been warranting a name that might not match the Originator’s authorization.
What C04 meant
C04 was the change code Incorrect Individual Name/Receiving Company Name
. Like any NOC, it answered an entry that had posted and told the Originator what to correct before the next one.
- Until March 20, 2015 an RDFI could send C04 when the name in the entry didn’t match the account holder’s — after a name change or a misspelling — with the corrected name in the Corrected Data.
- Nacha removed it because the RDFI would have been vouching for a name that might not match the authorization the Originator holds. A name mismatch is no longer a NOC reason: the RDFI posts by account number, or returns an entry it can’t match to an account (R03).
If you see C04 today
Nothing to change because of a C04 today: no RDFI should send one. If an old file or a vendor’s code list shows it, treat it as history; to correct a Receiver’s name, ask the Receiver and update the authorization you hold.
The change codes in use today are C01, C02, C03, C05, C06, C07, C08, C09, C13, C14; a file or code table that still lists C04 predates its removal.
How C04 appeared in a NACHA file
A NOC is a zero-dollar entry in a batch with SEC code COR. Its entry detail record carries a return-type transaction code (21, 26, 31 or 36) and one addenda record of type 98:
| Positions | Field | In a C04 NOC |
|---|---|---|
| 1 | Record Type Code | 7 (addenda) |
| 2–3 | Addenda Type Code | 98 (Notification of Change) |
| 4–6 | Change Code | C04 |
| 7–21 | Original Entry Trace Number | Trace number of the entry being corrected |
| 22–27 | Reserved | Blank |
| 28–35 | Original Receiving DFI Identification | First 8 digits of the original entry’s RDFI routing number |
| 36–64 | Corrected Data | Correct name in positions 1–22 |
| 65–79 | Reserved | Blank |
| 80–94 | Trace Number | The NOC entry’s own trace number |
To read a NOC file record by record, open the file in NACHA Navigator, a free sister site that parses NACHA files in your browser without uploading them.
Look up C04 from code or an AI agent
curl -s 'https://payopskit.com/api/v1/codes/C04?set=ach-noc'{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "lookup_payment_code",
"arguments": {
"code": "C04",
"set": "ach-noc"
}
}
}{
"code": "C04",
"set": "ach-noc",
"found": true,
"matches": [
{
"set": "ach-noc",
"code": "C04",
"name": "Incorrect Individual Name/Receiving Company Name",
"description": "Retired Notification of Change code: RDFIs no longer send it. Removed from the Nacha Rules by the amendment \"Removal of Change Code C04\", effective March 20, 2015: an RDFI would have been warranting a name that might not match the Originator’s authorization. Corrected data was: Correct name in positions 1–22.",
"details": {
"refused": false,
"retired": true,
"correctedData": "Correct name in positions 1–22",
"timeframe": "The RDFI transmits the NOC within 2 banking days of the settlement date of the original entry; the Originator makes the change within 6 banking days of receiving the NOC information or before its next entry, whichever is later",
"timeframeKind": "banking-days",
"timeframeDays": 2,
"caveat": "Retired. Removed from the Nacha Rules by the amendment \"Removal of Change Code C04\", effective March 20, 2015: an RDFI would have been warranting a name that might not match the Originator’s authorization. An RDFI should not send it today."
}
}
]
}The MCP server is at /mcp (Streamable HTTP, no key); the API and MCP docs show how to connect Claude, Cursor or VS Code.
Source: Nacha Operating Rules, Appendix Five (Notification of Change). The code’s title is the Rules’ own; the rest is this site’s plain-language summary, informational and not a substitute for the Rules or your ODFI agreement.