Skip to main content

Fedwire® Funds Services ISO 20022 Implementation Frequently Asked Questions (revised as of July 2018)

ISO 20022 Overview

  1. What is ISO 20022?

    ISO refers to the International Organization for Standardization, which is a network of national standards bodies that develop international standards. ISO publishes standards for a broad range of industries. The United States is a member of and contributor to ISO standards for the financial industry through Accredited Standards Committee X9–Financial Industry Standards, Inc.

    The ISO 20022 standard supports financial messaging and uses extensible markup language (XML) syntax. ISO 20022 messages can carry a considerable amount of information and are based on a common data dictionary that can support payment message flows from end to end, including the following:

    • Payment initiation (corporate to bank)
    • Interbank settlement (bank to bank)
    • Cash management (bank to corporate)

    The ISO standard is being adopted by an increasing number of the world’s payments, clearing & settlement systems (Europe, Japan, Switzerland, India, Canada...and more) and growing interest from financial institutions, corporations and financial applications providers.

  2. Where can I learn basics about ISO 20022?

    The Business Payments Coalition (Off-site) (BPC) has two publications to help people learn more about ISO 20022. The BPC is a volunteer industry group of organizations and individuals working together to promote greater adoption of electronic business-to-business (B2B) payments, remittance data, and invoices. The BPC promotes awareness of and education about ISO 20022 as a service to their membership.

    1. Understanding ISO® 20022 Resource Guide (2017) (Off-site, PDF)
      This guide is a curated compilation of existing resources that provide information on the ISO 20022 standard, including tools that help with transitioning to the new standard such as mapping tools and implementation guides.
    2. U.S. Adoption of ISO 20022 (2017) (Off-site, PDF)
      This white paper, a companion document to the Understanding ISO® 20022 Resource Guide, provides information about U.S. adoption of ISO 20022 for corporate to bank payment operations. It highlights key drivers and benefits for businesses to adopt ISO 20022 along with best practices and lessons learned.

  3. What is a SWIFT Message Type (MT)? Is that the same as or different than the ISO 20022 message format?

    SWIFT Message Types (MTs) are the format or schema used to send messages to financial institutions on the SWIFT network. The original message types were developed by SWIFT but retroactively incorporated into an ISO standard, ISO 15022. ISO 20022 is a new standard based in large part on the ISO 15022 standard but using XML as its syntax.

  4. Can you provide an example of how the ISO 20022 format looks?

    The following example uses the address fields to illustrate one difference between the current Fedwire Funds Service proprietary message format and the ISO 20022 format.

    Current Format to ISO Format Comparison
    For each of the party fields in the message, the Fedwire Funds Service proprietary format contains three free-text lines for address information. The ISO 20022 format uses XML syntax and contains discrete fields designed to contain specific address information, which makes it easier to identify components of the address (e.g., country code).
    Address Line 1 (up to 35 characters)
    Address Line 2 (up to 35 characters)
    Address Line 3 (up to 35 characters)
    Postal Address <PstlAdr>
    <AdrTp> (4 characters)
    <Dept> (up to 70 characters)
    <SubDept> (up to 70 characters)
    <StrtNm> (up to 70 characters)
    <BldgNb> (up to 16 characters)
    <PstCd> (up to 16 characters)
    <TwnNm> (up to 35 characters)
    <CtrySubDvsn> (up to 35 characters)
    <Ctry> (2 characters)
  5. Can you provide some use cases to illustrate the potential benefits of the ISO 20022 format?

    Answer – In 2016, the Federal Reserve Banks presented a webinar on ISO 20022 Use Cases for U.S. Wire Transfer Systems. The webinar presentation and recording can be found on the FedPaymentsImprovement.org website (Off-site) under “Event Summaries and Recordings” or directly at:


