< Blog

ISO 20022: deadlines are changing – what does this mean for your business?

24.09.26
Blog

ISO 20022: deadlines are changing – what does this mean for your business?

International standards, instant payments and structured data: what does ISO 20022 really change for businesses and their information systems?

For several years, the financial sector has been evolving its data exchange standards. At the heart of this transformation is ISO 20022, an international standard designed to make financial data exchanges more standardised and structured.

Rather than being simply a change to banking formats, ISO 20022 directly affects information systems, ERP solutions, banking interfaces and the quality of financial data used by businesses.

1. What is ISO 20022?

ISO 20022 defines a common language for exchanging financial data. In the payments field, the main message families include pain, pacs and camt, used respectively for certain exchanges between businesses and banks, between financial institutions, and for account information and bank statements.

The objective is to enable systems to exchange data that is more structured, richer and easier to process automatically.

It is important to remember that ISO 20022 is not a regulation with a single migration deadline. Its adoption depends on payment infrastructures, banks, payment schemes and the countries concerned. Deadlines can therefore vary depending on the payment flows used by each business.

2. A transformation that is already under way

The migration to ISO 20022 is already well under way across the financial sector.

In Europe, the Eurosystem’s T2 high-value payment infrastructure migrated to ISO 20022 in March 2023. Internationally, the migration of Swift cross-border payments under CBPR+ continued until the end of the coexistence period between legacy MT messages and ISO 20022 messages in November 2025.

In 2026, however, some deadlines have evolved. On 27 August 2026, Swift announced the postponement of certain changes planned as part of its Standards Release 2026, particularly those relating to addresses. A new timeline is to be defined in consultation with market participants.

The European Payments Council (EPC) has also postponed the deadline initially set for 15 November 2026 for the end of the use of unstructured addresses under its payment schemes. The EPC is expected to set a new end date in October 2026.

These postponements give businesses additional time to prepare, but they do not change the broader move towards more structured payment data.

3. Structured addresses: a key practical issue

The evolution of address data provides a good illustration of the impact of ISO 20022.

An address stored as a simple block of text is difficult for systems to process automatically. A structured address, by contrast, separates the different elements: name, street, number, town or city, postcode, country, etc.

This structure makes the data easier for different systems to process and can help improve automation, controls and payment processing.

For businesses, this information is generally stored upstream of the bank, directly within the ERP or other business systems. The ability to generate compliant future banking messages therefore depends partly on the quality of the data stored in the information system.

The postponed deadlines therefore provide an opportunity to review supplier and customer data, banking formats and existing interfaces.

4. What impact will ISO 20022 have on businesses?

The impact of ISO 20022 depends on each organisation’s specific circumstances: countries of operation, banks used, types of payments, international flows, currencies, banking formats and existing interfaces.

Several areas should be reviewed:

  • Data: names, addresses, bank details and other third-party information need to be sufficiently complete and structured.
  • Banking formats: payment and reporting files must comply with the requirements of the relevant banks and payment infrastructures.
  • Interfaces: ERP systems, EBICS, APIs, treasury platforms, middleware and bespoke developments may all be affected.
  • Financial processes: payment preparation and approval, file submission, statement processing and bank reconciliation may evolve.

The question is therefore not simply whether a business has “migrated to ISO 20022”, but which payment flows are affected and how they move between the information system and the banks.

5. Instant payments and Verification of Payee

ISO 20022 is also part of a broader transformation of European payments, including the development of instant payments and Verification of Payee (VoP).

VoP aims to check that the beneficiary information matches the IBAN before a payment is authorised. For businesses, this development further highlights the importance of high-quality supplier data.

Incorrect or incomplete information in an ERP system can therefore have consequences for payment controls and processing.

6. What are the implications for information systems?

ISO 20022 highlights a fundamental principle: the quality of a financial data flow depends on the quality of the data feeding it.

Well-structured data can be reused more easily across different systems and processes. It can also support automation, bank reconciliation, controls and reporting.

The gradual adoption of ISO 20022 can therefore provide businesses with an opportunity to review the quality of their financial data and the way it flows between their different systems.

7. What does this mean for businesses using Sage X3?

For businesses using Sage X3, it is particularly relevant to check whether their environment is able to support changes to banking formats.

Sage X3 supports various banking processes and formats, including formats based on ISO 20022. The management of structured addresses and banking files is also covered by specific functionality and documentation within Sage X3.

Businesses should in particular review:

  • the version of Sage X3 in use;
  • configured banking formats;
  • supplier and customer data;
  • address management;
  • interfaces with banks;
  • bespoke developments;
  • payment and reconciliation processes.

The objective is therefore not simply to determine whether a business needs to “migrate to ISO 20022”, but to check that the entire Sage X3 environment is able to support the evolution of the standards and banking flows used by the business.

8. What should businesses do now?

Even though some deadlines have been postponed, businesses can use this additional time to prepare their systems and data.

A first assessment could focus on the following questions:

  • Which banking formats do we currently use?
  • Which banks and infrastructures are connected to our information system?
  • What types of payments do we make?
  • Is our supplier and customer data sufficiently structured?
  • Do our banking interfaces use standard formats or bespoke developments?
  • Are our ERP and banking communication solutions up to date?
  • Have we identified the deadlines that apply to our different payment flows?

This mapping exercise helps turn what can sometimes be seen as a purely banking-related topic into a practical assessment of the impact on the information system.

Key takeaways

ISO 20022 does not represent a single migration that affects all businesses on the same date. It is a gradual evolution of financial standards, with requirements that vary depending on countries, banks, infrastructures and payment flows.

The postponements announced in 2026, particularly those relating to structured addresses, provide additional time for businesses to prepare. However, they do not change the broader move towards more structured and usable financial data.

For businesses, the main areas of focus are therefore data quality, banking formats, interfaces and financial processes.

For organisations using Sage X3, this evolution provides an opportunity to review supplier and customer data, banking formats, interfaces and any bespoke developments.

ISO 20022 should therefore be seen as a topic at the intersection of finance, data and information systems, with implications that go well beyond the format of banking files.

 

Sources :