Skip to content

Reference

NACHA file format: ACH record layouts

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.

Generated from the field definitions the NACHA Viewer validates against: 46 record layouts, 485 fields.

On this page

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. 1File HeaderOnce, on the first lineWho sent the file, to whom, and when.
  2. 5Company/Batch HeaderStarts each batchThe company, the SEC code and the effective date of the entries that follow.
  3. 6Entry DetailOne per paymentTransaction code, routing and account number, amount, receiver and trace number.
  4. 7AddendaOptional, after its entryRemittance details, or the reason for a return or a notification of change.
  5. 8Company/Batch ControlCloses each batchEntry and addenda count, entry hash, and debit and credit totals.
  6. 9File ControlOnce, after the last batchBatch, block and entry counts, entry hash and totals for the file.
  7. 9…Block fillOnly if neededLines of 94 nines that pad the file to a multiple of 10 records.
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.
  • Routing & IDs
  • Amounts
  • Dates
  • Names & text
  • Codes
  • Reserved
  • 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. The dots above stand for spaces.
  • 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.

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.
  • 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.
  • 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.
1

File Header Record

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

File Header Record: positions, fields and rules
PositionFieldLengthTypeM/R/ODescription
1Record Type Code1 charCodeAlways 1MandatoryIdentifies the type of record in the file.
  • Always "1" for the File Header Record
2–3Priority Code2 charsCodeAlways 01RequiredIdentifies the priority of the file.
  • Only "01" is used
4–13Immediate Destination10 charsRoutingbTTTTAAAACMandatoryRouting 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–23Immediate Origin10 charsRoutingbTTTTAAAACMandatoryRouting 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–29File Creation Date6 charsDateYYMMDDMandatoryThe date on which the file was created.
  • Format YYMMDD
  • Must be a valid calendar date
30–33File Creation Time4 charsTimeHHMMOptionalThe time at which the file was created.
  • Format HHMM, 24-hour clock
  • Optional; may be left blank
34File ID Modifier1 charAlphanumericMandatoryDistinguishes 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–37Record Size3 charsCodeAlways 094MandatoryThe number of characters in each record.
  • Always "094"
38–39Blocking Factor2 charsCodeAlways 10MandatoryThe 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
40Format Code1 charCodeAlways 1MandatoryIdentifies the format of the file.
  • Always "1"
41–63Immediate Destination Name23 charsAlphanumericOptionalName of the ACH Operator or receiving point to which the file is sent.
  • Optional
  • Left-justified and space-filled
64–86Immediate Origin Name23 charsAlphanumericOptionalName of the sending point or originating company that created the file.
  • Optional
  • Left-justified and space-filled
87–94Reference Code8 charsAlphanumericOptionalFor the originator's own use to describe or identify the file.
  • Optional; often blank
  • Left-justified and space-filled
5

Company/Batch Header Record

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

Company/Batch Header Record: positions, fields and rules
PositionFieldLengthTypeM/R/ODescription
1Record Type Code1 charCodeAlways 5MandatoryIdentifies the type of record in the file.
  • Always "5" for the Company/Batch Header Record
2–4Service Class Code3 charsCodeSee codesMandatoryIdentifies 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–20Company Name16 charsAlphanumericMandatoryName 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–40Company Discretionary Data20 charsAlphanumericOptionalFor the Originator or ODFI to use as they agree, e.g. internal reference data.
  • Optional
  • Left-justified and space-filled
41–50Company Identification10 charsAlphanumericMandatoryIdentifies 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–53Standard Entry Class Code3 charsCodeSee codesMandatoryThree-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–63Company Entry Description10 charsAlphanumericMandatoryTells the Receiver what the entries are for, e.g. PAYROLL or GAS BILL.
  • Usually printed on the Receiver's bank statement
  • Some values are required by the Rules: REVERSAL (reversing entries), RECLAIM (reclamations), RETURN FEE, RETRY PYMT (reinitiated entries), REDEPCHECK (RCK), AUTOENROLL (ENR), HCCLAIMPMT (healthcare claim payments), ACCTVERIFY (micro-entries)
  • From March 20, 2026: PAYROLL for PPD wage and salary credits, PURCHASE for e-commerce purchase debits
  • Left-justified and space-filled
64–69Company Descriptive Date6 charsAlphanumericOptionalA 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"
  • Same Day ACH convention: "SDHHMM" (e.g. SD1300) asks for same-day settlement at that time
  • Left-justified and space-filled
70–75Effective Entry Date6 charsDateYYMMDDRequiredThe 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–78Settlement Date (Julian)3 charsJulian dayDDDNot applicable: reserved, or filled in by the ACH OperatorDay 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
79Originator Status Code1 charCodeSee codesMandatoryIdentifies 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–87Originating DFI Identification8 charsRoutingTTTTAAAAMandatoryFirst 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–94Batch Number7 charsNumericMandatoryNumber 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.

IATInternational ACH Transaction17 fields

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

Company/Batch Header Record — IAT: positions, fields and rules
PositionFieldLengthTypeM/R/ODescription
1Record Type Code1 charCodeAlways 5MandatoryIdentifies the type of record in the file.
  • Always "5" for the Company/Batch Header Record
2–4Service Class Code3 charsCodeSee codesMandatoryIdentifies 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–20IAT Indicator16 charsAlphanumericOptionalBlank in IAT batches. Contains "IATCOR" in a batch of IAT Notifications of Change.
  • Left-justified and space-filled
21–22Foreign Exchange Indicator2 charsCodeSee codesMandatoryHow 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
23Foreign Exchange Reference Indicator1 charCodeSee codesMandatoryIdentifies what the Foreign Exchange Reference field contains.
  • 1 = foreign exchange rate
  • 2 = foreign exchange reference number
  • 3 = space-filled
24–38Foreign Exchange Reference15 charsAlphanumericRequiredThe exchange rate or reference number named by the indicator; blank when the indicator is 3.
  • Left-justified and space-filled
39–40ISO Destination Country Code2 charsAlphanumericMandatoryTwo-letter ISO 3166 code of the country in which the entry is to be received.
  • Uppercase letters, e.g. US, CA, MX
41–50Originator Identification10 charsAlphanumericMandatoryIdentifies the Originator (the IAT equivalent of Company Identification).
  • Must match the Company Identification in the Batch Control Record
51–53Standard Entry Class Code3 charsCodeSee codesMandatoryThree-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–63Company Entry Description10 charsAlphanumericMandatoryTells the Receiver what the entries are for, e.g. PAYROLL or GAS BILL.
  • Usually printed on the Receiver's bank statement
  • Some values are required by the Rules: REVERSAL (reversing entries), RECLAIM (reclamations), RETURN FEE, RETRY PYMT (reinitiated entries), REDEPCHECK (RCK), AUTOENROLL (ENR), HCCLAIMPMT (healthcare claim payments), ACCTVERIFY (micro-entries)
  • From March 20, 2026: PAYROLL for PPD wage and salary credits, PURCHASE for e-commerce purchase debits
  • Left-justified and space-filled
