ISO 20022 in Interbank Transfers: What Changes by 2026

ISO 20022 is an international standard for exchanging financial messages. For several years, the banking industry has been gradually migrating from the old SWIFT format (MT) to ISO 20022. The full transition for the SWIFT network is March 2025. By 2026, the system should be fully operating on the new standard.

What It Is

SWIFT MT is a bank message format developed in the 1970s. The structure is simple, fields are short, and information is limited. For example, in the payment purpose, you can only give a few lines of free text.

ISO 20022 is a modern XML/JSON format with a rich structure. It supports structured information about the recipient, payment purpose, tax attributes, settlement currency. The message becomes machine-readable.

What It Brings

Fewer errors. The structured format allows automatic validation and enrichment of payments: recipient name is checked against IBAN, currency pairs are verified, countries are compared against sanctions lists. This reduces the number of stuck payments and customer calls to the bank.

Better AML. Banks can more effectively screen payments for money laundering – structured information is easier to analyze than free text.

Automation potential. Accounting and treasury departments can automatically parse incoming payments, match them with invoices, and post them in accounting systems without manual entry.

What It Changes for the User

In most cases, it's invisible. SWIFT transfers still take 1-3 business days with their own fees. But:

Payment purpose becomes richer. You can transmit structured information: invoice number, contract reference, tax details. The recipient will see it in a recognizable format.

Fewer returns. Payments that used to get stuck due to incomplete information are now more often processed automatically.

SWIFT GPI. Alongside ISO 20022, tracking is widely implemented: SWIFT GPI provides a unique end-to-end transaction reference (UETR), allowing you to track the payment in real time like a package. Many banks already display this in their apps.

What Businesses Should Watch For

If you are integrated with the bank via files (ABA, MT940) or a proprietary API, check that the transition to the new standard has been handled correctly. Sometimes after migration, old fields come empty, and new information is not parsed by client software. This can be resolved on the bank's side, but you need to flag it.