Fedwire Funds Service ISO 20022 Implementation

  1. Why are the Federal Reserve Banks adopting ISO 20022 payment messages for the Fedwire Funds Service?

    The Federal Reserve Banks are adopting ISO 20022 messages for the Fedwire Funds Service as a strategic imperative. We believe modernizing the Fedwire Funds Service’s message format represents an investment for the future. Adopting the ISO 20022 message standard should help the Federal Reserve Banks meet increasing demands by customers for richer data, help customers more easily comply with evolving regulatory requirements, help improve the service’s interoperability with other payment systems given the interconnected, global economy, and help customers provide enhanced services to their clients. The table on the following page illustrates some strategic reasons for adopting ISO 20022 messages for the Fedwire Funds Service that were identified by the independent consultant that the Federal Reserve Banks, along with other organizations, retained to study the business case for adoption.

    Strategic Reasons to Adopt ISO 20022
    Reason Description
    Provides richer data The ISO 20022 format contains structured fields to support longer names and specific address components, including a country code, which could reduce the risk of data loss and might improve the regulatory screening process.

    The ISO 20022 format supports a structured format for extended remittance information, which could improve straight-through processing for corporate business-to-business payments.
    Promotes domestic & cross-border interoperability A common format promotes ease of transacting domestically and globally by using a single, open standard rather than multiple proprietary standards, which require mapping and can be costly and cumbersome for banks, corporates, and vendors.

    The ISO 20022 format contains fields that are common across the suite of ISO 20022 payment messages so that the same information can be carried from end to end of a funds transfer, which could increase accuracy and straight-through processing and reduce operating costs for all participants.

    Other payments markets, including those of key U.S. trading partners, have gone live with ISO 20022 (e.g., Bangladesh, Brunei, China, India, Japan, Switzerland) or are in the development stages of implementing ISO 20022 (e.g., Canada, Europe, United Kingdom).
    Provides opportunities to improve existing processes or add new services Moving to a common global format could:
    • Reduce the need for market practices that arise due to inconsistent formats and field and/or message capacity limitations
    • Improve extended remittance information capabilities
    • Support value-added services (e.g., payment tracking & prioritization, administrative and reporting functions)
    U.S. payment systems could fall behind the rest of the world and be perceived as “outdated” Lack of ISO 20022 adoption could:
    • Degrade the U.S. dollar’s leadership as a global settlement currency
    • Encourage migration of U.S. dollar clearing offshore, to other currencies, or to emerging payment systems built with new technologies.
  2. What will change in the Fedwire Funds Service as a result of implementing the ISO 20022 messaging standard?

    The Federal Reserve Banks will adopt ISO 20022 messages for both domestic and cross-border funds transfers, as well as all other inputs and outputs from the Fedwire Funds Service (i.e., all message types, inquiries, reports, etc.).

    The Fedwire Funds Service’s ISO 20022 implementation will also include enhancements based on customer feedback, including new fields for additional persons or entities identified in payment messages, purpose codes to help explain the business purpose of funds transfers, and structured address components, including a country code. You can view the webinar recordings under the Educational Event Summaries and Recordings section to learn more about the changes with this project.


  3. How will the Federal Reserve Banks migrate Fedwire Funds Service participants to the ISO 20022 format?

    Based on customer feedback, the ISO 20022 implementation will have three phases and will include a mandated sunset date for the Fedwire Funds Service’s legacy proprietary message format.

    Message Implementation Phased Approach
    Phase Implementation Approach
    Phase 1
    ISO 20022 Preparation
    "Big bang” implementation to align with SWIFT Message Type (MT) changes to originator and beneficiary fields and to prepare for and simplify the Fedwire Funds Service’s migration to ISO 20022 messages in Phases 2 and 3.
    Phase 2
    ISO 20022 Like for Like
    • Migrate Fedwire Funds Service participants in waves over 18 months to send and receive ISO 20022 messages that have fields and character lengths that are comparable to the legacy format.
    • The Fedwire Funds Service will translate the legacy format to ISO 20022 and vice versa when necessary to accommodate Fedwire senders and receivers that are not using the same format.
    • Fedwire Funds Service participants cannot send any enhancements during this phase; however, they will be required to demonstrate their ability in the Federal Reserve Banks’ test environment to receive ISO 20022 messages with the enhancements that will go live in Phase 3.
    • The Federal Reserve Banks will sunset the legacy format at end of this phase.
    Phase 3
    ISO 20022 Enhancements
    “Big bang” implementation to enable all Fedwire Funds Service participants to send optional enhancements.
  4. What are the key dates of the implementation plan?

    The key dates for each phase are outlined below.

    Implementation Key Dates
    Phase Implementation Date
    Phase 1
    ISO 20022 Preparation
    Saturday, November 21, 2020, with effect for the funds-transfer business day of Monday, November 23, 2020
    Phase 2
    ISO 20022 Like for Like
    Migrate participants in waves over 18 months to send and receive the ISO 20022 message format, which has fields and character lengths that are comparable to the legacy format:
    • Phase 2 begins Q1 2022
    • Phase 2 ends Q3 2023
    Phase 3
    ISO 20022 Enhancements
    Enable participants to send optional enhancements in Q4 2023
  5. Will the implementation phases overlap? For example, will Phase 1 and Phase 2 take place concurrently?

    No, the implementation phases will not overlap.

    Phase 1 is underway now and will be complete for all Fedwire Funds Service participants when the Fedwire Funds Service opens on Sunday evening, November 22, 2020, for the Monday, November 23, 2020, funds-transfer business day.

    Phase 2 will begin after Phase 1 is complete. This phase will begin in Q1 2022 and will involve migrating Fedwire Funds Service participants in waves over 18 months. Additional details will follow as the Federal Reserve Banks finalize the migration strategy. This phase will end in Q3 2023.

    Phase 3 will begin after Phase 2 is complete (i.e., after all Fedwire Funds Service participants have been migrated to the ISO 20022 message format). The date on which Phase 3 will be completed is yet to be determined but is planned to be in Q4 2023.

  6. What do I need to do to prepare for the Fedwire Funds Service’s implementation of ISO 20022 messages?

    The extent of your preparations will largely depend on:

    • How much technology you have integrated with the processing of your outgoing and incoming Fedwire Funds Service messages
    • The degree to which you perform your own software development
    • The degree to which you rely on service providers and/or software vendors to provide an interface to the Fedwire Funds Service

  7. What is the impact of the ISO 20022 implementation on my institution?

    The Federal Reserve Banks have published ISO 20022 format specifications for the Fedwire Funds Service. Participants may start their application development process and begin testing. Companies that develop software products that interface with the Fedwire Funds Service will also need to adapt and test those products to ensure they will be able to successfully interface with the Fedwire Funds Service once the format change is implemented.

    The table below shows how particular types of Fedwire Funds Service participants (or their service providers) will be affected by the ISO 20022 implementation.

    Customer Impact by Participant Method of Access
    Fedwire Funds Service Participants/Service Providers Impact
    Fedwire Funds Service participants and service providers that access the service via the FedLine Direct® solution or use the Import/Export feature of FedPayments® Manager – Funds over the FedLine Advantage® solution Participants may need to make (or may need to ensure their service providers make) significant changes to their payment applications or processes so they can send and receive messages in the new ISO 20002 message formats or import and export files with ISO 20022-formatted messages.

    This group of Fedwire Funds Service participants and service providers will need to obtain the ISO 20022 format specification documents, which will outline the changes needed to accommodate the ISO 20022 format for the Fedwire Funds Service. The Federal Reserve Banks will provide these Fedwire Funds participants and service providers with information about how to register for SWIFT’s MyStandards® service to obtain the ISO 20022 format specification documents when they become available later this year.

    Fedwire Funds Service participants that manually create messages directly into FedPayments Manager–Funds over the FedLine Advantage solution

    • The Federal Reserve Banks will make the necessary changes to the FedPayments Manager–Funds application and provide training on enhanced features.
    • Participants will need to become familiar with the look and feel of the updated application and with the enhanced features.
    Fedwire Funds Service participants that use the offline service
    • Participants’ current process for submitting messages to the offline service will not materially change.
    • There may be marginal changes around the type of information Wholesale Operations Site operators collect by telephone, as well as the order in which they collect the information, based on the new message format.
  8. Will the ISO 20022 implementation also apply to the Fedwire Securities Service or the FedACH Service?

    No, the Federal Reserve Banks are not implementing ISO 20022 messages for the Fedwire Securities Service or the FedACH Service. ISO 20022 messages are being implemented only for the Fedwire Funds Service.

