ISO 20022 is no longer a future change for the two wire systems that move the bulk of US high-value payments. The Federal Reserve switched the Fedwire Funds Service to the ISO 20022 message format on 14 July 2025, and CHIPS, the privately run system that clears most of the rest of the US dollar wire market, already supports the same standard. For many smaller banks and credit unions, the harder part of the work, lining up vendors, correspondents and screening systems with the new data, is still running.

What ISO 20022 changes in a wire message

ISO 20022 is a global messaging standard built around structured, tagged fields rather than free text. A payer’s name, address and payment reference each get their own field instead of being packed into a handful of lines a system then has to parse. Dan DeLuca, head of payment product strategy on the Federal Reserve Financial Services wholesale product team, described the result as a structured and data-rich common language that banks and corporations already use elsewhere, in place of the proprietary FAIM format Fedwire ran on before the switch.

Fedwire settles more than $4.7 trillion in wire transfers on average every day, so a change to its message format reaches almost every bank that sends or receives a US dollar wire, not only the institutions that build core payment infrastructure. The structured fields are meant to cut manual intervention, speed up reconciliation and sharpen sanctions screening, because screening software can now read a counterparty’s name and address as separate fields instead of pulling them out of one block of text. The same principle sits behind how a payment actually moves between banks, from initiation through to settlement.

Fedwire’s cutover is behind, not ahead

The Fedwire switch happened in a single scheduled changeover on 14 July 2025, not a phased rollout with a compliance date still to come. Earlier coverage of the migration framed it as a deadline banks were working towards. That framing no longer holds: the format change is complete, and every Fedwire participant has been sending and receiving ISO 20022 messages for well over a year. What remains unresolved, for a portion of the market, is how fully each institution’s own systems use the extra data the format carries, rather than treating it as a wrapper around the same limited fields they used before.

CHIPS carries the same data

CHIPS, operated by The Clearing House, is the other system behind most large-value US dollar wires, and it already supports ISO 20022 messaging for its participants. The Clearing House describes the format as helping institutions improve automation, extend remittance information and run sanctions and compliance screening more efficiently, the same benefits the Fed cites for Fedwire. With both systems on a common standard, a bank no longer needs two separate sets of logic for handling message data depending on which wire network carried the payment.

Why smaller banks still have work left

Large banks generally built or bought ISO 20022-capable systems well ahead of the Fedwire cutover, because they run or connect directly to both wire networks and had the technical teams to do it early. Community banks and credit unions more often reach Fedwire and CHIPS through a core banking vendor and a correspondent relationship, so their own readiness depends on a chain of other parties: the core provider’s release schedule, the correspondent’s own handling of incoming data, and whatever screening tools sit on top. A bank’s wires can keep settling without interruption while its systems still fail to capture or pass on the richer structured fields the format provides.

Real-time payment rails add a second pressure point. FedNow was built on ISO 20022 from the start, and the RTP network runs on the same standard, so a bank still mapping ISO 20022 data inconsistently on its wire side is likely to carry the same gaps into its faster payments integrations.

A practical checklist for catching up

For a bank that has not fully closed the gap, the work tends to sit in a short list of places.

  • Confirm with the core banking or payments vendor exactly which ISO 20022 fields are captured, stored and passed through. A wire that settles successfully does not by itself show that the richer fields are being used.
  • Test structured name and address fields with the bank’s main correspondents, since a correspondent that flattens the data back into legacy fields erases the benefit on both ends.
  • Update sanctions and anti-money laundering screening rules to use the newly available structured fields, instead of leaving screening logic built around older free-text parsing.
  • Review reconciliation processes to see whether staff are still manually matching payment references that the structured remittance fields could carry automatically.
  • Check that data handling is consistent across Fedwire, CHIPS, FedNow and RTP, so a payment does not get richer treatment on one rail and poorer treatment on another.

None of this needs a new deadline to justify doing it. The switch to ISO 20022 already happened; the pay-off, in faster reconciliation and sharper screening, only shows up once a bank’s own systems put the extra data to use. A fuller picture of how payments move across US rail types sits on Fintechly’s payments sector directory.

Is there still a compliance deadline coming for ISO 20022 on Fedwire?

No. Federal Reserve Financial Services completed the Fedwire Funds Service switch to ISO 20022 in a single changeover on 14 July 2025. There is no further compliance date ahead for that migration itself; the remaining work for some institutions is operational, not regulatory.

Why did a correspondent bank reject or strip data from a payment that used to go through fine?

This usually points to a correspondent or intermediary system that has not been updated to carry the full set of structured ISO 20022 fields, so it maps incoming data back into a narrower legacy format and drops information in the process. The fix sits with whichever party in the chain still runs the older mapping, not with the sending bank’s own compliance.

Does ISO 20022 change how fast a Fedwire payment settles?

No. ISO 20022 changes the structure and richness of the message carrying a payment, not Fedwire’s settlement mechanics. Fedwire remains a real-time gross settlement system; the format change affects what data travels with the payment, not when the money moves.

Do banks need to migrate separately from their core banking or payments vendor?

Not separately, but not automatically either. Most community banks and credit unions reach Fedwire and CHIPS through a core banking or payments vendor and a correspondent relationship, so actual readiness depends on that vendor’s release schedule and how completely it exposes the new fields. Ask the vendor directly for specifics on both.

Does the same readiness gap apply to FedNow and RTP?

FedNow and the RTP network were both built on ISO 20022 from launch, so neither involves a separate migration. A bank with gaps in how it handles ISO 20022 data on Fedwire is likely to carry similar gaps into its FedNow or RTP integrations, since the underlying data handling problem is the same.