2.3 Entry Detail Record (Type 6) & Addenda Records (Type 7)

Key Takeaways

  • The Entry Detail Record (Type 6) conveys transaction instructions for an individual Receiver, containing account numbers, dollar amounts, routing numbers, and the 15-digit Trace Number.
  • Transaction Codes identify the target account type (Demand/Checking: 20s, Savings: 30s, General Ledger: 40s, Loan: 50s) and transaction direction (Debit, Credit, Prenote, Zero-Dollar Remittance).
  • The 15-digit Trace Number uniquely identifies each transaction, composed of the ODFI's 8-digit routing number (Positions 80–87) and a 7-digit ascending sequence number (Positions 88–94).
  • The Addenda Record Indicator (Position 79) is set to '1' when one or more Type 7 Addenda records follow, and '0' when no addenda record is present.
  • Addenda Records (Type 7) utilize standardized Addenda Type Codes (05 for standard payment-related info, 98 for NOC, 99 for Returns, 10–18 for IAT) and link to parent entries via the Entry Detail Sequence Number.
Last updated: August 2026

2.3 Entry Detail Record (Type 6) & Addenda Records (Type 7)

The core payment instruction in an ACH transmission is embodied in the Entry Detail Record (Type 6). Each Type 6 record directs the transfer of funds into or out of an account at a Receiving Depository Financial Institution (RDFI), or transmits non-monetary account validation data.

When additional remittance, return, or international compliance information must accompany an entry, one or more Addenda Records (Type 7) are attached directly behind the Type 6 record.


Field-by-Field Specification: Entry Detail Record (Type 6)

The standard Type 6 record layout applies across consumer and corporate SEC codes (such as PPD, CCD, WEB, and TEL), with specific SEC codes repurposing certain discretionary fields.