64–66ISO Originating Currency Code3 charsAlphanumericMandatoryThree-letter ISO 4217 code of the currency in which the entry was originated.
  • Uppercase letters, e.g. USD
67–69ISO Destination Currency Code3 charsAlphanumericMandatoryThree-letter ISO 4217 code of the currency in which the entry is to be received.
  • Uppercase letters, e.g. CAD
70–75Effective Entry Date6 charsDateYYMMDDRequiredThe 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–78Settlement Date (Julian)3 charsJulian dayDDDNot applicable: reserved, or filled in by the ACH OperatorDay 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
79Originator Status Code1 charCodeSee codesMandatoryIdentifies 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–87Go Identification/Originating DFI Identification8 charsRoutingTTTTAAAAMandatoryFor 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–94Batch Number7 charsNumericMandatoryNumber 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
6

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
PositionFieldLengthTypeM/R/ODescription
1Record Type Code1 charCodeAlways 6MandatoryIdentifies the type of record in the file.
  • Always "6" for the Entry Detail Record
2–3Transaction Code2 charsCodeSee codesMandatoryIdentifies 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–11Receiving DFI Identification8 charsRoutingTTTTAAAAMandatoryFirst 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
12Check Digit1 charNumericMandatoryThe 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–29DFI Account Number17 charsAlphanumericRequiredThe 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–39Amount10 charsAmountCents, no decimal pointMandatoryThe 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–54Individual Identification Number15 charsAlphanumericOptionalNumber the Originator uses to identify the Receiver, such as an employee ID, customer or loan number.
  • Optional
  • Left-justified and space-filled
55–76Individual Name22 charsAlphanumericRequiredName of the Receiver.
  • Required
  • Left-justified and space-filled
  • May appear on the Receiver's bank statement
77–78Discretionary Data2 charsAlphanumericOptionalFor the ODFI or Originator to use as they agree; it has no meaning to the ACH Network.
  • Optional
  • Left-justified and space-filled
79Addenda Record Indicator1 charCodeSee codesMandatoryShows whether one or more Addenda Records follow this entry.
  • 0 = no Addenda Record follows
  • 1 = one or more Addenda Records follow
80–94Trace Number15 charsNumericMandatoryUniquely identifies the entry within the file 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
  • Must be unique within the file and in ascending order within the batch

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.

CCDCorporate Credit or DebitDiffers 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
PositionFieldLengthTypeM/R/ODescription
40–54Identification Number15 charsAlphanumericOptionalNumber the Originator uses to identify the Receiver, such as a vendor, customer or invoice number.
  • Optional
  • Left-justified and space-filled
55–76Receiving Company Name22 charsAlphanumericRequiredName of the Receiver (a business).
  • Required
  • Left-justified and space-filled

Positions not listed match the PPD layout.

CTXCorporate Trade ExchangeDiffers 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
PositionFieldLengthTypeM/R/ODescription
30–39Total Amount10 charsAmountCents, no decimal pointMandatoryTotal 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–54Identification Number15 charsAlphanumericOptionalNumber the Originator uses to identify the Receiver, such as a vendor, customer or invoice number.
  • Optional
  • Left-justified and space-filled
55–58Number of Addenda Records4 charsNumericMandatoryNumber 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–74Receiving Company Name/ID Number16 charsAlphanumericRequiredName or identification number of the Receiver (a business).
  • Required
  • Left-justified and space-filled
75–76Reserved2 charsAlphanumericNot applicable: reserved, or filled in by the ACH OperatorReserved for future use. Leave blank.
  • Space-filled

Positions not listed match the PPD layout.

WEBInternet-Initiated/Mobile EntryDiffers 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
PositionFieldLengthTypeM/R/ODescription
77–78Payment Type Code2 charsCodeSee codesRequiredShows whether a debit is recurring, a single entry, or a later entry under a standing authorization.
  • "R " = recurring
  • "S " = single entry
  • "ST" = subsequent entry under a standing authorization
  • Left-justified and space-filled; uppercase

Positions not listed match the PPD layout.

TELTelephone-Initiated EntryDiffers in positions 77–78

Consumer debit authorized orally over the telephone.

Entry Detail Record — TEL: fields that differ from PPD
PositionFieldLengthTypeM/R/ODescription
77–78Payment Type Code2 charsCodeSee codesRequiredShows whether a debit is recurring, a single entry, or a later entry under a standing authorization.
  • "R " = recurring
  • "S " = single entry
  • "ST" = subsequent entry under a standing authorization
  • Left-justified and space-filled; uppercase

Positions not listed match the PPD layout.

IATInternational ACH TransactionDiffers 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
PositionFieldLengthTypeM/R/ODescription
4–11Gateway Operator Identification/Receiving DFI Identification8 charsRoutingTTTTAAAAMandatoryFor 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–16Number of Addenda Records4 charsNumericMandatoryNumber 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–29Reserved13 charsAlphanumericNot applicable: reserved, or filled in by the ACH OperatorReserved for future use. Leave blank.
  • Space-filled
40–74Foreign Receiver's Account Number/DFI Account Number35 charsAlphanumericMandatoryThe Receiver's account number at the foreign or domestic receiving institution.
  • Left-justified and space-filled
75–76Reserved2 charsAlphanumericNot applicable: reserved, or filled in by the ACH OperatorReserved for future use. Leave blank.
  • Space-filled
77Gateway Operator OFAC Screening Indicator1 charCodeSee codesOptionalSet by the Gateway Operator when its OFAC screening flagged the entry.
  • "1" = flagged as a possible OFAC match
  • Blank or "0" = not flagged
78Secondary OFAC Screening Indicator1 charCodeSee codesOptionalSet 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.

ARCAccounts Receivable EntryDiffers in positions 40–76

Consumer check received by mail or at a drop box and converted to a one-time ACH debit.

Entry Detail Record — ARC: fields that differ from PPD
PositionFieldLengthTypeM/R/ODescription
40–54Check Serial Number15 charsAlphanumericMandatorySerial number of the source check, from its MICR line.
  • Mandatory
  • Left-justified and space-filled
55–76Individual Name22 charsAlphanumericOptionalName of the Receiver.
  • Optional
  • Left-justified and space-filled
  • May appear on the Receiver's bank statement

Positions not listed match the PPD layout.

BOCBack Office ConversionDiffers in positions 40–76

Check presented at a point of purchase or staffed payment location and converted to an ACH debit in the back office.

Entry Detail Record — BOC: fields that differ from PPD
PositionFieldLengthTypeM/R/ODescription
40–54Check Serial Number15 charsAlphanumericMandatorySerial number of the source check, from its MICR line.
  • Mandatory
  • Left-justified and space-filled
55–76Individual Name22 charsAlphanumericOptionalName of the Receiver.
  • Optional
  • Left-justified and space-filled
  • May appear on the Receiver's bank statement

Positions not listed match the PPD layout.

POPPoint-of-Purchase EntryDiffers in positions 40–76

Check converted to an ACH debit at the point of purchase.

