Fedwire Funds Service is the Federal Reserve's real-time gross settlement system. Learn how messages, master-account settlement, finality, and bank posting differ.
The Fedwire Funds Service is the Federal Reserve Banks’ real-time gross settlement system for U.S. dollar credit transfers between eligible participating institutions. When the service accepts a payment order, it debits the sender’s Federal Reserve master account, credits the receiving participant’s master account, and provides immediate interbank settlement finality under the governing rules.
Fedwire settles the interbank payment order, not every step of the customer’s transaction. The originator’s bank must accept the customer’s instruction, the beneficiary’s bank must process the incoming payment, and the beneficiary must match the receipt to the intended obligation. Those events can have different records and timestamps.
Fedwire lets a participating institution send an eligible payment order to its Federal Reserve Bank. For an accepted order, the Reserve Banks make corresponding final entries to the sender’s and receiver’s master accounts and send the receiving participant an advice of credit.
The service supports participants making payments for their own accounts and on behalf of customers. Federal Reserve materials identify uses that include:
The label Fedwire transfer should be used only when the Fedwire Funds Service is part of the payment route. A customer may casually call many account transfers “wires,” but ACH, FedNow, CHIPS, book transfers, and foreign payment systems have different rules and evidence.
| Party or record | Role | Evidence to examine |
|---|---|---|
| Originator | Gives its bank the underlying transfer instruction | Authorization, beneficiary details, amount, purpose, requested date, and fraud controls |
| Originator’s bank | Accepts or rejects the customer request and selects the payment route | Customer debit, payment order, approval, fee, route, and compliance review |
| Fedwire sender | Participating account holder that sends the payment order to a Reserve Bank | Sending routing number, message reference, amount, timestamp, acknowledgement, and master-account debit |
| Federal Reserve Bank | Receives, processes, rejects or accepts the message and makes applicable account entries | Fedwire timestamp, rejection or acknowledgement, sender debit, receiver credit, and advice of credit |
| Fedwire receiver | Participating institution identified to receive the payment order | Advice of credit, master-account credit, onward processing, and customer posting |
| Beneficiary’s bank | Holds or services the account to be credited, directly or after an intermediary | Beneficiary identification, incoming order, screening, account credit, value date, and availability status |
| Beneficiary | Intended recipient of the underlying funds transfer | Bank statement, remittance information, invoice, receivables ledger, and dispute record |
The Fedwire sender and originator’s bank may be the same institution, but a bank or other provider can use a correspondent or service arrangement. The Fedwire receiver may be the beneficiary’s bank, an intermediary, or a bank serving another institution. Therefore, the two routing numbers on the Fedwire leg do not necessarily identify the two customer-facing banks at the ends of the full payment chain.
Eligibility is tied to the Federal Reserve account and access framework. Current Operating Circular 6 defines a Funds Participant as an account holder authorized by a Reserve Bank to use Fedwire Funds Service. A customer, business, or nonparticipant bank ordinarily accesses the service through a participating institution rather than connecting directly as a retail user.
flowchart TD
A["Originator gives its bank a USD payment instruction"] --> B["Bank verifies authority, beneficiary data, funds, and payment purpose"]
B --> C["Fedwire sender submits a compliant payment order"]
C --> D["Fedwire time-stamps and processes the message"]
D --> E["Reserve Bank rejects the order or accepts it for settlement"]
E --> F["Sender master account is debited"]
F --> G["Receiver master account is credited with finality"]
G --> H["Receiving bank processes or routes the customer payment"]
H --> I["Beneficiary account is credited and the receipt is reconciled"]
The flow is simplified. Security procedures, account-balance controls, compliance review, service providers, intermediaries, and contingency processing can add steps.
For a normal online payment order:
Fedwire processing is only one layer. The Federal Reserve does not maintain the ordinary commercial deposit accounts of the originator and beneficiary in a typical customer transfer.
Real time means the service processes payment orders during its operating day without waiting for a scheduled batch settlement window. Gross settlement means each accepted order is settled individually for its full amount. The payment is not made final by netting it against unrelated incoming payments.
Assume Bank A sends three Fedwire payment orders:
| Payment order | Amount | Fedwire settlement entry |
|---|---|---|
| Bank A pays Bank B | $25 million | Debit A and credit B for $25 million |
| Bank A pays Bank C | $8 million | Debit A and credit C for $8 million |
| Bank B pays Bank A | $10 million | Debit B and credit A for $10 million |
The gross value is $43 million. Fedwire processes each accepted order separately. Bank A’s $25 million payment to Bank B does not wait to be reduced to $15 million by Bank B’s later payment to Bank A.
The participants’ account balances and available intraday credit still reflect all debit and credit activity over the day. Gross settlement therefore does not mean liquidity management is irrelevant. It means the legal and accounting settlement of each order is not conditional on a multilateral netting cycle.
This differs from CHIPS, which uses prefunded positions and liquidity-saving netting to identify valid opportunities to release payments with finality. Neither design is simply “better” for every transfer. Banks consider urgency, liquidity, reach, operating arrangements, cost, contingency planning, customer instructions, and current system rules.
Fedwire records distinguish value messages, which can generate Reserve Bank accounting entries, from nonvalue messages used for requests, reports, investigations, or administration.
| Status or record | What it can establish | What it does not establish by itself |
|---|---|---|
| Customer instruction accepted | Customer-facing bank agreed to process the request | Fedwire received or settled the payment order |
| Message queued by a participant system | Instruction is waiting for submission or service processing | Fedwire has time-stamped or accepted it |
| Fedwire receipt timestamp | Fedwire application received the message | Reserve Bank accepted the payment order for settlement |
| Rejection | Reserve Bank did not accept the submitted message under the applicable conditions | The customer obligation disappeared or no corrected order will be sent |
| Acknowledgement | Reserve Bank accepted the participant’s message | Beneficiary’s customer account was credited and available |
| Master-account debit and credit | Interbank settlement entries were made for an accepted payment order | Beneficiary matched the receipt to the intended invoice |
| Advice of credit | Receiving participant was advised of the Reserve Bank credit | Every downstream intermediary and customer posting is complete |
| Return request | Sender asked the other participant to return funds | Receiving participant agreed or the money was recovered |
| Customer statement credit | Beneficiary’s bank posted the payment to an account | Remittance data was correct or the invoice was applied properly |
Operating Circular 6 states that Reserve Bank records are conclusive as to the timing of acceptance and payment of a payment order. Customer screenshots and internal workflow labels should therefore be reconciled with the official participant and account records when system finality matters.
Federal Reserve materials describe Fedwire payments as immediate, final, and irrevocable once processed. Under Regulation J, payment to the receiving participant is final and irrevocable when the receiving participant’s Federal Reserve account is credited or the payment order is sent to the receiving participant, whichever occurs first under the rule.
Finality protects the settlement of the accepted payment order. It should not be misunderstood as a guarantee that:
Operating Circular 6 permits nonvalue messages that include requests for return of funds. It also states that a Reserve Bank has no obligation to cancel or amend a payment order merely because it receives such a request. If accepted for transmission, the Reserve Bank’s role is to send the request to the identified participant; the effectiveness of cancellation or amendment is governed separately.
For a suspected error or fraud, the sending customer should contact its bank immediately through an official channel. The bank can identify whether the order is still internal, queued, rejected, settled, or subject to a return request. Delay can reduce practical recovery options, but prompt reporting does not guarantee a return.
The final Fedwire credit is made to the receiving participant’s Federal Reserve master account, not automatically to every ultimate beneficiary’s commercial deposit account. After the Fedwire leg, the receiving institution may need to:
Current Federal Reserve research distinguishes the rules of Fedwire and CHIPS from the end-user availability rules used by newer instant-payment systems. A reviewer should therefore avoid saying “Fedwire settled at 10:04” when the intended fact is “the beneficiary could use the funds at 10:04.” Both may be true, but they require different evidence.
For treasury and accounting teams, the main timestamps can include instruction time, customer-account debit, Fedwire receipt, Fedwire settlement, receiving-bank posting, beneficiary availability, and invoice application. A policy should identify which timestamp controls each operational or accounting conclusion.
The Federal Reserve Banks publish the current operating schedule and can amend or extend it. As of this article’s review date, the Fedwire Funds Service business day generally:
9:00 p.m. ET on the preceding calendar day;7:00 p.m. ET on the funds-transfer business day;6:45 p.m. ET cutoff for listed customer-transfer messages; and7:00 p.m. ET cutoff for listed bank-transfer and other messages.The date attached to an overnight payment can therefore be counterintuitive. A transfer processed on Sunday evening after the service opens can belong to Monday’s Fedwire business day.
A bank’s customer cutoff can be earlier than the Fedwire cutoff because the bank needs time for approval, formatting, screening, funding, and submission. A customer instruction submitted before the system cutoff is not guaranteed same-day processing if the bank’s own cutoff or review requirements were not met.
Always use the current Federal Reserve schedule for an operational deadline. Holidays, extensions, contingency events, message types, and future service changes can affect the applicable time.
A routing number may identify whether and where an institution can receive Fedwire Funds transfers. The Federal Reserve’s E-Payments Routing Directory provides service-specific participant information.
The routing number does not prove that:
Regulation J and incorporated Article 4A rules address reliance on identifying numbers in specified circumstances. An inconsistency between a beneficiary name and number can create serious loss and legal issues. Customers should independently verify changed wire instructions through a trusted contact method rather than relying on an unexpected email, invoice, or message.
The bank should validate the appropriate Fedwire routing information for the intended message and account. A routing number copied from an ACH authorization may not be the correct Fedwire receiving endpoint.
Fedwire Funds Service migrated to ISO 20022 messaging in July 2025. The standard supports structured party, remittance, purpose, routing, status, and investigation data that can improve straight-through processing and reconciliation.
ISO 20022 is a message framework, not a separate payment rail. A technically valid ISO 20022 message can still contain fraudulent instructions, an incorrect beneficiary, duplicate data, or a payment that a bank must reject or investigate.
Useful controls include:
Assume Company A must pay Company B USD 12.5 million before a contractual closing. Company A’s bank and Company B’s bank are both Fedwire Funds participants.
| Stage | Expected evidence | Main question |
|---|---|---|
| Closing approval | Signed closing instruction for USD 12.5 million | Is the obligation valid and is the signer authorized? |
| Beneficiary verification | Independently confirmed bank and account instructions | Were last-minute changes checked through a trusted channel? |
| Customer debit | Company A bank entry and fee | Did the originator bank fund and release the customer instruction? |
| Fedwire receipt | Time-stamped payment order and reference | Did the service receive the compliant message? |
| Fedwire settlement | Sender master-account debit, receiver master-account credit, and advice | Did the interbank payment settle with finality? |
| Beneficiary posting | Company B bank credit and availability notice | Did the beneficiary bank complete customer posting? |
| Closing reconciliation | Shared reference matched to the acquisition documents | Was the correct obligation discharged? |
If the Fedwire order settles at 2:03 p.m. ET but Company B’s bank statement does not show the credit, the parties should not resend USD 12.5 million automatically. They should trace the original reference and determine whether Company B’s bank is the direct receiver, whether an intermediary is involved, and whether the payment is under repair or review.
If Company A discovers that the account number was fraudulent after settlement, its bank can send a return request and contact the receiving institution. The request does not unwind Fedwire settlement or guarantee recovery. Fraud response, legal rights, account freezes, insurance, and liability require immediate institution-specific investigation.
| System or method | Primary role | Settlement model | Important distinction |
|---|---|---|---|
| Fedwire Funds Service | Large-value and time-critical U.S. dollar credit transfers | Individual real-time gross settlement in Federal Reserve accounts | Accepted transfers settle with immediate interbank finality |
| CHIPS | Large-value domestic and cross-border U.S. dollar payments | Prefunded positions with liquidity-saving netting and intraday finality | Private-sector system operated by The Clearing House |
| FedNow Service | Instant credit transfers through participating institutions | Real-time gross settlement under FedNow rules | Separate service with different operating hours, access, messages, limits, and end-user availability requirements |
| ACH | Payroll, bills, account transfers, and other batch payments | Batch clearing with scheduled settlement | Supports credits and debits, returns, and different authorization rules |
| SWIFT | Standardized financial messaging | Does not settle merely by delivering a message | A SWIFT-supported payment may settle through Fedwire, CHIPS, correspondents, or another system |
| Fedwire Securities Service | Book-entry transfer and settlement of eligible securities | Separate securities-service rules and account structure | It is not the Fedwire Funds Service despite sharing the Fedwire name |
Fedwire is commonly associated with high-value payments, but the amount alone does not prove which rail was used. The bank’s payment confirmation, routing information, message reference, and settlement record should identify the system.
High-value wire controls commonly include independent beneficiary verification, dual approval, role separation, amount limits, trusted callback procedures, security controls, anomaly monitoring, message reconciliation, and rapid incident escalation. No single control guarantees prevention or recovery.
Official system material does not prove whether a particular instruction was authorized or whether an individual beneficiary received funds. Use the relevant participant, customer-account, legal, and transaction records for a specific case.
This article provides general financial education. It is not payment-operation, treasury, liquidity, accounting, legal, regulatory, sanctions, cybersecurity, fraud-recovery, or transaction-specific advice. Use current Federal Reserve rules, bank records, contracts, and qualified professional guidance for an actual payment.