# Fedwire Funds Service ISO 20022 & IMAD/OMAD Mapping Guide

> Map legacy FAIM tags to Fedwire Funds Service ISO 20022 pacs.008 and pacs.009 XML schemas, preserve IMAD/OMAD audit keys, and align SWIFT CBPR+ USD legs.

Canonical: https://payclearledger.com/rails/fedwire-funds-service-iso-20022-imad-omad-message-mapping
Last updated: 2026-11-14T23:29:21.645Z

**Publication:** PayClear Ledger
**Category:** Iso20022 Pacs008 Cbpr Plus Clearing
**Published:** 2026-11-14T15:25:25.915Z
**Author:** Claire Beaumont, CAMS, CTP (Certified Anti-Money Laundering Specialist (CAMS), Certified Treasury Professional (CTP))
**Reviewer:** Not recorded

## Answer-first summary

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.

## Key takeaways

- Fedwire Funds Service replaced proprietary FAIM 3.0.7 bracketed tags with native ISO 20022 pacs.008, pacs.009, and pacs.004 XML via a single-day cutover.
- Legacy 22-character IMAD and 34-character OMAD settlement proof references remain intact, mapped to head.001 BizMsgIdr and pacs.002 ClrSysRef respectively.
- Native XML expands party name tags from 35 to 140 characters and supports up to 9,000 characters of structured remittance data for multi-invoice B2B settlements.
- Harmonized party and UETR fields eliminate data loss when cross-border USD wires transition between SWIFT CBPR+, CHIPS, and FedLine Direct.

## Related financial entities

- **BCBS 248 Intraday Liquidity Management Framework** (BCBS-248) — license: Supervisory monitoring framework establishing quantitative metrics for banks and payment service providers to measure and manage intraday liquidity risk.
- **ISO 20022 pacs.008 Customer Credit Transfer Standard** (PACS-008) — product: Universal financial industry message scheme defining XML data structures for executing customer credit transfers across commercial banks, RTGS networks, and payment systems.
- **OFAC Specially Designated Nationals (SDN) Database** (OFAC-SDN) — license: Comprehensive list of individuals, entities, and vessels subject to U.S. economic sanctions administered by the Office of Foreign Assets Control.

## Analysis

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](/corridors/iso-20022-pacs008-standard), 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](/remitters/american-savings-bank) and [Bankers Bank](/remitters/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](/rails/swift-cbpr-plus-iso-20022-pacs008-pacs009-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.

![Fedwire Funds Service ISO 20022 pacs.008 settlement and IMAD OMAD confirmation flow](/api/figure?type=flow&title=Fedwire%20Native%20ISO%2020022%20RTGS%20Settlement%20Flow&subtitle=Cross-border%20CBPR%2B%20USD%20handoff%20into%20FedLine%20Direct%20Master%20Account%20finality&steps=1.%20Inbound%20CBPR%2B%20USD%3A%3AReceive%20pacs.008%20with%20UETR%20%2B%20structured%20PstlAdr%7C2.%20Map%20USABA%20%26%20IMAD%3A%3AAssign%2022-char%20IMAD%20in%20head.001%20BizMsgIdr%20%2B%209-digit%20ABA%7C3.%20FedLine%20Direct%20RTGS%3A%3AReal-time%20gross%20debit%2Fcredit%20on%20Fed%20Master%20Accounts%7C4.%20OMAD%20pacs.002%20Proof%3A%3AEmit%2034-char%20OMAD%20%2B%20UETR%20confirmation%20to%20both%20banks&metrics=Daily%20Fedwire%20Vol%3A%3A%244.4T%2B%3A%3AUS%20high-value%20RTGS%20rail%7CIMAD%20Length%3A%3A22%20chars%3A%3Ahead.001%20BizMsgIdr%20anchor%7CRmtInf%20Capacity%3A%3A9%2C000%20chars%3A%3AExtended%20EPN%2FFedwire%20XML%7COperating%20Window%3A%3A22%20hrs%2Fday%3A%3A21%3A00%20ET%20to%2019%3A00%20ET)

## 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](/rails/clearinghouse-chips-iso-20022-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](/corridors/ofac-sdn-sanctions-database) 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](/corridors/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](/calculators/nostro-sofr-prefunding-carry-calculator), align end-of-day reconciliation via [camt.053 and camt.054 Nostro automation](/rails/camt053-camt054-intraday-cash-reconciliation-nostro-automation), and explore the full [ISO 20022 clearing topic cluster](/topics/iso20022-pacs008-cbpr-plus-clearing).

![Payload capacity and structured remittance expansion on Fedwire ISO 20022 compared to FAIM 3.0.7](/api/figure?type=bars&title=Fedwire%20Data%20Capacity%20%26%20Truncation%20Elimination&subtitle=Maximum%20structured%20element%20support%20across%20Fedwire%20Funds%20ISO%2020022%20vs%20legacy%20FAIM&steps=Party%20Name%20Length%3A%3A140%20chars%20MX%20vs%2035%20chars%20FAIM%20%E2%80%94%204x%20legal%20entity%20capacity%7CStructured%20Remittance%3A%3A9%2C000%20chars%20MX%20vs%20truncated%20%7B6500%7D%2F%7B8200%7D%20addenda%7CLEI%20Identification%3A%3ANative%2020-char%20%3CLEI%3E%20tag%20on%20all%206%20payment%20party%20roles%7CCross-Border%20Mapping%3A%3AZero%20field%20stripping%20between%20CBPR%2B%20and%20FedLine%20Direct&metrics=Customer%20Cutoff%3A%3A18%3A30%20ET%3A%3Apacs.008%20third-party%20wires%7CSettlement%20Cutoff%3A%3A19%3A00%20ET%3A%3Apacs.009%20interbank%20close%7CDaylight%20Fee%20Rate%3A%3A50%20bps%3A%3AUncollateralized%20PSR%20rate%7CSystem%20Heartbeat%3A%3Aadmi.004%3A%3AReplaces%20FAIM%20broadcast)

## 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).

```formula
Daily_Daylight_Overdraft_Fee = Max(0, Avg_Uncollateralized_OD * (0.0050 / 360) * (22 / 24) - Deductible)
Avg_Uncollateralized_OD = Sum_t=1..1320 (Max(0, End_of_Min_Debit_t - Collateral_t)) / 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% * Risk_Based_Capital * (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
 Avg_Uncollateralized_OD = ($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.


## Source URLs

- https://www.frbservices.org/financial-services/wires/iso-20022-implementation-center
- https://www.federalreserve.gov/paymentsystems/fedfunds_about.htm
- https://www.bis.org/cpmi/publ/d223.htm

## Citation

- APA: Claire Beaumont, CAMS, CTP. (2026). 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-mapping
- Canonical article: [Fedwire Funds Service ISO 20022 Schema: IMAD/OMAD Mapping and High-Value Wire Transfer Settlement](https://payclearledger.com/rails/fedwire-funds-service-iso-20022-imad-omad-message-mapping)
- Site research index: [PayClear Ledger](https://payclearledger.com/llms-full.txt)