Entry Detail Record — POP: fields that differ from PPD
PositionFieldLengthTypeM/R/ODescription
40–48Check Serial Number9 charsAlphanumericMandatorySerial number of the source check, from its MICR line.
  • Mandatory
  • Left-justified and space-filled
49–52Terminal City4 charsAlphanumericMandatoryAbbreviated 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–54Terminal State2 charsAlphanumericMandatoryTwo-letter state abbreviation of the terminal location.
  • Uppercase postal abbreviation
55–76Individual Name22 charsAlphanumericOptionalName of the Receiver.
  • Optional
  • Left-justified and space-filled
  • May appear on the Receiver's bank statement

Positions not listed match the PPD layout.

RCKRe-presented Check EntryDiffers 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
PositionFieldLengthTypeM/R/ODescription
40–54Check Serial Number15 charsAlphanumericMandatorySerial number of the source check, from its MICR line.
  • Mandatory
  • Left-justified and space-filled
55–76Individual Name22 charsAlphanumericOptionalName of the Receiver.
  • Optional
  • Left-justified and space-filled
  • May appear on the Receiver's bank statement

Positions not listed match the PPD layout.

CIECustomer Initiated EntryDiffers 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
PositionFieldLengthTypeM/R/ODescription
40–54Individual Name15 charsAlphanumericRequiredName of the Receiver.
  • Required
  • Left-justified and space-filled
  • May appear on the Receiver's bank statement
55–76Individual Identification Number22 charsAlphanumericRequiredNumber 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.

MTEMachine Transfer EntryDiffers 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
PositionFieldLengthTypeM/R/ODescription
40–54Individual Name15 charsAlphanumericRequiredName of the Receiver.
  • Required
  • Left-justified and space-filled
  • May appear on the Receiver's bank statement
55–76Individual Identification Number22 charsAlphanumericRequiredNumber 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.

POSPoint-of-Sale EntryDiffers in positions 55–78

Debit card purchase at an electronic terminal. Followed by one type 02 addenda.

Entry Detail Record — POS: fields that differ from PPD
PositionFieldLengthTypeM/R/ODescription
55–76Individual Name22 charsAlphanumericOptionalName of the Receiver.
  • Optional
  • Left-justified and space-filled
  • May appear on the Receiver's bank statement
77–78Card Transaction Type Code2 charsCodeSee codesMandatoryIdentifies 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.

SHRShared Network TransactionDiffers in positions 40–78

Point-of-sale entry through a shared network. Followed by one type 02 addenda.

Entry Detail Record — SHR: fields that differ from PPD
PositionFieldLengthTypeM/R/ODescription
40–43Card Expiration Date4 charsDateMMYYMandatoryExpiration date of the card used.
  • Format MMYY
44–54Document Reference Number11 charsNumericMandatoryNumber identifying the transaction document.
  • Right-justified and zero-filled
55–76Individual Card Account Number22 charsAlphanumericMandatoryThe card account number used for the transaction.
  • Left-justified and space-filled
77–78Card Transaction Type Code2 charsCodeSee codesMandatoryIdentifies 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.

ACKACH Payment AcknowledgmentDiffers 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
PositionFieldLengthTypeM/R/ODescription
30–39Total Amount10 charsAmountCents, no decimal pointMandatoryTotal 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–54Original Entry Trace Number15 charsNumericMandatoryTrace Number of the entry being acknowledged.
  • 15 digits, copied from the original entry
55–76Receiving Company Name22 charsAlphanumericRequiredName of the Receiver (a business).
  • Required
  • Left-justified and space-filled

Positions not listed match the PPD layout.

ATXFinancial EDI AcknowledgmentDiffers 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
PositionFieldLengthTypeM/R/ODescription
30–39Total Amount10 charsAmountCents, no decimal pointMandatoryTotal 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–54Original Entry Trace Number15 charsNumericMandatoryTrace Number of the entry being acknowledged.
  • 15 digits, copied from the original entry
55–58Number of Addenda Records4 charsNumericMandatoryNumber 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–74Receiving Company Name/ID Number16 charsAlphanumericRequiredName or identification number of the Receiver (a business).
  • Required
  • Left-justified and space-filled
75–76Reserved2 charsAlphanumericNot applicable: reserved, or filled in by the ACH OperatorReserved for future use. Leave blank.
  • Space-filled

Positions not listed match the PPD layout.

DNEDeath Notification EntrySame 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.

ENRAutomated Enrollment EntryDiffers in positions 40–76

Zero-dollar entry a DFI sends to a Federal Government agency to enroll a beneficiary in direct deposit.

Entry Detail Record — ENR: fields that differ from PPD
PositionFieldLengthTypeM/R/ODescription
40–54Identification Number15 charsAlphanumericOptionalNumber the Originator uses to identify the Receiver, such as a vendor, customer or invoice number.
  • Optional
  • Left-justified and space-filled
55–58Number of Addenda Records4 charsNumericMandatoryNumber 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–74Receiving Company Name16 charsAlphanumericRequiredName of the Federal Government agency the enrollment is sent to.
  • Left-justified and space-filled
75–76Reserved2 charsAlphanumericNot applicable: reserved, or filled in by the ACH OperatorReserved for future use. Leave blank.
  • Space-filled

Positions not listed match the PPD layout.

TRCTruncated EntryDiffers in positions 40–78

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

Entry Detail Record — TRC: fields that differ from PPD
PositionFieldLengthTypeM/R/ODescription
40–54Check Serial Number15 charsAlphanumericMandatorySerial number of the source check, from its MICR line.
  • Mandatory
  • Left-justified and space-filled
55–60Process Control Field6 charsAlphanumericMandatoryThe process control (transaction code) field from the MICR line of the check.
  • Left-justified and space-filled
61–76Item Research Number16 charsAlphanumericMandatoryNumber that identifies the check for research, such as its item sequence number.
  • Left-justified and space-filled
77–78Item Type Indicator2 charsAlphanumericOptionalIdentifies the type of truncated item, as agreed between the participating DFIs.
  • Optional
  • Left-justified and space-filled

Positions not listed match the PPD layout.

TRXTruncated Entries ExchangeDiffers in positions 30–78

Batched debit for truncated checks; the individual checks are listed in up to 9,999 addenda records.

Entry Detail Record — TRX: fields that differ from PPD
PositionFieldLengthTypeM/R/ODescription
30–39Total Amount10 charsAmountCents, no decimal pointMandatoryTotal 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–54Identification Number15 charsAlphanumericOptionalNumber the Originator uses to identify the Receiver, such as a vendor, customer or invoice number.
  • Optional
  • Left-justified and space-filled
55–58Number of Addenda Records4 charsNumericMandatoryNumber 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–74Receiving Company Name/ID Number16 charsAlphanumericRequiredName or identification number of the Receiver (a business).
  • Required
  • Left-justified and space-filled
75–76Reserved2 charsAlphanumericNot applicable: reserved, or filled in by the ACH OperatorReserved for future use. Leave blank.
  • Space-filled