FieldPositionsLengthTypeNameContents / Validation Rules
101–011NRecord Type CodeMandatory constant 6. Identifies record as Entry Detail.
202–032NTransaction Code2-digit code identifying account type and payment direction (e.g., 22, 27, 23, 28, 32, 37, 42, 47, 52, 57).
304–118NReceiving DFI IdentificationThe first 8 digits of the RDFI's Transit Routing Number. Used in Entry Hash calculation.
412–121NCheck DigitThe 9th digit of the RDFI's Routing Number, calculated via Modulus 10 algorithm.
513–2917A/NDFI Account NumberReceiver's account number at RDFI. Left-justified, blank-filled if under 17 characters.
630–3910NAmountDollar amount in cents, zero-padded, right-justified (e.g., $1,250.75 is 0000125075). Zeroes (0000000000) for prenotes.
740–5415A/NIndividual Identification NumberOptional/Mandatory by SEC. Alphanumeric ID assigned by Originator (e.g., employee ID, customer account #, invoice #).
855–7622A/NIndividual Name / Receiving Company Name22 characters. Legal name of the Receiver whose account is debited or credited. Left-justified, blank-filled.
977–782A/NDiscretionary Data2 characters. Optional data (in WEB entries, indicates 'R' for recurring or 'S' for single entry).
1079–791NAddenda Record Indicator1 if one or more Type 7 Addenda records immediately follow; 0 if no addenda records follow.
1180–9415NTrace NumberUnique 15-digit identifier: Positions 80–87 = ODFI Routing # (8 digits); Positions 88–94 = 7-digit ascending sequence #.

Master Matrix of ACH Transaction Codes

Transaction Codes in Positions 02–03 dictate whether funds are credited or debited, designate the underlying account category, and identify non-monetary prenotifications.

+-----------------------------------------------------------------------------------------+
| NACHA TRANSACTION CODES                                                                 |
+---------------------+-------------------+---------------------+-------------------------+
| Account Category    | Live Credit ($)   | Live Debit ($)      | Prenote / Non-Dollar    |
+---------------------+-------------------+---------------------+-------------------------+
| Demand / Checking   | 22 (Credit)       | 27 (Debit)          | 23 (Prenote Credit)     |
|                     |                   |                     | 28 (Prenote Debit)      |
|                     |                   |                     | 24 (Zero-Dollar Remit)  |
+---------------------+-------------------+---------------------+-------------------------+
| Savings Account     | 32 (Credit)       | 37 (Debit)          | 33 (Prenote Credit)     |
|                     |                   |                     | 38 (Prenote Debit)      |
|                     |                   |                     | 34 (Zero-Dollar Remit)  |
+---------------------+-------------------+---------------------+-------------------------+
| General Ledger (GL) | 42 (Credit)       | 47 (Debit)          | 43 (Prenote Credit)     |
|                     |                   |                     | 48 (Prenote Debit)      |
|                     |                   |                     | 44 (Zero-Dollar Remit)  |
+---------------------+-------------------+---------------------+-------------------------+
| Loan Account        | 52 (Credit)       | 57 (Debit -         | 53 (Prenote Credit)     |
|                     |                   | Reversals Only)     | 58 (Prenote Debit)      |
+---------------------+-------------------+---------------------+-------------------------+

Critical Transaction Code Rules

  1. Loan Accounts (Code 57): A debit transaction to a loan account (57) is strictly prohibited for regular payment origination. It is permitted solely for reversing an erroneous credit entry previously posted to the loan account.
  2. Zero-Dollar Remittance (Codes 24, 34, 44): Used in CCD and CTX corporate payments to transmit ANSI ASC X12 or payment-related information via addenda records when no monetary funds transfer occurs.
  3. Prenotifications (Codes 23, 28, 33, 38, 43, 48, 53, 58): Non-dollar entries used to validate account number and routing validity prior to initiating live transactions. The Amount field in Position 30–39 must be all zeros (0000000000).

Trace Number Structure & Check Digit Modulus 10

1. Trace Number Composition (Positions 80–94)

Every Entry Detail record is assigned a globally unique 15-digit Trace Number by the ODFI: Trace Number=ODFI Routing Number (First 8 Digits)Positions 80–87+7-Digit Ascending Sequence NumberPositions 88–94\text{Trace Number} = \underbrace{\text{ODFI Routing Number (First 8 Digits)}}_{\text{Positions 80–87}} + \underbrace{\text{7-Digit Ascending Sequence Number}}_{\text{Positions 88–94}}

  • Example: If ODFI routing number is 121000358 and this is the 4th entry in the batch, the Trace Number is 121000350000004.
  • Audit & Tracing: The Trace Number is referenced in all subsequent exception processing, including Returns (Type 7, Addenda 99), Notifications of Change (Type 7, Addenda 98), and trace inquiries.

2. Modulus 10 Check Digit Calculation (Position 12)

The 9th digit of an RDFI routing number (Position 12) validates the preceding 8 digits (Positions 04–11) using the Modulus 10 weighting algorithm (weights: 3, 7, 1, 3, 7, 1, 3, 7):

Weighted Sum S=(d1×3)+(d2×7)+(d3×1)+(d4×3)+(d5×7)+(d6×1)+(d7×3)+(d8×7)\text{Weighted Sum } S = (d_1 \times 3) + (d_2 \times 7) + (d_3 \times 1) + (d_4 \times 3) + (d_5 \times 7) + (d_6 \times 1) + (d_7 \times 3) + (d_8 \times 7) Check Digit d9=(10(Smod10))mod10\text{Check Digit } d_9 = (10 - (S \bmod 10)) \bmod 10

Worked Example: Check Digit Calculation

For routing number 07100001: S=(0×3)+(7×7)+(1×1)+(0×3)+(0×7)+(0×1)+(0×3)+(1×7)S = (0 \times 3) + (7 \times 7) + (1 \times 1) + (0 \times 3) + (0 \times 7) + (0 \times 1) + (0 \times 3) + (1 \times 7) S=0+49+1+0+0+0+0+7=57S = 0 + 49 + 1 + 0 + 0 + 0 + 0 + 7 = 57 d9=(10(57mod10))mod10=(107)mod10=3d_9 = (10 - (57 \bmod 10)) \bmod 10 = (10 - 7) \bmod 10 = 3 Complete 9-Digit Routing Number=071000013\text{Complete 9-Digit Routing Number} = \mathbf{071000013}


Addenda Record Architecture (Type 7)

When Position 79 of a Type 6 record is set to 1, one or more Type 7 Addenda records immediately follow.

FieldPositionsLengthTypeNameContents / Validation Rules
101–011NRecord Type CodeMandatory constant 7. Identifies record as Addenda.
202–032NAddenda Type CodeIdentifies addenda category: 05 (Payment Related), 98 (NOC), 99 (Return), 1018 (IAT).
304–8380A/NPayment Related / Exception Information80 characters of ANSI ASC X12 EDI text, return reason codes/original trace, or NOC change data.
484–874NAddenda Sequence NumberSequential integer starting at 0001 for each addenda attached to this Type 6 entry.
588–947NEntry Detail Sequence NumberMust exactly match Positions 88–94 of the parent Type 6 Trace Number. Links addenda to entry.

Key Addenda Type Codes

  1. 05 (Payment Related Information): Used with PPD, CCD, and WEB (single addenda) and CTX (up to 9,999 addenda) to convey invoice numbers, account descriptions, or ASC X12 820 payment orders.
  2. 98 (Notification of Change / NOC): Generated by RDFIs using COR SEC code. Contains Change Code (C01C13), original entry trace number, and corrected routing/account data.
  3. 99 (ACH Return Record): Generated by RDFIs to return dishonored or unauthorized entries. Contains the 3-character Return Reason Code (R01R99), Original Entry Trace Number, Date of Death (if applicable), and Original RDFI Routing Number.
  4. 10 through 18 (International ACH Transactions / IAT): Mandatory sequence of 7 addenda records conveying foreign exchange data, Originator address, Beneficiary address, and correspondent bank identifiers for OFAC screening.
Loading diagram...
Type 6 Entry Detail to Type 7 Addenda Record Structural Linkage
Test Your Knowledge

An Originator sends a non-dollar prenotification to verify a consumer's savings account before initiating future direct debits. Which Transaction Code must be placed in Positions 02–03 of the Entry Detail Record (Type 6)?

A
B
C
D
Test Your Knowledge

How is the 15-digit Trace Number structured in Positions 80–94 of a Type 6 Entry Detail Record?

A
B
C
D
Test Your Knowledge

When an RDFI initiates an ACH Return Record (such as an R01 Insufficient Funds return), which Addenda Type Code is populated in Positions 02–03 of the Type 7 Addenda Record?

A
B
C
D
Test Your Knowledge

In a Type 7 Addenda Record, what specific data must be placed in Positions 88–94 (Entry Detail Sequence Number)?

A
B
C
D