Format Documentation

  1. What documentation will be available to explain the ISO 20022 implementation for the Fedwire Funds Service?

    The table below shows the different format specification documents that will be available in each phase.

    Documentation Availability on MyStandards by Phase
    Release Documentation Date Available
    Phase 1
    ISO 20022 Preparation
    • Fedwire Application Interface Manual (FAIM) version 4.0.1
    • High-level scope document highlighting changes

    March 2018 (Final)
    Phase 2
    ISO 20022 Like-for-Like
    &
    Phase 3
    ISO 20022 Enhancements
    • Mapping Spreadsheets - Two Excel® spreadsheets that map the legacy FAIM 4.0 format to ISO 20022 messages. ISO 20022 to legacy mapping documents targeted to be available in 2019.
    • Usage Guidelines - Explains the elements that are permitted in each ISO 20022 message and outlines other requirements (e.g., allowable codes, field lengths, allowable characters).
    • Implementation “Rulebook” - Overview of ISO 20022 implementation for the Fedwire Funds Service with message flow diagrams and includes suggested practices.
    July 2018 (Final)
  2. How will my institution get the format specifications to prepare for the ISO 20022 Fedwire Funds Service implementation?

    The Federal Reserve Banks will utilize a private page on SWIFT’s MyStandards website to provide Fedwire Funds Service format specification documents to Fedwire Funds Service participants so they can prepare for the phased implementation of ISO 20022 messages for the Fedwire Funds Service. A separate communication was previously sent to authorized individuals at your institution with instructions to gain access to the Federal Reserve Banks’ private page on the MyStandards website.

    • If your institution performs its own software development, authorized technical staff at your institution will need to obtain the Fedwire Funds Service format specification documents. If you have not yet requested MyStandards access for those individuals, please contact your account executive.
    • If your institution uses software developed by an outside vendor, the Federal Reserve Banks are working directly with the vendors to provide access to the format documents. Check this website to see if your software vendor is listed. If your vendor is not listed on the website, please submit the legal name of the vendor (Off-site) as well as contact information.
    • If your institution acts as a service provider to send and receive Fedwire Funds Service messages for other institutions, the Federal Reserve Banks do not plan to provide those other institutions with access to the MyStandards platform. If you are aware that those institutions nevertheless have a business need to view the Fedwire Funds Service format specification documents, please contact your account executive. We strongly encourage you to communicate this approach to those other institutions.

  3. My institution acts as a service provider for other institutions. Will our customers need to sign up for access to MyStandards?

    If your institution acts as a service provider to send and receive Fedwire Funds Service messages for other institutions, the Federal Reserve Banks do not plan to separately provide those institutions with access to the MyStandards website.

    If you are aware that those institutions nevertheless have a business need to view the Fedwire Funds Service format specification documents, please contact your account executive.