77–78Item Type Indicator2 charsAlphanumericOptionalIdentifies the type of truncated item, as agreed between the participating DFIs.
  • Optional
  • Left-justified and space-filled

Positions not listed match the PPD layout.

XCKDestroyed Check EntryDiffers in positions 40–76

Debit used to collect a check that was lost or destroyed in transit.

Entry Detail Record — XCK: fields that differ from PPD
PositionFieldLengthTypeM/R/ODescription
40–54Check Serial Number15 charsAlphanumericMandatorySerial number of the source check, from its MICR line.
  • Mandatory
  • Left-justified and space-filled
55–60Process Control Field6 charsAlphanumericMandatoryThe process control (transaction code) field from the MICR line of the check.
  • Left-justified and space-filled
61–76Item Research Number16 charsAlphanumericMandatoryNumber that identifies the check for research, such as its item sequence number.
  • Left-justified and space-filled

Positions not listed match the PPD layout.

CORNotification of Change / Refused NOCDiffers 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
PositionFieldLengthTypeM/R/ODescription
40–54Identification Number15 charsAlphanumericOptionalCopied from the original entry (Individual Identification Number or Identification Number).
  • Left-justified and space-filled
55–76Individual Name/Receiving Company Name22 charsAlphanumericRequiredCopied from the original entry.
  • Left-justified and space-filled

Positions not listed match the PPD layout.

ADVAutomated Accounting AdviceDiffers in positions 13–94

Accounting advice an ACH Operator sends to a DFI summarizing its ACH activity.

Entry Detail Record — ADV: fields that differ from PPD
PositionFieldLengthTypeM/R/ODescription
13–27DFI Account Number15 charsAlphanumericMandatoryThe account at the DFI the advice applies to.
  • Left-justified and space-filled
28–39Amount12 charsAmountCents, no decimal pointMandatoryThe amount of the advice, in cents.
  • 12 digits, in cents, zero-filled
40–48Advice Routing Number9 charsRoutingTTTTAAAACMandatoryRouting number of the institution the advice is for.
  • 9 digits, including the check digit
49–53File Identification5 charsAlphanumericOptionalIdentifies the file the advice relates to.
  • Left-justified and space-filled
54ACH Operator Data1 charAlphanumericOptionalFor use by the ACH Operator.
55–76Individual Name22 charsAlphanumericMandatoryName of the Receiver.
  • Mandatory
  • Left-justified and space-filled
  • May appear on the Receiver's bank statement
80–87Routing Number of ACH Operator8 charsRoutingTTTTAAAAMandatoryFirst 8 digits of the routing number of the ACH Operator that created the advice.
88–90Julian Date on Which This Advice Is Created3 charsJulian dayDDDMandatoryDay of the year on which the advice was created.
  • 001–366
91–94Sequence Number Within Batch4 charsNumericMandatorySequence number of the advice within its batch.
  • Right-justified and zero-filled

Positions not listed match the PPD layout.

7

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
PositionFieldLengthTypeM/R/ODescription
1Record Type Code1 charCodeAlways 7MandatoryIdentifies the type of record in the file.
  • Always "7" for the Addenda Record
2–3Addenda Type Code2 charsCodeAlways 05MandatoryIdentifies 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
84–87Addenda Sequence Number4 charsNumericMandatoryPosition 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–94Entry Detail Sequence Number7 charsNumericMandatoryThe 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.

02Point-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
PositionFieldLengthTypeM/R/ODescription
1Record Type Code1 charCodeAlways 7MandatoryIdentifies the type of record in the file.
  • Always "7" for the Addenda Record
2–3Addenda Type Code2 charsCodeAlways 02MandatoryIdentifies 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–10Reference Information #17 charsAlphanumericOptionalAdditional reference data identifying the transaction.
  • Optional
  • Left-justified and space-filled
11–13Reference Information #23 charsAlphanumericOptionalAdditional reference data identifying the transaction.
  • Optional
  • Left-justified and space-filled
14–19Terminal Identification Code6 charsAlphanumericRequiredIdentifies the electronic terminal where the transaction took place.
  • Left-justified and space-filled
20–25Transaction Serial Number6 charsAlphanumericRequiredSerial number the terminal assigned to the transaction.
  • Left-justified and space-filled
26–29Transaction Date4 charsDateMMDDRequiredMonth and day of the transaction.
  • Format MMDD
30–35Authorization Code or Card Expiration Date6 charsAlphanumericOptionalAuthorization code from the card issuer, or the card expiration date.
  • Optional
  • Left-justified and space-filled
36–62Terminal Location27 charsAlphanumericRequiredStreet address or description of where the terminal is.
  • Left-justified and space-filled
63–77Terminal City15 charsAlphanumericRequiredCity where the terminal is located.
  • Left-justified and space-filled
78–79Terminal State2 charsAlphanumericRequiredTwo-letter state abbreviation of the terminal location.
  • Uppercase postal abbreviation
80–94Trace Number15 charsNumericMandatoryThe 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
98Notification of Change9 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
PositionFieldLengthTypeM/R/ODescription
1Record Type Code1 charCodeAlways 7MandatoryIdentifies the type of record in the file.
  • Always "7" for the Addenda Record
2–3Addenda Type Code2 charsCodeAlways 98MandatoryIdentifies 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–6Change Code3 charsCodeSee codesMandatoryIdentifies the information the RDFI is correcting (C01–C14).
  • "C" followed by two digits
  • Determines how Corrected Data is laid out
7–21Original Entry Trace Number15 charsNumericMandatoryTrace Number of the entry the NOC corrects.
  • 15 digits, copied unchanged
22–27Reserved6 charsAlphanumericNot applicable: reserved, or filled in by the ACH OperatorReserved for future use. Leave blank.
  • Space-filled
28–35Original Receiving DFI Identification8 charsRoutingTTTTAAAAMandatoryThe Receiving DFI Identification (positions 4–11) from the original entry.
  • 8 digits, without the check digit
36–64Corrected Data29 charsAlphanumericMandatoryThe correct information, laid out as the change code requires.
  • C01: correct account number in the first 17 positions · C02: correct routing number (9 digits)
  • C03: routing number, 3 blanks, then the account number · C05: correct transaction code (2 digits)
  • C06: account number (17) followed by the transaction code · C07: routing (9), account (17), transaction code (2)
  • C04 and C09: correct name or ID number in the first 22 positions
65–79Reserved15 charsAlphanumericNot applicable: reserved, or filled in by the ACH OperatorReserved for future use. Leave blank.
  • Space-filled
80–94Trace Number15 charsNumericMandatoryThe 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
98Refused 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
PositionFieldLengthTypeM/R/ODescription
1Record Type Code1 charCodeAlways 7MandatoryIdentifies the type of record in the file.
  • Always "7" for the Addenda Record
2–3Addenda Type Code2 charsCodeAlways 98MandatoryIdentifies 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–6Refused COR Code3 charsCodeSee codesMandatoryWhy the ODFI is refusing the NOC (C61–C69).
  • "C" followed by two digits
