What changed when Fedwire moved to ISO 20022?

On July 14, 2025, Federal Reserve Financial Services (FRFS) replaced the Fedwire Funds Service's proprietary FAIM message format with ISO 20022 in a single-day implementation, after moving the date from March 10, 2025. Every Fedwire funds message now has an ISO 20022 form, such as pacs.008 for customer transfers and pacs.009 for bank-to-bank transfers, with a mandatory UETR and discrete address fields. The follow-on release that removes the unstructured address option was rescheduled in August 2026 from November 2026 to November 2027.

All dates and rules below come from the Federal Reserve's own Fedwire pages at frbservices.org. Your bank, service provider or core vendor may have additional cutoffs.

When did Fedwire move to ISO 20022?

The Fed's completion announcement noted that the Fedwire Funds Service settles more than $4.7 trillion in wire transfers on average per day, and its FAQ says processing speed did not change after the cutover. FRFS: migration complete Fedwire ISO 20022 FAQ

Which ISO 20022 messages replaced FAIM?

The Fed's format FAQ sets out which message to use for each job. Fedwire format FAQ

The account reports are worth a separate look if you reconcile Fedwire activity. The Fed's account reporting FAQ says each camt.052 arrives as one message, the Activity Report is capped at four megabytes (roughly 2,000 transactions), and high-volume receivers should check the page number and last-page indicator. camt.053 vs camt.054 vs MT940 compares reporting formats more broadly.

What changed in the payment data?

Addresses. FAIM carried three free-text address lines per party; ISO 20022 has discrete fields for specific address components. Fedwire ISO 20022 FAQ The Fed's newsletter describes the legacy lines as 35 characters each. On the Wire, January 2026

UETR. The unique end-to-end transaction reference is mandatory in pacs.008, pacs.009 and pacs.004, and must conform to UUID version 4 (IETF RFC 4122). Fedwire validates the format but not uniqueness. In a pacs.004 the original UETR is mandatory; if the original FAIM-era payment had none, the returning party assigns a new one. Fedwire format FAQ

IMAD and OMAD. These Fedwire references did not disappear. The Fed publishes guidance on carrying them in the Business Application Header and group header, checks for duplicate IMADs and rejects a message with a duplicate IMAD for the same sender. Fedwire format FAQ

Field length and structure. The Fed says the format allows more structured and longer fields, for example names and address components, which it expects to help with fraud mitigation, sanctions screening and anti-money-laundering compliance. FRFS: migration complete

For what each pacs.008 element does, see pacs.008 explained.

What happens in the November 2027 release?

On August 27, 2026, FRFS moved its next release from November 2026 to November 2027 after Swift delayed its own November 2026 standards release, citing the industry's request for more time to prepare for removing the unstructured postal address format. FRFS: release rescheduled

What the Fed has said so far:

• Until the release goes live, Fedwire supports only unstructured and structured postal address formats for key parties and agents, and the Fed strongly encourages customers to start sending structured addresses. November 2027 release FAQ
• The hybrid format described in the Fed's materials requires structured town name and country, allows other structured elements, and permits up to two free-text address lines of 70 characters as a supplement, not a repeat. Release FAQ
• Final usage guidelines, including the Fedwire Funds Service ISO 20022 Implementation Guide, are planned for MyStandards in November 2026, with the exact date and scope of the release to follow. Fedwire ISO 20022 Implementation Center · November 2027 release FAQ
• No fallback. The Fed's release FAQ, written while the release was still set for November 2026, describes a "fix in place" approach: if issues arise after deployment, FRFS will not revert to the previous version but will ship software fixes once they are identified and tested. It also says the date is aligned with Swift and CHIPS. Release FAQ

Some older Fed pages still show November 16, 2026. Treat those as superseded by the August 2026 notice.

How does Fedwire's ISO 20022 relate to Swift CBPR+?

Fedwire is the Reserve Banks' own service, not part of Swift, but the two often meet: an international dollar wire can arrive over Swift and settle between US banks over Fedwire, as Swift vs wire transfer explains. Both now use pacs.008 and pacs.009 and both require a UETR, yet each publishes its own usage guidelines. Fedwire's are on MyStandards, and a field that is optional on one route can be mandatory on the other.

Check how your bank carries the inbound Swift UETR, remittance information and party data into the Fedwire leg, and what it does when a field does not fit. The CBPR+ side is covered in MT vs MX messaging formats.

What should banks, fintechs and corporates check now?

The wider delivery method, from data mapping to partner testing, is in the ISO 20022 migration guide for product teams.

FAQ

When did Fedwire switch to ISO 20022?

The Fedwire Funds Service moved to ISO 20022 on July 14, 2025, in a single-day implementation. The date had been rescheduled from March 10, 2025.

Is the FAIM format still accepted on Fedwire?

No. FRFS retired the proprietary FAIM format and replaced all FAIM messages with ISO 20022 messages at the July 2025 cutover.

Does Fedwire use pacs.008?

Yes. Fedwire uses pacs.008 when at least one party is not a financial institution, and pacs.009 when all parties are financial institutions. Both require a UETR.

What is the Fedwire November 2027 release?

It is the follow-on ISO 20022 release, moved from November 2026, that replaces the unstructured address option with a hybrid format for key parties and agents. The Fed says the exact date and scope will be announced separately.

Is Fedwire the same as Swift?

No. Fedwire Funds is the Federal Reserve Banks' own US dollar wire transfer service, while Swift is an international messaging network. An international wire may use both.