Software Vendor Information

  1. What do I need to do if I use a software application other than the FedPayments Manager to create funds-transfer messages that are submitted to the Fedwire Funds Service for processing?

    As part of their work implementing ISO 20022 messages for the Fedwire Funds Service, the Federal Reserve Banks plan to work directly with software vendors whose products interface with the Fedwire Funds Service.

    To date, the Federal Reserve Banks are aware of the software vendors whose products interface with the Fedwire Funds Service identified on this page. The Federal Reserve Banks will provide the Fedwire Funds Service format specification documents directly to those vendors.

  2. My vendor is not on the list you mentioned in response to question D1. What does my institution need to do to ensure our vendor is included?

    If your institution uses a vendor that provides software products that interface with the Fedwire Funds Service, including products that take advantage of the FedPayments Manager–Funds import/export feature but the name of that vendor does not appear on this page, please submit the legal name of the vendor (Off-site) as well as the contact information so the Federal Reserve Banks may provide the necessary information to the vendor.

    Submit Software Vendor Contact Information (Off-site)

Testing Strategy

  1. When will the Depository Institution Testing (DIT) environment be available for each of the phases?

    The Federal Reserve Banks plan to make the DIT available for customer and software vendor testing as noted below:

    • Phase 1: February 2020 (9 months)
    • Phase 2: March 2021 (1 year)
    • Phase 3: November 2022 (1 Year)

  2. Who will be required to complete testing in the Depository Institution Testing (DIT) environment? Does this also apply to Production Testing on a Saturday?

    Fedwire Funds Service participants and service providers that access the service via the FedLine Direct solution and/or that use the import/export feature of the FedPayments Manager–Funds application will be required to complete testing. In 2019, the Federal Reserve Banks will to share details about the testing strategy for all phases of the ISO 20022 implementation.

  3. Will the Fed provide a mechanism for customers and vendors to test their ISO 20022 schemas against the ISO 20022 usage guidelines for the Fedwire Funds Service?

    In 2019, the Federal Reserve Banks will leverage the MyStandards Readiness Portal to allow customers and vendors to test their schemas against the ISO 20022 usage guidelines for the Fedwire Funds Service.

  4. When will the Federal Reserve Banks publish the testing strategy for each of the three phases and the customer migration strategy for Phase 2?

    The Federal Reserve Banks plan to publish the testing strategy for Phase 1 by yearend 2018. For Phases 2 and 3 testing strategy and customer migration strategy for Phase 2 will be announced in 2019.

