ISO 20022

ISO 20022 provides a common framework and repository for financial message definitions. Payment implementations often use structured XML, but the version and applicable scheme/bank rules determine what data is required and what actually arrives. A structured field is an opportunity for better data, not a guarantee of end-to-end preservation.

The Three Message Families Operators Meet

pacs covers payments clearing and settlement: for example, pacs.008 for a customer credit transfer between financial institutions, pacs.002 for status and pacs.004 for a return. An MT/ISO correspondence is not necessarily a field-for-field conversion; use the mapping reference for implementation boundaries.

camt covers cash management, reporting and investigations. camt.052/053/054 are reporting/notification messages. camt.056 requests cancellation and camt.029 communicates a resolution under the applicable workflow; it is not universally a negative response. A request does not itself recover funds. See the camt reference.

pain covers customer-to-bank initiation and status. pain.001 and pain.002 answer different questions from an interbank settlement message.

Where ISO 20022 Is Live

Migration dates belong to a service and message scope. Swift's November 2025 guide concerns cross-border financial-institution payment instructions. It does not establish one deadline for every reporting, corporate or investigation message.

The ECB confirms T2 went live on 20 March 2023, replacing TARGET2 and adopting ISO 20022. November 2022 was a planned launch, not the actual cutover.

Other systems, including SEPA and domestic payment infrastructures, have their own implementation guidelines, message versions and release calendars. Check the actual scheme and bank interface before planning a format change.

What Changed for Operators

Structured data can improve validation and reconciliation when the sending, intermediary and receiving implementations preserve it. The standard does not guarantee data completeness, successful screening or straight-through processing.

A practical interface check

For a hypothetical invoice, record the invoice reference, party details and payment identifier sent to the bank. Compare them with the bank acknowledgement and final report. If the reference is missing, establish where it was omitted, translated or truncated before assuming that adopting XML fixes reconciliation.

Ask the bank for the exact message version, usage guideline, mandatory fields and sample output. Treat a UETR as an identifier for the in-scope workflow, not proof of settlement. Swift's investigation guidance also separates cancellation messages from newer investigation request/response services.