7–21Original Entry Trace Number15 charsNumericMandatoryTrace Number of the entry the refused NOC related to.
  • 15 digits, copied unchanged
22–27Reserved6 charsAlphanumericNot applicable: reserved, or filled in by the ACH OperatorReserved for future use. Leave blank.
  • Space-filled
28–35Original Receiving DFI Identification8 charsRoutingTTTTAAAAMandatoryThe Receiving DFI Identification (positions 4–11) from the original entry.
  • 8 digits, without the check digit
36–64Corrected Data29 charsAlphanumericMandatoryThe Corrected Data from the NOC being refused.
  • Copied from the NOC
65–67Change Code3 charsCodeSee codesMandatoryThe change code of the NOC being refused.
  • Copied from the NOC
68–74Trace Sequence Number7 charsNumericMandatoryThe last 7 digits of the Trace Number of the NOC being refused.
  • Right-justified and zero-filled
75–79Reserved5 charsAlphanumericNot applicable: reserved, or filled in by the ACH OperatorReserved for future use. Leave blank.
  • Space-filled
80–94Trace Number15 charsNumericMandatoryThe 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
99Return8 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
PositionFieldLengthTypeM/R/ODescription
1Record Type Code1 charCodeAlways 7MandatoryIdentifies the type of record in the file.
  • Always "7" for the Addenda Record
2–3Addenda Type Code2 charsCodeAlways 99MandatoryIdentifies 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–6Return Reason Code3 charsCodeSee codesMandatoryWhy the RDFI returned the entry (R01–R85).
  • "R" followed by two digits
7–21Original Entry Trace Number15 charsNumericMandatoryTrace Number of the entry being returned.
  • 15 digits, copied unchanged
22–27Date of Death6 charsDateYYMMDDOptionalDate of death of the account holder or beneficiary; used with return reasons R14 and R15.
  • Format YYMMDD
  • Blank for other return reasons
28–35Original Receiving DFI Identification8 charsRoutingTTTTAAAAMandatoryThe Receiving DFI Identification (positions 4–11) from the original entry.
  • 8 digits, without the check digit
36–79Addenda Information44 charsAlphanumericOptionalAdditional information from the RDFI about the return.
  • Optional
  • Left-justified and space-filled
80–94Trace Number15 charsNumericMandatoryThe 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
99Dishonored 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
PositionFieldLengthTypeM/R/ODescription
1Record Type Code1 charCodeAlways 7MandatoryIdentifies the type of record in the file.
  • Always "7" for the Addenda Record
2–3Addenda Type Code2 charsCodeAlways 99MandatoryIdentifies 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–6Dishonored Return Reason Code3 charsCodeSee codesMandatoryWhy the ODFI is dishonoring the return.
  • R61, R62, R67, R68, R69 or R70
7–21Original Entry Trace Number15 charsNumericMandatoryTrace Number of the original forward entry.
  • 15 digits, copied unchanged
22–27Reserved6 charsAlphanumericNot applicable: reserved, or filled in by the ACH OperatorReserved for future use. Leave blank.
  • Space-filled
28–35Original Receiving DFI Identification8 charsRoutingTTTTAAAAMandatoryThe Receiving DFI Identification (positions 4–11) from the original entry.
  • 8 digits, without the check digit
36–38Reserved3 charsAlphanumericNot applicable: reserved, or filled in by the ACH OperatorReserved for future use. Leave blank.
  • Space-filled
39–53Return Trace Number15 charsNumericMandatoryTrace Number of the return entry.
  • 15 digits, copied from the return
54–56Return Settlement Date3 charsJulian dayDDDMandatoryDay of the year on which the return settled.
  • Day of the year, 001–366
57–58Return Reason Code2 charsCodeSee codesMandatoryReason code of the return being dishonored.
  • The two digits of the return reason code, without the "R" (e.g. "01" for R01)
59–79Addenda Information21 charsAlphanumericOptionalAdditional information from the ODFI.
  • Optional
  • Left-justified and space-filled
80–94Trace Number15 charsNumericMandatoryThe 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
99Contested 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
PositionFieldLengthTypeM/R/ODescription
1Record Type Code1 charCodeAlways 7MandatoryIdentifies the type of record in the file.
  • Always "7" for the Addenda Record
2–3Addenda Type Code2 charsCodeAlways 99MandatoryIdentifies 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–6Contested Dishonored Return Reason Code3 charsCodeSee codesMandatoryWhy the RDFI is contesting the dishonored return.
  • R71–R77
7–21Original Entry Trace Number15 charsNumericMandatoryTrace Number of the original forward entry.
  • 15 digits, copied unchanged
22–27Date Original Entry Returned6 charsDateYYMMDDMandatoryThe date on which the original entry was returned.
  • Format YYMMDD
28–35Original Receiving DFI Identification8 charsRoutingTTTTAAAAMandatoryThe Receiving DFI Identification (positions 4–11) from the original entry.
  • 8 digits, without the check digit
36–38Original Settlement Date3 charsJulian dayDDDMandatoryDay of the year on which the original entry settled.
  • Day of the year, 001–366
39–53Return Trace Number15 charsNumericMandatoryTrace Number of the return entry.
  • 15 digits, copied from the return
54–56Return Settlement Date3 charsJulian dayDDDMandatoryDay of the year on which the return settled.
  • Day of the year, 001–366
57–58Return Reason Code2 charsCodeSee codesMandatoryReason code of the original return.
  • The two digits of the return reason code, without the "R" (e.g. "01" for R01)
59–73Dishonored Return Trace Number15 charsNumericMandatoryTrace Number of the dishonored return entry.
  • 15 digits
74–76Dishonored Return Settlement Date3 charsJulian dayDDDMandatoryDay of the year on which the dishonored return settled.
  • Day of the year, 001–366
77–78Dishonored Return Reason Code2 charsCodeSee codesMandatoryReason code of the dishonored return.
  • The two digits of the code, without the "R" (e.g. "69" for R69)
79Reserved1 charAlphanumericNot applicable: reserved, or filled in by the ACH OperatorReserved for future use. Leave blank.
  • Space-filled
80–94Trace Number15 charsNumericMandatoryThe 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
10IAT transaction and receiver8 fields

First mandatory IAT addenda.

Addenda Record — type 10: positions, fields and rules
PositionFieldLengthTypeM/R/ODescription
1Record Type Code1 charCodeAlways 7MandatoryIdentifies the type of record in the file.
  • Always "7" for the Addenda Record
2–3Addenda Type Code2 charsCodeAlways 10MandatoryIdentifies 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–6Transaction Type Code3 charsCodeSee codesMandatoryIdentifies the reason for the international payment.
  • e.g. SAL = salary/payroll, BUS = business, PEN = pension, ANN = annuity, MIS = miscellaneous
7–24Foreign Payment Amount18 charsAmountCents, no decimal pointRequiredFor inbound IAT, the amount of the payment in the originating currency, in its smallest unit.
  • Right-justified and zero-filled