Education and Training

  1. Where can I get more information on the ISO 20022 implementation for the Fedwire Funds Service?

    For the latest information on the Federal Reserve Banks’ approach to implementing ISO 20022 messages for the Fedwire Funds Service and planned educational outreach events, please visit the Fedwire Funds Service ISO 20022 Implementation Center page. For additional background information, please visit The Fed’s Resource Center for Adoption of ISO 20022 for Wire Transfers and ACH Payments (Off-site). You can also request a free copy of ISO 20022 for Dummies (Off-site).

  2. How can I learn more about the ISO 20022 implementation for the Fedwire Funds Service?

    The Federal Reserve Banks have designed an educational outreach program to increase awareness of their ISO 20022 initiative for the Fedwire Funds Service and the changes it will bring. You can view the webinar recordings under the Educational Event Summaries and Recordings section to learn more about this project.

  3. We create wires manually in FedPayments Manager-Funds application. When will we get trained on the new screens?

    In late 2019, the Federal Reserve Banks will host webinars to help Fedwire Funds Service participants familiarize themselves with the new look and feel of the screens for the Phase 1 implementation. Training webinars for Phases 2 and 3 will be announced at a later date.

Additional Questions

  1. My institution uses templates in the FedPayments Manager–Funds application. Will I have to update my templates?

    If your institution uses templates in the FedPayments Manager–Funds application, these templates will no longer work when the Phase 1 release is implemented in November 2020. Given significant changes that will be included in this release, the Federal Reserve Banks will not be able to convert existing templates that have been created in the current format version. Your institution will be required to recreate templates that you need in the new format after Phase 1 is implemented.

    To prepare for this change, your institution can:

    • review how the templates are currently being used;
    • consider reducing the number of templates you have and only keep those that are critical for your operation;
    • test in the Depository Institution Test environment to become familiar with the template feature in the new format; and,
    • be prepared to recreate those critical templates in the new format after Phase 1 is implemented.

  2. Will broadcast messages for E-Payments Directory and Fedwire Securities Service move to the ISO 20022 standard?

    Broadcast messages related to the E-Payments Directory and Fedwire Securities Service will remain in the legacy format.

  3. We receive the end-of-day Financial Institution Reconcilement Data (FIRD) file from the Fed. Will this file be changed in anyway with the ISO 20022 project?

    The Federal Reserve Banks will implement a change to one field that contains the type/subtype code (i.e., four numeric characters). With the Phase 2 implementation targeted to begin in March 2022, this field will be replaced by a new local instrument code, which will be in four alphanumeric characters. See example below:

    Example of the Message Type with the Type/Subtype and the Local Instrument Code
    Message Type Type/Subtype Local Instrument Code
    Customer Transfer 1000 CTR0
    Bank Transfer 1600 BTR6

Top of Page