---
title: "NACHA File Format: ACH File Layout, Field by Field"
description: "NACHA file format reference: field positions, lengths and rules for File Header, Batch Header, Entry Detail, Addenda, Batch Control and File Control records."
canonical: https://nacha-navigator.com/nacha-file-format
updated: 2026-10-30
---

# NACHA file format: ACH record layouts

Reference

Every field of every NACHA record type, with its position, length, format and rules, plus the transaction, SEC, return and change codes that go in them.

Last updated October 30, 2026. Generated from the field definitions the NACHA Viewer validates against: 46 record layouts, 485 fields.

## How a NACHA file is organized

A NACHA file, also called an ACH file, is plain text made of fixed-width records. Every record is exactly 94 characters long and sits on its own line, and its first character, the record type code, says what it is. Records always come in this order:

1. [File Header (record type 1): Once, on the first line. Who sent the file, to whom, and when.](https://nacha-navigator.com/nacha-file-format#file-header)
2. [Company/Batch Header (record type 5): Starts each batch. The company, the SEC code and the effective date of the entries that follow.](https://nacha-navigator.com/nacha-file-format#batch-header)
3. [Entry Detail (record type 6): One per payment. Transaction code, routing and account number, amount, receiver and trace number.](https://nacha-navigator.com/nacha-file-format#entry-ppd)
4. [Addenda (record type 7): Optional, after its entry. Remittance details, or the reason for a return or a notification of change.](https://nacha-navigator.com/nacha-file-format#addenda-05)
5. [Company/Batch Control (record type 8): Closes each batch. Entry and addenda count, entry hash, and debit and credit totals.](https://nacha-navigator.com/nacha-file-format#batch-control)
6. [File Control (record type 9): Once, after the last batch. Batch, block and entry counts, entry hash and totals for the file.](https://nacha-navigator.com/nacha-file-format#file-control)
7. [Block fill (all nines): Only if needed. Lines of 94 nines that pad the file to a multiple of 10 records.](https://nacha-navigator.com/nacha-file-format#block-fill)

Records 5 to 8 repeat for every batch; a file can hold any number of batches.

## Field rules

Each field has a fixed position. Here is line 3 of the sample file, an Entry Detail record, coloured by what each field holds:

An Entry Detail record: transaction code 22 (checking credit), routing number 065503348, account 1111111, amount $0.10, receiver JOHN M SMITH, trace number 065503680000001.

- **Positions** count from 1 and include both ends: positions 4–11 are the 4th through the 11th characters, 8 in all.
- **Numeric fields** are right-justified and zero-filled. Amounts are in cents with no decimal point, so $1,250.00 is `0000125000`.
- **Alphanumeric fields** are left-justified and space-filled, in uppercase by convention.
- **Dates** are `YYMMDD` and times `HHMM`; the settlement date is a three-digit day of the year that the ACH Operator fills in.
- **M/R/O** says whether a field is **Mandatory** (missing or invalid data gets the file or batch rejected), **Required** (missing data can get the entry returned) or **Optional**. N/A marks reserved positions and data the ACH Operator adds.

The NACHA Viewer checks every field against these rules. [NACHA file errors](https://nacha-navigator.com/nacha-file-errors) explains each error and warning it can report, and how to fix it.

## Totals and check digits

- **Entry hash:** add up the 8-digit Receiving DFI Identification (positions 4–11) of every entry in the batch and keep the rightmost 10 digits. The File Control does the same across all batches.
- **Control totals:** each Company/Batch Control counts the batch’s entries and addenda and totals its debits and credits in cents; the File Control totals the whole file and adds the batch and block counts. The transaction code says which total an entry counts in (see [ACH transaction codes](https://nacha-navigator.com/ach-transaction-codes)).
- **Check digit:** the ninth routing digit satisfies the ABA 3-7-1 rule: 3×(d1+d4+d7) + 7×(d2+d5+d8) + (d3+d6+d9) is a multiple of 10. To check one routing number, use the [routing number tool on PayOps Kit](https://payopskit.com/routing-number).
- **Blocking:** records are grouped in blocks of 10. If the last block is short, it is filled with block-fill records of 94 nines, and the File Control’s block count includes them.

The NACHA Viewer recomputes each of these and reports any that don’t match, such as an [entry hash mismatch](https://nacha-navigator.com/nacha-file-errors#bc-entry-hash), a [routing number that fails its check digit](https://nacha-navigator.com/nacha-file-errors#routing-check-digit) or a [file that isn’t padded to a multiple of 10 records](https://nacha-navigator.com/nacha-file-errors#block-fill-missing).

## File Header Record

Contains routing and other information to identify the origin and destination of the file.

**File Header Record: positions, fields and rules**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 1 | **Record Type Code** | 1 char | Code Always 1 | Mandatory | Identifies the type of record in the file. • Always "1" for the File Header Record |
| 2–3 | **Priority Code** | 2 chars | Code Always 01 | Required | Identifies the priority of the file. • Only "01" is used |
| 4–13 | **Immediate Destination** | 10 chars | Routing bTTTTAAAAC | Mandatory | Routing number of the ACH Operator or receiving point (usually your bank) to which the file is being sent. • Format bTTTTAAAAC: a blank followed by the 9-digit routing number, including its check digit • TTTT = Federal Reserve Routing Symbol, AAAA = ABA Institution Identifier, C = check digit • Right-justified with one leading blank • Must pass the ABA check-digit test |
| 14–23 | **Immediate Origin** | 10 chars | Routing bTTTTAAAAC | Mandatory | Routing number of the sending point (usually the ODFI), or another 10-character identifier agreed with the receiving point. • Usually bTTTTAAAAC: a blank followed by the 9-digit routing number • Some banks assign a 10-character company identifier instead (often "1" followed by the Federal Tax ID); use the value your bank specifies • When it is a routing number it must pass the ABA check-digit test |
| 24–29 | **File Creation Date** | 6 chars | Date YYMMDD | Mandatory | The date on which the file was created. • Format YYMMDD • Must be a valid calendar date |
| 30–33 | **File Creation Time** | 4 chars | Time HHMM | Optional | The time at which the file was created. • Format HHMM, 24-hour clock • Optional; may be left blank |
| 34 | **File ID Modifier** | 1 char | Alphanumeric | Mandatory | Distinguishes between multiple files created on the same date for the same destination and origin. • Uppercase A–Z or a digit 0–9 • Use "A" for the first file of the day and the next value for each additional file • Lets the receiving point detect duplicate files |
| 35–37 | **Record Size** | 3 chars | Code Always 094 | Mandatory | The number of characters in each record. • Always "094" |
| 38–39 | **Blocking Factor** | 2 chars | Code Always 10 | Mandatory | The number of records in each physical block. • Must be "10" • The file is padded with block-fill records (94 nines) to a multiple of 10 records |
| 40 | **Format Code** | 1 char | Code Always 1 | Mandatory | Identifies the format of the file. • Always "1" |
| 41–63 | **Immediate Destination Name** | 23 chars | Alphanumeric | Optional | Name of the ACH Operator or receiving point to which the file is sent. • Optional • Left-justified and space-filled |
| 64–86 | **Immediate Origin Name** | 23 chars | Alphanumeric | Optional | Name of the sending point or originating company that created the file. • Optional • Left-justified and space-filled |
| 87–94 | **Reference Code** | 8 chars | Alphanumeric | Optional | For the originator's own use to describe or identify the file. • Optional; often blank • Left-justified and space-filled |

## Company/Batch Header Record

Identifies the originator and purpose of the entries contained in the batch.

**Company/Batch Header Record: positions, fields and rules**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 1 | **Record Type Code** | 1 char | Code Always 5 | Mandatory | Identifies the type of record in the file. • Always "5" for the Company/Batch Header Record |
| 2–4 | **Service Class Code** | 3 chars | Code [See codes](https://nacha-navigator.com/nacha-file-format#service-class-codes) | Mandatory | Identifies whether the batch contains debits, credits or both. • 200 = mixed debits and credits • 220 = credits only • 225 = debits only • 280 = automated accounting advices (ADV) • Must match the Service Class Code in the Batch Control Record |
| 5–20 | **Company Name** | 16 chars | Alphanumeric | Mandatory | Name of the Originator, as known to and readily recognized by the Receiver. • Usually appears on the Receiver's bank statement • Left-justified and space-filled |
| 21–40 | **Company Discretionary Data** | 20 chars | Alphanumeric | Optional | For the Originator or ODFI to use as they agree, e.g. internal reference data. • Optional • Left-justified and space-filled |
| 41–50 | **Company Identification** | 10 chars | Alphanumeric | Mandatory | Identifies the Originator to the ODFI and the RDFI. • Usually "1" followed by the 9-digit IRS Employer Identification Number (EIN) • Other prefixes: "3" = DUNS number, "9" = number assigned by the user • Must match the Company Identification in the Batch Control Record • Use the value your ODFI assigned or agreed |
| 51–53 | **Standard Entry Class Code** | 3 chars | Code [See codes](https://nacha-navigator.com/nacha-file-format#sec-codes) | Mandatory | Three-letter code identifying the kind of entries in the batch and how they were authorized. • PPD = consumer prearranged payments and deposits · CCD = corporate credits or debits • CTX = corporate trade exchange with EDI remittance · WEB = internet or mobile · TEL = telephone • IAT = international · ARC, BOC, POP, RCK = converted checks · COR = notifications of change • Must be uppercase |
| 54–63 | **Company Entry Description** | 10 chars | Alphanumeric | Mandatory | Tells the Receiver what the entries are for, e.g. PAYROLL or GAS BILL. • Usually printed on the Receiver's bank statement • Required by the Rules for some batches: REVERSAL (reversing entries), RECLAIM (reclamations), RETURN FEE, RETRY PYMT (reinitiated entries), NONSETTLED (entries that could not settle), ACCTVERIFY (micro-entries) • By SEC code: REDEPCHECK (RCK), AUTOENROLL (ENR), NO CHECK (XCK), HCCLAIMPMT (CCD health care payments); TRX carries the keeper’s routing number, and WEB person-to-person credits need a description the Receiver will recognize • Since March 20, 2026: PAYROLL on PPD credits for wages, salaries and similar pay; PURCHASE on consumer debits for online purchases of goods (WEB, or PPD or TEL under a Standing Authorization) • Left-justified and space-filled |
| 64–69 | **Company Descriptive Date** | 6 chars | Alphanumeric | Optional | A date the Originator wants shown to the Receiver, such as a pay period, in any format. • Optional and free-form, e.g. YYMMDD or "MAR 15" • Optional same-day indicator: "SDHHMM" (e.g. SD1300) shows the Originator intends settlement in that same-day window; it does not by itself make entries settle the same day • Left-justified and space-filled |
| 70–75 | **Effective Entry Date** | 6 chars | Date YYMMDD | Required | The banking day on which the Originator intends the entries to settle. • Format YYMMDD • Should be a banking day: not a weekend or Federal Reserve holiday • A past or non-banking date settles at the ACH Operator's next settlement opportunity • For Same Day ACH, use the current day's date and submit before the same-day deadline |
| 76–78 | **Settlement Date (Julian)** | 3 chars | Julian day DDD | Not applicable: reserved, or filled in by the ACH Operator | Day of the year on which the batch settles. Inserted by the receiving ACH Operator. • Leave blank when creating a file; the ACH Operator fills it in • Format DDD: 001–366 |
| 79 | **Originator Status Code** | 1 char | Code [See codes](https://nacha-navigator.com/nacha-file-format#other-codes) | Mandatory | Identifies the status of the Originator under the Nacha Rules. • 1 = depository financial institution bound by the Nacha Rules (used on virtually all files) • 2 = Federal Government entity or agency not subject to the Rules • 0 = ADV file prepared by an ACH Operator |
| 80–87 | **Originating DFI Identification** | 8 chars | Routing TTTTAAAA | Mandatory | First 8 digits of the routing number of the ODFI (no check digit). • Must match the ODFI in the Batch Control Record • Trace numbers in the batch start with this value • In return and NOC batches this is the RDFI that is sending them back |
| 88–94 | **Batch Number** | 7 chars | Numeric | Mandatory | Number assigned in ascending sequence to each batch in the file. • Usually starts at 0000001 • Must match the Batch Number in the Batch Control Record • Right-justified and zero-filled |

### International (IAT) batches

IAT batches use their own header layout, with foreign-exchange and currency fields.

#### IAT: International ACH Transaction

17 fields

Batch header for international entries: replaces company fields with foreign-exchange and country data.

**Company/Batch Header Record — IAT: positions, fields and rules**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 1 | **Record Type Code** | 1 char | Code Always 5 | Mandatory | Identifies the type of record in the file. • Always "5" for the Company/Batch Header Record |
| 2–4 | **Service Class Code** | 3 chars | Code [See codes](https://nacha-navigator.com/nacha-file-format#service-class-codes) | Mandatory | Identifies whether the batch contains debits, credits or both. • 200 = mixed debits and credits • 220 = credits only • 225 = debits only • 280 = automated accounting advices (ADV) • Must match the Service Class Code in the Batch Control Record |
| 5–20 | **IAT Indicator** | 16 chars | Alphanumeric | Optional | Blank in IAT batches. Contains "IATCOR" in a batch of IAT Notifications of Change. • Left-justified and space-filled |
| 21–22 | **Foreign Exchange Indicator** | 2 chars | Code [See codes](https://nacha-navigator.com/nacha-file-format#other-codes) | Mandatory | How the amount is converted between currencies. • FV = fixed-to-variable: sent as a fixed amount, received after conversion • VF = variable-to-fixed: converted so that a fixed amount is received • FF = fixed-to-fixed: same currency at both ends, no conversion |
| 23 | **Foreign Exchange Reference Indicator** | 1 char | Code [See codes](https://nacha-navigator.com/nacha-file-format#other-codes) | Mandatory | Identifies what the Foreign Exchange Reference field contains. • 1 = foreign exchange rate • 2 = foreign exchange reference number • 3 = space-filled |
| 24–38 | **Foreign Exchange Reference** | 15 chars | Alphanumeric | Required | The exchange rate or reference number named by the indicator; blank when the indicator is 3. • Left-justified and space-filled |
| 39–40 | **ISO Destination Country Code** | 2 chars | Alphanumeric | Mandatory | Two-letter ISO 3166 code of the country in which the entry is to be received. • Uppercase letters, e.g. US, CA, MX |
| 41–50 | **Originator Identification** | 10 chars | Alphanumeric | Mandatory | Identifies the Originator (the IAT equivalent of Company Identification). • Must match the Company Identification in the Batch Control Record |
| 51–53 | **Standard Entry Class Code** | 3 chars | Code [See codes](https://nacha-navigator.com/nacha-file-format#sec-codes) | Mandatory | Three-letter code identifying the kind of entries in the batch and how they were authorized. • PPD = consumer prearranged payments and deposits · CCD = corporate credits or debits • CTX = corporate trade exchange with EDI remittance · WEB = internet or mobile · TEL = telephone • IAT = international · ARC, BOC, POP, RCK = converted checks · COR = notifications of change • Must be uppercase |
| 54–63 | **Company Entry Description** | 10 chars | Alphanumeric | Mandatory | Tells the Receiver what the entries are for, e.g. PAYROLL or GAS BILL. • Usually printed on the Receiver's bank statement • Required by the Rules for some batches: REVERSAL (reversing entries), RECLAIM (reclamations), RETURN FEE, RETRY PYMT (reinitiated entries), NONSETTLED (entries that could not settle), ACCTVERIFY (micro-entries) • By SEC code: REDEPCHECK (RCK), AUTOENROLL (ENR), NO CHECK (XCK), HCCLAIMPMT (CCD health care payments); TRX carries the keeper’s routing number, and WEB person-to-person credits need a description the Receiver will recognize • Since March 20, 2026: PAYROLL on PPD credits for wages, salaries and similar pay; PURCHASE on consumer debits for online purchases of goods (WEB, or PPD or TEL under a Standing Authorization) • Left-justified and space-filled |
| 64–66 | **ISO Originating Currency Code** | 3 chars | Alphanumeric | Mandatory | Three-letter ISO 4217 code of the currency in which the entry was originated. • Uppercase letters, e.g. USD |
| 67–69 | **ISO Destination Currency Code** | 3 chars | Alphanumeric | Mandatory | Three-letter ISO 4217 code of the currency in which the entry is to be received. • Uppercase letters, e.g. CAD |
| 70–75 | **Effective Entry Date** | 6 chars | Date YYMMDD | Required | The banking day on which the Originator intends the entries to settle. • Format YYMMDD • Should be a banking day: not a weekend or Federal Reserve holiday • A past or non-banking date settles at the ACH Operator's next settlement opportunity • For Same Day ACH, use the current day's date and submit before the same-day deadline |
| 76–78 | **Settlement Date (Julian)** | 3 chars | Julian day DDD | Not applicable: reserved, or filled in by the ACH Operator | Day of the year on which the batch settles. Inserted by the receiving ACH Operator. • Leave blank when creating a file; the ACH Operator fills it in • Format DDD: 001–366 |
| 79 | **Originator Status Code** | 1 char | Code [See codes](https://nacha-navigator.com/nacha-file-format#other-codes) | Mandatory | Identifies the status of the Originator under the Nacha Rules. • 1 = depository financial institution bound by the Nacha Rules (used on virtually all files) • 2 = Federal Government entity or agency not subject to the Rules • 0 = ADV file prepared by an ACH Operator |
| 80–87 | **Go Identification/Originating DFI Identification** | 8 chars | Routing TTTTAAAA | Mandatory | For outbound IAT, the ODFI routing number (first 8 digits); for inbound IAT, the U.S. Gateway Operator identification. • Must match the ODFI in the Batch Control Record • Trace numbers in the batch start with this value |
| 88–94 | **Batch Number** | 7 chars | Numeric | Mandatory | Number assigned in ascending sequence to each batch in the file. • Usually starts at 0000001 • Must match the Batch Number in the Batch Control Record • Right-justified and zero-filled |

## Entry Detail Record

Contains the data for the individual entry, including the transaction code, account information, and amount. The table shows the PPD layout, the most common; the other SEC codes follow it.

**Entry Detail Record — PPD: positions, fields and rules**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 1 | **Record Type Code** | 1 char | Code Always 6 | Mandatory | Identifies the type of record in the file. • Always "6" for the Entry Detail Record |
| 2–3 | **Transaction Code** | 2 chars | Code [See codes](https://nacha-navigator.com/nacha-file-format#transaction-codes) | Mandatory | Identifies the type of account and whether the entry is a credit, a debit, a prenote, a zero-dollar entry or a return/NOC. • First digit: 2 = checking, 3 = savings, 4 = general ledger, 5 = loan • Last digit: 2 = credit, 3 = credit prenote, 4 = zero-dollar credit, 1 = return or NOC of a credit • Last digit: 7 = debit, 8 = debit prenote, 9 = zero-dollar debit, 6 = return or NOC of a debit • 22 = checking credit · 27 = checking debit · 32 = savings credit · 37 = savings debit |
| 4–11 | **Receiving DFI Identification** | 8 chars | Routing TTTTAAAA | Mandatory | First 8 digits of the routing number of the Receiver's financial institution (the RDFI). • TTTT = Federal Reserve Routing Symbol, AAAA = ABA Institution Identifier • The check digit (the 9th digit) follows in position 12 • Added up across the batch to produce the Entry Hash |
| 12 | **Check Digit** | 1 char | Numeric | Mandatory | The ninth digit of the RDFI routing number, computed from the first eight. • ABA 3-7-1 rule: 3×(d1+d4+d7) + 7×(d2+d5+d8) + (d3+d6+d9) must be a multiple of 10 • A wrong check digit means the routing number was mistyped |
| 13–29 | **DFI Account Number** | 17 chars | Alphanumeric | Required | The Receiver's account number at the RDFI. • Left-justified and space-filled • Enter the significant characters only; omit embedded spaces • For a prenote, the account that will receive future live entries |
| 30–39 | **Amount** | 10 chars | Amount Cents, no decimal point | Mandatory | The amount of the entry, in cents. • In cents, with no decimal point: $100.00 is "0000010000" • Right-justified and zero-filled; the largest amount is $99,999,999.99 • Must be zero for prenotes and zero-dollar entries |
| 40–54 | **Individual Identification Number** | 15 chars | Alphanumeric | Optional | Number the Originator uses to identify the Receiver, such as an employee ID, customer or loan number. • Optional • Left-justified and space-filled |
| 55–76 | **Individual Name** | 22 chars | Alphanumeric | Required | Name of the Receiver. • Required • Left-justified and space-filled • May appear on the Receiver's bank statement |
| 77–78 | **Discretionary Data** | 2 chars | Alphanumeric | Optional | For the ODFI or Originator to use as they agree; it has no meaning to the ACH Network. • Optional • Left-justified and space-filled |
| 79 | **Addenda Record Indicator** | 1 char | Code [See codes](https://nacha-navigator.com/nacha-file-format#other-codes) | Mandatory | Shows whether one or more Addenda Records follow this entry. • 0 = no Addenda Record follows • 1 = one or more Addenda Records follow |
| 80–94 | **Trace Number** | 15 chars | Numeric | Mandatory | Uniquely identifies the entry within its batch and lets it be traced through the ACH Network. • First 8 digits: the ODFI routing number from the Company/Batch Header (no check digit) • Last 7 digits: a sequence number assigned by the ODFI • Unique within the batch and in ascending order within it • With the Batch Number, File Creation Date and File ID Modifier it identifies the entry in the file; many ODFIs also want it unique in the file |

### Entry Detail by SEC code

Positions 1–39 and 79–94 are the same for almost every Standard Entry Class code; the middle of the record changes. Each layout below lists only the fields that differ from PPD, with the full layout one click away.

#### CCD: Corporate Credit or Debit

Differs from PPD in positions 40–76

Credit or debit between business accounts; may carry one addenda record of remittance data.

**Entry Detail Record — CCD: fields that differ from PPD**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 40–54 | **Identification Number** | 15 chars | Alphanumeric | Optional | Number the Originator uses to identify the Receiver, such as a vendor, customer or invoice number. • Optional • Left-justified and space-filled |
| 55–76 | **Receiving Company Name** | 22 chars | Alphanumeric | Required | Name of the Receiver (a business). • Required • Left-justified and space-filled |

Positions not listed match the PPD layout.

#### CTX: Corporate Trade Exchange

Differs from PPD in positions 30–76

Business-to-business payment carrying up to 9,999 addenda records of EDI remittance data.

**Entry Detail Record — CTX: fields that differ from PPD**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 30–39 | **Total Amount** | 10 chars | Amount Cents, no decimal point | Mandatory | Total amount of the entry, in cents. • In cents, with no decimal point: $100.00 is "0000010000" • Right-justified and zero-filled; the largest amount is $99,999,999.99 • Zero for acknowledgment entries |
| 40–54 | **Identification Number** | 15 chars | Alphanumeric | Optional | Number the Originator uses to identify the Receiver, such as a vendor, customer or invoice number. • Optional • Left-justified and space-filled |
| 55–58 | **Number of Addenda Records** | 4 chars | Numeric | Mandatory | Number of Addenda Records that follow this entry (type 05 remittance addenda, 0000–9999). • Must equal the number of Addenda Records actually following the entry • Right-justified and zero-filled |
| 59–74 | **Receiving Company Name/ID Number** | 16 chars | Alphanumeric | Required | Name or identification number of the Receiver (a business). • Required • Left-justified and space-filled |
| 75–76 | **Reserved** | 2 chars | Alphanumeric | Not applicable: reserved, or filled in by the ACH Operator | Reserved for future use. Leave blank. • Space-filled |

Positions not listed match the PPD layout.

#### WEB: Internet-Initiated/Mobile Entry

Differs from PPD in positions 77–78

Consumer debit authorized over the internet or a mobile device, or a person-to-person credit.

**Entry Detail Record — WEB: fields that differ from PPD**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 77–78 | **Payment Type Code** | 2 chars | Code [See codes](https://nacha-navigator.com/nacha-file-format#other-codes) | Optional | Optional code the Originator may use to show whether a debit is recurring or a single entry. • Optional since September 17, 2021; ask your ODFI whether it wants one • "R " = recurring and "S " = single entry are the usual values • Other values have no standard meaning, and RDFIs cannot rely on the field • Left-justified and space-filled |

Positions not listed match the PPD layout.

#### TEL: Telephone-Initiated Entry

Differs from PPD in positions 77–78

Consumer debit authorized orally over the telephone.

**Entry Detail Record — TEL: fields that differ from PPD**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 77–78 | **Payment Type Code** | 2 chars | Code [See codes](https://nacha-navigator.com/nacha-file-format#other-codes) | Optional | Optional code the Originator may use to show whether a debit is recurring or a single entry. • Optional since September 17, 2021; ask your ODFI whether it wants one • "R " = recurring and "S " = single entry are the usual values • Other values have no standard meaning, and RDFIs cannot rely on the field • Left-justified and space-filled |

Positions not listed match the PPD layout.

#### IAT: International ACH Transaction

Differs from PPD in positions 4–78

International entry. Followed by seven mandatory addenda (types 10–16) and up to seven optional ones.

**Entry Detail Record — IAT: fields that differ from PPD**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 4–11 | **Gateway Operator Identification/Receiving DFI Identification** | 8 chars | Routing TTTTAAAA | Mandatory | For outbound IAT, the routing number (first 8 digits) of the U.S. Gateway Operator; for inbound IAT, of the RDFI. • The check digit follows in position 12 • Added up across the batch to produce the Entry Hash |
| 13–16 | **Number of Addenda Records** | 4 chars | Numeric | Mandatory | Number of Addenda Records that follow this entry (all IAT addenda: seven mandatory plus up to two type 17 and five type 18). • Must equal the number of Addenda Records actually following the entry • Right-justified and zero-filled |
| 17–29 | **Reserved** | 13 chars | Alphanumeric | Not applicable: reserved, or filled in by the ACH Operator | Reserved for future use. Leave blank. • Space-filled |
| 40–74 | **Foreign Receiver's Account Number/DFI Account Number** | 35 chars | Alphanumeric | Mandatory | The Receiver's account number at the foreign or domestic receiving institution. • Left-justified and space-filled |
| 75–76 | **Reserved** | 2 chars | Alphanumeric | Not applicable: reserved, or filled in by the ACH Operator | Reserved for future use. Leave blank. • Space-filled |
| 77 | **Gateway Operator OFAC Screening Indicator** | 1 char | Code [See codes](https://nacha-navigator.com/nacha-file-format#other-codes) | Optional | Set by the Gateway Operator when its OFAC screening flagged the entry. • "1" = flagged as a possible OFAC match • Blank or "0" = not flagged |
| 78 | **Secondary OFAC Screening Indicator** | 1 char | Code [See codes](https://nacha-navigator.com/nacha-file-format#other-codes) | Optional | Set by a secondary screener (such as the ODFI or RDFI) when its OFAC screening flagged the entry. • "1" = flagged as a possible OFAC match • Blank or "0" = not flagged |

Positions not listed match the PPD layout.

#### ARC: Accounts Receivable Entry

Differs from PPD in positions 40–76

Eligible check received by mail or delivery service, at a dropbox, or in person to pay a bill at a staffed location, converted to a one-time ACH debit.

**Entry Detail Record — ARC: fields that differ from PPD**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 40–54 | **Check Serial Number** | 15 chars | Alphanumeric | Mandatory | Serial number of the source check, from its MICR line. • Mandatory • Left-justified and space-filled |
| 55–76 | **Individual Name** | 22 chars | Alphanumeric | Optional | Name of the Receiver. • Optional • Left-justified and space-filled • May appear on the Receiver's bank statement |

Positions not listed match the PPD layout.

#### BOC: Back Office Conversion

Differs from PPD in positions 40–76

Eligible check presented at a point of purchase or a staffed bill-payment location and converted to a one-time ACH debit in the back office.

**Entry Detail Record — BOC: fields that differ from PPD**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 40–54 | **Check Serial Number** | 15 chars | Alphanumeric | Mandatory | Serial number of the source check, from its MICR line. • Mandatory • Left-justified and space-filled |
| 55–76 | **Individual Name** | 22 chars | Alphanumeric | Optional | Name of the Receiver. • Optional • Left-justified and space-filled • May appear on the Receiver's bank statement |

Positions not listed match the PPD layout.

#### POP: Point-of-Purchase Entry

Differs from PPD in positions 40–76

Eligible check converted to a one-time ACH debit on the spot, at a point of purchase or a staffed bill-payment location; the voided check is handed back.

**Entry Detail Record — POP: fields that differ from PPD**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 40–48 | **Check Serial Number** | 9 chars | Alphanumeric | Mandatory | Serial number of the source check, from its MICR line. • Mandatory • Left-justified and space-filled |
| 49–52 | **Terminal City** | 4 chars | Alphanumeric | Mandatory | Abbreviated name of the city where the point-of-purchase terminal is located. • First four characters of the city name • Left-justified and space-filled |
| 53–54 | **Terminal State** | 2 chars | Alphanumeric | Mandatory | Two-letter state abbreviation of the terminal location. • Uppercase postal abbreviation |
| 55–76 | **Individual Name** | 22 chars | Alphanumeric | Optional | Name of the Receiver. • Optional • Left-justified and space-filled • May appear on the Receiver's bank statement |

Positions not listed match the PPD layout.

#### RCK: Re-presented Check Entry

Differs from PPD in positions 40–76

A check returned for insufficient or uncollected funds, re-presented as an ACH debit.

**Entry Detail Record — RCK: fields that differ from PPD**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 40–54 | **Check Serial Number** | 15 chars | Alphanumeric | Mandatory | Serial number of the source check, from its MICR line. • Mandatory • Left-justified and space-filled |
| 55–76 | **Individual Name** | 22 chars | Alphanumeric | Optional | Name of the Receiver. • Optional • Left-justified and space-filled • May appear on the Receiver's bank statement |

Positions not listed match the PPD layout.

#### CIE: Customer Initiated Entry

Differs from PPD in positions 40–76

Credit initiated by a consumer, e.g. a bill payment through online banking. Name comes before the ID number.

**Entry Detail Record — CIE: fields that differ from PPD**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 40–54 | **Individual Name** | 15 chars | Alphanumeric | Required | Name of the Receiver. • Required • Left-justified and space-filled • May appear on the Receiver's bank statement |
| 55–76 | **Individual Identification Number** | 22 chars | Alphanumeric | Required | Number the Originator uses to identify the Receiver, such as an employee ID, customer or loan number. • Required • Left-justified and space-filled |

Positions not listed match the PPD layout.

#### MTE: Machine Transfer Entry

Differs from PPD in positions 40–76

Entry initiated at an ATM or other electronic terminal. Followed by one type 02 addenda.

**Entry Detail Record — MTE: fields that differ from PPD**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 40–54 | **Individual Name** | 15 chars | Alphanumeric | Required | Name of the Receiver. • Required • Left-justified and space-filled • May appear on the Receiver's bank statement |
| 55–76 | **Individual Identification Number** | 22 chars | Alphanumeric | Required | Number the Originator uses to identify the Receiver, such as an employee ID, customer or loan number. • Required • Left-justified and space-filled |

Positions not listed match the PPD layout.

#### POS: Point-of-Sale Entry

Differs from PPD in positions 55–78

Consumer debit at an electronic terminal to pay for a purchase or withdraw cash, or a credit that adjusts one. Followed by one type 02 addenda.

**Entry Detail Record — POS: fields that differ from PPD**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 55–76 | **Individual Name** | 22 chars | Alphanumeric | Optional | Name of the Receiver. • Optional • Left-justified and space-filled • May appear on the Receiver's bank statement |
| 77–78 | **Card Transaction Type Code** | 2 chars | Code [See codes](https://nacha-navigator.com/nacha-file-format#other-codes) | Mandatory | Identifies the kind of card transaction. • 01 = purchase of goods or services · 02 = cash · 03 = return reversal • 11 = purchase reversal · 12 = cash reversal · 13 = return · 21 = adjustment · 99 = miscellaneous |

Positions not listed match the PPD layout.

#### SHR: Shared Network Transaction

Differs from PPD in positions 40–78

Point-of-sale debit, or a credit that adjusts one, in a shared network where the ODFI and RDFI have an agreement beyond the Rules. Followed by one type 02 addenda.

**Entry Detail Record — SHR: fields that differ from PPD**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 40–43 | **Card Expiration Date** | 4 chars | Date MMYY | Mandatory | Expiration date of the card used. • Format MMYY |
| 44–54 | **Document Reference Number** | 11 chars | Numeric | Mandatory | Number identifying the transaction document. • Right-justified and zero-filled |
| 55–76 | **Individual Card Account Number** | 22 chars | Alphanumeric | Mandatory | The card account number used for the transaction. • Left-justified and space-filled |
| 77–78 | **Card Transaction Type Code** | 2 chars | Code [See codes](https://nacha-navigator.com/nacha-file-format#other-codes) | Mandatory | Identifies the kind of card transaction. • 01 = purchase of goods or services · 02 = cash · 03 = return reversal • 11 = purchase reversal · 12 = cash reversal · 13 = return · 21 = adjustment · 99 = miscellaneous |

Positions not listed match the PPD layout.

#### ACK: ACH Payment Acknowledgment

Differs from PPD in positions 30–76

Zero-dollar entry an RDFI sends to acknowledge receipt of a CCD credit.

**Entry Detail Record — ACK: fields that differ from PPD**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 30–39 | **Total Amount** | 10 chars | Amount Cents, no decimal point | Mandatory | Total amount of the entry, in cents. • In cents, with no decimal point: $100.00 is "0000010000" • Right-justified and zero-filled; the largest amount is $99,999,999.99 • Zero for acknowledgment entries |
| 40–54 | **Original Entry Trace Number** | 15 chars | Numeric | Mandatory | Trace Number of the entry being acknowledged. • 15 digits, copied from the original entry |
| 55–76 | **Receiving Company Name** | 22 chars | Alphanumeric | Required | Name of the Receiver (a business). • Required • Left-justified and space-filled |

Positions not listed match the PPD layout.

#### ATX: Financial EDI Acknowledgment

Differs from PPD in positions 30–76

Zero-dollar entry an RDFI sends to acknowledge receipt of a CTX credit.

**Entry Detail Record — ATX: fields that differ from PPD**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 30–39 | **Total Amount** | 10 chars | Amount Cents, no decimal point | Mandatory | Total amount of the entry, in cents. • In cents, with no decimal point: $100.00 is "0000010000" • Right-justified and zero-filled; the largest amount is $99,999,999.99 • Zero for acknowledgment entries |
| 40–54 | **Original Entry Trace Number** | 15 chars | Numeric | Mandatory | Trace Number of the entry being acknowledged. • 15 digits, copied from the original entry |
| 55–58 | **Number of Addenda Records** | 4 chars | Numeric | Mandatory | Number of Addenda Records that follow this entry (type 05 addenda, 0000–9999). • Must equal the number of Addenda Records actually following the entry • Right-justified and zero-filled |
| 59–74 | **Receiving Company Name/ID Number** | 16 chars | Alphanumeric | Required | Name or identification number of the Receiver (a business). • Required • Left-justified and space-filled |
| 75–76 | **Reserved** | 2 chars | Alphanumeric | Not applicable: reserved, or filled in by the ACH Operator | Reserved for future use. Leave blank. • Space-filled |

Positions not listed match the PPD layout.

#### DNE: Death Notification Entry

Same positions as PPD

Zero-dollar entry from a Federal Government agency reporting the death of a benefit recipient; carries one addenda.

Every position matches the PPD layout above; only the Standard Entry Class code in the batch header differs.

#### ENR: Automated Enrollment Entry

Differs from PPD in positions 13–76

Zero-dollar entry a DFI sends to a Federal Government agency to enroll a beneficiary in direct deposit. The enrollee’s account details travel in the addenda, so positions 13–29 are left blank.

**Entry Detail Record — ENR: fields that differ from PPD**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 13–29 | **DFI Account Number** | 17 chars | Alphanumeric | Optional | Left blank on an enrollment: the enrollee’s account number is in the type 05 addenda. • Left blank for Federal Government enrollments • The RDFI fields (positions 4–12) hold the routing number of the agency program |
| 40–54 | **Identification Number** | 15 chars | Alphanumeric | Optional | Number the Originator uses to identify the Receiver, such as a vendor, customer or invoice number. • Optional • Left-justified and space-filled |
| 55–58 | **Number of Addenda Records** | 4 chars | Numeric | Mandatory | Number of Addenda Records that follow this entry (type 05 addenda carrying the enrollment data). • Must equal the number of Addenda Records actually following the entry • Right-justified and zero-filled |
| 59–74 | **Receiving Company Name/ID Number** | 16 chars | Alphanumeric | Required | Identifies the Federal Government benefit program the enrollment is for, such as SOCIAL SECURITY. • The program code the Treasury Green Book lists for the agency • Left-justified and space-filled |
| 75–76 | **Reserved** | 2 chars | Alphanumeric | Not applicable: reserved, or filled in by the ACH Operator | Reserved for future use. Leave blank. • Space-filled |

Positions not listed match the PPD layout.

#### TRC: Check Truncation Entry

Differs from PPD in positions 40–78

Debit for a single check that was truncated (kept by the collecting institution) under a check truncation program.

**Entry Detail Record — TRC: fields that differ from PPD**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 40–54 | **Check Serial Number** | 15 chars | Alphanumeric | Mandatory | Serial number of the source check, from its MICR line. • Mandatory • Left-justified and space-filled |
| 55–60 | **Process Control Field** | 6 chars | Alphanumeric | Mandatory | The process control (transaction code) field from the MICR line of the check. • Left-justified and space-filled |
| 61–76 | **Item Research Number** | 16 chars | Alphanumeric | Mandatory | Number that identifies the check for research, such as its item sequence number. • Left-justified and space-filled |
| 77–78 | **Item Type Indicator** | 2 chars | Alphanumeric | Optional | Identifies the type of truncated item, as agreed between the participating DFIs. • Optional • Left-justified and space-filled |

Positions not listed match the PPD layout.

#### TRX: Check Truncation Entries Exchange

Differs from PPD in positions 30–78

One debit for several truncated checks drawn on the same paying bank; the checks are listed in up to 9,999 addenda records.

**Entry Detail Record — TRX: fields that differ from PPD**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 30–39 | **Total Amount** | 10 chars | Amount Cents, no decimal point | Mandatory | Total amount of the entry, in cents. • In cents, with no decimal point: $100.00 is "0000010000" • Right-justified and zero-filled; the largest amount is $99,999,999.99 • Zero for acknowledgment entries |
| 40–54 | **Identification Number** | 15 chars | Alphanumeric | Optional | Number the Originator uses to identify the Receiver, such as a vendor, customer or invoice number. • Optional • Left-justified and space-filled |
| 55–58 | **Number of Addenda Records** | 4 chars | Numeric | Mandatory | Number of Addenda Records that follow this entry (type 05 addenda, 0000–9999). • Must equal the number of Addenda Records actually following the entry • Right-justified and zero-filled |
| 59–74 | **Receiving Company Name/ID Number** | 16 chars | Alphanumeric | Required | Name or identification number of the Receiver (a business). • Required • Left-justified and space-filled |
| 75–76 | **Reserved** | 2 chars | Alphanumeric | Not applicable: reserved, or filled in by the ACH Operator | Reserved for future use. Leave blank. • Space-filled |
| 77–78 | **Item Type Indicator** | 2 chars | Alphanumeric | Optional | Identifies the type of truncated item, as agreed between the participating DFIs. • Optional • Left-justified and space-filled |

Positions not listed match the PPD layout.

#### XCK: Destroyed Check Entry

Differs from PPD in positions 40–76

Debit used to collect an eligible check that was lost or destroyed, or damaged so it cannot be processed. The batch description is NO CHECK.

**Entry Detail Record — XCK: fields that differ from PPD**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 40–54 | **Check Serial Number** | 15 chars | Alphanumeric | Mandatory | Serial number of the source check, from its MICR line. • Mandatory • Left-justified and space-filled |
| 55–60 | **Process Control Field** | 6 chars | Alphanumeric | Mandatory | The process control (transaction code) field from the MICR line of the check. • Left-justified and space-filled |
| 61–76 | **Item Research Number** | 16 chars | Alphanumeric | Mandatory | Number that identifies the check for research, such as its item sequence number. • Left-justified and space-filled |

Positions not listed match the PPD layout.

#### COR: Notification of Change / Refused NOC

Differs from PPD in positions 40–76

Zero-dollar entry an RDFI sends to tell the Originator that information in an entry was wrong. Carries one type 98 addenda.

**Entry Detail Record — COR: fields that differ from PPD**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 40–54 | **Identification Number** | 15 chars | Alphanumeric | Optional | Copied from the original entry (Individual Identification Number or Identification Number). • Left-justified and space-filled |
| 55–76 | **Individual Name/Receiving Company Name** | 22 chars | Alphanumeric | Required | Copied from the original entry. • Left-justified and space-filled |

Positions not listed match the PPD layout.

#### ADV: Automated Accounting Advice

Differs from PPD in positions 13–94

Non-monetary accounting advice an ACH Operator sends to a DFI about its ACH activity: the amounts are information, not money moved.

**Entry Detail Record — ADV: fields that differ from PPD**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 13–27 | **DFI Account Number** | 15 chars | Alphanumeric | Mandatory | The account at the DFI the advice applies to. • Left-justified and space-filled |
| 28–39 | **Amount** | 12 chars | Amount Cents, no decimal point | Mandatory | The amount of the advice, in cents. • 12 digits, in cents, zero-filled |
| 40–48 | **Advice Routing Number** | 9 chars | Routing TTTTAAAAC | Mandatory | Routing number of the institution the advice is for. • 9 digits, including the check digit |
| 49–53 | **File Identification** | 5 chars | Alphanumeric | Optional | Identifies the file the advice relates to. • Left-justified and space-filled |
| 54 | **ACH Operator Data** | 1 char | Alphanumeric | Optional | For use by the ACH Operator. |
| 55–76 | **Individual Name** | 22 chars | Alphanumeric | Mandatory | Name of the Receiver. • Mandatory • Left-justified and space-filled • May appear on the Receiver's bank statement |
| 80–87 | **Routing Number of ACH Operator** | 8 chars | Routing TTTTAAAA | Mandatory | First 8 digits of the routing number of the ACH Operator that created the advice. |
| 88–90 | **Julian Date on Which This Advice Is Created** | 3 chars | Julian day DDD | Mandatory | Day of the year on which the advice was created. • 001–366 |
| 91–94 | **Sequence Number Within Batch** | 4 chars | Numeric | Mandatory | Sequence number of the advice within its batch. • Right-justified and zero-filled |

Positions not listed match the PPD layout.

## Addenda Record

Provides additional information about the preceding Entry Detail Record. The table shows type 05, payment related information; the other types follow it.

**Addenda Record — type 05: positions, fields and rules**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 1 | **Record Type Code** | 1 char | Code Always 7 | Mandatory | Identifies the type of record in the file. • Always "7" for the Addenda Record |
| 2–3 | **Addenda Type Code** | 2 chars | Code Always 05 | Mandatory | Identifies the layout of the Addenda Record. • Always "05" in this layout • 02 = terminal information (POS, SHR, MTE) · 05 = payment related information • 10–18 = IAT addenda · 98 = Notification of Change · 99 = return |
| 4–83 | **Payment Related Information** | 80 chars | Alphanumeric | Optional | Remittance information for the Receiver: free-form text, ANSI ASC X12 data segments, or Nacha-endorsed banking conventions. • ACK, CCD, CIE, PPD and WEB entries may carry one; a DNE entry carries exactly one • ENR entries carry 1 to 9,999; ATX, CTX and TRX entries up to 9,999 • X12 segments end with a terminator, usually a backslash (\\) or a tilde (\~) • Left-justified and space-filled |
| 84–87 | **Addenda Sequence Number** | 4 chars | Numeric | Mandatory | Position of this addenda among the type 05 addenda that belong to the same entry, starting at 0001. • Starts at 0001 and increases by one for each addenda of the entry • Right-justified and zero-filled |
| 88–94 | **Entry Detail Sequence Number** | 7 chars | Numeric | Mandatory | The last 7 digits of the Trace Number of the Entry Detail Record this addenda belongs to. • Links the addenda to its entry • Right-justified and zero-filled |

### Other addenda types

The Addenda Type Code in positions 2–3 decides the layout: 02 for terminal data, 98 for notifications of change, 99 for returns, and 10–18 for international (IAT) entries.

#### 02: Point-of-sale terminal information (POS, SHR, MTE)

12 fields

Where and when a card or ATM transaction happened. Exactly one follows each POS, SHR and MTE entry.

**Addenda Record — type 02: positions, fields and rules**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 1 | **Record Type Code** | 1 char | Code Always 7 | Mandatory | Identifies the type of record in the file. • Always "7" for the Addenda Record |
| 2–3 | **Addenda Type Code** | 2 chars | Code Always 02 | Mandatory | Identifies the layout of the Addenda Record. • Always "02" in this layout • 02 = terminal information (POS, SHR, MTE) · 05 = payment related information • 10–18 = IAT addenda · 98 = Notification of Change · 99 = return |
| 4–10 | **Reference Information #1** | 7 chars | Alphanumeric | Optional | Additional reference data identifying the transaction. • Optional • Left-justified and space-filled |
| 11–13 | **Reference Information #2** | 3 chars | Alphanumeric | Optional | Additional reference data identifying the transaction. • Optional • Left-justified and space-filled |
| 14–19 | **Terminal Identification Code** | 6 chars | Alphanumeric | Required | Identifies the electronic terminal where the transaction took place. • Left-justified and space-filled |
| 20–25 | **Transaction Serial Number** | 6 chars | Alphanumeric | Required | Serial number the terminal assigned to the transaction. • Left-justified and space-filled |
| 26–29 | **Transaction Date** | 4 chars | Date MMDD | Required | Month and day of the transaction. • Format MMDD |
| 30–35 | **Authorization Code or Card Expiration Date** | 6 chars | Alphanumeric | Optional | Authorization code from the card issuer, or the card expiration date. • Optional • Left-justified and space-filled |
| 36–62 | **Terminal Location** | 27 chars | Alphanumeric | Required | Street address or description of where the terminal is. • Left-justified and space-filled |
| 63–77 | **Terminal City** | 15 chars | Alphanumeric | Required | City where the terminal is located. • Left-justified and space-filled |
| 78–79 | **Terminal State** | 2 chars | Alphanumeric | Required | Two-letter state abbreviation of the terminal location. • Uppercase postal abbreviation |
| 80–94 | **Trace Number** | 15 chars | Numeric | Mandatory | The Trace Number of the entry this addenda belongs to (the same value as in its Entry Detail Record). • Identical to positions 80–94 of the Entry Detail Record it follows |

#### 98: Notification of Change

9 fields

Sent by the RDFI on a COR entry to tell the Originator which information in an earlier entry was wrong.

**Addenda Record — type 98: positions, fields and rules**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 1 | **Record Type Code** | 1 char | Code Always 7 | Mandatory | Identifies the type of record in the file. • Always "7" for the Addenda Record |
| 2–3 | **Addenda Type Code** | 2 chars | Code Always 98 | Mandatory | Identifies the layout of the Addenda Record. • Always "98" in this layout • 02 = terminal information (POS, SHR, MTE) · 05 = payment related information • 10–18 = IAT addenda · 98 = Notification of Change · 99 = return |
| 4–6 | **Change Code** | 3 chars | Code [See codes](https://nacha-navigator.com/nacha-file-format#change-codes) | Mandatory | Identifies the information the RDFI is correcting (C01–C03, C05–C09, C13 or C14). • "C" followed by two digits • Determines how Corrected Data is laid out • C04 and C10–C12 are retired: the Rules no longer define them |
| 7–21 | **Original Entry Trace Number** | 15 chars | Numeric | Mandatory | Trace Number of the entry the NOC corrects. • 15 digits, copied unchanged |
| 22–27 | **Reserved** | 6 chars | Alphanumeric | Not applicable: reserved, or filled in by the ACH Operator | Reserved for future use. Leave blank. • Space-filled |
| 28–35 | **Original Receiving DFI Identification** | 8 chars | Routing TTTTAAAA | Mandatory | The Receiving DFI Identification (positions 4–11) from the original entry. • 8 digits, without the check digit |
| 36–64 | **Corrected Data** | 29 chars | Alphanumeric | Mandatory | The correct information, laid out as the change code requires. • C01: correct account number in positions 1–17 · C02: correct routing number (9 digits) in 1–9 • C03: routing number in 1–9, blanks in 10–12, account number in 13–29 · C05: correct transaction code in 1–2 • C06: account number in 1–17, blanks in 18–20, transaction code in 21–22 · C07: routing (9), account (17), transaction code (2) • C08 (IAT): correct Receiving DFI Identification · C09: correct individual or receiver ID number in 1–22 • C13: no fixed layout · C14: "IAT" in 1–3 |
| 65–79 | **Reserved** | 15 chars | Alphanumeric | Not applicable: reserved, or filled in by the ACH Operator | Reserved for future use. Leave blank. • Space-filled |
| 80–94 | **Trace Number** | 15 chars | Numeric | Mandatory | The Trace Number of the NOC entry this addenda belongs to (the same value as in its Entry Detail Record). • Identical to positions 80–94 of the Entry Detail Record it follows |

#### 98: Refused Notification of Change (C61–C69)

11 fields

Sent by the ODFI to refuse a Notification of Change that was misrouted or incorrectly formatted.

**Addenda Record — type 98: positions, fields and rules**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 1 | **Record Type Code** | 1 char | Code Always 7 | Mandatory | Identifies the type of record in the file. • Always "7" for the Addenda Record |
| 2–3 | **Addenda Type Code** | 2 chars | Code Always 98 | Mandatory | Identifies the layout of the Addenda Record. • Always "98" in this layout • 02 = terminal information (POS, SHR, MTE) · 05 = payment related information • 10–18 = IAT addenda · 98 = Notification of Change · 99 = return |
| 4–6 | **Refused COR Code** | 3 chars | Code [See codes](https://nacha-navigator.com/nacha-file-format#change-codes) | Mandatory | Why the ODFI is refusing the NOC (C61–C69). • "C" followed by two digits |
| 7–21 | **Original Entry Trace Number** | 15 chars | Numeric | Mandatory | Trace Number of the entry the refused NOC related to. • 15 digits, copied unchanged |
| 22–27 | **Reserved** | 6 chars | Alphanumeric | Not applicable: reserved, or filled in by the ACH Operator | Reserved for future use. Leave blank. • Space-filled |
| 28–35 | **Original Receiving DFI Identification** | 8 chars | Routing TTTTAAAA | Mandatory | The Receiving DFI Identification (positions 4–11) from the original entry. • 8 digits, without the check digit |
| 36–64 | **Corrected Data** | 29 chars | Alphanumeric | Mandatory | The Corrected Data from the NOC being refused. • Copied from the NOC |
| 65–67 | **Change Code** | 3 chars | Code [See codes](https://nacha-navigator.com/nacha-file-format#change-codes) | Mandatory | The change code of the NOC being refused. • Copied from the NOC |
| 68–74 | **Trace Sequence Number** | 7 chars | Numeric | Mandatory | The last 7 digits of the Trace Number of the NOC being refused. • Right-justified and zero-filled |
| 75–79 | **Reserved** | 5 chars | Alphanumeric | Not applicable: reserved, or filled in by the ACH Operator | Reserved for future use. Leave blank. • Space-filled |
| 80–94 | **Trace Number** | 15 chars | Numeric | Mandatory | The Trace Number of the refused NOC entry this addenda belongs to (the same value as in its Entry Detail Record). • Identical to positions 80–94 of the Entry Detail Record it follows |

#### 99: Return

8 fields

Sent by the RDFI with a return entry to identify the original entry and the reason it was returned.

**Addenda Record — type 99: positions, fields and rules**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 1 | **Record Type Code** | 1 char | Code Always 7 | Mandatory | Identifies the type of record in the file. • Always "7" for the Addenda Record |
| 2–3 | **Addenda Type Code** | 2 chars | Code Always 99 | Mandatory | Identifies the layout of the Addenda Record. • Always "99" in this layout • 02 = terminal information (POS, SHR, MTE) · 05 = payment related information • 10–18 = IAT addenda · 98 = Notification of Change · 99 = return |
| 4–6 | **Return Reason Code** | 3 chars | Code [See codes](https://nacha-navigator.com/nacha-file-format#return-reason-codes) | Mandatory | Why the RDFI returned the entry (R01–R85; R90 from March 17, 2028). • "R" followed by two digits |
| 7–21 | **Original Entry Trace Number** | 15 chars | Numeric | Mandatory | Trace Number of the entry being returned. • 15 digits, copied unchanged |
| 22–27 | **Date of Death** | 6 chars | Date YYMMDD | Optional | Date of death of the account holder or beneficiary; used with return reasons R14 and R15. • Format YYMMDD • Blank for other return reasons |
| 28–35 | **Original Receiving DFI Identification** | 8 chars | Routing TTTTAAAA | Mandatory | The Receiving DFI Identification (positions 4–11) from the original entry. • 8 digits, without the check digit |
| 36–79 | **Addenda Information** | 44 chars | Alphanumeric | Optional | Additional information from the RDFI about the return. • Optional • Left-justified and space-filled |
| 80–94 | **Trace Number** | 15 chars | Numeric | Mandatory | The Trace Number of the return entry this addenda belongs to (the same value as in its Entry Detail Record). • Identical to positions 80–94 of the Entry Detail Record it follows |

#### 99: Dishonored return (R61, R62, R67–R70)

12 fields

Sent by the ODFI to dishonor a return that was misrouted, untimely, duplicated or contained errors.

**Addenda Record — type 99: positions, fields and rules**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 1 | **Record Type Code** | 1 char | Code Always 7 | Mandatory | Identifies the type of record in the file. • Always "7" for the Addenda Record |
| 2–3 | **Addenda Type Code** | 2 chars | Code Always 99 | Mandatory | Identifies the layout of the Addenda Record. • Always "99" in this layout • 02 = terminal information (POS, SHR, MTE) · 05 = payment related information • 10–18 = IAT addenda · 98 = Notification of Change · 99 = return |
| 4–6 | **Dishonored Return Reason Code** | 3 chars | Code [See codes](https://nacha-navigator.com/nacha-file-format#return-reason-codes) | Mandatory | Why the ODFI is dishonoring the return. • R61, R62, R67, R68, R69 or R70 |
| 7–21 | **Original Entry Trace Number** | 15 chars | Numeric | Mandatory | Trace Number of the original forward entry. • 15 digits, copied unchanged |
| 22–27 | **Reserved** | 6 chars | Alphanumeric | Not applicable: reserved, or filled in by the ACH Operator | Reserved for future use. Leave blank. • Space-filled |
| 28–35 | **Original Receiving DFI Identification** | 8 chars | Routing TTTTAAAA | Mandatory | The Receiving DFI Identification (positions 4–11) from the original entry. • 8 digits, without the check digit |
| 36–38 | **Reserved** | 3 chars | Alphanumeric | Not applicable: reserved, or filled in by the ACH Operator | Reserved for future use. Leave blank. • Space-filled |
| 39–53 | **Return Trace Number** | 15 chars | Numeric | Mandatory | Trace Number of the return entry. • 15 digits, copied from the return |
| 54–56 | **Return Settlement Date** | 3 chars | Julian day DDD | Mandatory | Day of the year on which the return settled. • Day of the year, 001–366 |
| 57–58 | **Return Reason Code** | 2 chars | Code [See codes](https://nacha-navigator.com/nacha-file-format#return-reason-codes) | Mandatory | Reason code of the return being dishonored. • The two digits of the return reason code, without the "R" (e.g. "01" for R01) |
| 59–79 | **Addenda Information** | 21 chars | Alphanumeric | Optional | Additional information from the ODFI. • Optional • Left-justified and space-filled |
| 80–94 | **Trace Number** | 15 chars | Numeric | Mandatory | The Trace Number of the dishonored return entry this addenda belongs to (the same value as in its Entry Detail Record). • Identical to positions 80–94 of the Entry Detail Record it follows |

#### 99: Contested dishonored return (R71–R77)

15 fields

Sent by the RDFI to contest an ODFI’s dishonor of its return.

**Addenda Record — type 99: positions, fields and rules**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 1 | **Record Type Code** | 1 char | Code Always 7 | Mandatory | Identifies the type of record in the file. • Always "7" for the Addenda Record |
| 2–3 | **Addenda Type Code** | 2 chars | Code Always 99 | Mandatory | Identifies the layout of the Addenda Record. • Always "99" in this layout • 02 = terminal information (POS, SHR, MTE) · 05 = payment related information • 10–18 = IAT addenda · 98 = Notification of Change · 99 = return |
| 4–6 | **Contested Dishonored Return Reason Code** | 3 chars | Code [See codes](https://nacha-navigator.com/nacha-file-format#return-reason-codes) | Mandatory | Why the RDFI is contesting the dishonored return. • R71–R77 |
| 7–21 | **Original Entry Trace Number** | 15 chars | Numeric | Mandatory | Trace Number of the original forward entry. • 15 digits, copied unchanged |
| 22–27 | **Date Original Entry Returned** | 6 chars | Date YYMMDD | Mandatory | The date on which the original entry was returned. • Format YYMMDD |
| 28–35 | **Original Receiving DFI Identification** | 8 chars | Routing TTTTAAAA | Mandatory | The Receiving DFI Identification (positions 4–11) from the original entry. • 8 digits, without the check digit |
| 36–38 | **Original Settlement Date** | 3 chars | Julian day DDD | Mandatory | Day of the year on which the original entry settled. • Day of the year, 001–366 |
| 39–53 | **Return Trace Number** | 15 chars | Numeric | Mandatory | Trace Number of the return entry. • 15 digits, copied from the return |
| 54–56 | **Return Settlement Date** | 3 chars | Julian day DDD | Mandatory | Day of the year on which the return settled. • Day of the year, 001–366 |
| 57–58 | **Return Reason Code** | 2 chars | Code [See codes](https://nacha-navigator.com/nacha-file-format#return-reason-codes) | Mandatory | Reason code of the original return. • The two digits of the return reason code, without the "R" (e.g. "01" for R01) |
| 59–73 | **Dishonored Return Trace Number** | 15 chars | Numeric | Mandatory | Trace Number of the dishonored return entry. • 15 digits |
| 74–76 | **Dishonored Return Settlement Date** | 3 chars | Julian day DDD | Mandatory | Day of the year on which the dishonored return settled. • Day of the year, 001–366 |
| 77–78 | **Dishonored Return Reason Code** | 2 chars | Code [See codes](https://nacha-navigator.com/nacha-file-format#return-reason-codes) | Mandatory | Reason code of the dishonored return. • The two digits of the code, without the "R" (e.g. "69" for R69) |
| 79 | **Reserved** | 1 char | Alphanumeric | Not applicable: reserved, or filled in by the ACH Operator | Reserved for future use. Leave blank. • Space-filled |
| 80–94 | **Trace Number** | 15 chars | Numeric | Mandatory | The Trace Number of the contested dishonored return entry this addenda belongs to (the same value as in its Entry Detail Record). • Identical to positions 80–94 of the Entry Detail Record it follows |

#### 10: IAT transaction and receiver

8 fields

First mandatory IAT addenda.

**Addenda Record — type 10: positions, fields and rules**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 1 | **Record Type Code** | 1 char | Code Always 7 | Mandatory | Identifies the type of record in the file. • Always "7" for the Addenda Record |
| 2–3 | **Addenda Type Code** | 2 chars | Code Always 10 | Mandatory | Identifies the layout of the Addenda Record. • Always "10" in this layout • 02 = terminal information (POS, SHR, MTE) · 05 = payment related information • 10–18 = IAT addenda · 98 = Notification of Change · 99 = return |
| 4–6 | **Transaction Type Code** | 3 chars | Code [See codes](https://nacha-navigator.com/nacha-file-format#other-codes) | Mandatory | Identifies the reason for the international payment. • e.g. SAL = salary/payroll, BUS = business, PEN = pension, ANN = annuity, MIS = miscellaneous |
| 7–24 | **Foreign Payment Amount** | 18 chars | Amount Cents, no decimal point | Required | For inbound IAT, the amount of the payment in the originating currency, in its smallest unit. • Right-justified and zero-filled |
| 25–46 | **Foreign Trace Number** | 22 chars | Alphanumeric | Optional | Trace number assigned to the entry in the originating national payment system. • Optional • Left-justified and space-filled |
| 47–81 | **Receiving Company Name/Individual Name** | 35 chars | Alphanumeric | Mandatory | Name of the Receiver. • Mandatory • Left-justified and space-filled |
| 82–87 | **Reserved** | 6 chars | Alphanumeric | Not applicable: reserved, or filled in by the ACH Operator | Reserved for future use. Leave blank. • Space-filled |
| 88–94 | **Entry Detail Sequence Number** | 7 chars | Numeric | Mandatory | The last 7 digits of the Trace Number of the Entry Detail Record this addenda belongs to. • Links the addenda to its entry • Right-justified and zero-filled |

#### 11: IAT originator name and address

6 fields

Second mandatory IAT addenda.

**Addenda Record — type 11: positions, fields and rules**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 1 | **Record Type Code** | 1 char | Code Always 7 | Mandatory | Identifies the type of record in the file. • Always "7" for the Addenda Record |
| 2–3 | **Addenda Type Code** | 2 chars | Code Always 11 | Mandatory | Identifies the layout of the Addenda Record. • Always "11" in this layout • 02 = terminal information (POS, SHR, MTE) · 05 = payment related information • 10–18 = IAT addenda · 98 = Notification of Change · 99 = return |
| 4–38 | **Originator Name** | 35 chars | Alphanumeric | Mandatory | Name of the Originator. • Mandatory • Left-justified and space-filled |
| 39–73 | **Originator Street Address** | 35 chars | Alphanumeric | Mandatory | Street address of the Originator. • Mandatory • Left-justified and space-filled |
| 74–87 | **Reserved** | 14 chars | Alphanumeric | Not applicable: reserved, or filled in by the ACH Operator | Reserved for future use. Leave blank. • Space-filled |
| 88–94 | **Entry Detail Sequence Number** | 7 chars | Numeric | Mandatory | The last 7 digits of the Trace Number of the Entry Detail Record this addenda belongs to. • Links the addenda to its entry • Right-justified and zero-filled |

#### 12: IAT originator city and country

6 fields

Third mandatory IAT addenda.

**Addenda Record — type 12: positions, fields and rules**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 1 | **Record Type Code** | 1 char | Code Always 7 | Mandatory | Identifies the type of record in the file. • Always "7" for the Addenda Record |
| 2–3 | **Addenda Type Code** | 2 chars | Code Always 12 | Mandatory | Identifies the layout of the Addenda Record. • Always "12" in this layout • 02 = terminal information (POS, SHR, MTE) · 05 = payment related information • 10–18 = IAT addenda · 98 = Notification of Change · 99 = return |
| 4–38 | **Originator City & State/Province** | 35 chars | Alphanumeric | Mandatory | City and state or province of the Originator, separated by an asterisk and ending with a backslash. • Mandatory • Left-justified and space-filled |
| 39–73 | **Originator Country & Postal Code** | 35 chars | Alphanumeric | Mandatory | Country and postal code of the Originator, separated by an asterisk and ending with a backslash. • Mandatory • Left-justified and space-filled |
| 74–87 | **Reserved** | 14 chars | Alphanumeric | Not applicable: reserved, or filled in by the ACH Operator | Reserved for future use. Leave blank. • Space-filled • From March 19, 2027, positions 74–83 may carry the Originator’s date of birth (optional) |
| 88–94 | **Entry Detail Sequence Number** | 7 chars | Numeric | Mandatory | The last 7 digits of the Trace Number of the Entry Detail Record this addenda belongs to. • Links the addenda to its entry • Right-justified and zero-filled |

#### 13: IAT originating DFI

8 fields

Fourth mandatory IAT addenda.

**Addenda Record — type 13: positions, fields and rules**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 1 | **Record Type Code** | 1 char | Code Always 7 | Mandatory | Identifies the type of record in the file. • Always "7" for the Addenda Record |
| 2–3 | **Addenda Type Code** | 2 chars | Code Always 13 | Mandatory | Identifies the layout of the Addenda Record. • Always "13" in this layout • 02 = terminal information (POS, SHR, MTE) · 05 = payment related information • 10–18 = IAT addenda · 98 = Notification of Change · 99 = return |
| 4–38 | **Originating DFI Name** | 35 chars | Alphanumeric | Mandatory | Name of the ODFI (for inbound IAT, the foreign correspondent that sent it). • Mandatory • Left-justified and space-filled |
| 39–40 | **Originating DFI Identification Number Qualifier** | 2 chars | Code [See codes](https://nacha-navigator.com/nacha-file-format#other-codes) | Mandatory | Identifies the kind of identification number that follows. • 01 = national clearing system number • 02 = BIC code • 03 = IBAN code • From March 19, 2027, 03 is deleted and a qualifier for non-bank foreign financial agencies is added |
| 41–74 | **Originating DFI Identification** | 34 chars | Alphanumeric | Mandatory | Identification number of the ODFI, of the kind named by the qualifier. • Mandatory • Left-justified and space-filled |
| 75–77 | **Originating DFI Branch Country Code** | 3 chars | Alphanumeric | Mandatory | ISO 3166 country code of the ODFI branch. • ISO 3166 country code, left-justified |
| 78–87 | **Reserved** | 10 chars | Alphanumeric | Not applicable: reserved, or filled in by the ACH Operator | Reserved for future use. Leave blank. • Space-filled |
| 88–94 | **Entry Detail Sequence Number** | 7 chars | Numeric | Mandatory | The last 7 digits of the Trace Number of the Entry Detail Record this addenda belongs to. • Links the addenda to its entry • Right-justified and zero-filled |

#### 14: IAT receiving DFI

8 fields

Fifth mandatory IAT addenda.

**Addenda Record — type 14: positions, fields and rules**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 1 | **Record Type Code** | 1 char | Code Always 7 | Mandatory | Identifies the type of record in the file. • Always "7" for the Addenda Record |
| 2–3 | **Addenda Type Code** | 2 chars | Code Always 14 | Mandatory | Identifies the layout of the Addenda Record. • Always "14" in this layout • 02 = terminal information (POS, SHR, MTE) · 05 = payment related information • 10–18 = IAT addenda · 98 = Notification of Change · 99 = return |
| 4–38 | **Receiving DFI Name** | 35 chars | Alphanumeric | Mandatory | Name of the RDFI. • Mandatory • Left-justified and space-filled |
| 39–40 | **Receiving DFI Identification Number Qualifier** | 2 chars | Code [See codes](https://nacha-navigator.com/nacha-file-format#other-codes) | Mandatory | Identifies the kind of identification number that follows. • 01 = national clearing system number • 02 = BIC code • 03 = IBAN code • From March 19, 2027, 03 is deleted and a qualifier for non-bank foreign financial agencies is added |
| 41–74 | **Receiving DFI Identification** | 34 chars | Alphanumeric | Mandatory | Identification number of the RDFI, of the kind named by the qualifier. • Mandatory • Left-justified and space-filled |
| 75–77 | **Receiving DFI Branch Country Code** | 3 chars | Alphanumeric | Mandatory | ISO 3166 country code of the RDFI branch. • ISO 3166 country code, left-justified |
| 78–87 | **Reserved** | 10 chars | Alphanumeric | Not applicable: reserved, or filled in by the ACH Operator | Reserved for future use. Leave blank. • Space-filled |
| 88–94 | **Entry Detail Sequence Number** | 7 chars | Numeric | Mandatory | The last 7 digits of the Trace Number of the Entry Detail Record this addenda belongs to. • Links the addenda to its entry • Right-justified and zero-filled |

#### 15: IAT receiver identification and address

6 fields

Sixth mandatory IAT addenda.

**Addenda Record — type 15: positions, fields and rules**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 1 | **Record Type Code** | 1 char | Code Always 7 | Mandatory | Identifies the type of record in the file. • Always "7" for the Addenda Record |
| 2–3 | **Addenda Type Code** | 2 chars | Code Always 15 | Mandatory | Identifies the layout of the Addenda Record. • Always "15" in this layout • 02 = terminal information (POS, SHR, MTE) · 05 = payment related information • 10–18 = IAT addenda · 98 = Notification of Change · 99 = return |
| 4–18 | **Receiver Identification Number** | 15 chars | Alphanumeric | Optional | Number the Originator uses to identify the Receiver. • Optional • Left-justified and space-filled |
| 19–53 | **Receiver Street Address** | 35 chars | Alphanumeric | Mandatory | Street address of the Receiver. • Mandatory • Left-justified and space-filled |
| 54–87 | **Reserved** | 34 chars | Alphanumeric | Not applicable: reserved, or filled in by the ACH Operator | Reserved for future use. Leave blank. • Space-filled |
| 88–94 | **Entry Detail Sequence Number** | 7 chars | Numeric | Mandatory | The last 7 digits of the Trace Number of the Entry Detail Record this addenda belongs to. • Links the addenda to its entry • Right-justified and zero-filled |

#### 16: IAT receiver city and country

6 fields

Seventh mandatory IAT addenda.

**Addenda Record — type 16: positions, fields and rules**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 1 | **Record Type Code** | 1 char | Code Always 7 | Mandatory | Identifies the type of record in the file. • Always "7" for the Addenda Record |
| 2–3 | **Addenda Type Code** | 2 chars | Code Always 16 | Mandatory | Identifies the layout of the Addenda Record. • Always "16" in this layout • 02 = terminal information (POS, SHR, MTE) · 05 = payment related information • 10–18 = IAT addenda · 98 = Notification of Change · 99 = return |
| 4–38 | **Receiver City & State/Province** | 35 chars | Alphanumeric | Mandatory | City and state or province of the Receiver, separated by an asterisk and ending with a backslash. • Mandatory • Left-justified and space-filled |
| 39–73 | **Receiver Country & Postal Code** | 35 chars | Alphanumeric | Mandatory | Country and postal code of the Receiver, separated by an asterisk and ending with a backslash. • Mandatory • Left-justified and space-filled |
| 74–87 | **Reserved** | 14 chars | Alphanumeric | Not applicable: reserved, or filled in by the ACH Operator | Reserved for future use. Leave blank. • Space-filled • From March 19, 2027, positions 74–83 may carry the Receiver’s date of birth (optional) |
| 88–94 | **Entry Detail Sequence Number** | 7 chars | Numeric | Mandatory | The last 7 digits of the Trace Number of the Entry Detail Record this addenda belongs to. • Links the addenda to its entry • Right-justified and zero-filled |

#### 17: IAT remittance information (optional, up to 2)

5 fields

Optional IAT payment related information.

**Addenda Record — type 17: positions, fields and rules**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 1 | **Record Type Code** | 1 char | Code Always 7 | Mandatory | Identifies the type of record in the file. • Always "7" for the Addenda Record |
| 2–3 | **Addenda Type Code** | 2 chars | Code Always 17 | Mandatory | Identifies the layout of the Addenda Record. • Always "17" in this layout • 02 = terminal information (POS, SHR, MTE) · 05 = payment related information • 10–18 = IAT addenda · 98 = Notification of Change · 99 = return |
| 4–83 | **Payment Related Information** | 80 chars | Alphanumeric | Optional | Remittance information for the Receiver. • Up to two type 17 addenda per IAT entry • Left-justified and space-filled |
| 84–87 | **Addenda Sequence Number** | 4 chars | Numeric | Mandatory | Position of this addenda among the type 17 addenda that belong to the same entry, starting at 0001. • Starts at 0001 and increases by one for each addenda of the entry • Right-justified and zero-filled |
| 88–94 | **Entry Detail Sequence Number** | 7 chars | Numeric | Mandatory | The last 7 digits of the Trace Number of the Entry Detail Record this addenda belongs to. • Links the addenda to its entry • Right-justified and zero-filled |

#### 18: IAT foreign correspondent bank (optional, up to 5)

9 fields

Identifies a foreign correspondent bank involved in the payment.

**Addenda Record — type 18: positions, fields and rules**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 1 | **Record Type Code** | 1 char | Code Always 7 | Mandatory | Identifies the type of record in the file. • Always "7" for the Addenda Record |
| 2–3 | **Addenda Type Code** | 2 chars | Code Always 18 | Mandatory | Identifies the layout of the Addenda Record. • Always "18" in this layout • 02 = terminal information (POS, SHR, MTE) · 05 = payment related information • 10–18 = IAT addenda · 98 = Notification of Change · 99 = return |
| 4–38 | **Foreign Correspondent Bank Name** | 35 chars | Alphanumeric | Mandatory | Name of the foreign correspondent bank. • Mandatory • Left-justified and space-filled |
| 39–40 | **Foreign Correspondent Bank Identification Number Qualifier** | 2 chars | Code [See codes](https://nacha-navigator.com/nacha-file-format#other-codes) | Mandatory | Identifies the kind of identification number that follows. • 01 = national clearing system number • 02 = BIC code • 03 = IBAN code • From March 19, 2027, 03 is deleted and a qualifier for non-bank foreign financial agencies is added |
| 41–74 | **Foreign Correspondent Bank Identification Number** | 34 chars | Alphanumeric | Mandatory | Identification number of the correspondent bank, of the kind named by the qualifier. • Mandatory • Left-justified and space-filled |
| 75–77 | **Foreign Correspondent Bank Branch Country Code** | 3 chars | Alphanumeric | Mandatory | ISO 3166 country code of the correspondent bank branch. • ISO 3166 country code, left-justified |
| 78–83 | **Reserved** | 6 chars | Alphanumeric | Not applicable: reserved, or filled in by the ACH Operator | Reserved for future use. Leave blank. • Space-filled |
| 84–87 | **Addenda Sequence Number** | 4 chars | Numeric | Mandatory | Position of this addenda among the type 18 addenda that belong to the same entry, starting at 0001. • Starts at 0001 and increases by one for each addenda of the entry • Right-justified and zero-filled |
| 88–94 | **Entry Detail Sequence Number** | 7 chars | Numeric | Mandatory | The last 7 digits of the Trace Number of the Entry Detail Record this addenda belongs to. • Links the addenda to its entry • Right-justified and zero-filled |

## Company/Batch Control Record

Contains the counts, hash totals, and total dollar amounts for the preceding batch.

**Company/Batch Control Record: positions, fields and rules**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 1 | **Record Type Code** | 1 char | Code Always 8 | Mandatory | Identifies the type of record in the file. • Always "8" for the Company/Batch Control Record |
| 2–4 | **Service Class Code** | 3 chars | Code [See codes](https://nacha-navigator.com/nacha-file-format#service-class-codes) | Mandatory | Identifies whether the batch contains debits, credits or both. • Must match the Service Class Code in the Company/Batch Header Record |
| 5–10 | **Entry/Addenda Count** | 6 chars | Numeric | Mandatory | The number of Entry Detail and Addenda Records in the batch. • Counts every type 6 and type 7 record in the batch • Right-justified and zero-filled |
| 11–20 | **Entry Hash** | 10 chars | Numeric | Mandatory | Sum of the 8-digit Receiving DFI Identifications (positions 4–11) of every entry in the batch. • If the sum has more than 10 digits, only the rightmost 10 are kept • Right-justified and zero-filled |
| 21–32 | **Total Debit Entry Dollar Amount** | 12 chars | Amount Cents, no decimal point | Mandatory | Total of all debit entries in the batch, in cents. • In cents, with no decimal point; zero when the batch has no debits • Right-justified and zero-filled |
| 33–44 | **Total Credit Entry Dollar Amount** | 12 chars | Amount Cents, no decimal point | Mandatory | Total of all credit entries in the batch, in cents. • In cents, with no decimal point; zero when the batch has no credits • Right-justified and zero-filled |
| 45–54 | **Company Identification** | 10 chars | Alphanumeric | Required | Identifies the Originator. • Must match the Company Identification (IAT: Originator Identification) in the Company/Batch Header Record |
| 55–73 | **Message Authentication Code** | 19 chars | Alphanumeric | Optional | Code used to authenticate the batch when the ODFI and RDFI use message authentication. • Optional; normally blank • Left-justified and space-filled |
| 74–79 | **Reserved** | 6 chars | Alphanumeric | Not applicable: reserved, or filled in by the ACH Operator | Reserved for future use. Leave blank. • Space-filled |
| 80–87 | **Originating DFI Identification** | 8 chars | Routing TTTTAAAA | Mandatory | First 8 digits of the routing number of the ODFI. • Must match the ODFI in the Company/Batch Header Record |
| 88–94 | **Batch Number** | 7 chars | Numeric | Mandatory | The number of the batch this record closes. • Must match the Batch Number in the Company/Batch Header Record • Right-justified and zero-filled |

### Accounting advice (ADV) batches

#### ADV: Automated Accounting Advices

9 fields

Batch control for ADV batches (Service Class Code 280); dollar totals are 20 digits long.

**Company/Batch Control Record — ADV: positions, fields and rules**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 1 | **Record Type Code** | 1 char | Code Always 8 | Mandatory | Identifies the type of record in the file. • Always "8" for the Company/Batch Control Record |
| 2–4 | **Service Class Code** | 3 chars | Code [See codes](https://nacha-navigator.com/nacha-file-format#service-class-codes) | Mandatory | Identifies whether the batch contains debits, credits or both. • Must match the Service Class Code in the Company/Batch Header Record |
| 5–10 | **Entry/Addenda Count** | 6 chars | Numeric | Mandatory | The number of Entry Detail and Addenda Records in the batch. • Counts every type 6 and type 7 record in the batch • Right-justified and zero-filled |
| 11–20 | **Entry Hash** | 10 chars | Numeric | Mandatory | Sum of the 8-digit Receiving DFI Identifications (positions 4–11) of every entry in the batch. • If the sum has more than 10 digits, only the rightmost 10 are kept • Right-justified and zero-filled |
| 21–40 | **Total Debit Entry Dollar Amount** | 20 chars | Amount Cents, no decimal point | Mandatory | Total of all debit advices in the batch, in cents. • 20 digits, in cents, zero-filled |
| 41–60 | **Total Credit Entry Dollar Amount** | 20 chars | Amount Cents, no decimal point | Mandatory | Total of all credit advices in the batch, in cents. • 20 digits, in cents, zero-filled |
| 61–79 | **ACH Operator Data** | 19 chars | Alphanumeric | Optional | For use by the ACH Operator that prepared the advice file. • Left-justified and space-filled |
| 80–87 | **Originating DFI Identification** | 8 chars | Routing TTTTAAAA | Mandatory | First 8 digits of the routing number of the ODFI. • Must match the ODFI in the Company/Batch Header Record |
| 88–94 | **Batch Number** | 7 chars | Numeric | Mandatory | The number of the batch this record closes. • Must match the Batch Number in the Company/Batch Header Record • Right-justified and zero-filled |

## File Control Record

Contains the counts, hash totals, and total dollar amounts for all batches in the file.

**File Control Record: positions, fields and rules**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 1 | **Record Type Code** | 1 char | Code Always 9 | Mandatory | Identifies the type of record in the file. • Always "9" for the File Control Record |
| 2–7 | **Batch Count** | 6 chars | Numeric | Mandatory | The number of batches (Company/Batch Header Records) in the file. • Right-justified and zero-filled |
| 8–13 | **Block Count** | 6 chars | Numeric | Mandatory | The number of 10-record blocks in the file, counting the File Header, File Control and block-fill records. • Equals the total number of records divided by 10 • Right-justified and zero-filled |
| 14–21 | **Entry/Addenda Count** | 8 chars | Numeric | Mandatory | The total number of Entry Detail and Addenda Records in the file. • Equals the sum of the Entry/Addenda Count fields of all Batch Control Records • Right-justified and zero-filled |
| 22–31 | **Entry Hash** | 10 chars | Numeric | Mandatory | Sum of the Entry Hash fields of all Company/Batch Control Records in the file. • If the sum has more than 10 digits, only the rightmost 10 are kept • Right-justified and zero-filled |
| 32–43 | **Total Debit Entry Dollar Amount in File** | 12 chars | Amount Cents, no decimal point | Mandatory | Total of all debit entries in the file, in cents. • Sum of the Total Debit Entry Dollar Amount fields of all Batch Control Records • In cents, with no decimal point; zero-filled |
| 44–55 | **Total Credit Entry Dollar Amount in File** | 12 chars | Amount Cents, no decimal point | Mandatory | Total of all credit entries in the file, in cents. • Sum of the Total Credit Entry Dollar Amount fields of all Batch Control Records • In cents, with no decimal point; zero-filled |
| 56–94 | **Reserved** | 39 chars | Alphanumeric | Not applicable: reserved, or filled in by the ACH Operator | Reserved for future use. Leave blank. • Space-filled |

### Accounting advice (ADV) files

#### ADV: Automated Accounting Advices

8 fields

File Control Record of an ADV file prepared by an ACH Operator; dollar totals are 20 digits long.

**File Control Record — ADV: positions, fields and rules**

| Position | Field | Length | Type | M/R/O | Description |
| --- | --- | --- | --- | --- | --- |
| 1 | **Record Type Code** | 1 char | Code Always 9 | Mandatory | Identifies the type of record in the file. • Always "9" for the File Control Record |
| 2–7 | **Batch Count** | 6 chars | Numeric | Mandatory | The number of batches (Company/Batch Header Records) in the file. • Right-justified and zero-filled |
| 8–13 | **Block Count** | 6 chars | Numeric | Mandatory | The number of 10-record blocks in the file, counting the File Header, File Control and block-fill records. • Equals the total number of records divided by 10 • Right-justified and zero-filled |
| 14–21 | **Entry/Addenda Count** | 8 chars | Numeric | Mandatory | The total number of Entry Detail and Addenda Records in the file. • Equals the sum of the Entry/Addenda Count fields of all Batch Control Records • Right-justified and zero-filled |
| 22–31 | **Entry Hash** | 10 chars | Numeric | Mandatory | Sum of the Entry Hash fields of all Company/Batch Control Records in the file. • If the sum has more than 10 digits, only the rightmost 10 are kept • Right-justified and zero-filled |
| 32–51 | **Total Debit Entry Dollar Amount in File** | 20 chars | Amount Cents, no decimal point | Mandatory | Total of all debit advices in the file, in cents. • 20 digits, in cents, zero-filled |
| 52–71 | **Total Credit Entry Dollar Amount in File** | 20 chars | Amount Cents, no decimal point | Mandatory | Total of all credit advices in the file, in cents. • 20 digits, in cents, zero-filled |
| 72–94 | **Reserved** | 23 chars | Alphanumeric | Not applicable: reserved, or filled in by the ACH Operator | Reserved for future use. Leave blank. • Space-filled |

## Block-fill records

A file’s record count must be a multiple of 10 (the blocking factor in the File Header). When it isn’t, records of 94 nines follow the File Control to fill the last block. They carry no data, and the File Control’s block count includes them.

`9999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999`

Code tables

## The codes, decoded

The values that go in the code fields above, from the same tables the viewer uses to explain a file. Every code row can be linked to directly: [#return-r01](https://nacha-navigator.com/nacha-file-format#return-r01) goes to R01.

### Transaction codes

Entry Detail: positions 2–3. The first digit is the account type; the second says whether it is a credit (1–4) or a debit (5–9), and whether it is live, a prenote, zero-dollar or a return. [ACH transaction codes](https://nacha-navigator.com/ach-transaction-codes) explains how the digits combine, with prenotes, returns and the codes a reversal flips.

| Code | Meaning | Account | Direction |
| --- | --- | --- | --- |
| 21 | Return or NOC of a checking credit (original code 22, 23 or 24) | Checking | Credit |
| 22 | Checking credit (deposit) | Checking | Credit |
| 23 | Prenote: checking credit (also DNE and ENR non-dollar entries) | Checking | Credit |
| 24 | Zero-dollar checking credit with remittance data (CCD, CTX, IAT); ACK and ATX acknowledgments | Checking | Credit |
| 26 | Return or NOC of a checking debit (original code 27, 28 or 29) | Checking | Debit |
| 27 | Checking debit (payment) | Checking | Debit |
| 28 | Prenote: checking debit | Checking | Debit |
| 29 | Zero-dollar checking debit with remittance data (CCD, CTX, IAT) | Checking | Debit |
| 31 | Return or NOC of a savings credit (original code 32, 33 or 34) | Savings | Credit |
| 32 | Savings credit (deposit) | Savings | Credit |
| 33 | Prenote: savings credit (also DNE and ENR non-dollar entries) | Savings | Credit |
| 34 | Zero-dollar savings credit with remittance data (CCD, CTX, IAT); ACK and ATX acknowledgments | Savings | Credit |
| 36 | Return or NOC of a savings debit (original code 37, 38 or 39) | Savings | Debit |
| 37 | Savings debit (payment) | Savings | Debit |
| 38 | Prenote: savings debit | Savings | Debit |
| 39 | Zero-dollar savings debit with remittance data (CCD, CTX, IAT) | Savings | Debit |
| 41 | Return or NOC of a general ledger credit (original code 42, 43 or 44) | General ledger | Credit |
| 42 | General ledger credit (deposit) | General ledger | Credit |
| 43 | Prenote: general ledger credit | General ledger | Credit |
| 44 | Zero-dollar general ledger credit with remittance data (CCD, CTX) | General ledger | Credit |
| 46 | Return or NOC of a general ledger debit (original code 47, 48 or 49) | General ledger | Debit |
| 47 | General ledger debit (payment) | General ledger | Debit |
| 48 | Prenote: general ledger debit | General ledger | Debit |
| 49 | Zero-dollar general ledger debit with remittance data (CCD, CTX) | General ledger | Debit |
| 51 | Return or NOC of a loan credit (original code 52, 53 or 54) | Loan | Credit |
| 52 | Loan account credit (deposit to a loan) | Loan | Credit |
| 53 | Prenote: loan credit | Loan | Credit |
| 54 | Zero-dollar loan credit with remittance data (CCD, CTX) | Loan | Credit |
| 55 | Loan account debit (reversals only) | Loan | Debit |
| 56 | Return or NOC of a loan debit (original code 55) | Loan | Debit |
| 81 | ADV: credit for ACH debits originated | Accounting (ADV) | Credit |
| 82 | ADV: debit for ACH credits originated | Accounting (ADV) | Debit |
| 83 | ADV: credit for ACH credits received | Accounting (ADV) | Credit |
| 84 | ADV: debit for ACH debits received | Accounting (ADV) | Debit |
| 85 | ADV: credit for ACH credits in rejected batches | Accounting (ADV) | Credit |
| 86 | ADV: debit for ACH debits in rejected batches | Accounting (ADV) | Debit |
| 87 | ADV: summary credit for respondent ACH activity | Accounting (ADV) | Credit |
| 88 | ADV: summary debit for respondent ACH activity | Accounting (ADV) | Debit |

### Standard Entry Class (SEC) codes

Company/Batch Header: positions 51–53. The SEC code decides the Entry Detail layout and which addenda an entry may carry.

| SEC | Name | Used for | Moves | Addenda |
| --- | --- | --- | --- | --- |
| [ACK on PayOps Kit](https://payopskit.com/sec-codes/ack) | ACH Payment Acknowledgment | Zero-dollar acknowledgment of a CCD credit, sent by the RDFI. | Zero-dollar | Up to 1 (type 05) |
| [ADV on PayOps Kit](https://payopskit.com/sec-codes/adv) | Automated Accounting Advice | Non-monetary accounting information an ACH Operator sends to a DFI that asked for it (Service Class Code 280). | Accounting advice (non-monetary) | None |
| [ARC on PayOps Kit](https://payopskit.com/sec-codes/arc) | Accounts Receivable Entry | One-time debit converted from an eligible check received by mail or delivery service, at a dropbox, or in person to pay a bill at a staffed location. | Debits | None |
| [ATX on PayOps Kit](https://payopskit.com/sec-codes/atx) | Financial EDI Acknowledgment | Zero-dollar acknowledgment of a CTX credit, sent by the RDFI. | Zero-dollar | Up to 9,999 (type 05) |
| [BOC on PayOps Kit](https://payopskit.com/sec-codes/boc) | Back Office Conversion Entry | One-time debit converted in the back office from an eligible check presented at a point of purchase or a staffed bill-payment location. | Debits | None |
| [CCD on PayOps Kit](https://payopskit.com/sec-codes/ccd) | Corporate Credit or Debit Entry | Credit or debit between business accounts. | Credits and debits | Up to 1 (type 05) |
| [CIE on PayOps Kit](https://payopskit.com/sec-codes/cie) | Customer Initiated Entry | Credit initiated by a consumer, such as an online bill payment. | Credits | Up to 1 (type 05) |
| [COR on PayOps Kit](https://payopskit.com/sec-codes/cor) | Notification of Change or Refused Notification of Change | Zero-dollar entry correcting information in an earlier entry. | Zero-dollar | 1 required (type 98) |
| [CTX on PayOps Kit](https://payopskit.com/sec-codes/ctx) | Corporate Trade Exchange | Business-to-business payment with up to 9,999 addenda of EDI remittance data. | Credits and debits | Up to 9,999 (type 05) |
| [DNE on PayOps Kit](https://payopskit.com/sec-codes/dne) | Death Notification Entry | Zero-dollar notice from a Federal Government agency that a benefit recipient has died. | Zero-dollar | 1 required (type 05) |
| [ENR on PayOps Kit](https://payopskit.com/sec-codes/enr) | Automated Enrollment Entry | Zero-dollar entry enrolling a beneficiary in Federal Government direct deposit. | Zero-dollar | 1 to 9,999 (type 05) |
| [IAT on PayOps Kit](https://payopskit.com/sec-codes/iat) | International ACH Transaction | Entry involving a financial agency outside the United States. | Credits and debits | 7 to 14 (type 10–18) |
| [MTE on PayOps Kit](https://payopskit.com/sec-codes/mte) | Machine Transfer Entry | Entry initiated at an ATM or other electronic terminal. | Credits and debits | 1 required (type 02) |
| [POP on PayOps Kit](https://payopskit.com/sec-codes/pop) | Point-of-Purchase Entry | One-time debit converted on the spot from an eligible check presented at a point of purchase or a staffed bill-payment location. | Debits | None |
| [POS on PayOps Kit](https://payopskit.com/sec-codes/pos) | Point-of-Sale Entry | Consumer debit at an electronic terminal to pay for a purchase or withdraw cash, and related adjusting or other credits. | Credits and debits | 1 required (type 02) |
| [PPD on PayOps Kit](https://payopskit.com/sec-codes/ppd) | Prearranged Payment and Deposit Entry | Consumer credit or debit authorized in advance, once or recurring, e.g. payroll direct deposit or a recurring bill. | Credits and debits | Up to 1 (type 05) |
| [RCK on PayOps Kit](https://payopskit.com/sec-codes/rck) | Re-presented Check Entry | Returned check re-presented as a debit. | Debits | None |
| [SHR on PayOps Kit](https://payopskit.com/sec-codes/shr) | Shared Network Transaction | Consumer debit at a point-of-sale terminal in a shared network where the ODFI and RDFI have an agreement beyond the Rules, and related credits. | Credits and debits | 1 required (type 02) |
| [TEL on PayOps Kit](https://payopskit.com/sec-codes/tel) | Telephone-Initiated Entry | Consumer debit authorized orally over the telephone. | Debits | None |
| [TRC on PayOps Kit](https://payopskit.com/sec-codes/trc) | Check Truncation Entry | Debit for one check truncated (kept by the collecting bank) under a check truncation program. | Debits | None |
| [TRX on PayOps Kit](https://payopskit.com/sec-codes/trx) | Check Truncation Entries Exchange | Debit for several truncated checks drawn on the same paying bank, listed in addenda records. | Debits | Up to 9,999 (type 05) |
| [WEB on PayOps Kit](https://payopskit.com/sec-codes/web) | Internet-Initiated/Mobile Entry | Consumer debit authorized online or on a mobile device, or a person-to-person credit. | Credits and debits | Up to 1 (type 05) |
| [XCK on PayOps Kit](https://payopskit.com/sec-codes/xck) | Destroyed Check Entry | Debit collecting an eligible check that was lost or destroyed, or damaged so it cannot be processed; the batch description is NO CHECK. | Debits | None |

### Service class codes

Company/Batch Header: positions 2–4; Company/Batch Control: positions 2–4. Whether a batch holds credits, debits or both.

| Code | Meaning |
| --- | --- |
| 200 | ACH entries mixed debits and credits |
| 220 | ACH credits only |
| 225 | ACH debits only |
| 280 | ACH automated accounting advices (ADV) |

### Return reason codes

Addenda (type 99): positions 4–6, 57–58 and 77–78. Why an RDFI returned an entry, plus the dishonored and contested return codes. R90 can be used from March 17, 2028; until then, a return made on an OFAC instruction uses R16.

| Code | Reason | Note |
| --- | --- | --- |
| [R01 on PayOps Kit](https://payopskit.com/ach-return-codes/r01) | Insufficient Funds |  |
| [R02 on PayOps Kit](https://payopskit.com/ach-return-codes/r02) | Account Closed |  |
| [R03 on PayOps Kit](https://payopskit.com/ach-return-codes/r03) | No Account/Unable to Locate Account |  |
| [R04 on PayOps Kit](https://payopskit.com/ach-return-codes/r04) | Invalid Account Number Structure |  |
| [R05 on PayOps Kit](https://payopskit.com/ach-return-codes/r05) | Unauthorized Debit to Consumer Account Using Corporate SEC Code |  |
| [R06 on PayOps Kit](https://payopskit.com/ach-return-codes/r06) | Returned per ODFI's Request |  |
| [R07 on PayOps Kit](https://payopskit.com/ach-return-codes/r07) | Authorization Revoked by Customer |  |
| [R08 on PayOps Kit](https://payopskit.com/ach-return-codes/r08) | Payment Stopped |  |
| [R09 on PayOps Kit](https://payopskit.com/ach-return-codes/r09) | Uncollected Funds |  |
| [R10 on PayOps Kit](https://payopskit.com/ach-return-codes/r10) | Customer Advises Originator is Not Known to Receiver and/or Originator is Not Authorized by Receiver to Debit Receiver's Account |  |
| [R11 on PayOps Kit](https://payopskit.com/ach-return-codes/r11) | Customer Advises Entry Not in Accordance with the Terms of the Authorization |  |
| [R12 on PayOps Kit](https://payopskit.com/ach-return-codes/r12) | Account Sold to Another DFI |  |
| [R13 on PayOps Kit](https://payopskit.com/ach-return-codes/r13) | Invalid ACH Routing Number |  |
| [R14 on PayOps Kit](https://payopskit.com/ach-return-codes/r14) | Representative Payee Deceased or Unable to Continue in That Capacity |  |
| [R15 on PayOps Kit](https://payopskit.com/ach-return-codes/r15) | Beneficiary or Account Holder (Other Than a Representative Payee) Deceased |  |
| [R16 on PayOps Kit](https://payopskit.com/ach-return-codes/r16) | Account Frozen/Entry Returned per OFAC Instruction | Becomes "Account Frozen" on March 17, 2028; sanctions returns move to R90 |
| [R17 on PayOps Kit](https://payopskit.com/ach-return-codes/r17) | File Record Edit Criteria/Entry Initiated Under Questionable Circumstances/Return of Improperly-Initiated Reversal | Since October 1, 2024 also for an entry the RDFI believes fraudulent, with QUESTIONABLE in the first 12 positions of the addenda information |
| [R18 on PayOps Kit](https://payopskit.com/ach-return-codes/r18) | Improper Effective Entry Date |  |
| [R19 on PayOps Kit](https://payopskit.com/ach-return-codes/r19) | Amount Field Error |  |
| [R20 on PayOps Kit](https://payopskit.com/ach-return-codes/r20) | Non-Transaction Account |  |
| [R21 on PayOps Kit](https://payopskit.com/ach-return-codes/r21) | Invalid Company Identification |  |
| [R22 on PayOps Kit](https://payopskit.com/ach-return-codes/r22) | Invalid Individual ID Number |  |
| [R23 on PayOps Kit](https://payopskit.com/ach-return-codes/r23) | Credit Entry Refused by Receiver |  |
| [R24 on PayOps Kit](https://payopskit.com/ach-return-codes/r24) | Duplicate Entry |  |
| [R25 on PayOps Kit](https://payopskit.com/ach-return-codes/r25) | Addenda Error |  |
| [R26 on PayOps Kit](https://payopskit.com/ach-return-codes/r26) | Mandatory Field Error |  |
| [R27 on PayOps Kit](https://payopskit.com/ach-return-codes/r27) | Trace Number Error |  |
| [R28 on PayOps Kit](https://payopskit.com/ach-return-codes/r28) | Routing Number Check Digit Error |  |
| [R29 on PayOps Kit](https://payopskit.com/ach-return-codes/r29) | Corporate Customer Advises Not Authorized |  |
| [R30 on PayOps Kit](https://payopskit.com/ach-return-codes/r30) | RDFI Not Participant in Check Truncation Program |  |
| [R31 on PayOps Kit](https://payopskit.com/ach-return-codes/r31) | Permissible Return Entry | CCD and CTX only |
| [R32 on PayOps Kit](https://payopskit.com/ach-return-codes/r32) | RDFI Non-Settlement |  |
| [R33 on PayOps Kit](https://payopskit.com/ach-return-codes/r33) | Return of XCK Entry |  |
| [R34 on PayOps Kit](https://payopskit.com/ach-return-codes/r34) | Limited Participation DFI |  |
| [R35 on PayOps Kit](https://payopskit.com/ach-return-codes/r35) | Return of Improper Debit Entry |  |
| [R36 on PayOps Kit](https://payopskit.com/ach-return-codes/r36) | Return of Improper Credit Entry |  |
| [R37 on PayOps Kit](https://payopskit.com/ach-return-codes/r37) | Source Document Presented for Payment |  |
| [R38 on PayOps Kit](https://payopskit.com/ach-return-codes/r38) | Stop Payment on Source Document |  |
| [R39 on PayOps Kit](https://payopskit.com/ach-return-codes/r39) | Improper Source Document/Source Document Presented for Payment |  |
| [R40 on PayOps Kit](https://payopskit.com/ach-return-codes/r40) | Return of ENR Entry by Federal Government Agency | ENR only |
| [R41 on PayOps Kit](https://payopskit.com/ach-return-codes/r41) | Invalid Transaction Code | ENR only |
| [R42 on PayOps Kit](https://payopskit.com/ach-return-codes/r42) | Routing Number/Check Digit Error | ENR only |
| [R43 on PayOps Kit](https://payopskit.com/ach-return-codes/r43) | Invalid DFI Account Number | ENR only |
| [R44 on PayOps Kit](https://payopskit.com/ach-return-codes/r44) | Invalid Individual ID Number/Identification Number | ENR only |
| [R45 on PayOps Kit](https://payopskit.com/ach-return-codes/r45) | Invalid Individual Name/Company Name | ENR only |
| [R46 on PayOps Kit](https://payopskit.com/ach-return-codes/r46) | Invalid Representative Payee Indicator | ENR only |
| [R47 on PayOps Kit](https://payopskit.com/ach-return-codes/r47) | Duplicate Enrollment | ENR only |
| [R50 on PayOps Kit](https://payopskit.com/ach-return-codes/r50) | State Law Affecting RCK Acceptance |  |
| [R51 on PayOps Kit](https://payopskit.com/ach-return-codes/r51) | Item Related to RCK Entry is Ineligible or RCK Entry is Improper |  |
| [R52 on PayOps Kit](https://payopskit.com/ach-return-codes/r52) | Stop Payment on Item Related to RCK Entry |  |
| [R53 on PayOps Kit](https://payopskit.com/ach-return-codes/r53) | Item and RCK Entry Presented for Payment |  |
| [R61 on PayOps Kit](https://payopskit.com/ach-return-codes/r61) | Misrouted Return | Dishonored return (sent by the ODFI) |
| [R62 on PayOps Kit](https://payopskit.com/ach-return-codes/r62) | Return of Erroneous or Reversing Debit | Dishonored return (sent by the ODFI) |
| [R67 on PayOps Kit](https://payopskit.com/ach-return-codes/r67) | Duplicate Return | Dishonored return (sent by the ODFI) |
| [R68 on PayOps Kit](https://payopskit.com/ach-return-codes/r68) | Untimely Return | Dishonored return (sent by the ODFI) |
| [R69 on PayOps Kit](https://payopskit.com/ach-return-codes/r69) | Field Error(s) | Dishonored return (sent by the ODFI) |
| [R70 on PayOps Kit](https://payopskit.com/ach-return-codes/r70) | Permissible Return Entry Not Accepted/Return Not Requested by ODFI | Dishonored return (sent by the ODFI) |
| [R71 on PayOps Kit](https://payopskit.com/ach-return-codes/r71) | Misrouted Dishonored Return | Contested dishonored return (sent by the RDFI) |
| [R72 on PayOps Kit](https://payopskit.com/ach-return-codes/r72) | Untimely Dishonored Return | Contested dishonored return (sent by the RDFI) |
| [R73 on PayOps Kit](https://payopskit.com/ach-return-codes/r73) | Timely Original Return | Contested dishonored return (sent by the RDFI) |
| [R74 on PayOps Kit](https://payopskit.com/ach-return-codes/r74) | Corrected Return | Contested dishonored return (sent by the RDFI) |
| [R75 on PayOps Kit](https://payopskit.com/ach-return-codes/r75) | Return Not a Duplicate | Contested dishonored return (sent by the RDFI) |
| [R76 on PayOps Kit](https://payopskit.com/ach-return-codes/r76) | No Errors Found | Contested dishonored return (sent by the RDFI) |
| [R77 on PayOps Kit](https://payopskit.com/ach-return-codes/r77) | Non-Acceptance of R62 Dishonored Return | Contested dishonored return (sent by the RDFI) |
| [R80 on PayOps Kit](https://payopskit.com/ach-return-codes/r80) | IAT Entry Coding Error | IAT only |
| [R81 on PayOps Kit](https://payopskit.com/ach-return-codes/r81) | Non-Participant in IAT Program | IAT only |
| [R82 on PayOps Kit](https://payopskit.com/ach-return-codes/r82) | Invalid Foreign Receiving DFI Identification | IAT only |
| [R83 on PayOps Kit](https://payopskit.com/ach-return-codes/r83) | Foreign Receiving DFI Unable to Settle | IAT only |
| [R84 on PayOps Kit](https://payopskit.com/ach-return-codes/r84) | Entry Not Processed by Gateway | IAT only |
| [R85 on PayOps Kit](https://payopskit.com/ach-return-codes/r85) | Incorrectly Coded Outbound International Payment | Gateway; a non-IAT entry that should have been IAT |
| [R90 on PayOps Kit](https://payopskit.com/ach-return-codes/r90) | Entry Returned Due to RDFI's Sanctions Compliance Obligations | Effective March 17, 2028 |

### Change codes (notifications of change)

Addenda (type 98): positions 4–6 and 65–67. What an RDFI is correcting, and how the corrected data is laid out.

| Code | Change | Corrected data |
| --- | --- | --- |
| [C01 on PayOps Kit](https://payopskit.com/noc-codes/c01) | Incorrect DFI Account Number | Correct DFI Account Number in the first 17 positions |
| [C02 on PayOps Kit](https://payopskit.com/noc-codes/c02) | Incorrect Routing Number | Correct routing number (9 digits, with check digit) in the first 9 positions |
| [C03 on PayOps Kit](https://payopskit.com/noc-codes/c03) | Incorrect Routing Number and Incorrect DFI Account Number | Correct routing number (9), three blanks, then the correct DFI Account Number (17) |
| [C05 on PayOps Kit](https://payopskit.com/noc-codes/c05) | Incorrect Transaction Code | Correct Transaction Code in the first 2 positions |
| [C06 on PayOps Kit](https://payopskit.com/noc-codes/c06) | Incorrect DFI Account Number and Incorrect Transaction Code | Correct DFI Account Number in positions 1–17, three blanks (18–20), then the correct Transaction Code in 21–22 |
| [C07 on PayOps Kit](https://payopskit.com/noc-codes/c07) | Incorrect Routing Number, Incorrect DFI Account Number, and Incorrect Transaction Code | Correct routing number (9), DFI Account Number (17) and Transaction Code (2) |
| [C08 on PayOps Kit](https://payopskit.com/noc-codes/c08) | Incorrect Receiving DFI Identification (IAT only) | Correct Receiving DFI Identification. Published tables say it fills the first 34 positions, more than this 29-character field holds |
| [C09 on PayOps Kit](https://payopskit.com/noc-codes/c09) | Incorrect Individual Identification Number/Incorrect Receiver Identification Number | Correct Individual Identification Number or Receiver Identification Number in the first 22 positions |
| [C13 on PayOps Kit](https://payopskit.com/noc-codes/c13) | Addenda Format Error | No fixed layout: the code reports addenda information that was unclear or badly formatted |
| [C14 on PayOps Kit](https://payopskit.com/noc-codes/c14) | Incorrect SEC Code for Outbound International Payment | "IAT" in the first 3 positions |
| [C61 on PayOps Kit](https://payopskit.com/noc-codes/c61) | Misrouted Notification of Change | Refused NOC: sent back by the ODFI |
| [C62 on PayOps Kit](https://payopskit.com/noc-codes/c62) | Incorrect Trace Number | Refused NOC: sent back by the ODFI |
| [C63 on PayOps Kit](https://payopskit.com/noc-codes/c63) | Incorrect Company Identification Number | Refused NOC: sent back by the ODFI |
| [C64 on PayOps Kit](https://payopskit.com/noc-codes/c64) | Incorrect Individual Identification Number/Identification Number | Refused NOC: sent back by the ODFI |
| [C65 on PayOps Kit](https://payopskit.com/noc-codes/c65) | Incorrectly Formatted Corrected Data | Refused NOC: sent back by the ODFI |
| [C66 on PayOps Kit](https://payopskit.com/noc-codes/c66) | Incorrect Discretionary Data | Refused NOC: sent back by the ODFI |
| [C67 on PayOps Kit](https://payopskit.com/noc-codes/c67) | Routing Number Not From Original Entry Detail Record | Refused NOC: sent back by the ODFI |
| [C68 on PayOps Kit](https://payopskit.com/noc-codes/c68) | DFI Account Number Not From Original Entry Detail Record | Refused NOC: sent back by the ODFI |
| [C69 on PayOps Kit](https://payopskit.com/noc-codes/c69) | Incorrect Transaction Code | Refused NOC: sent back by the ODFI |

#### Retired change codes

No longer in the Nacha Rules, so a new NOC may not use them. An old file can still carry one: the NACHA Viewer decodes it and [reports it as retired](https://nacha-navigator.com/nacha-file-errors#ad-change-code).

| Code | Former title | Status |
| --- | --- | --- |
| C04 | Incorrect Individual Name/Receiving Company Name | Removed from the Nacha Rules |
| C10 | Incorrect Company Name | Removed from the Nacha Rules in 2003 |
| C11 | Incorrect Company Identification | Removed from the Nacha Rules in 2003 |
| C12 | Incorrect Company Name and Company Identification | Removed from the Nacha Rules in 2003 |

### Addenda type codes

Addenda: positions 2–3. Each type has its own layout, listed under Addenda Record above.

| Code | Meaning |
| --- | --- |
| 02 | Point-of-sale terminal information (POS, SHR, MTE) |
| 05 | Payment related information |
| 10 | IAT: transaction type, foreign amount and receiver name |
| 11 | IAT: originator name and street address |
| 12 | IAT: originator city, state, country and postal code |
| 13 | IAT: originating DFI name, identification and branch country |
| 14 | IAT: receiving DFI name, identification and branch country |
| 15 | IAT: receiver identification number and street address |
| 16 | IAT: receiver city, state, country and postal code |
| 17 | IAT: payment related information (optional) |
| 18 | IAT: foreign correspondent bank (optional) |
| 98 | Notification of Change or refused Notification of Change |
| 99 | Return, dishonored return or contested dishonored return |

### Other codes

Smaller code lists used by specific fields and entry types.

#### Originator status codes

Company/Batch Header: position 79

| Code | Meaning |
| --- | --- |
| 0 | ADV file prepared by an ACH Operator |
| 1 | Depository financial institution bound by the Nacha Rules |
| 2 | Federal Government entity or agency not subject to the Nacha Rules |

#### Addenda record indicator

Entry Detail: position 79

| Code | Meaning |
| --- | --- |
| 0 | No addenda record follows |
| 1 | One or more addenda records follow |

#### Payment type codes (optional)

Entry Detail (WEB, TEL): positions 77–78

| Code | Meaning |
| --- | --- |
| R | Recurring |
| S | Single entry |

#### Card transaction type codes

Entry Detail (POS, SHR): positions 77–78

| Code | Meaning |
| --- | --- |
| 01 | Purchase of goods or services |
| 02 | Cash |
| 03 | Return reversal |
| 11 | Purchase reversal |
| 12 | Cash reversal |
| 13 | Return |
| 21 | Adjustment |
| 99 | Miscellaneous transaction |

#### IAT transaction type codes

Addenda (type 10): positions 4–6

| Code | Meaning |
| --- | --- |
| ANN | Annuity |
| BUS | Business/Commercial |
| DEP | Deposit |
| LOA | Loan |
| MIS | Miscellaneous |
| MOR | Mortgage |
| PEN | Pension |
| REM | Remittance |
| RLS | Rent/Lease |
| SAL | Salary/Payroll |
| TAX | Tax |
| ARC | Accounts Receivable Check |
| BOC | Back Office Conversion |
| MTE | Machine Transfer Entry |
| POP | Point-of-Purchase |
| POS | Point-of-Sale |
| RCK | Re-presented Check |
| SHR | Shared Network Transaction |
| TEL | Telephone-Initiated |
| WEB | Internet-Initiated/Mobile |

#### Foreign exchange indicators

Company/Batch Header (IAT): positions 21–22

| Code | Meaning |
| --- | --- |
| FV | Fixed-to-variable: originated as a fixed amount, received after currency conversion |
| VF | Variable-to-fixed: converted at a rate so that a fixed amount is received |
| FF | Fixed-to-fixed: same currency at both ends, no conversion |

#### Foreign exchange reference indicators

Company/Batch Header (IAT): position 23

| Code | Meaning |
| --- | --- |
| 1 | Foreign exchange rate |
| 2 | Foreign exchange reference number |
| 3 | Space-filled (no reference) |

#### ID number qualifiers

Addenda (type 13, type 14, type 18): positions 39–40

| Code | Meaning |
| --- | --- |
| 01 | National clearing system number |
| 02 | BIC code |
| 03 | IBAN code (deleted from March 19, 2027) |

#### OFAC screening indicators

Entry Detail (IAT): positions 77 and 78

| Code | Meaning |
| --- | --- |
| 0 | Not flagged by OFAC screening |
| 1 | Flagged as a possible OFAC match |

## The official rules

This reference follows the record formats in the Nacha Operating Rules. Nacha publishes the rules and updates them every year; check the current edition before you build or certify a file. NACHA Navigator is independent and not affiliated with or endorsed by Nacha, and this page is general information, not legal or compliance advice.

[Nacha Operating Rules](https://www.nacha.org/rules) [Open the NACHA Viewer](https://nacha-navigator.com/)