ACH — a notification of change (C01, corrected account number)
A notification of change — and the thing to understand is that it is NOT a rejection. The payment went through. The receiving bank is asking for the stored data to be corrected before the NEXT payment: re-sending this one would pay the receiver twice. That is why the entry carries an amount of ZERO, and why the batch SEC code is COR. The addenda 98 carries C01 with the corrected account number in positions 36-52 of the record.
Nacha 94-character — Valid
A notification of change — and the thing to understand is that it is NOT a rejection. The payment went through. The receiving bank is asking for the stored data to be corrected before the NEXT payment: re-sending this one would pay the receiver twice. That is why the entry carries an amount of ZERO, and why the batch SEC code is COR. The addenda 98 carries C01 with the corrected account number in positions 36-52 of the record.
What this file shows
A notification of change — and the thing to understand is that it is NOT a rejection. The payment went through. The receiving bank is asking for the stored data to be corrected before the NEXT payment: re-sending this one would pay the receiver twice. That is why the entry carries an amount of ZERO, and why the batch SEC code is COR. The addenda 98 carries C01 with the corrected account number in positions 36-52 of the record.
| Transactions | 1 |
|---|---|
| Total | $0.00 |
| Date in the file | 2026-07-12 |
Every party, IBAN and amount below is fictitious. The IBANs are structurally valid — they pass the mod-97 check — but they belong to no real account.
File content
101 091000019 0910000192607121200A094101RECEIVING BANK ORIGIN BANK
5220YOUR COMPANY, IN 121042882 CORVENDOR PAY 260712 1091000010000001
6212313801044744-5678-99 0000000000LOCATION #23 BEST CO. #23 S 1121042880000001
798C01121042880000001 121042889876543210 091012980000088
82200000020023138010000000000000000000000000 091000010000001
9000001000001000000020023138010000000000000000000000000
9999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999
9999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999
9999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999
9999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999
How we know these results hold
Every file in this library is run through the site's own validator on each build. The expected result stated above is asserted by an automated test — if a file stopped matching what this page claims, the build would fail. Two inherited fixtures were repaired this way before publication: three IBANs failed the mod-97 check and several names used characters outside the basic SEPA character set.
ACH / NACHA file (US)
- ACH — a returned WEB debit (R01, insufficient funds)
- ACH — an international entry (IAT) with its seven mandatory addenda
- ACH — PPD payroll credits, balanced with an offset debit
- ACH — CCD corporate debits with an addenda 05 remittance
- ACH — WEB debits (e-commerce, recurring and single-entry)
- ACH — CTX with seven addenda 05 carrying an EDI 820
- ACH — entry hash mismatch (truncated or tampered file)
- ACH — batch control debit total ≠ the sum of its entries
- ACH — invalid ABA 3-7-1 check digit on an entry routing number