25–46Foreign Trace Number22 charsAlphanumericOptionalTrace number assigned to the entry in the originating national payment system.
  • Optional
  • Left-justified and space-filled
47–81Receiving Company Name/Individual Name35 charsAlphanumericMandatoryName of the Receiver.
  • Mandatory
  • Left-justified and space-filled
82–87Reserved6 charsAlphanumericNot applicable: reserved, or filled in by the ACH OperatorReserved for future use. Leave blank.
  • Space-filled
88–94Entry Detail Sequence Number7 charsNumericMandatoryThe 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
11IAT originator name and address6 fields

Second mandatory IAT addenda.

Addenda Record — type 11: positions, fields and rules
PositionFieldLengthTypeM/R/ODescription
1Record Type Code1 charCodeAlways 7MandatoryIdentifies the type of record in the file.
  • Always "7" for the Addenda Record
2–3Addenda Type Code2 charsCodeAlways 11MandatoryIdentifies 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–38Originator Name35 charsAlphanumericMandatoryName of the Originator.
  • Mandatory
  • Left-justified and space-filled
39–73Originator Street Address35 charsAlphanumericMandatoryStreet address of the Originator.
  • Mandatory
  • Left-justified and space-filled
74–87Reserved14 charsAlphanumericNot applicable: reserved, or filled in by the ACH OperatorReserved for future use. Leave blank.
  • Space-filled
88–94Entry Detail Sequence Number7 charsNumericMandatoryThe 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
12IAT originator city and country6 fields

Third mandatory IAT addenda.

Addenda Record — type 12: positions, fields and rules
PositionFieldLengthTypeM/R/ODescription
1Record Type Code1 charCodeAlways 7MandatoryIdentifies the type of record in the file.
  • Always "7" for the Addenda Record
2–3Addenda Type Code2 charsCodeAlways 12MandatoryIdentifies 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–38Originator City & State/Province35 charsAlphanumericMandatoryCity and state or province of the Originator, separated by an asterisk and ending with a backslash.
  • Mandatory
  • Left-justified and space-filled
39–73Originator Country & Postal Code35 charsAlphanumericMandatoryCountry and postal code of the Originator, separated by an asterisk and ending with a backslash.
  • Mandatory
  • Left-justified and space-filled
74–87Reserved14 charsAlphanumericNot applicable: reserved, or filled in by the ACH OperatorReserved for future use. Leave blank.
  • Space-filled
88–94Entry Detail Sequence Number7 charsNumericMandatoryThe 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
13IAT originating DFI8 fields

Fourth mandatory IAT addenda.

Addenda Record — type 13: positions, fields and rules
PositionFieldLengthTypeM/R/ODescription
1Record Type Code1 charCodeAlways 7MandatoryIdentifies the type of record in the file.
  • Always "7" for the Addenda Record
2–3Addenda Type Code2 charsCodeAlways 13MandatoryIdentifies 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–38Originating DFI Name35 charsAlphanumericMandatoryName of the ODFI (for inbound IAT, the foreign correspondent that sent it).
  • Mandatory
  • Left-justified and space-filled
39–40Originating DFI Identification Number Qualifier2 charsCodeSee codesMandatoryIdentifies the kind of identification number that follows.
  • 01 = national clearing system number
  • 02 = BIC code
  • 03 = IBAN code
41–74Originating DFI Identification34 charsAlphanumericMandatoryIdentification number of the ODFI, of the kind named by the qualifier.
  • Mandatory
  • Left-justified and space-filled
75–77Originating DFI Branch Country Code3 charsAlphanumericMandatoryISO 3166 country code of the ODFI branch.
  • ISO 3166 country code, left-justified
78–87Reserved10 charsAlphanumericNot applicable: reserved, or filled in by the ACH OperatorReserved for future use. Leave blank.
  • Space-filled
88–94Entry Detail Sequence Number7 charsNumericMandatoryThe 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
14IAT receiving DFI8 fields

Fifth mandatory IAT addenda.

Addenda Record — type 14: positions, fields and rules
PositionFieldLengthTypeM/R/ODescription
1Record Type Code1 charCodeAlways 7MandatoryIdentifies the type of record in the file.
  • Always "7" for the Addenda Record
2–3Addenda Type Code2 charsCodeAlways 14MandatoryIdentifies 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–38Receiving DFI Name35 charsAlphanumericMandatoryName of the RDFI.
  • Mandatory
  • Left-justified and space-filled
39–40Receiving DFI Identification Number Qualifier2 charsCodeSee codesMandatoryIdentifies the kind of identification number that follows.
  • 01 = national clearing system number
  • 02 = BIC code
  • 03 = IBAN code
41–74Receiving DFI Identification34 charsAlphanumericMandatoryIdentification number of the RDFI, of the kind named by the qualifier.
  • Mandatory
  • Left-justified and space-filled
75–77Receiving DFI Branch Country Code3 charsAlphanumericMandatoryISO 3166 country code of the RDFI branch.
  • ISO 3166 country code, left-justified
78–87Reserved10 charsAlphanumericNot applicable: reserved, or filled in by the ACH OperatorReserved for future use. Leave blank.
  • Space-filled
88–94Entry Detail Sequence Number7 charsNumericMandatoryThe 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
15IAT receiver identification and address6 fields

Sixth mandatory IAT addenda.

Addenda Record — type 15: positions, fields and rules
PositionFieldLengthTypeM/R/ODescription
1Record Type Code1 charCodeAlways 7MandatoryIdentifies the type of record in the file.
  • Always "7" for the Addenda Record
2–3Addenda Type Code2 charsCodeAlways 15MandatoryIdentifies 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–18Receiver Identification Number15 charsAlphanumericOptionalNumber the Originator uses to identify the Receiver.
  • Optional
  • Left-justified and space-filled
19–53Receiver Street Address35 charsAlphanumericMandatoryStreet address of the Receiver.
  • Mandatory
  • Left-justified and space-filled
54–87Reserved34 charsAlphanumericNot applicable: reserved, or filled in by the ACH OperatorReserved for future use. Leave blank.
  • Space-filled
88–94Entry Detail Sequence Number7 charsNumericMandatoryThe 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
16IAT receiver city and country6 fields

Seventh mandatory IAT addenda.

Addenda Record — type 16: positions, fields and rules
PositionFieldLengthTypeM/R/ODescription
1Record Type Code1 charCodeAlways 7MandatoryIdentifies the type of record in the file.
  • Always "7" for the Addenda Record
2–3Addenda Type Code2 charsCodeAlways 16MandatoryIdentifies 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–38Receiver City & State/Province35 charsAlphanumericMandatoryCity and state or province of the Receiver, separated by an asterisk and ending with a backslash.
  • Mandatory
  • Left-justified and space-filled
39–73Receiver Country & Postal Code35 charsAlphanumericMandatoryCountry and postal code of the Receiver, separated by an asterisk and ending with a backslash.
  • Mandatory
  • Left-justified and space-filled
