Wire transfers have long been the default rail for large, time-sensitive business payments in the United States. Since July 2025, the Fedwire Funds Service that carries them has used a different message format, ISO 20022, and that change affects what payment data accompanies a wire. This article explains what changed, what stayed the same, and why finance and accounts receivable teams may notice differences in remittance data. It is an explainer of mechanics, not a recommendation.
What changed on July 14, 2025
According to the Federal Reserve Banks’ Fedwire Funds Service ISO 20022 implementation FAQ, the service moved to ISO 20022 payment messages on July 14, 2025. The Federal Reserve Board had announced in 2022 a single-day adoption on March 10, 2025. The Reserve Banks later moved the date to July 14, 2025, which the FAQ attributes to industry requests and an assessment of customer readiness.
The older proprietary format, known as FAIM, was replaced with an XML-based ISO 20022 format built on a common data dictionary. The FAQ states that processing speed was not affected: messages process at the same speed as before.
Structured data instead of free-text lines
The most practical difference is how information is organized. The FAQ explains that the previous format allowed three free-text address lines of up to 35 characters each. ISO 20022 instead uses discrete fields with defined limits, for example up to 70 characters for a street name, up to 35 characters for a town name, up to 16 characters for a postal code, and a 2-character country code.
The FAQ also says the new format supports longer names, specific address components including a country code, and a structured format for extended remittance information. It lists possible benefits as reduced data loss, support for regulatory screening, and improved straight-through processing.
Why remittance data matters for B2B
For a business receiving a large payment, the money is only half the story. Accounts receivable staff must match each incoming payment to open invoices. When remittance details are truncated or missing, matching becomes manual work. A structured remittance field gives banks and software a place to carry invoice references in a consistent form. Whether a given payment actually carries that detail still depends on how the sending business, its bank, and the receiving bank populate and pass along the fields, so results will vary by institution.
Cash application and reconciliation workflows may therefore need to be reviewed to confirm which fields arrive from the bank and how they map into accounting or ERP systems. Banks and software vendors typically publish their own guidance on this.
How wires fit alongside other rails
Wires are one of several ways businesses move money. Our earlier articles cover the comparison from other angles: ACH vs. real-time payments, how FedNow complements ACH and cards, ACH for B2B invoicing and same-day settlement, and paper checks vs. ACH. The Federal Reserve’s FAQ notes that the Fedwire Funds Service ISO 20022 implementation was aligned with the FedNow Service as closely as possible, though Fedwire does not support FedNow’s request-for-information feature.
Scale of the Fedwire Funds Service
The Federal Reserve Banks publish annual Fedwire Funds Service statistics. For 2025 they list 217,296,700 transfers originated, with a value of 1,148,267,267 million dollars. For 2024 they list 209,916,835 transfers, valued at 1,133,419,684 million dollars. These figures show that the service handles a comparatively small number of very large-value payments, which is why message quality and data handling matter to participants.
Questions to review internally
- Which remittance and address fields does our bank deliver for incoming wires, and in what format?
- Do our ERP or cash application tools read structured remittance data, or only the legacy text?
- For outgoing wires, are our vendor and customer records stored in a way that fits discrete address fields, such as separate street, town, postal code and country values?
- Who owns the process when an incoming payment cannot be matched automatically?
Treasury teams commonly raise these with their bank relationship managers and software providers, since implementation details differ.
Sources
- Federal Reserve Financial Services, Fedwire Funds Service ISO 20022 Implementation FAQ
- Federal Reserve Board press release, June 27, 2022
- Federal Reserve Financial Services, Fedwire Funds Service Annual Statistics
This content is for general informational purposes only and is not financial, legal, tax or investment advice. Payment rules, formats and bank practices change, so consult your bank, payment provider or a qualified professional about your specific situation.
Need Help With Payment Processing?
Talk to our team about rates, gateways, and solutions for your business.
Get a Free Quote →