Why this paper exists

Banks completed their migration to ISO 20022 in November 2025. Many of the companies that pay suppliers overseas did not move with them, and every legacy file they send is now repaired, charged for, or rejected. That cost is real but scattered: repair fees, delayed suppliers, held shipments, FX slippage, and receipts matched to invoices by hand. This paper puts the pieces in one place and shows why closing the gap does not require replacing your ERP or treasury system.

Inside the paper

The industry moved. Many corporate systems did not

What changed with ISO 20022, the migration the banking industry completed, and the road ahead through 2028.

What happens if you are still sending legacy formats

Conversion charges, rejections, and why Swift’s fallback service is not a substitute for fixing the gap.

What legacy payment formats cost the business

Supply chain delays, foreign-exchange exposure, reconciliation effort, and the five questions finance leaders should ask.

Modernize the payment message, not the finance stack

A conversion layer in the payment flow, what it changes for the business, and who this approach is for.

How the conversion works, and what changes for your team

The six steps from existing format to validated ISO 20022 output, and the questions controllers ask first.

Why the industry is not ready, and what that means for you

The structured address requirement, the state of readiness, and why the data work can start now.

Industries covered

●

Banking and Financial Services

●

Payments and Fintech

●

Enterprises in any industry that pay suppliers across borders

Who should read it

Finance and treasury leaders whose systems still produce MT101s, positional files, or bank-specific CSVs, and who want the gap closed without a payments transformation program. One section is written specifically for transaction banking and client-servicing teams whose corporate clients still send legacy formats.

The industry moved. Many corporate systems did not

What happens if you are still sending legacy formats

What legacy payment formats cost the business

Modernize the payment message, not the finance stack

How the conversion works, and what changes for your team

Why the industry is not ready, and what that means for you

Altimetrik

Get the White Paper

The Hidden Cost of Legacy Cross-Border Payments

The industry moved. Many corporate systems did not

What happens if you are still sending legacy formats

What legacy payment formats cost the business

Modernize the payment message, not the finance stack

How the conversion works, and what changes for your team

Why the industry is not ready, and what that means for you

Altimetrik

Get the White Paper

What we do

Industries

Ecosystem

What We Think

Who We Are

Contact Us