The reasons for which an RDFI will initiate a Notification of Change are categorized by specific Change Codes. The examples given below for each code are not intended to exclude other situations in which a specific code might be used.

C01 Incorrect DFI Account Number
The Account Number structure is not valid. For example, the Originator uses the on-us field of a check or sharedraft to obtain the account number, but additional or fewer characters are needed to post the ACH entry. The account number could also be incorrect due to the transposition of characters, etc. The Correct Account Number appears in the first (left justified) 17 positions of the Corrected Data Field. For outbound cross-border entries, the correct Foreign Receiver's Account Number will appear in the first (left justified) 25 positions of the Corrected Data Field.

C02 Incorrect Routing Number
Due to merger or consolidation, a once-valid Routing Number must be changed. The Correct Routing Number (including Check Digit) appears in the first nine positions of the Corrected Data Field. For outbound cross-border entries, this field will refer to the Originating Gateway Operator's routing number.

C03 Incorrect Routing Number and Incorrect DFI Account Number
Due to merger or consolidation, a once-valid Routing Number and Account Number must be changed. This code could also be used when the Originator obtains both the Routing Number and the Account Number from the MICR encoding on a check or share draft, and both are invalid for ACH entries (payable- through information). The Correct Routing Number (including Check Digit) appears in the first nine positions of the Corrected Data Field. The Correct Account Number appears in the 13th through 29th positions of the same field with a space in the 10th, 11th, and 12th positions. This code should not be used for outbound cross-border entries due to field length limitations.

C04 Incorrect Individual Name/Receiving Company Name
The Individual Name field on the entry needs to be changed. The Correct Account Name appears in the first 22 positions of the Corrected Data Field.

C05 Incorrect Transaction Code
The entry is being directed to the wrong type of account. For example, a savings account transaction code is needed, but a demand account transaction code is being used, or vice versa. The Correct Transaction Code appears in the first two positions of the Corrected Data Field.

C06 Incorrect DFI Account Number and Incorrect Transaction Code
A once-valid Account Number and Transaction Code must both be changed; for example, an entry posting to a savings account should actually be going to a demand account or vice versa, and the account number is also incorrect. The correct Account Number appears in the first (left justified) 17 positions of the Corrected Data Field; the correct Transaction Code appears in the 21st and 22nd positions of the same field with spaces in the 18th, 19th, and 20th positions. For outbound cross-border entries, the correct Foreign Receiver's Account Number will appear in the first (left justified) 25 positions of the Corrected Data Field. The correct Transaction Code will appear in the 28th and 29th positions of the same field, with spaces in the 26th and 27th positions.

C07 Incorrect Routing Number, Incorrect DFI Account Number, and Incorrect Transaction Code
The Routing Number, Account Number, and Transaction Code are all incorrect and must be changed; for example, an entry posting to a savings account should actually be going to a demand account or vice versa, and the Routing Number and account number are also incorrect. The correct Routing Number (including Check Digit) appears in the first nine positions of the Corrected Data Field; the correct Account Number appears in the 10th through 26th positions of the same field; the correct Transaction Code appears in the 27th and 28th positions of the same field. This change code should not be used for outbound cross- border entries due to field length limitations.

C08 Incorrect Foreign Receiving DFI Identification
This Change Code is used to indicate an Incorrect Foreign Receiving DFI Identification for CBR and PBR entries. The correct Foreign Receiving DFI Identification appears in the first (left justified) 11 positions of the Corrected Data Field.

C09 Incorrect Individual Identification Number
 Individual's account number with the Originator is incorrect. The Correct Account Number appears in the first 22 positions of the Corrected Data Field.

C10 Incorrect Company Name
For example, due to a merger or consolidation, the Company Name carried on the file of the ODFI is no longer valid and should be changed. The Correct Company Name appears in the first 16 positions of the Corrected Data Field.

C11 Incorrect Company Identification
For example, due to merger or consolidation, the Company Identification Number on the file of the ODFI is no longer valid and should be changed. The Correct Company Identification appears in the first 10 positions of the Corrected Data Field.

C12 Incorrect Company Name and Company Identification
For example, due to merger or consolidation, the Company Name and Company Identification Number are no longer valid and should be changed. The Correct Company Name appears in the first 16 positions of the Corrected Data Field. The Correct Company Identification appears in the 20th through 29th positions of the same field with spaces in the 17th, 18th, and 19th positions.

C13 Addenda Format Error
Information in the Entry Detail Record was correct and the entry was able to be processed and posted by the RDFI. However, information found in the Addenda Record was unclear or was formatted incorrectly. Example: An entry is received with an "05" Addenda Type Code, but the addenda information does not contain ANSI ASC X12.4 data segments or a NACHA endorsed banking convention.

Refused: by the ODFI/Originator - In this case, the Notification of Change has been processed through the ACH system; however, the Originator or ODFI was not able to handle the NOC for a specific reason. The ODFI or Originator may use the Refused Notification of Change process to indicate why the NOC could not be handled.

Refused Notification of Change Codes

Refused Notification of Change codes designate the reason for refusal by the ODFI or Originator. They are listed below.

C61 Misrouted Notification of Change

C62 Incorrect Trace Number

C63 Incorrect Company Identification Number

*Source NACHA Operating Rules and Guidelines 2002