Study guide
2.1 File Hierarchy: 94-Character Records, Blocking Factors & File Header (Type 1)
Nacha Accredited ACH Professional AAP
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: ACH Network Overview, Participants & Transaction Flow
1.1 ACH Network Structure, Governance & History 1.2 Five Key ACH Participants: Originator, ODFI, Operator, RDFI, Receiver 1.3 Third-Party Senders (TPS) and Third-Party Service Providers (TPSP) 1.4 End-to-End Transaction Flow, Clearing & Settlement Mechanics
2 Chapter 2: ACH File Architecture & Record Formatting
2.1 File Hierarchy: 94-Character Records, Blocking Factors & File Header (Type 1) 2.2 Company/Batch Header Record (Type 5) & Service Class Codes 2.3 Entry Detail Record (Type 6) & Addenda Records (Type 7) 2.4 Batch Control (Type 8), File Control (Type 9) & Entry Hash Calculations 2.5 Exception Record Formats: Return (Addenda 99) & Notification of Change (Addenda 98) Layouts
3 Chapter 3: Nacha Operating Rules Framework & Participant Warranties
3.1 Structure of Nacha Operating Rules, Rulemaking Process & Effective Dates 3.2 ODFI Warranties, Indemnifications & Participant Obligations 3.3 RDFI Warranties, Receipt Obligations & Statement Requirements 3.4 Nacha Return Rate Thresholds & Monitoring Requirements
4 Chapter 4: Standard Entry Class (SEC) Codes: Consumer Applications
4.1 PPD (Prearranged Payment and Deposit): Direct Deposit & Consumer Debits 4.2 WEB (Internet-Initiated Entries): Authorization, Authentication & Validation 4.3 TEL (Telephone-Initiated Entries): Inbound vs. Outbound Rules & Recording Requirements 4.4 CIE, MTE, POS & SHR: Machine and Point-of-Sale Consumer Entries 4.5 Same Day ACH: Windows, Limits ($1,000,000) & Eligibility Rules
5 Chapter 5: SEC Codes: Commercial, Check Conversion & Specialized Applications
5.1 CCD/CCD+ and CTX: Corporate Payments, Addenda & EDI / ASC X12 Formatting 5.2 Check Conversion SEC Codes: ARC, BOC & POP Rules and Notices 5.3 RCK (Re-presented Checks) & XCK (Destroyed Check Entries) 5.4 IAT (International ACH Transactions): Mandatory Addenda & OFAC Screening 5.5 Non-Monetary & Specialty Entries: Prenotifications, DNE & ENR
6 Chapter 6: Authorization Standards, Authentication & Record Retention
6.1 Fundamentals of Valid Authorization: Consumer vs. Commercial 6.2 E-SIGN Act Compliance, Electronic Signatures & Oral Authorizations 6.3 WEB Debit Account Validation Rule & Fraud Detection Systems 6.4 Authorization Retention (2 Years) & Copy Provision Rules
7 Chapter 7: Exception Processing: Returns & Return Reason Codes
7.1 Return Processing Overview: Two-Banking-Day Rule vs. Extended Return Rule 7.2 Administrative & Operational R-Codes (R01-R04, R08, R16, R17) 7.3 Unauthorized Consumer Returns: R05, R07, R10, R11 & The WSUD 7.4 Unauthorized Corporate Debits: R29, Contract Rights & the UCC Article 4A Boundary 7.5 Dishonored Returns (R61-R70) & Contested Dishonored Returns (R71-R76)
8 Chapter 8: Exception Processing: Notifications of Change (NOC) & Reversals
8.1 Notification of Change (NOC / COR): Structure & Change Codes (C01-C07) 8.2 NOC Timelines: RDFI Origination & Originator 6-Day Mandatory Action 8.3 Reversing Entries & Reversal Files: 5-Day Deadline & Erroneous Reasons 8.4 Federal Reclamation Procedures & Deceased Beneficiary Handling
9 Chapter 9: ACH Risk Management, Fraud Monitoring & Exposure Controls
9.1 ACH Risk Taxonomy: Credit, Operational, Fraud, Systemic & Compliance Risks 9.2 ODFI Originator Onboarding, Underwriting & Exposure Limits 9.3 Third-Party Sender (TPS) Due Diligence, Monitoring & Registration 9.4 Fraud Schemes: Business Email Compromise (BEC), Account Takeover & Controls 9.5 The 2026 Fraud Monitoring Rules: ODFIs, Originators, TPSPs & Third-Party Senders 9.6 RDFI ACH Credit Monitoring & the False Pretenses Definition 9.7 ACH Data Security: Article One, Sections 1.6 and 1.7 & the ACH Security Framework 9.8 Nacha's Risk Management Portal: Contact Registry, TPS & Direct Access Registration, Terminated Originator Database 9.9 ACH Risk Assessments, Regulatory Expectations & Operational Resilience
10 Chapter 10: Legal & Regulatory Framework for ACH
10.1 Regulation E (12 CFR 1005): Consumer Protections, Disclosures & Error Resolution 10.2 Uniform Commercial Code (UCC) Article 4A: Wholesale Funds Transfers & Security Procedures 10.3 BSA/AML, SAR/CTR Reporting & OFAC Sanctions Compliance in ACH 10.4 31 CFR Part 210 (The Green Book), Reg CC, Reg D & Reg J Interactions
11 Chapter 11: Nacha Rules Compliance Audit & National System of Fines
11.1 Annual ACH Rules Compliance Audit (Article One, §1.2.2): Scope & Requirements 11.2 Auditor Independence & 6-Year Audit Record Retention 11.3 National System of Fines: Complaint Process, Panel Review & Fine Classes 11.4 The Nacha Rules Effective-Date Calendar: 2026 Through 2028
12 Chapter 12: Alternative & Complementary Payment Systems
12.1 Fedwire Funds Service & CHIPS vs. ACH Network 12.2 Instant Payments: RTP and FedNow vs. Same Day ACH 12.3 Card Networks, Check 21 & Interoperability Across Payment Rails
2.1 File Hierarchy: 94-Character Records, Blocking Factors & File Header (Type 1)
Key Takeaways Explain This Topic AI
Every logical record in an ACH transmission is strictly 94 ASCII characters in length, structured within a rigid four-tier nested envelope hierarchy of File, Batch, Entry Detail, and Addenda records.
ACH files mandate a blocking factor of 10 records (940 characters per physical block); incomplete final blocks must be padded with fill records containing ninety-four consecutive 9s.
The File Header Record (Type 1) establishes physical transmission parameters between the Immediate Origin and Immediate Destination and initiates file-level integrity tracking.
The 10-character Immediate Destination field (Positions 04–13) contains the 9-digit routing number of the receiving ACH Operator or endpoint, preceded by a mandatory blank space.
ACH Operators utilize a composite key consisting of Immediate Origin, Immediate Destination, File Creation Date, and File ID Modifier (A–Z, 0–9) to detect and reject duplicate file transmissions.
Last updated: August 2026
2.1 File Hierarchy: 94-Character Records, Blocking Factors & File Header (Type 1)
Core Principle: The Automated Clearing House (ACH) Network operates as a batch-oriented, store-and-forward electronic funds transfer ecosystem. To ensure seamless interoperability among thousands of financial institutions, corporate originators, and ACH Operators (the Federal Reserve Bank's FedACH and The Clearing House's EPN), Nacha establishes strict, immutable structural specifications for all transmitted data.
Every participant preparing for the Accredited ACH Professional (AAP) examination must master the underlying technical blueprint of ACH files. File processing failures, operator rejections, and transmission delays almost invariably stem from formatting non-compliance, miscalculated blocking factors, or invalid header parameters.
The Hierarchical File Envelope Model
An ACH file is constructed using a nested envelope hierarchy. This structure allows financial institutions to aggregate thousands of individual debit and credit transactions into logically organized operational units with distinct clearing rules, settlement schedules, and legal warranties. +-------------------------------------------------------------------------+
- | FILE HEADER RECORD (Type 1) |
- | +-------------------------------------------------------------------+ |
- | | COMPANY / BATCH HEADER RECORD (Type 5) - Batch 0000001 | |
- | | +-------------------------------------------------------------+ | |
- | | | Entry Detail Record (Type 6) #1 | | |
- | | | Addenda Record (Type 7) #1 (Optional / SEC Dependent) | | |
- | | | Entry Detail Record (Type 6) #2 | | |
- | | | Entry Detail Record (Type 6) #3 | | |
- | | +-------------------------------------------------------------+ | |
- | | COMPANY / BATCH CONTROL RECORD (Type 8) - Batch 0000001 | |
- | +-------------------------------------------------------------------+ |
- | +-------------------------------------------------------------------+ |
- | | COMPANY / BATCH HEADER RECORD (Type 5) - Batch 0000002 | |
- | | +-------------------------------------------------------------+ | |
- | | | Entry Detail Record (Type 6) #1 | | |
- | | +-------------------------------------------------------------+ | |
- | | COMPANY / BATCH CONTROL RECORD (Type 8) - Batch 0000002 | |
- | +-------------------------------------------------------------------+ |
- | FILE CONTROL RECORD (Type 9) |
- | PADDING RECORDS (All 9s records to complete 10-record block) |
- +-------------------------------------------------------------------------+
- The Four Structural Levels
File Level (Outer Envelope) : Delimited by a single File Header Record (Type 1) at the beginning and sealed by a single File Control Record (Type 9) at the end. It encapsulates all batches, establishes origin/destination routing, and accumulates file-wide control totals.
Batch Level (Inner Envelope) : Delimited by a Company/Batch Header Record (Type 5) and sealed by a Company/Batch Control Record (Type 8) . A file can contain one or multiple batches. Each batch isolates transactions that share identical origination characteristics, such as Standard Entry Class (SEC) code, Company ID, Effective Entry Date, and Service Class Code.
Entry Detail Level (Transaction Instruction) : Defined by individual Entry Detail Records (Type 6) . Each Type 6 record represents a specific financial or non-monetary transaction directed to an account at a Receiving Depository Financial Institution (RDFI).
Addenda Level (Supplemental Data) : Represented by Addenda Records (Type 7) attached directly behind their parent Type 6 record. Addenda records convey electronic data interchange (EDI) remittance data, return reason codes, or Notification of Change (NOC) details.
The 94-Character Fixed-Length Standard
Every record within an ACH transmission—regardless of whether it is a header, detail, addenda, control, or padding record—must contain exactly 94 ASCII characters .
No Delimiter Reliance : Fields within an ACH record are fixed-width and positional. They do not rely on commas, tabs, or variable tags. If a field contains fewer characters than its designated length, it must be padded with leading zeros (for numeric fields) or trailing blank spaces (for alphanumeric fields).
Record Delimiters : While transmission protocols may append carriage return ( CR ) and line feed ( LF ) characters at byte positions 95 and 96 for stream parsing, the logical Nacha record payload is strictly 94 bytes. Any file containing records of 93 or 95 characters is immediately rejected by ACH Operator validation engines.
Blocking Factors & End-of-File Nines Padding
ACH files utilize a mandatory blocking factor of 10 . This mainframe-era transmission optimization requires records to be grouped into physical transmission blocks of 10 records (940 characters) . Physical Block Size = 10 records × 94 characters/record = 940 characters \text{Physical Block Size} = 10 \text{ records} \times 94 \text{ characters/record} = 940 \text{ characters} Physical Block Size = 10 records × 94 characters/record = 940 characters
The Mathematical Padding Rule
If the total count of active logical records in a file (Type 1 + Type 5s + Type 6s + Type 7s + Type 8s + Type 9) is not an exact multiple of 10, the file must be padded with fill records containing ninety-four consecutive 9s ( 9999999999... ) until the next multiple of 10 is reached. Total Required Records = ⌈ Active Records 10 ⌉ × 10 \text{Total Required Records} = \lceil \frac{\text{Active Records}}{10} \rceil \times 10 Total Required Records = ⌈ 10 Active Records ⌉ × 10 Padding Records Required = Total Required Records − Active Records \text{Padding Records Required} = \text{Total Required Records} - \text{Active Records} Padding Records Required = Total Required Records − Active Records
Worked Example: Block Calculation
Suppose an ODFI generates an ACH file containing:
- 1 File Header Record (Type 1)
- 2 Company/Batch Header Records (Type 5)
- 18 Entry Detail Records (Type 6)
- 4 Addenda Records (Type 7)
- 2 Company/Batch Control Records (Type 8)
1 File Control Record (Type 9) Active Logical Records = 1 + 2 + 18 + 4 + 2 + 1 = 28 records \text{Active Logical Records} = 1 + 2 + 18 + 4 + 2 + 1 = 28 \text{ records} Active Logical Records = 1 + 2 + 18 + 4 + 2 + 1 = 28 records Block Count = ⌈ 28 10 ⌉ = 3 blocks (30 total records = 2,820 characters) \text{Block Count} = \lceil \frac{28}{10} \rceil = 3 \text{ blocks (30 total records = 2,820 characters)} Block Count = ⌈ 10 28 ⌉ = 3 blocks (30 total records = 2,820 characters) Nines Padding Records = 30 − 28 = 2 records (Records 29 and 30) \text{Nines Padding Records} = 30 - 28 = 2 \text{ records (Records 29 and 30)} Nines Padding Records = 30 − 28 = 2 records (Records 29 and 30)
If this file were transmitted with only 28 records, the ACH Operator would reject the entire file with a fatal framing/blocking error.
Field-by-Field Specification: File Header Record (Type 1)
The File Header Record identifies the physical sender and receiver of the transmission, establishes file creation timestamps, assigns processing priorities, and prevents duplicate file ingestion.
Field Positions Length Type Name Contents / Validation Rules
1 01–01 1 N Record Type Code Mandatory constant 1 . Identifies record as File Header.
2 02–03 2 N Priority Code Default 01 . Reserved for ACH Operator transmission priority handling.
3 04–13 10 A/N Immediate Destination 10 characters: a leading blank followed by the 9-digit Routing Transit Number (RTN) of the receiving ACH Operator or endpoint.
4 14–23 10 A/N Immediate Origin 10 characters. Formatted as a space ( ) or '1' followed by the 9-digit RTN or Tax ID/EIN of the sending ODFI or transmitting entity.
5 24–29 6 N File Creation Date Format YYMMDD . The calendar date the file was generated by the ODFI/sending point.
6 30–33 4 N File Creation Time Format HHMM . 24-hour military time indicating when file creation was completed.
7 34–34 1 A/N File ID Modifier A – Z (uppercase) or 0 – 9 . Distinguishes multiple files transmitted between the same Origin and Destination on the same Creation Date.
8 35–37 3 N Record Size Mandatory constant 094 . Specifies 94 characters per record.
9 38–39 2 N Blocking Factor Mandatory constant 10 . Specifies 10 records per physical block.
10 40–40 1 N Format Code Mandatory constant 1 . Specifies Nacha standard record format.
11 41–63 23 A/N Immediate Destination Name Left-justified, blank-filled name of receiving ACH Operator/DFI (e.g., FED REGIONAL ACH ).
12 64–86 23 A/N Immediate Origin Name Left-justified, blank-filled name of sending ODFI/institution (e.g., FIRST NATIONAL BANK ).
13 87–94 8 A/N Reference Code Optional. Left-justified, blank-filled tracking code for internal ODFI/sender record-keeping.
- Deep Dive: Critical File Header Mechanics
- 1. Immediate Destination vs. Immediate Origin Formatting
Nacha rules specify that routing transit numbers are 9 digits in length. Because Fields 3 and 4 are allocated 10 character positions, specific formatting rules apply:
Immediate Destination (Positions 04–13) : The receiving ACH Operator routing number (for example, 021000021 ) is preceded by a single blank ( 021000021 ).
Immediate Origin (Positions 14–23) : If the sending entity uses a 9-digit routing number, it is preceded by a space ( 121000358 ). If a 9-digit Federal Employer Identification Number (EIN) is used, it is commonly preceded by a 1 ( 1123456789 ).
2. The File ID Modifier & Duplicate File Detection
ACH Operators utilize a composite key to detect and reject duplicate file transmissions within their operational window: Duplicate Key = Immediate Origin + Immediate Destination + File Creation Date + File ID Modifier \text{Duplicate Key} = \text{Immediate Origin} + \text{Immediate Destination} + \text{File Creation Date} + \text{File ID Modifier} Duplicate Key = Immediate Origin + Immediate Destination + File Creation Date + File ID Modifier
If an ODFI transmits three distinct files to the Federal Reserve on October 24, 2026 ( 261024 ):
- File 1: File ID Modifier = A (Accepted)
- File 2: File ID Modifier = B (Accepted)
File 3: File ID Modifier = A ( REJECTED — Operator detects duplicate file key, even if the internal batch and dollar amounts differ).
If an ODFI exhausts alphabetic characters A through Z in a single day, it advances to numeric digits 0 through 9 .