Skip to content
PayOps Kit
Donate

ACH Notification of Change code

C14 NOC code: Incorrect SEC Code for Outbound International Payment

An RDFI sends C14 instead of returning an entry it could post but that carried outdated or wrong information. Corrected data: "IAT" in positions 1–3.

What C14 means

C14 is the change code Incorrect SEC Code for Outbound International Payment. The entry it answers was posted (or, for a prenotification, accepted); the NOC tells the Originator what to correct before the next one.

  • A payment that is part of an outbound international transfer was sent with a domestic SEC code instead of IAT.

What to update, and by when

Send future payments to this Receiver as IAT entries, with the IAT addenda records.

The Rules give the Originator six banking days from receiving the NOC information, or until its next entry to the account, whichever is later. NOCs carry no money: the entry they answer settled normally.

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.

Worked example

For an entry that settled on Wednesday, November 25, 2026, the day before Thanksgiving: the RDFI must transmit the NOC by Monday, November 30, 2026.

Try your own settlement date in the ACH date calculator

How C14 appears 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:

Notification of Change addenda record (type 98) with C14
PositionsFieldIn a C14 NOC
1Record Type Code7 (addenda)
2–3Addenda Type Code98 (Notification of Change)
4–6Change CodeC14
7–21Original Entry Trace NumberTrace number of the entry being corrected
22–27ReservedBlank
28–35Original Receiving DFI IdentificationFirst 8 digits of the original entry’s RDFI routing number
36–64Corrected Data"IAT" in positions 1–3
65–79ReservedBlank
80–94Trace NumberThe 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 C14 from code or an AI agent

REST · GET · no key
curl -s 'https://payopskit.com/api/v1/codes/C14?set=ach-noc'
MCP · tools/call · lookup_payment_code
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "lookup_payment_code",
    "arguments": {
      "code": "C14",
      "set": "ach-noc"
    }
  }
}
Response (JSON)
{
  "code": "C14",
  "set": "ach-noc",
  "found": true,
  "matches": [
    {
      "set": "ach-noc",
      "code": "C14",
      "name": "Incorrect SEC Code for Outbound International Payment",
      "description": "Notification of Change. Corrected data: \"IAT\" in positions 1–3.",
      "details": {
        "refused": false,
        "retired": false,
        "correctedData": "\"IAT\" in positions 1–3",
        "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": null
      }
    }
  ]
}

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.