Fedwire Funds Service ISO 20022 implementation

What the authority record establishes

The Federal Reserve migrated the Fedwire Funds Service to ISO 20022 messages and maintains implementation resources.

Fedwire rules, agreements, and applicable law govern participants

The exact official title, issuing body, jurisdiction, version or application record, and linked source define the scope of this page. Readers should not transfer the authority's status to a commercial product or infer transaction-, patient-, system-, site-, or organization-specific applicability from this summary.

Why it matters to this market

Treasury buyers need proof that ERP, TMS, bank, middleware, screening, approval, reconciliation, and reporting paths preserve the required data and statuses.

Affected operating stages

• Scope
• Control Design
• Execution
• Monitoring
• Evidence
• Improvement

Capabilities to examine

Bank Connectivity And Statement Ingestion

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for bank connectivity and statement ingestion.

Payment Initiation Approval And Release Control

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for payment initiation approval and release control.

Payment Fraud Controls And Beneficiary Validation

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for payment fraud controls and beneficiary validation.

Cash And Bank Reconciliation

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for cash and bank reconciliation.

ERP Accounting Market-Data And API Integration

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for ERP accounting market-data and API integration.

Treasury Master-Data Normalization And Lineage

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for treasury master-data normalization and lineage.

Audit Trail Control Evidence And Record Retention

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for audit trail control evidence and record retention.

Affected buyer audiences

• treasury
• finance
• payments
• risk and controls

Implementation questions

• Which entities, products, populations, transactions, systems, sites, or jurisdictions are actually within scope?
• What is binding, what is guidance, and what is a technical or consensus standard?
• Which publication, adoption, effective, application, transition, and enforcement dates differ?
• Who owns legal, clinical, quality, regulatory, policy, or operational interpretation?
• How will a source revision affect open work and historical decisions?

Interpretation boundary

The implementation record does not certify a treasury product, bank connector, mapping, or corporate payment process.