Study guide
5.4 IAT (International ACH Transactions): Mandatory Addenda & OFAC Screening
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
5.4 IAT (International ACH Transactions): Mandatory Addenda & OFAC Screening
Key Takeaways Explain This Topic AI
An International ACH Transaction (IAT) is an entry that is part of a payment transaction involving a financial agency located outside the territorial jurisdiction of the United States.
IAT applies universally to both inbound and outbound transactions, consumer and commercial accounts, and both credit and debit entries.
Every IAT Entry Detail Record strictly mandates a sequence of seven (7) Addenda Records (Addenda Type Codes 10–16) containing foreign exchange data, full physical addresses of Originator and Receiver, and financial agency identifiers.
Gateway Operators, ODFIs, and RDFIs are legally mandated to execute strict Office of Foreign Assets Control (OFAC) sanctions screening against the Specially Designated Nationals (SDN) list for all IAT transactions.
IAT entries are currently excluded from Same Day ACH processing. Treat that as an eligibility rule for the October 2026 exam, not as a permanent technical impossibility.
Last updated: August 2026
5.4 IAT (International ACH Transactions): Mandatory Addenda & OFAC Screening
Core Principle: An International ACH Transaction (IAT) is a Standard Entry Class code mandated for any ACH payment that involves a Financial Agency located outside the territorial jurisdiction of the United States. Designed to align the ACH Network with the Bank Secrecy Act (BSA) , FinCEN Travel Rule (31 CFR Section 1010.410) , and Office of Foreign Assets Control (OFAC) sanctions requirements, IAT enforces a rigid 7-addenda record payload and strict screening mandates.
- 1. IAT Scope & Defining Criteria
- The Definition of a Financial Agency
Under Nacha Operating Rules (Article Eight), a Financial Agency is defined broadly as an entity authorized by a foreign government to accept deposits, issue letters of credit, hold funds, or execute funds transfers—including foreign commercial banks, central banks, offshore branches of U.S. banks, money services businesses (MSBs), and licensed currency transmitters.
When Must a Transaction Be Classified as IAT?
A transaction MUST be originated using the IAT SEC code whenever:
Direct Cross-Border Flow: Funds move directly between a U.S. financial institution and a foreign financial agency.
Indirect / Intermediary Cross-Border Flow: A foreign financial agency acts as an intermediary, sender, instructing party, or ultimate beneficiary in the payment chain—even if the entry clears between two domestic U.S. bank accounts. IAT IDENTIFICATION SCENARIOS
- Scenario 1: Direct Inbound
- [Foreign Employer Bank (London)] ===> [U.S. Gateway Operator] ===> [U.S. RDFI (Payroll Direct Deposit)]
- => MUST BE IAT
- Scenario 2: Direct Outbound
- [U.S. Corporate Originator] ===> [U.S. ODFI] ===> [U.S. Gateway Operator] ===> [Foreign Supplier Bank (Tokyo)]
- => MUST BE IAT
- Scenario 3: Domestic Leg of Cross-Border Movement (Funded Transfer)
- [Foreign Parent Co] --(Wire)--> [U.S. Account A] --(ACH Transfer)--> [U.S. Account B]
- => If U.S. ACH transfer is explicitly funded from foreign wire, it MUST BE IAT
- Inbound vs. Outbound IAT
Inbound IAT: Originates outside the U.S., enters the domestic ACH Network through a U.S. Gateway Operator (FedACH or EPN) acting as the ODFI, and is delivered to a domestic RDFI.
Outbound IAT: Originates from a domestic U.S. Originator/ODFI, clears through a U.S. Gateway Operator, and is delivered to a foreign receiving gateway / foreign financial agency.
2. Technical Blueprint: The Mandatory 7-Addenda Record Structure
Unlike domestic SEC codes that carry zero, one, or variable addenda records, every single IAT Entry Detail Record (Type 6) MUST be accompanied by a minimum of seven (7) mandatory Addenda Records (Type 7) in an unalterable sequential order (Addenda Type Codes 10 through 16 ). THE IAT 7-MANDATORY ADDENDA STACK
- +-----------------------------------------------------------------------------------------+
- | Type 6: IAT Entry Detail Record (Addenda Indicator = '1') |
- +-----------------------------------------------------------------------------------------+
- ├── Type 7: Addenda 10 -> Foreign Exchange Indicator, ISO Country Code, Currency Code
- ├── Type 7: Addenda 11 -> Originator Name & Originator Street Address
- ├── Type 7: Addenda 12 -> Originator City, State/Province, Postal Code & Country Code
- ├── Type 7: Addenda 13 -> Originating DFI / Foreign Financial Agency Name & Identifier
- ├── Type 7: Addenda 14 -> Receiving DFI / Foreign Financial Agency Name & Identifier
- ├── Type 7: Addenda 15 -> Receiver Name & Receiver Street Address
- └── Type 7: Addenda 16 -> Receiver City, State/Province, Postal Code & Country Code
- ----------------------------------------------------------------------------------------
- (Additional Addenda Records Follow Below)
- ├── Type 7: Addenda 17 -> Remittance Information (ANSI ASC X12 / Invoice data, Max 2)
└── Type 7: Addenda 18 -> Foreign Correspondent Bank Information (Up to 5 when foreign correspondents are involved)
Field-by-Field Breakdown of IAT Addenda Records (10–18)
Addenda Type Code Record Name Mandatory / Optional Critical Field Elements Included
10 First IAT Addenda Mandatory Foreign Exchange Indicator ( FV , FF , VF ), ISO Destination Country Code, ISO Destination Currency Code, FX Reference.
11 Second IAT Addenda Mandatory Originator Name (Positions 04–38), Originator Street Address (Positions 39–73).
12 Third IAT Addenda Mandatory Originator City & State/Province (Positions 04–38), Originator Postal Code & ISO Country Code (Positions 39–73).
13 Fourth IAT Addenda Mandatory Originating DFI Name, ID Qualifier (BIC/SWIFT, CHIPS, National Clearing Code), DFI Identification Number, ISO Branch Country Code.
14 Fifth IAT Addenda Mandatory Receiving DFI Name, ID Qualifier (BIC/SWIFT, CHIPS, Routing Number), DFI Identification Number, ISO Branch Country Code.
15 Sixth IAT Addenda Mandatory Receiver Name (Positions 04–38), Receiver Street Address (Positions 39–73).
16 Seventh IAT Addenda Mandatory Receiver City & State/Province (Positions 04–38), Receiver Postal Code & ISO Country Code (Positions 39–73).
17 Remittance Data Optional Up to two (2) records for invoice details, ANSI ASC X12 segments, or free-form remittance notes.
18 Correspondent Bank Conditional Up to five (5) records identifying intermediary and correspondent financial agencies when foreign correspondent banks handle the payment.
Foreign Exchange Rate Indicators in Addenda 10
FV (Fixed-to-Variable): Entry originated in fixed U.S. Dollars; converts to a variable foreign currency amount at the receiving endpoint.
FF (Fixed-to-Fixed): Entry originated in a fixed foreign currency and settles in the exact same fixed amount in foreign currency (or vice versa).
VF (Variable-to-Fixed): Entry originated in variable U.S. Dollars calculated to yield a fixed target foreign currency payout.
3. OFAC Sanctions Compliance & Screening Obligations
The Office of Foreign Assets Control (OFAC) of the U.S. Department of the Treasury administers and enforces economic and trade sanctions against targeted foreign countries, terrorists, international narcotics traffickers, and entities engaged in weapons proliferation. OFAC SANCTIONS SCREENING WORKFLOW
- ┌────────────────────────────────────┐
- │ Incoming IAT Entry (Addenda 10-16) │
- └─────────────────┬──────────────────┘
- │
- ▼
- ┌────────────────────────────────────┐
- │ Screen all Parties against SDN List│
- │ (Originator, Receiver, Banks) │
- └─────────────────┬──────────────────┘
- │
- ┌───────────────────────────┴───────────────────────────┐
- ▼ ▼
- ┌───────────────────────────┐ ┌───────────────────────────┐
- │ NO MATCH / FALSE POSITIVE │ │ TRUE MATCH (SDN HIT) │
- │ Post / Transmit Entry │ │ Check Program Mandate │
- └───────────────────────────┘ └─────────────┬─────────────┘
- │
- ┌───────────────────────────┴───────────────────────────┐
- ▼ ▼
- ┌───────────────────────────┐ ┌───────────────────────────┐
- │ BLOCK / FREEZE FUNDS │ │ REJECT / PROHIBIT │
- │ • Place in Blocked Acct │ │ • Return Entry via ACH │
- │ • DO NOT RETURN via ACH │ │ • Return Code: R16 │
- │ • Report to OFAC in 10 d │ │ • Report to OFAC in 10 d │
- └───────────────────────────┘ └───────────────────────────┘
- Screening Obligations by Participant
U.S. Gateway Operators: Must screen all inbound and outbound IAT entries passing through their central clearing facilities.
Originating DFIs (ODFIs): Must screen all outbound IAT entries, including Originator, Receiver, and all foreign financial agencies identified in Addenda 10–18, before releasing the file into the ACH Network.
Receiving DFIs (RDFIs): Must screen all inbound IAT entries against the Specially Designated Nationals and Blocked Persons (SDN) List prior to posting funds to customer accounts.
The Critical Distinction: Blocking vs. Rejecting
When an RDFI or Gateway Operator identifies a confirmed OFAC match, it must determine whether the specific sanctions program mandates Blocking (Freezing) or Rejecting :
Blocking (Asset Freeze):
Required under comprehensive sanctions (e.g., targeted terrorist organizations, narcotics kingpins, specific sanctioned regimes).
Action: The RDFI must freeze the funds immediately and hold them in a segregated, interest-bearing blocked account.
STRICT PROHIBITION: The RDFI MUST NOT return the entry through the ACH Network ! Returning a blocked entry releases the funds back into the financial stream, violating federal law.
Reporting: Must file a formal blocking report with OFAC within ten (10) business days .
Rejecting (Transaction Prohibition):
Required when a transaction is prohibited by OFAC policy but no blockable property interest exists.
Action: Follow OFAC instructions. During the October 2026 exam window, use R16 when OFAC instructs the RDFI to return the Entry. R85 addresses an incorrect foreign-exchange indicator and is not a sanctions-return code.
Reporting: Must file a formal rejection report with OFAC within ten (10) business days .
Bank Secrecy Act / FinCEN Travel Rule (31 CFR Section 1010.410)
The IAT 7-addenda format satisfies the FinCEN Travel Rule mandate for funds transfers of $3,000 or more , ensuring that full originator name, street address, account number, identity of financial institutions, and beneficiary data travel with the payment order throughout the complete clearing chain.
4. Exclusion from Same Day ACH
Under the Nacha Operating Rules in force for the October 2026 exam, IAT entries are excluded from Same Day ACH processing .
This is a Rules eligibility restriction, not a conclusion that IAT files are technologically impossible to process quickly. IAT screening, gateway, foreign-payment, and addenda obligations still apply, but the exam answer turns on the explicit Same Day eligibility rule. Same Day ACH Eligibility = PPD, CCD, CTX, WEB, TEL — IAT (Strictly Excluded) \text{Same Day ACH Eligibility} = \text{PPD, CCD, CTX, WEB, TEL} \quad \text{---} \quad \text{IAT (Strictly Excluded)} Same Day ACH Eligibility = PPD, CCD, CTX, WEB, TEL — IAT (Strictly Excluded)
If an Originator attempts to transmit an IAT entry with a same-day Effective Entry Date, the ACH Operator automatically assigns the transaction to the next standard (next-day) clearing window.