Global commerce is expanding faster than the infrastructure moving money around the world.
Until 2025, global payments relied on a messaging framework designed for an era before today’s computing power, bandwidth and storage. While that system enabled the early growth of cross-border banking, it has to be modernised to keep up with present demands for speed and transparency.
The widening gap between business needs and payment capability has driven the global shift toward ISO 20022 – a new standard for financial messaging that is designed for high-volume, real-time and multi-currency environments, in line with the demands of modern digital commerce.
Understanding why this shift matters requires a closer look at what ISO 20022 changes for CFOs and treasury professionals – and what it also makes possible.
Payments evolution outpacing messaging standards
The Society for Worldwide Interbank Financial Telecommunication (SWIFT) was founded in 1973 to create a standardised messaging system that allowed banks to securely exchange payment instructions across borders.
The SWIFT Message Type (MT) format was revolutionary: it used short, fixed fields with strict character limits, enabling reliable communication between banks operating with limited computing capacity, while ensuring smooth payment flows.
But today’s banking needs have started to outgrow the MT format’s constraints.
Multinational supply chains, e-commerce, digital banking and real-time settlement expectations have driven a surge in cross-border transaction volumes. The global payments industry generated US$2.5 trillion in revenue and is expected to grow to US$3 trillion by 2029. Concurrently, regulatory KYC/AML requirements covering cross-border payments have intensified.
Legacy MT messages were not designed to support this level of complexity. Its limitations meant financial institutions had to spend resources manually reconciling payment data, creating operational friction and increasing the risk of delays or errors.
ISO 20022: a new foundation for global financial messaging
ISO 20022 introduces a fundamentally different approach to how payment information is structured and transmitted.
Instead of short, loosely defined text fields, this new standard uses structured XML-based messaging: a more machine-readable framework where every data element has a clearly defined meaning and location within the payment message. Payment messages now include detailed remittance information, precise entity identification and clearer contextual data about the transaction itself.
For all parties – financial institutions, regulators and corporates alike – ISO 20022 compliance reduces ambiguity in how payment data is interpreted and processed across institutions and jurisdictions. Richer data fields allow counterparties to be identified more accurately and regulatory requirements applied more consistently.
Recognising its advantages, SWIFT began adopting ISO 20022 for cross-border payments in 2018. The transition culminated in November 2025, when the MT standard was formally retired for cross-border messaging. By that point, ISO 20022 was already used in over 70 countries and forecast to be used in 80% of clearing and settlement of high value payments by 2025.
Why the shift matters for CFOs and treasury teams
For CFOs and corporate treasurers, the industry shift towards ISO 20022 introduces a new level of data visibility and automation that can directly improve treasury operations.
Greater visibility over global liquidity
Treasury teams rely on timely and accurate data to manage global cash positions. ISO 20022 allows more detailed remittance information to travel with each payment, providing better context around the source and purpose of transactions.
The Unique End-to-End Transaction Reference (UETR) functions like a tracking number for international payments, allowing treasurers to monitor the status of transfers as they move through the clearing chain. With more consistent and detailed data, treasury teams can forecast inbound and outbound cash flows with greater confidence.
Meeting regulatory demands more efficiently
Compliance requirements around AML screening, sanctions enforcement and transaction reporting have become significantly more stringent in recent years. ISO 20022 helps address this by standardising how payment information is captured and transmitted.
Structured address data, Legal Entity Identifiers (LEIs) and Purpose of Payment (PoP) codes provide clearer context for each transaction, making it easier for financial institutions and regulators to analyse payments consistently. For corporate treasury teams, this can reduce the number of false alerts generated during sanctions screening and minimise time spent manually responding to compliance enquiries or payment investigations.
For teams managing treasury platforms, aligning with ISO 20022 is therefore becoming a foundational capability. Systems that structure and preserve rich transaction data across the payment lifecycle can provide greater data integrity for both their customers and regulatory authorities.
For example, Bettr’s real-time treasury infrastructure is built on ISO 20022 messaging across cross-border transactions, enabling payments to carry consistent, structured data across more than 100 currencies while supporting emerging forms of digital value such as tokenised deposits and settlement tokens.
Stronger protection against payment fraud
Payment fraud continues to be a major concern for finance leaders. AccessPay’s Finance Trends Report 2025 found that 60% of finance teams rank invoice fraud as their top risk, followed by fraudulent online payments and impersonation scams.
ISO 20022 helps mitigate this risk by providing richer, structured payment data that can be automatically validated and screened before funds are released. With clearer transaction details, finance teams can implement stronger verification checks and detect anomalies earlier in the payment process.
Additional capabilities are also being introduced with ISO 20022. By November 2026, Stop and Recall messaging will allow banks to halt and attempt recovery of payments that have already entered the cross-border processing chain — a critical capability when responding to fraud incidents.
Futureproofing operations through AI
The structured data model underpinning ISO 20022 is also well suited for advanced analytics and machine learning.
With transaction data consistently formatted across institutions, AI models can interpret and analyse payment information and patterns more efficiently – creating opportunities for more accurate forecasting, improved anomaly detection and automated financial workflows. According to Eastnets, machine learning models trained on ISO 20022’s structured data can identify anomalies that traditional monitoring systems may miss, potentially reducing false positives in compliance screening by 50% or more.
Over time, this richer data environment could enable treasury platforms to deliver more sophisticated capabilities, including predictive liquidity forecasting and more precise foreign exchange execution.
Key differences between legacy SWIFT MT and ISO 20022 MX
| What’s changed | Legacy SWIFT MT | ISO 20022 MX | Why it matters for CFOs and treasury |
|---|---|---|---|
| Data structure | Mostly unstructured information packed into text fields | Structured XML with clearly defined data elements | Less manual reconciliation and more automation in payment processing |
| Data richness | Strict character limits for payment information | Expanded capacity for remittance details and party data | Better visibility into transactions and easier invoice matching |
| Address & entity data | Unstructured address lines prone to truncation and screening errors | Structured address fields and identifiers like LEIs | Reduces false sanctions alerts and manual payment investigations |
| Payment tracking | Limited visibility once payments are sent | Unique End-to-End Transaction Reference (UETR) enables tracking | Treasury teams gain clearer visibility over payment status and global cash flows |
| Compliance data | Limited fields for regulatory information | Dedicated fields for Purpose of Payment and other compliance data | Easier regulatory reporting and fewer manual investigations |
| Data for analytics | Limited structured data for advanced analysis | Consistent, structured data across institutions | Enables AI-driven forecasting, fraud detection and liquidity management |
What corporate treasury teams should do now
SWIFT completed the migration to ISO 20022 in November 2025 and officially retired the legacy MT standard for cross-border payments. ISO 20022 is now the sole messaging format.
However, despite early communications, some corporates still remain unprepared. AccessPay Finance Trends Report 2025 found a quarter of corporate respondents were still unaware of ISO 20022, while half of those who were aware had not made any preparations.
CFOs and corporate treasury teams should note that the timeline for full readiness is tightening. By November 2026, payment messages containing fully unstructured address data will be rejected by SWIFT and major clearing systems such as CHAPS and Fedwire.
As such, corporate treasury teams should take three immediate steps to prepare:
- Conduct an internal readiness assessment. Review Enterprise Resource Planning (ERP) systems, treasury management platforms and payment workflows to ensure they can generate ISO 20022-compliant messages and structured data fields.
- Capture richer data at source. Ensure systems can store and transmit structured data elements such as Purpose of Payment codes (PoP) and Legal Entity Identifiers (LEIs), which regulators increasingly require for payment screening and reporting.
- Prepare operational teams. Treasury and operations teams should understand how ISO 20022 messages are structured, as well as the terminology used within the new standard. They should also familiarise themselves with the newly introduced Stop and Recall mandate for cancellation requests.
What has changed in ISO 20022 in 2026?
The ISO 20022 transition has moved beyond the initial migration from legacy MT messaging. In 2026, the focus is increasingly shifting from adopting the standard to improving the quality and structure of payment data.
This matters for transaction banking iso 20022 because the responsibility for structured payment data increasingly moves upstream. Corporate customers need to capture, store and transmit accurate address information through ERP, treasury management and banking channels rather than relying on downstream banks to interpret or repair incomplete data. SWIFT’s latest guidance specifically highlights the need for corporates to source creditor address information through their own channels and provide it to banks at payment initiation.
The 2026 roadmap also extends beyond address data. Payment cancellation and exception-handling processes are continuing to move towards structured ISO 20022 messages and centralised Case Management, reinforcing the industry’s broader shift towards automated, data-rich transaction processing.
For CFOs and treasury leaders, the message is clear: ISO 20022 readiness in 2026 is no longer simply about whether a bank or payment platform can send an MX message. It is increasingly about whether the organisation can capture, validate, preserve and use structured transaction data throughout the payment lifecycle.
Frequently Asked Questions
1. What does ISO 20022 mean for transaction banking?
ISO 20022 provides a common, structured data standard that can support payments, cash management, liquidity management and other transaction banking services. For banks and corporates, this creates a more consistent data foundation for automation, reconciliation, reporting and compliance.
2. Is ISO 20022 replacing SWIFT?
ISO 20022 is not a replacement for SWIFT itself. SWIFT remains a global financial messaging network, while ISO 20022 is the messaging standard used to structure financial information.
3. What is changing for ISO 20022 in November 2026?
From 14 November 2026, fully unstructured postal addresses will no longer be accepted in CBPR+ cross-border payment messages. Where an address is provided, it must use either a fully structured or hybrid format, including at least the required Town Name and Country fields.
4. Why does ISO 20022 matter for corporate treasury teams?
ISO 20022 can provide richer and more consistent payment information, helping treasury teams improve cash visibility, reconciliation, compliance screening and payment tracking. It also creates a stronger data foundation for connecting bank transactions with ERP and treasury management systems.
5. How should companies prepare for ISO 20022?
Companies should review their ERP, treasury management and payment systems, identify where payment data is captured and transformed, and ensure that structured information can be stored and transmitted correctly. In particular, corporates should review address data before the November 2026 deadline and work with banking partners on testing and implementation requirements.
Turning a regulatory transition into a strategic advantage
The shift to ISO 20022 marks one of the most significant changes to global payment infrastructure in decades.
For CFOs and treasury teams, the transition represents more than a compliance exercise or a technical messaging upgrade. The roll out of ISO 20022 is about creating a richer data environment that has the potential to improve cash visibility, strengthen fraud controls and streamline cross-border payment operations.
CFOs and treasury teams that adapt early can turn this transition into a strategic advantage: using structured payment data to improve liquidity management, strengthen fraud controls and streamline cross-border transactions.
Treasury platforms built on ISO 20022-ready infrastructure will play an important role in helping corporates unlock these benefits as the global payments ecosystem continues to evolve.
Contact us to explore Bettr’s ISO 20022-enabled treasury solutions and future-proof your financial infrastructure.
This article is intended for informational purposes only and does not constitute legal advice or professional advice. This article should not be regarded as constituting an offer or a solicitation to buy or sell any regulated or financial products or services. Bettr makes no representations or warranties regarding the accuracy, completeness, or applicability of the content, and readers are encouraged to consult with legal professionals or other professionals for advice tailored to their specific situation. Bettr does not guarantee the accuracy and completeness of this article and expressly disclaims any and all liability to any person in respect of the consequences of anything done or omitted to be done wholly or partly in reliance on this article.
