Published and sources checked: 2026-09-25. Scope: bank messaging formats in front of a settlement leg — the ISO 20022 implementation on Fedwire (United States, 14 July 2025) and the end of MT/ISO coexistence on the Swift network for cross-border payments (global, 22 November 2025), read from operator announcements, operator FAQs and a CPMI report. This is message-format research for teams that match bank transfers to orders; it is not advice about any particular bank's schedule.
Two cutovers, ten weeks apart
They landed in the same summer and they are not the same event. On the United States side: "Federal Reserve Financial Services (FRFS) today announced the completed migration to the ISO 20022 message format for the Fedwire Funds Service", on 15 July 2025, one day after the format went live.[2] On the cross-border side, Swift reported on 25 November 2025: "The final switch happened on 22 November, with the end of coexistence with the traditional MT message format."[1] The scale of the second one: "Yesterday we observed 97% of payment instructions sent using ISO 20022."[1]
Why a merchant should care at all: these are the rails a payout or a bank settlement leg travels on, and the reference your reconciliation matches against travels inside the message. Swift's own framing of the transition is the useful part — "In March 2023, Swift began a period of coexistence with the MT format for cross-border payments and reporting (CBPR+) to enable a smooth transition for the community."[1] Coexistence was the safety net; it is gone.
The free-text pile is now a set of shelves
The most concrete change for a matcher is where loose text goes. Fedwire's format FAQ states it plainly: "The functionality previously supported by tag {6500} Sender to Receiver Information is now accommodated by enhanced ISO 20022 message capabilities (e.g., additional data elements are available to capture additional parties and agents involved in payments — see guidance table below)".[3] The single field that used to carry your order reference, your invoice number and someone's note now has candidates: structured party and agent elements, structured or unstructured remittance information, and address blocks with defined widths.
That is the failure mode worth testing. A matching rule that greps one legacy field will silently stop matching, not loudly fail, and the payment still settles. The same FAQ gives a second, smaller trap with real operational cost: "FRFS recommends that Fedwire senders do not include spaces in free-formatted text elements in their messages to avoid delays in the successful processing of their transactions", because "Use of only spaces in free-formatted text elements (e.g., unstructured remittance information) is causing issues for Fedwire receivers’ downstream systems and applications."[3] Padding a field with blanks is no longer harmless formatting.
The data model behind the deadline
The deadlines are not arbitrary. The Fedwire FAQ links the implementation to a published standard: "The implementation of ISO 20022 on July 14, 2025, enabled Fedwire Funds Service participants to apply the CPMI data model described in the report."[3] That report is the Committee on Payments and Market Infrastructures' "Harmonised ISO 20022 data requirements for enhancing cross-border payments", published 17 October 2023 as CPMI Papers No 218 under the G20 cross-border payments programme.[4] In other words the field names your parser now sees were chosen for end-to-end processing across institutions, not for your convenience.
What it does not change
Amounts, dates and your own order identifiers are still yours. The format migration moves text between elements; it does not rename your invoice, re-price a transfer, or make a matched payment more certain than it was. And rich data is an operator benefit claim, not a guarantee about your counterparty: FRFS says the format "will enable more intelligent risk and fraud mitigation and provide a richer set of payment data that will facilitate banks' and other entities’ compliance with sanctions and anti-money laundering requirements", which is a statement about the network's capability.[2] The Fedwire service itself "settles more than $4.7 trillion in wire transfers on average per day", which is why a format change at this scale had to be planned for years.[2]
Re-test instead of assume
Editorial reasoning drawn from the sources above. Five checks, in order: (1) take one settled transfer from before each cutover and one after, and diff where the reference, the payer name and the remittance text actually arrived; (2) make the matcher look in every current location — structured party fields, unstructured remittance text, and the legacy tag on any message that still carries it — rather than in one field; (3) trim and normalise, because whitespace-only segments are now a documented processing hazard; (4) confirm with your bank which structured and hybrid address formats it sends, since the FAQ distinguishes interim and hybrid/end-state postal address rules; (5) keep a fallback path for messages converted in flight by an operator's contingency service, because converted data is not authored data. None of this requires a project plan; it requires two samples and an afternoon.
Sources and limits
Checked 2026-09-25. Operator announcements and FAQs are quoted as retrieved; the Swift press release page blocks plain scripted retrieval, so its text was captured through a retrieval service and stored with this batch's evidence. The Fedwire FAQ is a living page with no publication date displayed, which is stated per source. No claim is made about any particular bank's migration status or timetable; verify with your own institution.
- [1] Global financial community completes switch to ISO 20022 (Swift) — 2025-11-25; global cross-border; checked: 2026-09-25.
- [2] Federal Reserve Financial Services completes ISO 20022 migration for Fedwire Funds Service — 2025-07-15; United States; checked: 2026-09-25.
- [3] Fedwire Funds Service ISO 20022 Implementation FAQ — format questions — Living page, no publication date displayed, retrieved 2026-09-25; United States; checked: 2026-09-25.
- [4] Harmonised ISO 20022 data requirements for enhancing cross-border payments (CPMI Papers No 218) — Published 2023-10-17; global; checked: 2026-09-25.