- Home
- Resources
- Financial Services
- ACH
- FedACH® Frequently Asked Questions
- International ACH Transaction (IAT) Frequently Asked Questions
Federal Reserve Financial Services is committed to providing the answers and information you need. Answers to many of our customers most frequently asked questions can be found using the links below.
If your question is not answered by the information provided on the site, Contact provides a comprehensive list of service and support contacts who can assist you.
IAT is a new standard class entry (SEC) code that will replace the CBR and PBR SEC codes that are currently in use today. NACHA rules will require the IAT code and format of all ACH payments entering or exiting the U.S.
The IAT SEC code will be used for both consumer and corporate international ACH credits and debits. In addition to requiring data elements defined by the Bank Secrecy Act’s (BSA) "Travel Rule", OFAC screening indicators will be included with each payment to help RDFIs identify suspicious payments. Furthermore, all international inbound transactions will allow the use of a secondary SEC code to further identify the file type for all WEB, TEL, ARC, POP, BOC, and RCK transactions where applicable.
IAT was developed to respond to OFAC’s request to align the NACHA Rules with OFAC compliance obligations and to make it easier for RDFIs to comply with those obligations. In the current environment, many U.S. financial institutions are receiving international payments that cannot be properly identified. These unidentifiable payments enter the U.S. through correspondent banking relationships and are often difficult to trace or accurately process as international payments. The new IAT code supports the end of anonymity and promotes traceability of international electronic payments.
The introduction of the IAT code will impact all U.S. financial institutions, including those that do not currently send or receive international payments as any financial institution is a potential receiver of an IAT transaction.
Yes, OFAC rules apply to all payments, both domestic and international. DFIs and their customers should consult with their internal compliance officer on their requirements. Further information can also be found on the OFAC website (Off-site).
This section includes questions related to IAT record layouts and format considerations.
The new format will accommodate the following data elements:
The Foreign Correspondent Bank addenda record refers to the correspondent bank of the foreign originating financial institution and is used only with inbound items.
ACH Operators will reject an IAT item when the maximum number of addenda records [12] is exceeded. Similarly, if the number of addenda records entered in Field 5 of the entry detail record does not match the number of actual addenda records edited, the item will also reject.
Although the ISO Destination Country Code field found in the Company/Batch Header Record is two digits in length and the Originating DFI Branch Country Code field found in the addenda record is three digits in length, all ISO country codes are to be identified using a two digit alpha designation. The branch country code will occupy the two leftmost positions, with a space filling the third position. It is important to note that ACH Operators do not validate the contents of this mandatory field other than to confirm it does not contain all spaces or all zeroes.
There are two OFAC screening indicator fields in the IAT Record: In the Entry Detail Record, Field 10 is the Gateway Operator OFAC Screening Indicator, and Field 11 is the Secondary OFAC screening indicator.
The reason for payment must be included in IAT entries to provide relevant information in support of Regulation E. The IAT transaction type code field is a required field that will carry the three-character code indicating the reason for payment. Reason for payment is currently used for CBR / PBR transactions and the code listing can be found in Section 2.2 “Code Values” of the NACHA Rules book. With IAT, the use of the transaction type code field will be expanded for inbound IAT transactions to carry a secondary SEC code for WEB, TEL, ARC, POP, BOC, RCK, POS, SHR and MTE.
You can find extensive information about the new IAT format in the section of the 2008 ACH Rules entitled 2009 Rules Changes. To purchase your copy of the ACH Rules, please contact the nearest regional payments association which can be found through the following URL: http://www.nacha.org/ (Off-site).
The GO Identification/Receiving DFI Identification field in the IAT entry detail record will be populated just as CBR and PBR entries are formatted today. An RTN is currently used to represent each FedGlobal Service country. The RTNs of the service countries can be found in each corresponding FedGlobal Service Manual.
This section includes questions related to Office of Foreign Assets Control (OFAC) compliance and related responsibilities of financial institutions.
All depository financial institutions, whether originating or receiving, are responsible for OFAC compliance. Likewise, OFAC compliance applies to third-party service providers, including processors and correspondent/respondent banks. Although a financial institution might contract with a third-party provider to do the actual OFAC review of the transactions, OFAC rules clearly indicate that a financial institution cannot contract away its liability for OFAC compliance.
Yes. OFAC rules apply to all payments, both domestic and international. Depository financial institutions and their customers should consult with their internal compliance officer on their organizations’ requirements. Further information can also be found on the OFAC website (Off-site).
Gateway operators are required to perform OFAC screening on all incoming IAT items. The gateway operator will flag each item with either a “1” to indicate a possible hit or a “0” to indicate that there was no hit. ACH operators acting as gateways operators are not required, however, to validate potential hits and will not block transactions or freeze funds. ODFIs acting as gateway operators, on the other hand, do have additional OFAC obligations. Further information can also be found on the OFAC website (Off-site)
There are two OFAC screening indicators for IAT records: in the Entry Detail Record, field 10 is the Gateway Operator OFAC Screening Indicator, and field 11 is the Secondary OFAC Screening Indicator.
Ultimately, the receiving financial institution bears all responsibility for OFAC compliance. Although the gateway operator will perform inbound screening on inbound IAT items and populate the necessary fields, the receiving financial institution is still required to perform the necessary due diligence on IAT items in order to properly comply with OFAC obligations.
No. The Federal Reserve, in its capacity as a gateway operator, will only perform OFAC screening on those incoming IAT items that flow through FedGlobal Services. Inbound IAT items entering the country through another gateway operator will not be screened by the Federal Reserve but rather by that gateway operator.
This section includes questions related to FedACH testing availability, gateway operator vs. ACH operator roles, processing differences, and FedGlobal® enhancements.
Yes, the Federal Reserve acting as a gateway operator will screen any inbound IAT items that are processed as part of our FedGlobal Services. As an ACH operator, the Federal Reserve is not obligated to screen IAT items coming from or to other ACH participants including other U.S. gateway operators.
No, the Federal Reserve, acting as a gateway operator, will not allow inbound debit entries through FedGlobal Services. The reasoning is because the Federal Reserve cannot offer the same warranties as an ODFI to ACH network participants regarding IAT items. ODFI warranties are outlined in the NACHA Rules.
The Federal Reserve acting as gateway operator will populate the Gateway Operator OFAC Screening Indicator, field 10 in the IAT entry detail record, with either a “1” to indicate a possible match or a “0” to indicate that there was no match. The Federal Reserve will not hold, pend or reject any IAT item, regardless of whether that item has been flagged as a potential match.
As an ACH operator, the Federal Reserve will process all IAT items according to the ACH Rules, which allow for prenotification and notification of change (NOC) entries. However, as a gateway operator, the Federal Reserve will apply edits according to FedGlobal Services specifications and business operating procedures. These differences include, but are not limited to, prenotifications, NOCs, recalls and reversals. For additional details regarding FedGlobal Services, please refer to the appropriate service implementation manual.
The GO Identification/Receiving DFI Identification field in the IAT entry detail record will be populated just as CBR and PBR entries are formatted today. An RTN is currently used to represent each FedGlobal Service country. The RTNs of the service countries can be found in each corresponding FedGlobal Service Manual.
Yes, the “Derive a Return Item” feature in FedLine Web will be updated to support the return of IAT items.
The Federal Reserve will offer the following tools that will readily identify IAT items sent to RDFIs:
FedGlobal Services is currently exploring opportunities to expand the countries accessed as well as product features. To receive the latest news about FedGlobal enhancements, sign up for Email Alert Notification on FRBservices.org and select FedACH Services.
Prior to participation, a DFI should complete and return the Service Request Form to the FedACH Services Sales Specialist at is servicing Reserve Bank. You may complete one form for all or any of the FedGlobal Services. The forms are available in the respective Service Implementation Manuals for each partner country, which are available on the FedGlobal Processing Resources.