IAT Entries (International ACH Transaction)
IAT entries are used when the originating or receiving financial institution is outside the United States. It may additionally be used in scenarios where the funds related to the transaction are sourced from or ultimately sent to a country outside the United States even if that transfer does not take place over the ACH network.
Currently, PlatformNext supports only IAT transactions between US financial institutions in USD currency. This allows originators who must provide the additional details required in an IAT transaction to remain in compliance with applicable laws and regulations.
Formatting Requirements
The NACHA rules require additional details regarding the transaction to be transmitted in a sequence of specially designated addenda records to the transaction. There are 7 mandatory records and an additional 2 types of optional records that may be included up to a maximum of 12 total addenda records.
When processing an IAT in PlatformNext, these records should be provided in the Ach Addenda Records field. Each record is a fixed width text line. The layout of each record as expected by PlatformNext is detailed below. Additional details can be found in the NACHA Operating Rules and Guidelines.
Record Layout Overview
Minimum of 7 and maximum of 12 addenda records per payment. | ||
Seven (7) addenda records | Mandatory | ‘710’ Foreign Payment Amount / Receiver’s Name ‘711’ Originator’s Name / Street ‘712’ Originator’s City / State / Country / Postal Code ‘713’ ODFI Name / ID/ Branch Country Code ‘714’ RDFI Name / ID / Branch Country Code ‘715’ Receiver’s ID Number / Street ‘716’ Receiver’s City / State / Country / Postal Code |
One (1) or two (2) remittance addenda records | Optional | ‘717’ |
Up to five (5) Correspondent Bank addenda records | Conditional | ‘718’ |
First IAT Addenda Record
Field | 1 | 2 | 3 | 4 | 5 | 6 |
Data Element Name | Record Type Code | Addenda Type Code | Transaction Type Code | Foreign Payment Amount | Foreign Trace Number | Receiving Company Name / Individual Name |
Contents | '7' | ‘10’ | Alphameric1 | Zero (0) Filled | Space Filled | Alphameric |
Length | 1 | 2 | 3 | 18 | 22 | 35 |
Position | 01-01 | 02-03 | 04-06 | 07-24 | 25-46 | 47-81 |
1 Transaction Type Code should specify the reason for the payment using one of the following identifiers:
‘ANN’ (Annuity)
‘BUS’ (Business/Commercial)
‘DEP’ (Deposit)
‘LOA’ (Loan)
‘MIS’ (Miscellaneous)
‘MOR’ (Mortgage)
‘PEN’ (Pension)
‘REM’ (Remittance)
‘RLS’ (Rent/Lease)
‘SAL’ (Salary/Payroll)
‘TAX’ (Tax)
Second IAT Addenda Record
Field | 1 | 2 | 3 | 4 |
Data Element Name | Record Type Code | Addenda Type Code | Originator Name | Originator Street Address |
Contents | '7' | ‘11’ | Alphameric | Alphameric |
Length | 1 | 2 | 35 | 35 |
Position | 01-01 | 02-03 | 04-38 | 39-73 |
Third IAT Addenda Record
Field | 1 | 2 | 3 | 4 |
Data Element Name | Record Type Code | Addenda Type Code | Originator City & State / Province1 | Originator Country & Postal Code2 |
Contents | '7' | ‘12’ | Alphameric | Alphameric |
Length | 1 | 2 | 35 | 35 |
Position | 01-01 | 02-03 | 04-38 | 39-73 |
1 The City and State / Province should be separated with and asterisk (*) and end with a tilde (~).
Example: Pittsburgh*PA~
2 The Country and Postal Code should be separated with and asterisk (*) and end with a tilde (~). The country should be a valid ISO 3166-1-alpha-2 code.
Example: US*15212~
Fourth IAT Addenda Record
Field | 1 | 2 | 3 | 4 | 5 | 6 |
Data Element Name | Record Type Code | Addenda Type Code | Originating DFI Name | Originating DFI Identification Number Qualifier | Originating DFI Identification | Originating DFI Branch Country Code |
Contents | '7' | ‘13’ | Alphameric | Alphameric1 | Alphameric | Alphameric2 |
Length | 1 | 2 | 35 | 2 | 34 | 3 |
Position | 01-01 | 02-03 | 04-38 | 39-40 | 41-74 | 75-77 |
1 Originating DFI Identification Number Qualifier should be a value from the following list:
‘01’ - National Clearing System Number
‘02’ - BIC Code
‘03’ - IBAN
2 The country code should be a valid ISO 3166-1-alpha-2 code even though the field is 3 characters.
Fifth IAT Addenda Record
Field | 1 | 2 | 3 | 4 | 5 | 6 |
Data Element Name | Record Type Code | Addenda Type Code | Receiving DFI Name | Receiving DFI Identification Number Qualifier | Receiving DFI Identification | Receiving DFI Branch Country Code |
Contents | '7' | ‘14’ | Alphameric | Alphameric1 | Alphameric | Alphameric2 |
Length | 1 | 2 | 35 | 2 | 34 | 3 |
Position | 01-01 | 02-03 | 04-38 | 39-40 | 41-74 | 75-77 |
1 Receiving DFI Identification Number Qualifier should be a value from the following list:
‘01’ - National Clearing System Number
‘02’ - BIC Code
‘03’ - IBAN
2 The country code should be a valid ISO 3166-1-alpha-2 code even though the field is 3 characters.
Sixth IAT Addenda Record
Field | 1 | 2 | 3 | 4 |
Data Element Name | Record Type Code | Addenda Type Code | Receiver Identification Number1 | Receiver Street Address |
Contents | '7' | ‘15’ | Alphameric | Alphameric |
Length | 1 | 2 | 15 | 35 |
Position | 01-01 | 02-03 | 04-18 | 19-53 |
1 Receiver Identification Number may be used by the Originator to include a value for their own purposes.
Seventh IAT Addenda Record
Field | 1 | 2 | 3 | 4 |
Data Element Name | Record Type Code | Addenda Type Code | Receiver City & State / Province1 | Receiver Country & Postal Code2 |
Contents | '7' | ‘16’ | Alphameric | Alphameric |
Length | 1 | 2 | 35 | 35 |
Position | 01-01 | 02-03 | 04-38 | 39-73 |
1 The City and State / Province should be separated with and asterisk (*) and end with a tilde (~).
Example: Pittsburgh*PA~
2 The Country and Postal Code should be separated with and asterisk (*) and end with a tilde (~). The country should be a valid ISO 3166-1-alpha-2 code.
Example: US*15212~
IAT Addenda Record for Remittance Information
Field | 1 | 2 | 3 |
Data Element Name | Record Type Code | Addenda Type Code | Payment Related Information |
Contents | '7' | ‘17’ | Alphameric |
Length | 1 | 2 | 80 |
Position | 01-01 | 02-03 | 04-83 |
NOTE: A maximum of two optional remittance addenda records may be included.
IAT Addenda Record for Foreign Correspondent Bank Information
Field | 1 | 2 | 3 | 4 | 5 | 6 |
Data Element Name | Record Type Code | Addenda Type Code | Foreign Correspondent Bank Name | Foreign Correspondent Bank Identification Number Qualifier | Foreign Correspondent Bank Identification | Foreign Correspondent Bank Branch Country Code |
Contents | '7' | ‘18’ | Alphameric | Alphameric1 | Alphameric | Alphameric2 |
Length | 1 | 2 | 35 | 2 | 34 | 3 |
Position | 01-01 | 02-03 | 04-38 | 39-40 | 41-74 | 75-77 |
NOTE: A maximum of five conditional foreign correspondent bank addenda records may be included.
1 Foreign Correspondent Bank Identification Number Qualifier should be a value from the following list:
‘01’ - National Clearing System Number
‘02’ - BIC Code
‘03’ - IBAN
2 The country code should be a valid ISO 3166-1-alpha-2 code even though the field is 3 characters.
Example Addenda Records
710MIS000000000000000000 John Brown
711ACME Inc. 15 West Place Street
712Pittsburgh*PA~ US*15212~
713Wells Fargo 01121042882 US
714Citadel Bank 01231380104 US
715 2121 Front Street
716Nashville*TN~ US*37201~
717Additional optional payment information
718Scotiabank 02NOSCCATTXXX CA