Fedwire Funds Transfer

Rail: Fedwire Operator: Federal Reserve Banks Standard: ISO 20022 (since March 10, 2025) Last updated: March 2026

Overview

Fedwire Funds Service is the Federal Reserve's real-time gross settlement (RTGS) system for high-value, time-critical US dollar transfers. Unlike ACH batch processing, Fedwire settles each transaction individually and immediately — there is no netting. Once a Fedwire payment is settled, it is irrevocable and final.

Fedwire is the primary rail for: large interbank transfers, government securities settlements, corporate acquisitions and real estate closings, time-sensitive business payments, and same-day settlement of Fed obligations. The system processes over $4 trillion in daily transaction volume.

RTGS vs. Batch Fedwire settles gross (one by one, immediately) vs. ACH's net batch settlement. This means there is no deferred settlement risk — the RDFI's Federal Reserve account is credited the moment the transaction is processed. This is why Fedwire is preferred for large, time-critical payments.

ISO 20022 Migration — Effective March 10, 2025

The Federal Reserve completed the Fedwire ISO 20022 migration on March 10, 2025. The legacy Fedwire proprietary message format (fixed-width, tag-based) was replaced by the ISO 20022 pacs.008 (Customer Credit Transfer) and pacs.009 (Financial Institution Credit Transfer) message formats.

Legacy Format Retired The Fedwire legacy format is no longer accepted as of March 10, 2025. All Fedwire messages must use ISO 20022 XML. If your core banking system or payment hub has not been upgraded, outgoing Fedwire transactions will fail. Contact your technology team immediately if your system still generates legacy-format Fedwire messages.

Key Changes in the ISO 20022 Fedwire Format

Element	Legacy Format	ISO 20022 (Current)
Format type	Fixed-width, tag-based (e.g., {1000}, {2000})	XML — pacs.008 / pacs.009
Remittance data	Limited — 140 characters max	Structured and unstructured — up to 9,000 characters
Name/address fields	Abbreviated, unstructured	Structured — separate Name, Street, City, Country fields
End-to-end reference	IMAD (Input Message Accountability Data)	End-to-end ID (EndToEndId) + UETR (Unique End-to-end Transaction Reference)
LEI support	Not supported	Legal Entity Identifier (LEI) supported in party fields
Purpose of payment	Not supported	Purpose code supported (e.g., CORT, TREA, SALA)

Key Participants

Participant	Role
Sending Bank (ODFI equivalent)	The financial institution initiating the Fedwire transfer on behalf of its customer. Must hold a Federal Reserve master account or use a correspondent bank that does.
Fedwire Funds Service	Federal Reserve Banks. Routes and settles the transfer gross, in real time, between the sending and receiving bank's Fed accounts.
Receiving Bank	The financial institution receiving the funds. Settlement occurs in their Federal Reserve master account upon receipt.
Beneficiary	The customer or entity whose account will be credited. The Receiving Bank posts funds to the beneficiary account upon receipt of the Fedwire settlement.
Intermediary Bank	Optional. A correspondent bank used when the Receiving Bank does not have a direct Federal Reserve master account. The intermediary receives funds on Fedwire and then forwards via internal transfer or separate wire.

Processing Flow

Customer
Initiates Wire

→

Sending Bank
Validates & Queues

→

Fedwire
Processes (RTGS)

→

Receiving Bank
Receives Notification

→

Beneficiary
Account Credited

Customer Wire Request: The originating customer submits a wire request — in person, via online banking portal, or through a system-to-system API connection — specifying the beneficiary name, account number, receiving bank routing/ABA number, amount, and remittance information.
Compliance Screening (Sending Bank): Before submission to Fedwire, the Sending Bank must perform OFAC SDN screening on the wire instruction. A sanctions match triggers a hold and escalation to Compliance. No wire may be submitted to Fedwire with an unresolved OFAC match.
Message Construction: The Sending Bank's payment hub constructs the ISO 20022 pacs.008 XML message, populated with the required fields: instructed amount, ordering customer, creditor account, creditor agent (ABA routing number), purpose code, and end-to-end reference (UETR).
Submission to Fedwire: The message is submitted to the Fedwire Funds Service via the Fed's secure connection (FedLine network). The system validates the message format and the Sending Bank's available funds in its Federal Reserve account.
RTGS Settlement: Fedwire immediately debits the Sending Bank's Federal Reserve account and credits the Receiving Bank's Federal Reserve account. Settlement is immediate and final — no reversals after this point.
Receiving Bank Notification: The Receiving Bank receives the incoming Fedwire credit notification (pacs.008) via FedLine. The bank's core system posts the funds to the beneficiary's account, typically within minutes of receipt.

Operating Hours

Fedwire operates on a schedule defined by the Federal Reserve. Understanding the operating window and cut-off times is critical for same-day settlement commitments.

Day	Service Window	Customer Cut-Off (typical)	Notes
Monday – Friday	9:00 PM (prior day) ET – 6:30 PM ET	Customer cut-off: 5:00–5:30 PM ET (institution-defined)	Operating window spans approximately 21.5 hours. Many banks close customer wire acceptance by 5:00 PM ET.
Saturday	Not available	—	Fedwire does not operate on Saturdays
Sunday	Not available	—	Fedwire does not operate on Sundays
Federal Reserve holidays	Not available	—	Fedwire is closed on all Federal Reserve Bank holidays. Same-day wires received after cut-off on the prior business day will be processed next business day.

Liquidity Management Banks with insufficient balances in their Federal Reserve master account will have Fedwire messages queued. Queued messages are released when sufficient funds become available — either through incoming Fedwire credits or daylight overdraft facilities. Daylight overdrafts are subject to Fed collateral requirements and cap limits. Monitor intraday liquidity positions carefully to avoid end-of-day overdrafts.