74–87Reserved14 charsAlphanumericNot applicable: reserved, or filled in by the ACH OperatorReserved for future use. Leave blank.
  • Space-filled
88–94Entry Detail Sequence Number7 charsNumericMandatoryThe 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
17IAT remittance information (optional, up to 2)5 fields

Optional IAT payment related information.

Addenda Record — type 17: positions, fields and rules
PositionFieldLengthTypeM/R/ODescription
1Record Type Code1 charCodeAlways 7MandatoryIdentifies the type of record in the file.
  • Always "7" for the Addenda Record
2–3Addenda Type Code2 charsCodeAlways 17MandatoryIdentifies 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
84–87Addenda Sequence Number4 charsNumericMandatoryPosition 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–94Entry Detail Sequence Number7 charsNumericMandatoryThe 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
18IAT 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
PositionFieldLengthTypeM/R/ODescription
1Record Type Code1 charCodeAlways 7MandatoryIdentifies the type of record in the file.
  • Always "7" for the Addenda Record
2–3Addenda Type Code2 charsCodeAlways 18MandatoryIdentifies 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–38Foreign Correspondent Bank Name35 charsAlphanumericMandatoryName of the foreign correspondent bank.
  • Mandatory
  • Left-justified and space-filled
39–40Foreign Correspondent Bank Identification Number Qualifier2 charsCodeSee codesMandatoryIdentifies the kind of identification number that follows.
  • 01 = national clearing system number
  • 02 = BIC code
  • 03 = IBAN code
41–74Foreign Correspondent Bank Identification Number34 charsAlphanumericMandatoryIdentification number of the correspondent bank, of the kind named by the qualifier.
  • Mandatory
  • Left-justified and space-filled
75–77Foreign Correspondent Bank Branch Country Code3 charsAlphanumericMandatoryISO 3166 country code of the correspondent bank branch.
  • ISO 3166 country code, left-justified
78–83Reserved6 charsAlphanumericNot applicable: reserved, or filled in by the ACH OperatorReserved for future use. Leave blank.
  • Space-filled
84–87Addenda Sequence Number4 charsNumericMandatoryPosition 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–94Entry Detail Sequence Number7 charsNumericMandatoryThe 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
8

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
PositionFieldLengthTypeM/R/ODescription
1Record Type Code1 charCodeAlways 8MandatoryIdentifies the type of record in the file.
  • Always "8" for the Company/Batch Control Record
2–4Service Class Code3 charsCodeSee codesMandatoryIdentifies whether the batch contains debits, credits or both.
  • Must match the Service Class Code in the Company/Batch Header Record
5–10Entry/Addenda Count6 charsNumericMandatoryThe 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–20Entry Hash10 charsNumericMandatorySum 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–32Total Debit Entry Dollar Amount12 charsAmountCents, no decimal pointMandatoryTotal 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–44Total Credit Entry Dollar Amount12 charsAmountCents, no decimal pointMandatoryTotal 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–54Company Identification10 charsAlphanumericRequiredIdentifies the Originator.
  • Must match the Company Identification (IAT: Originator Identification) in the Company/Batch Header Record
55–73Message Authentication Code19 charsAlphanumericOptionalCode used to authenticate the batch when the ODFI and RDFI use message authentication.
  • Optional; normally blank
  • Left-justified and space-filled
74–79Reserved6 charsAlphanumericNot applicable: reserved, or filled in by the ACH OperatorReserved for future use. Leave blank.
  • Space-filled
80–87Originating DFI Identification8 charsRoutingTTTTAAAAMandatoryFirst 8 digits of the routing number of the ODFI.
  • Must match the ODFI in the Company/Batch Header Record
88–94Batch Number7 charsNumericMandatoryThe 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

ADVAutomated Accounting Advices9 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
PositionFieldLengthTypeM/R/ODescription
1Record Type Code1 charCodeAlways 8MandatoryIdentifies the type of record in the file.
  • Always "8" for the Company/Batch Control Record
2–4Service Class Code3 charsCodeSee codesMandatoryIdentifies whether the batch contains debits, credits or both.
  • Must match the Service Class Code in the Company/Batch Header Record
5–10Entry/Addenda Count6 charsNumericMandatoryThe 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–20Entry Hash10 charsNumericMandatorySum 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–40Total Debit Entry Dollar Amount20 charsAmountCents, no decimal pointMandatoryTotal of all debit advices in the batch, in cents.
  • 20 digits, in cents, zero-filled
41–60Total Credit Entry Dollar Amount20 charsAmountCents, no decimal pointMandatoryTotal of all credit advices in the batch, in cents.
  • 20 digits, in cents, zero-filled
61–79ACH Operator Data19 charsAlphanumericOptionalFor use by the ACH Operator that prepared the advice file.
  • Left-justified and space-filled
80–87Originating DFI Identification8 charsRoutingTTTTAAAAMandatoryFirst 8 digits of the routing number of the ODFI.
  • Must match the ODFI in the Company/Batch Header Record
88–94Batch Number7 charsNumericMandatoryThe number of the batch this record closes.
  • Must match the Batch Number in the Company/Batch Header Record
  • Right-justified and zero-filled
9

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
PositionFieldLengthTypeM/R/ODescription
1Record Type Code1 charCodeAlways 9MandatoryIdentifies the type of record in the file.
  • Always "9" for the File Control Record
2–7Batch Count6 charsNumericMandatoryThe number of batches (Company/Batch Header Records) in the file.
  • Right-justified and zero-filled
8–13Block Count6 charsNumericMandatoryThe 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–21Entry/Addenda Count8 charsNumericMandatoryThe 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–31Entry Hash10 charsNumericMandatorySum 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–43Total Debit Entry Dollar Amount in File12 charsAmountCents, no decimal pointMandatoryTotal 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–55Total Credit Entry Dollar Amount in File12 charsAmountCents, no decimal pointMandatoryTotal 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–94Reserved39 charsAlphanumericNot applicable: reserved, or filled in by the ACH OperatorReserved for future use. Leave blank.
  • Space-filled

Accounting advice (ADV) files

ADVAutomated Accounting Advices8 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
PositionFieldLengthTypeM/R/ODescription
1Record Type Code1 charCodeAlways 9MandatoryIdentifies the type of record in the file.
  • Always "9" for the File Control Record
2–7Batch Count6 charsNumericMandatoryThe number of batches (Company/Batch Header Records) in the file.
  • Right-justified and zero-filled
8–13Block Count6 charsNumericMandatoryThe 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–21Entry/Addenda Count8 charsNumericMandatoryThe 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–31Entry Hash10 charsNumericMandatorySum 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–51Total Debit Entry Dollar Amount in File20 charsAmountCents, no decimal pointMandatoryTotal of all debit advices in the file, in cents.
  • 20 digits, in cents, zero-filled
52–71Total Credit Entry Dollar Amount in File20 charsAmountCents, no decimal pointMandatoryTotal of all credit advices in the file, in cents.
  • 20 digits, in cents, zero-filled
