The Legacy of Fedwire Message Formats

The Federal Reserve's Fedwire Funds Service is the backbone of large-value US dollar payments — a real-time gross settlement system that moves trillions of dollars a day with immediate finality. Its message format carries a distinctive lineage, evolving from telegraphic transfers into a structured, tag-based standard. Understanding that format explains a lot about how high-value payments are described, and about the industry-wide shift now underway to ISO 20022.

A real-time gross settlement rail

Fedwire is not a batch system. Each payment is settled individually and immediately across the sending and receiving banks' accounts at the Federal Reserve, with finality at the moment of settlement — the funds cannot be recalled. Participants are identified by their ABA routing number (also called the Fedwire routing number), the nine-digit identifier with its own check digit. This individual, final, central-bank-money settlement is what makes Fedwire the rail of choice for time-critical, high-value transfers.

The tag-based message structure

Historically, a Fedwire message is built from a series of tags — curly-brace-delimited codes such as {1510}, {2000}, {3400}, and {4200}, each introducing a specific field. Rather than fixed columns, the format uses these tag markers to signal what follows:

• Type and subtype code (tag {1510}) – a pair that classifies the message. The type code (for example 10 for a basic funds transfer) says what kind of message it is, while the subtype code (such as 00 for a normal transfer) refines it. Other type/subtype combinations cover requests for reversal, requests for credit, and service messages.
• Amount (tag {2000}) – the transfer value.
• Sender and receiver depository institutions – identified by routing number.
• Originator, beneficiary and their financial institutions – tags in the {5000}–{6000} range carrying the underlying parties.
• Reference and remittance tags – carrying originator-to-beneficiary information and reference identifiers.

Each message also carries a unique identifier — the IMAD/OMAD (Input/Output Message Accountability Data) — that stamps it for tracing and reconciliation across the network.

Why the format looks the way it does

The tag structure reflects decades of incremental evolution. Fields were added over time for new regulatory needs — richer originator and beneficiary details for sanctions and Bank Secrecy Act compliance, cover-payment information, and structured reference data — without breaking the existing layout. The result is powerful but idiosyncratic: parsers must know the meaning and constraints of each tag, and free-text party fields have long been a pain point for automated sanctions screening because critical data was not always in predictable, discrete elements.

The move to ISO 20022

That idiosyncrasy is precisely why the Federal Reserve has migrated Fedwire Funds to ISO 20022, aligning it with the global standard already adopted by other major high-value systems such as the Eurosystem's T2 and the UK's CHAPS, and by cross-border messaging on SWIFT. ISO 20022's XML messages replace terse tags with richly structured, self-describing elements — discrete fields for structured addresses, LEIs, and detailed remittance information. The payoff is better sanctions screening, cleaner reconciliation, and interoperability across borders. The challenge is that institutions must map decades of tag-based logic onto the new structure and preserve data fidelity through the transition.

Why the legacy still matters

Even as ISO 20022 takes over, the Fedwire legacy persists in institutional knowledge, back-office systems, and the mental model of everyone who works with US dollar wires. Type/subtype codes, routing numbers, and IMAD references are not disappearing; they are being re-expressed. For builders, the lesson is that a payment format is never purely technical — it encodes years of regulatory and operational history, and migrating it is as much about faithfully carrying that history forward as it is about new syntax.

Fedwire is not CHIPS

A common confusion worth clearing up is that Fedwire is not the only large-value dollar rail. CHIPS (the Clearing House Interbank Payments System), operated privately by The Clearing House, also moves large-value dollar payments but works differently: it nets obligations continuously through the day and settles positions rather than paying each transfer gross in real time. Fedwire, by contrast, is the Federal Reserve's gross-settlement rail with immediate finality per payment. Many international dollar payments touch both — cleared over CHIPS and settled through Fedwire — so practitioners must know which rail carries which leg. Both have moved toward ISO 20022 alignment, but their settlement mechanics, and therefore their finality timing, remain distinct.

Key takeaways

• Fedwire is a real-time gross settlement rail for high-value US dollar payments with immediate finality.
• Its legacy format uses curly-brace tags (e.g. {1510}, {2000}) with type and subtype codes classifying each message.
• Participants are identified by nine-digit ABA routing numbers; messages carry IMAD/OMAD tracing identifiers.
• Free-text party fields made automated sanctions screening harder — a key driver for change.
• Fedwire has migrated to ISO 20022 for structured data, better screening and cross-border interoperability.