ISO 20022 Message Format Overview

Fedwire uses two primary ISO 20022 message types. Operations and technology teams must understand the structure for format validation and exception diagnosis.

Message Type	ISO 20022 Code	Use Case
Customer Credit Transfer	`pacs.008.001.08`	Payment from a non-bank customer (individual or corporate) to a beneficiary. Most common Fedwire message type.
Financial Institution Credit Transfer	`pacs.009.001.08`	Bank-to-bank transfer with no end customer. Used for interbank settlements, nostro funding, treasury operations.

Key Fields in pacs.008 (Fedwire)

Field	ISO 20022 Element	Description	Required?
Message ID	`MsgId`	Unique ID assigned by the Sending Bank. Used for duplicate detection.	Mandatory
End-to-End ID	`EndToEndId`	Reference passed through the full payment chain — from Originator to final beneficiary.	Mandatory
UETR	`UETR`	Universally unique end-to-end transaction reference (UUID format). Enables SWIFT gpi-style tracking for cross-border interoperability.	Mandatory
Instructed Amount	`IntrBkSttlmAmt`	The interbank settlement amount in USD. Cannot be zero.	Mandatory
Creditor Agent (ABA)	`CdtrAgt / FinInstnId / ClrSysMmbId`	9-digit ABA routing number of the Receiving Bank. Must be a valid FedACH/Fedwire participant.	Mandatory
Creditor Name	`Cdtr / Nm`	Beneficiary name. Structured name and address fields available.	Mandatory
Creditor Account	`CdtrAcct / Id`	Beneficiary account number at the Receiving Bank.	Mandatory
Remittance Info	`RmtInf`	Structured or unstructured remittance data. ISO 20022 allows significantly more remittance detail than legacy format.	Optional
Purpose Code	`Purp / Cd`	ISO 20022 purpose code (e.g., CORT = trade settlement, TREA = treasury, SALA = salary).	Optional (recommended)

Settlement and Finality

Fedwire settlement is real-time, gross, and final. Once the Federal Reserve processes a Fedwire payment and credits the Receiving Bank's account, the settlement is irrevocable. The Receiving Bank can post funds to the beneficiary immediately upon receipt.

No Reversals After Settlement Unlike ACH, there is no return mechanism in Fedwire once settlement occurs. If funds are sent in error (wrong beneficiary, wrong amount), recovery requires the cooperation of the Receiving Bank and, ultimately, the beneficiary. Initiate a wire recall request immediately. There is no guaranteed recovery.

Compliance Requirements

OFAC Screening — Mandatory Pre-Submission

All Fedwire outgoing instructions must be screened against the OFAC SDN List before submission.
Screen all parties: ordering customer, beneficiary, intermediary banks, and any referenced third parties in remittance fields.
A confirmed OFAC match must result in immediate hold and escalation to Compliance. Do not release the wire.

Regulation J (12 CFR Part 210)

Regulation J governs the use of Fedwire by depository institutions and establishes the rights and responsibilities of Sending and Receiving Banks.
Receiving Banks are responsible for posting funds to beneficiary accounts in accordance with the payment instructions received on the Fedwire credit notification.
Sending Banks warrant that the payment instruction is legitimate and that the originating customer has authorized the transfer.

BSA / Travel Rule (31 CFR 103.33)

For wire transfers of $3,000 or more: Sending Banks must collect and retain originator information (name, address, account number) and beneficiary information.
This information must be passed to any intermediary banks and to the Receiving Bank in the payment instruction.
ISO 20022 structured fields facilitate full Travel Rule compliance. Ensure that originator name, address, and account fields are populated for all qualifying wires.

Exceptions and Wire Recalls

When to Initiate a Wire Recall

Payment sent to incorrect beneficiary account
Duplicate wire transmission
Incorrect amount sent
Payment instruction sent in error (customer cancellation request within minutes of submission)

Wire Recall Procedure

Identify the UETR (Unique End-to-end Transaction Reference) from the original Fedwire message. This is the primary identifier used in recall communications.
Contact the Receiving Bank's wire operations department immediately by phone and in writing. Provide: UETR, original date/time of wire, amount, and sender/beneficiary details.
Submit a formal written recall request via SWIFT gSRP (global Stop and Recall Payments) if the Receiving Bank is a SWIFT participant. For domestic-only institutions, use Fed funds transfer callback procedures.
The Receiving Bank is not legally obligated to return funds if they have been posted to the beneficiary and the beneficiary has used or withdrawn them. Recovery is voluntary cooperation.
Document all communications and escalate to the Operations Manager and Legal team if the Receiving Bank does not respond within 24 hours.
File a SAR if there is reason to believe the erroneous wire may be associated with fraud.

Reconciliation Procedures

Intraday Reconciliation

Fedwire activity must be monitored throughout the business day, not just at end of day. Operations teams should reconcile outgoing and incoming Fedwire transactions against the institution's Federal Reserve account statement (available in real time via FedLine).

Obtain the real-time Federal Reserve account statement via FedLine Advantage at minimum three times daily: morning, midday, and prior to cut-off.
Match each outgoing Fedwire debit against the corresponding customer wire request in the payment queue (reference: UETR).
Match each incoming Fedwire credit against the core banking system posting (UETR, amount, beneficiary account).
Investigate any unmatched items immediately — do not carry forward to next-day reconciliation without resolution.
Confirm that end-of-day Federal Reserve account position matches the institution's expected net Fedwire position.
Archive the daily Fedwire settlement statement and reconciliation worksheet per records retention policy.

← Back to ACH Next: SWIFT →