ISO 20022: Making your payments more reliable before November 2026

Imagine the scene: you receive an urgent call from your treasury department. An international payment has just been rejected. No clear explanation. The supplier is awaiting payment. You contact your bank, which tells you: “Your flows do not comply with the ISO 20022 standard.”

Many companies will experience this scenario as early as November 2026 if they have not anticipated their migration to structured payment formats. The good news? There’s still time to act. Here’s how.

ISO 20022: definition and challenges for finance departments

What is ISO 20022?

ISO 20022 is an international financial messaging standard designed to harmonize and modernize exchanges between banks, companies and payment infrastructures. Unlike previous formats (SWIFT MT, CFONB, AFB320), it is based on an enriched XML language, enabling much more structured information to be transmitted.

In concrete terms, ISO 20022 makes it possible to :

• Reduce errors and rejected payments
• Improve regulatory compliance (KYC, anti-money laundering, sanctions)
• Facilitate automated transaction processing
• Enhancing the traceability and transparency of financial flows

Why is this migration essential?

This standard is gradually being adopted worldwide for all types of flows: SEPA credit transfers, cross-border payments, collections, interbank messages. The old formats will be definitively abandoned, making migration compulsory for all companies making international payments.

November 2026: the critical deadline for structured addresses

The ISO 20022 migration timetable is accelerating. While banks have finalized their transition by November 2025, companies have until November 18, 2026 to comply with a major requirement: theban on unstructured addresses in payment messages.

End of MT101/MT103 and AFB320 formats

From this date, the old file formats (SWIFT MT101, MT103, AFB320) will be replaced by XML pain.001 (Payment Initiation) files.

This change requires new rigor in the structuring of data, particularly beneficiary addresses.

The 3 ISO 20022 address structuring levels

ISO 20022 defines three address formats:

• Unstructured address
  • All information in a free text block
  • Example: “123 rue de la Paix, 75008 Paris, France”.
  • Banned from November 2026
• Hybrid address (authorized)
  • City and country in dedicated tags
  • The rest is free text
  • Acceptable temporary solution
• Structured address (recommended)
  • Each element in its own XML tag
  • Separate street number, street name, zip code, city, country
  • Optimum format to avoid rejects

Please note: Although hybrid addresses are still permitted, they may be rejected depending on the requirements of certain banks or countries. The structured address is the only guarantee of total compliance to secure your payments over the long term.

Why do companies underestimate this migration?

A project wrongly perceived as purely IT

ISO 20022 migration is still too often seen as a technical project for the IT department. This is a strategic error. This subject primarily concerns finance departments, and more specifically :

• Treasury and cash management teams
• Procure to Pay (P2P) departments, responsible for scheduling outgoing flows
• Departments in charge of supplier, intercompany and treasury payments

The mistake of waiting for a signal from your banks

Many companies adopt a wait-and-see attitude: they hope their banks will alert them early enough, or that the deadline will be postponed.

This strategy is risky. The banks have finalized their own migration in November 2025. They are under no obligation to support you in yours. And the November 18, 2026 deadline is firm: neither SWIFT nor the EPC (European Payments Council) are planning any postponements.

The risk? A cascade of rejected payments as early as November 2026, with a direct impact on your cash flow and supplier relations.

Operational roadmap: 6 steps to avoid chargebacks

As you can see, waiting is no longer an option. Here’s the roadmap we recommend to our customers for successfully migrating to ISO 20022 before November 2026.

1. Audit & Diagnosis: mapping your ecosystem

• Objective: Identify all payment systems, flows and formats concerned by the migration.

• Concrete actions:
  • Map your payment systems (ERP, TMS, treasury software)
  • Auditing your third-party repositories: how many beneficiaries? What data quality?

💡 Our Council: This phase must involve the IT department, but also and above all the business teams (treasury, P2P, accounts payable).

2. Cleaning & enrichment of third-party repositories

• Objective: Structure your beneficiaries’ addresses to avoid rejections.

• Concrete actions:
  • Identify unstructured addresses in your databases
  • Update your third-party repository in your ERP or TMS

⚠️ Points to watch: This is often the longest and most underestimated project.

3. Upgrade your payment systems (ERP/TMS)

• Objective: Ensure that your tools generate pain.001 compliant XML files.

• Concrete actions:
  • Check that your ERP or TMS supports the pain.001 format (versions v3 or v9)
  • Adapt your validation and scheduling workflows

💡 O ur Council: Some ERPs require upgrades or add-on modules. Anticipate deployment times.

4. Be proactive with your banking partners

• Objective: Understand the specific requirements of each bank.

• Concrete action:
  • Contact each partner bank to find out its precise requirements (structured or hybrid address accepted?)

⚠️ A word of caution: Not all banks are at the same level of maturity. Some will temporarily accept hybrid addresses, others will not.

5. Plan and test all your flows

• Objective: Validate the compliance of your payments before the deadline.

• Concrete actions:
  • Test each type of flow (SEPA, international, inter-company)
  • Test with each partner bank

💡 O ur Council: Plan several waves of testing between June and October 2026. Don’t test at the last minute.

6. Anticipate cascading discharges

• Objective: Implement a continuity plan in the event of a discharge.

• Concrete actions:
  • Define a reject treatment process
  • Communicating risks and procedures internally

⚠️ Point of vigilance: The first few days after November 18, 2026 will be critical. Anticipate an increased workload.

Conclusion: migration to ISO 20022 is not just a technical project

This migration is a strategic challenge for the continuity of your financial operations. Rejected payments, tensions with your suppliers, cash flow bottlenecks: the risks are real if you don’t act now.

At SQORUS, we’ve been helping finance departments with their transformation projects for over 35 years. Our AMOA teams specialized in cash management, treasury and payments work alongside you to audit your ecosystem, clean up your third-party repositories, parameterize your systems (ERP/TMS), manage banking tests and secure your go-live.