Iso20022 Pacs008 Cbpr Plus Clearing
Fedwire Funds Service ISO 20022 Schema: IMAD/OMAD Mapping and High-Value Wire Transfer Settlement
Federal Reserve Fedwire Funds Service native ISO 20022 execution replaces proprietary FAIM tag-value strings with pacs.008 and pacs.009 XML while preserving IMAD and OMAD audit references.

Migrating the Federal Reserve’s Fedwire Funds Service from its proprietary Fedwire Application Interface Manual (FAIM 3.0.7) tag-value format to native ISO 20022 XML (pacs.008, pacs.009, pacs.004, camt.056, and admi.004) unified over USD 4.4 trillion in daily US high-value wire transfer clearing with global cross-border standards. By retiring legacy {1500}–{6500} bracketed tags, US depository institutions and New York USD correspondents preserve structured party roles, 36-character UETRs, and up to 9,000 characters of remittance data end-to-end without field-stripping when cross-border SWIFT CBPR+ instructions settle across Federal Reserve Master Accounts.
Replacing Proprietary FAIM Type/Subtype Codes With Native pacs Schemas#
Under legacy FAIM formatting, Fedwire distinguished customer transfers from bank-to-bank settlement transfers using two-digit Type Codes (10 Customer Transfer, 15 Foreign Transfer, 16 Settlement Transfer) combined with Subtype Codes (00 Basic, 02 Reversal, 90 Request for Credit). Native Fedwire ISO 20022 maps Type 10 and 15 customer wires to ISO 20022 pacs.008 standards, maps Type 16 interbank transfers to pacs.009, and replaces Subtype 02 / 08 reversals with structured pacs.004 Payment Return messages.
Crucially for respondent institutions such as American Savings Bank and Bankers Bank, Fedwire rolled out ISO 20022 via a single-day big-bang cutover rather than a multi-year coexistence translator. Every FedLine Advantage and FedLine Direct participant must validate Federal Reserve MyStandards Usage Guidelines locally alongside our SWIFT CBPR+ ISO 20022 clearing guide.
Where IMAD and OMAD Live Inside Fedwire ISO 20022 XML Envelopes#
Corporate treasurers, wire rooms, and real-estate escrow desks rely on the 22-character Input Message Accountability Data (IMAD: YYYYMMDD + 8-char Source ABA/Endpoint + 6-digit Sequence) and 34-character Output Message Accountability Data (OMAD) as definitive proof of Federal Reserve RTGS finality. Rather than discarding IMAD and OMAD, Federal Reserve Financial Services mapped them deterministically into the Business Application Header (head.001) and pacs.002 settlement acknowledgements.
Specifically, the sender’s 22-character IMAD populates <BizMsgIdr> inside the outbound head.001 header sent to Fedwire, while Fedwire returns both the IMAD and the Federal Reserve-assigned OMAD inside the pacs.002 acceptance confirmation (<ClrSysRef> and <OrgnlBizQuery>) delivered simultaneously with final reserve account debit/credit.
Routing ABA Numbers (USSSW) vs BICFI and CHIPS Interoperability#
While cross-border SWIFT CBPR+ identifies financial institutions primarily via 8- or 11-character ISO 9362 <BICFI> codes, Fedwire domestic settlement requires 9-digit American Bankers Association (ABA) routing transit numbers carried inside <ClrSysMmbId><ClrSysId><Cd>USABA</Cd> and <MmbId>. New York clearing banks bridging offshore USD wires between SWIFT CBPR+, CHIPS multilateral netting finality, and Fedwire map the incoming foreign bank BIC into <DbtrAgt><FinInstnId><BICFI> while inserting the Fedwire participant’s 9-digit ABA into <InstgAgt> and <InstdAgt>.
Because both Fedwire and CBPR+ adhere to CPMI harmonization rules, OFAC SDN sanctions screening engines inspect structured <UltmtDbtr>, <Dbtr>, <Cdtr>, and <UltmtCdtr> tags identically across both systems, eliminating the legacy FAIM {6000} free-text truncation blind spots.
| Legacy FAIM Tag | FAIM Field Description | Fedwire ISO 20022 XML XPath | Message Scope | Data Gain vs FAIM |
|---|---|---|---|---|
{1510} Type/Subtype | 1000 Customer / 1600 Bank Wire | pacs.008.001.08 / pacs.009.001.08 | Message Root | Direct global CBPR+ schema parity |
{1520} IMAD | Input Message Accountability Data | AppHdr/BizMsgIdr (22 chars) | head.001 Header | Preserves client wire tracking key |
{1120} OMAD | Output Message Accountability Data | TxInfAndSts/ClrSysRef | pacs.002 Confirm | Instant RTGS settlement timestamp |
{3100} / {3400} | Sender / Receiver 9-Digit ABA | InstgAgt / InstdAgt (USABA) | pacs.008 / 009 | Coexists cleanly with global BICFI |
{3320} Sender Ref / UETR | Point-to-point + GPI reference | PmtId/InstrId + PmtId/UETR | CdtTrfTxInf | Unbroken cross-border UETR tracking |
{5000} / {4200} | Originator / Beneficiary 4x35 lines | <Dbtr> / <Cdtr> Structured PstlAdr | CdtTrfTxInf | Eliminates 35-char line truncation |
Fedwire Operating Hours (21:00 ET Prior Day to 19:00 ET) and Reserve Liquidity#
Fedwire Funds opens at 21:00 ET on the preceding calendar day (overlapping Asian and European morning trade) and closes customer transfers at 18:30 ET and interbank pacs.009 settlement transfers at 19:00 ET. Managing Federal Reserve Master Account daylight overdrafts across this 22-hour cycle under BCBS 248 intraday liquidity rules requires real-time camt.052 account balance telemetry.
Compare intraday Federal Reserve daylight overdraft fees against overnight Nostro prefunding drag using our Nostro SOFR prefunding carry calculator, align end-of-day reconciliation via camt.053 and camt.054 Nostro automation, and explore the full ISO 20022 clearing topic cluster.
Federal Reserve Daylight Overdraft Fee vs Reserve Prefunding Model#
Uncollateralized Federal Reserve daylight overdrafts above an institution’s net debit cap assessment threshold incur an annualized 50 bps fee prorated across the 22-hour Fedwire operating day (22/24 day fraction), less deductible reserve capital multipliers. Treasury desks weigh this intraday facility against holding excess reserve balances overnight.
The Fedwire intraday overdraft charge formula below follows the Federal Reserve Policy on Payment System Risk (PSR).
- AvgUncollateralizedOD = Sumt=1..1320 (Max(0, EndofMinDebitt - Collateralt)) / 1,320
- Where:
- 1,320 minutes = 22-hour Fedwire operating day (21:01 ET to 19:00 ET)
- 0.0050 = 50 bps annualized Federal Reserve PSR uncollateralized fee rate
- Deductible = 10% * RiskBasedCapital * (0.0050 / 360) * (22 / 24) -> assume $420/day
- Worked Intraday Stress Example:
- Peak 4-hour uncollateralized debit of $1.80B (240 mins); zero overdraft remaining 1,080 mins
- AvgUncollateralizedOD = ($1,800,000,000 * 240) / 1,320 = $327,272,727.27
- Gross Daily Fee = $327,272,727.27 * (0.0050 / 360) * (22 / 24) = $4,166.67
- Net Daily Fed PSR Charge= $4,166.67 - $420.00 = $3,746.67
Frequently asked questions
Did Fedwire eliminate IMAD and OMAD tracking numbers after migrating to ISO 20022?
No. Fedwire retained both IMAD and OMAD for customer wire verification: the sending bank places the 22-character IMAD in the Business Application Header BizMsgIdr, and the Federal Reserve returns the OMAD in the pacs.002 settlement confirmation.
How are 9-digit US ABA routing numbers represented in Fedwire pacs.008 XML?
ABA routing transit numbers populate <ClrSysMmbId><MmbId> paired with clearing system code USABA inside Instructing Agent and Instructed Agent blocks, alongside optional BICFI identifiers for cross-border participants.
What is the Fedwire Funds cutoff time difference between pacs.008 and pacs.009?
Third-party customer credit transfers (pacs.008) close at 18:30 ET (with foreign clearing extensions where applicable), whereas bank-to-bank settlement transfers (pacs.009) remain open until 19:00 ET for final reserve squaring.
Can Fedwire carry a 36-character SWIFT GPI UETR unchanged?
Yes. Fedwire ISO 20022 requires or preserves the UUIDv4 UETR inside <PmtId><UETR>, allowing foreign correspondent banks to track USD clearing legs end-to-end without broken references.
Publication record
- Published
- November 14, 2026
- Updated
- November 14, 2026
- Author
- Claire Beaumont, CAMS, CTP
- Review
- Review not recorded
- Automated fact check
- Passed in the stored pipeline record
- Source URLs
- 3 recorded
AI assistance recorded: anthropic/claude-opus-4.6. This field does not establish human review or source verification.
Academic & Institutional Attribution
Cite This Research & Embed Live Data Card
Standard academic & institutional research paper citation format.
Claire Beaumont, CAMS, CTP. (2026, November 14). Fedwire Funds Service ISO 20022 Schema: IMAD/OMAD Mapping and High-Value Wire Transfer Settlement. PayClear Ledger. https://payclearledger.com/rails/fedwire-funds-service-iso-20022-imad-omad-message-mappingRelated Iso20022 Pacs008 Cbpr Plus Clearing & Institutional Briefings
Explore Iso20022 Pacs008 Cbpr Plus Clearing Hub (20) →Iso20022 Pacs008 Cbpr Plus Clearing
SWIFT CBPR+ ISO 20022 pacs.008 & pacs.009 Clearing Architecture: 2026 Institutional GuideIso20022 Pacs008 Cbpr Plus Clearing
Bank of England CHAPS ISO 20022 Enhanced Data: Purpose Codes and LEI Mandates in Sterling ClearingIso20022 Pacs008 Cbpr Plus Clearing
Eurosystem T2 RTGS ISO 20022 Clearing: Central Liquidity Management and pacs.009 Wholesale SettlementIso20022 Pacs008 Cbpr Plus Clearing
CHIPS ISO 20022 High-Value Clearinghouse Mechanics: Multilateral Netting Algorithms and Intraday FinalityIso20022 Pacs008 Cbpr Plus Clearing
Serial pacs.008 vs Cover Method pacs.009 COV Routing: Transparency and Settlement Latency on SWIFT RailsIso20022 Pacs008 Cbpr Plus Clearing
Preventing ISO 20022 Field Truncation: UTF-8 MX Character Sets and Legacy Payment Gateway RepairIso20022 Pacs008 Cbpr Plus Clearing
Ultimate Debtor and Ultimate Creditor Tags in ISO 20022: POBO and ROBO Payment Settlement StructuresIso20022 Pacs008 Cbpr Plus Clearing
Automated Nostro Reconciliation with ISO 20022 camt.053 Statements and camt.054 Debit/Credit NotificationsEmi Safeguarding Psd2 Psr Accounts
Annual Independent Safeguarding Audits for UK EMIs and PIs: Material Breach Reporting and RemediationEmi Safeguarding Psd2 Psr Accounts
Direct Non-Bank PSP Access to Bank of England CHAPS and Eurosystem TARGET Settlement AccountsEmi Safeguarding Psd2 Psr Accounts
EU Settlement Finality Directive Reform: Unlocking Direct Clearinghouse Participation for EMIs and PIsEmi Safeguarding Psd2 Psr Accounts
Virtual IBAN (vIBAN) Issuance Under EBA and PSD3: Cross-Border IBAN Discrimination and Pooled Safeguarding
PayClear Ledger Data, Benchmarks & Contributor Records
CC BY 4.0 Open Data
Open Institutional Datasets (CSV / JSON) →
Download desk-compiled quantitative series & schemas.
2026 Reference Matrix
2026 Institutional Benchmarks & Thresholds →
Statutory capital, clearing, margin & rate conventions.
Editorial Records
Authors & Review Records →
View named contributors where those records are available.
Complete Index
Master Research & Dossier Archive →
Browse all published briefings by topic pillar & date.