72–94Reserved23 charsAlphanumericNot applicable: reserved, or filled in by the ACH OperatorReserved for future use. Leave blank.
  • Space-filled
9

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.

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.

Transaction codes
CodeMeaningAccountDirection
21Return or NOC of a checking credit (original code 22, 23 or 24)CheckingCredit
22Checking credit (deposit)CheckingCredit
23Prenote: checking credit (also DNE and ENR non-dollar entries)CheckingCredit
24Zero-dollar checking credit with remittance data (CCD, CTX, IAT); ACK and ATX acknowledgmentsCheckingCredit
25Reserved (not assigned)CheckingDebit
26Return or NOC of a checking debit (original code 27, 28 or 29)CheckingDebit
27Checking debit (payment)CheckingDebit
28Prenote: checking debitCheckingDebit
29Zero-dollar checking debit with remittance data (CCD, CTX, IAT)CheckingDebit
31Return or NOC of a savings credit (original code 32, 33 or 34)SavingsCredit
32Savings credit (deposit)SavingsCredit
33Prenote: savings credit (also DNE and ENR non-dollar entries)SavingsCredit
12 of 41 transaction codes

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.

Standard Entry Class (SEC) codes
SECNameUsed forMovesAddenda
ACKACH Payment AcknowledgmentZero-dollar acknowledgment of a CCD credit, sent by the RDFI.Zero-dollarUp to 1 (type 05)
ADVAutomated Accounting AdviceAccounting advices an ACH Operator sends to a DFI (Service Class Code 280).Credits and debitsNone
ARCAccounts Receivable EntryConsumer check received by mail or at a drop box, converted to a one-time debit.DebitsNone
ATXFinancial EDI AcknowledgmentZero-dollar acknowledgment of a CTX credit, sent by the RDFI.Zero-dollarUp to 9,999 (type 05)
BOCBack Office Conversion EntryCheck presented in person and converted to a debit in the back office.DebitsNone
CCDCorporate Credit or Debit EntryCredit or debit between business accounts.Credits and debitsUp to 1 (type 05)
CIECustomer Initiated EntryCredit initiated by a consumer, such as an online bill payment.CreditsUp to 1 (type 05)
CORNotification of Change or Refused Notification of ChangeZero-dollar entry correcting information in an earlier entry.Zero-dollar1 required (type 98)
CTXCorporate Trade ExchangeBusiness-to-business payment with up to 9,999 addenda of EDI remittance data.Credits and debitsUp to 9,999 (type 05)
DNEDeath Notification EntryZero-dollar notice from a Federal Government agency that a benefit recipient has died.Zero-dollar1 required (type 05)
10 of 23 SEC codes

Service class codes

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

Service class codes
CodeMeaning
200ACH entries mixed debits and credits
220ACH credits only
225ACH debits only
280ACH 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.

Return reason codes
CodeReasonNote
R01Insufficient Funds
R02Account Closed
R03No Account/Unable to Locate Account
R04Invalid Account Number Structure
R05Unauthorized Debit to Consumer Account Using Corporate SEC Code
R06Returned per ODFI's Request
R07Authorization Revoked by Customer
R08Payment Stopped
R09Uncollected Funds
R10Customer Advises Originator is Not Known to Receiver and/or Originator is Not Authorized by Receiver to Debit Receiver's Account
R11Customer Advises Entry Not in Accordance with the Terms of the Authorization
R12Account Sold to Another DFI
12 of 70 return codes

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.

Change codes (notifications of change)
CodeChangeCorrected data
C01Incorrect DFI Account NumberCorrect DFI Account Number in the first 17 positions
C02Incorrect Routing NumberCorrect routing number (9 digits, with check digit) in the first 9 positions
C03Incorrect Routing Number and Incorrect DFI Account NumberCorrect routing number (9), three blanks, then the correct DFI Account Number (17)
C04Incorrect Individual Name/Receiving Company NameCorrect name in the first 22 positions
C05Incorrect Transaction CodeCorrect Transaction Code in the first 2 positions
C06Incorrect DFI Account Number and Incorrect Transaction CodeCorrect DFI Account Number (17) followed by the correct Transaction Code (2)
C07Incorrect Routing Number, Incorrect DFI Account Number, and Incorrect Transaction CodeCorrect routing number (9), DFI Account Number (17) and Transaction Code (2)
C08Incorrect Receiving DFI Identification (IAT only)Correct Receiving DFI Identification
C09Incorrect Individual Identification NumberCorrect Individual Identification Number in the first 22 positions
C10Incorrect Company NameCorrect Company Name in the first 16 positions
C11Incorrect Company IdentificationCorrect Company Identification in the first 10 positions
C12Incorrect Company Name and Company IdentificationCorrect Company Name (16) and Company Identification (10)
C13Addenda Format ErrorInformation that was incorrectly formatted in the addenda
C14Incorrect SEC Code for Outbound International Payment"IAT" in the first 3 positions
14 of 23 change codes

Addenda type codes

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

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

Originator status codes
CodeMeaning
0ADV file prepared by an ACH Operator
1Depository financial institution bound by the Nacha Rules
2Federal Government entity or agency not subject to the Nacha Rules

Addenda record indicator

Entry Detail: position 79

Addenda record indicator
CodeMeaning
0No addenda record follows
1One or more addenda records follow

Payment type codes

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

Payment type codes
CodeMeaning
RRecurring
SSingle entry
STSubsequent entry under a standing authorization

Card transaction type codes

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

Card transaction type codes
CodeMeaning
01Purchase of goods or services
02Cash
03Return reversal
11Purchase reversal
12Cash reversal
13Return
21Adjustment
99Miscellaneous transaction

IAT transaction type codes

Addenda (type 10): positions 4–6

IAT transaction type codes
CodeMeaning
ANNAnnuity
BUSBusiness/Commercial
DEPDeposit
LOALoan
MISMiscellaneous
MORMortgage
PENPension
REMRemittance
RLSRent/Lease
SALSalary/Payroll
TAXTax
ARCAccounts Receivable Check
BOCBack Office Conversion
MTEMachine Transfer Entry
POPPoint-of-Purchase
POSPoint-of-Sale
RCKRe-presented Check
SHRShared Network Transaction
TELTelephone-Initiated
WEBInternet-Initiated/Mobile

Foreign exchange indicators

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

Foreign exchange indicators
CodeMeaning
FVFixed-to-variable: originated as a fixed amount, received after currency conversion
VFVariable-to-fixed: converted at a rate so that a fixed amount is received
FFFixed-to-fixed: same currency at both ends, no conversion

Foreign exchange reference indicators

Company/Batch Header (IAT): position 23

Foreign exchange reference indicators
CodeMeaning
1Foreign exchange rate
2Foreign exchange reference number
3Space-filled (no reference)

ID number qualifiers

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

ID number qualifiers
CodeMeaning
01National clearing system number
02BIC code
03IBAN code

OFAC screening indicators

Entry Detail (IAT): positions 77 and 78

OFAC screening indicators
CodeMeaning
0Not flagged by OFAC screening
1Flagged 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 Nacha.