ISO 20022 Parser

What is ISO 20022?

ISO 20022 is the international standard for electronic financial messaging, maintained by the International Organization for Standardization. Unlike the proprietary SWIFT MT format that uses tagged text fields, ISO 20022 employs XML-based messages (also called MX messages) with a rich, hierarchical data model that can represent complex financial transactions with far greater precision.

The standard was first published in 2004 and has since become the foundation for major payment systems worldwide, including SEPA in Europe, Fedwire in the United States (ISO 20022 adoption in 2025), and real-time payment systems in over 70 countries. ISO 20022 is not just a messaging format — it is a methodology for building financial message definitions using a common data dictionary.

The migration from SWIFT MT to ISO 20022 represents the largest transformation in financial messaging history, affecting every bank, market infrastructure, and corporate treasury connected to the SWIFT network.

MT vs MX: Side-by-Side Comparison

MT to MX Mapping

The following table shows how the most common SWIFT MT message types map to their ISO 20022 (MX) equivalents:

MT Message	MX Equivalent	Business Area	Description
MT103	pacs.008	Payments Clearing	Customer credit transfer (FI to FI)
MT202	pacs.009	Payments Clearing	Financial institution credit transfer
MT940	camt.053	Cash Management	End-of-day account statement
MT942	camt.052	Cash Management	Intraday account report
MT101	pain.001	Payment Initiation	Request for transfer (customer to bank)
MT900/910	camt.054	Cash Management	Debit/credit notification
MT199	admi.004	Administration	Free format message / system event

How ISO 20022 Messages Work

ISO 20022 messages follow a consistent XML structure with three main layers:

1. Business Area prefix identifies the domain: pain (Payment Initiation), pacs (Payments Clearing and Settlement), camt (Cash Management), sese (Securities Settlement)
2. Message identifier specifies the exact message type (e.g., 008 for customer credit transfer within pacs)
3. Version number tracks schema evolution (e.g., 001.08 is version 8 of variant 1)

Every MX message contains a Group Header (GrpHdr) with metadata like message ID, creation timestamp, number of transactions, and settlement method. The transaction-level data follows in repeating structures specific to the message type.

The XML schema (XSD) for each message type enforces strict validation rules — data types, mandatory elements, allowed values, and cross-field dependencies are all defined in the schema. This makes automated validation far more reliable than with free-form MT tags.

Migration Timeline

The SWIFT network migration from MT to ISO 20022 follows this schedule:

• March 2023: Start of coexistence period — both MT and MX accepted on SWIFT
• November 2025: End of coexistence for cross-border payments and reporting (pacs/camt)
• 2025+: Continued migration for securities (sese/semt) and trade finance messages
• Target state: Full ISO 20022 adoption across all SWIFT traffic categories

During coexistence, SWIFT provides in-network translation between MT and MX formats. However, data truncation occurs when converting rich MX messages to shorter MT fields, which is why institutions are encouraged to adopt ISO 20022 natively.

Common Use Cases

• Cross-border payments: pacs.008 and pacs.009 handle customer and interbank transfers with full structured data
• Cash management: camt.052, camt.053, and camt.054 deliver account reports and statements with rich transaction details
• Payment initiation: pain.001 and pain.002 support customer-to-bank payment requests and status reports
• Real-time payments: Most instant payment schemes (TIPS, FedNow, FAST) use ISO 20022 natively
• Regulatory reporting: The richer data model supports enhanced compliance, sanctions screening, and AML checks
• Corporate treasury: Structured remittance data enables straight-through reconciliation without manual matching