What does the ISO 20022 migration actually cost a mid-market company?

By Saurabh Goyal, Founder & CEO of Phlo Systems. Published 25 August 2026.

There is a strange asymmetry in the ISO 20022 migration. On the bank side, the costs are public and enormous: Celent estimated banks had put over $100 billion into the standard by early 2023, recent survey coverage puts individual banks at around $20 million each for the November 2026 requirements, larger institutions above $30 million, and 44% of banks say they are behind. On the corporate side, where finance directors are now being told to restructure addresses and rebuild payment files by 14 November 2026, there is no published benchmark at all. Advisory firms write about "the silent cost" and treasury vendors say "allocate budget for system updates and data remediation" — but nobody prints a number.

The 30-second answer: for a mid-market company the honest range runs from near zero to the mid tens of thousands of pounds, and the spread is not vendor pricing games — it is scope. The compliance-critical piece (structured addresses by 14 November 2026) is small: for a typical mid-market ledger it is days of clerical work, and if it is folded into a data project already underway, it can genuinely cost nothing incremental. The expensive piece is the certified bank interface (the new pain.001.001.09 file built to your bank's specification, certified through its test cycles, delivered over a secure channel) — and that piece, for most corporates, has no deadline yet. Companies get bad outcomes when a quote bundles the two, prices the full menu of payment types they do not use, and charges technical rates for clerical data work their own team could do in a week.

Where the money actually goes

Every corporate-side migration decomposes into the same six components, whoever delivers it:

1. Address data cleansing — splitting every supplier and customer address into the bank-required structured fields. Cost driver: record count. A mid-market trading company with a few hundred counterparties is looking at days of methodical clerical work, not a project. This is also the only component with a hard deadline.
2. Structured capture — changing ERP entry screens so new records are born compliant. Small, one-off configuration.
3. Payment file generation — building the new format to your bank's published implementation guide. Stock ERP output does not match any bank's profile; even SAP customers are asking their community for format development for exactly this. Cost driver: how many payment types you actually use — each one carries its own mapping rules.
4. Status messages back — handling the bank's acknowledgements and rejections into your ledger, so a bounced payment is visible the same morning.
5. The secure channel — host-to-host or API connectivity, certificates, registration.
6. Bank certification — validated test files per payment type through the bank's own gates. Cost driver: calendar more than effort. Industry practice puts corporate-to-bank connectivity at four to twelve weeks per bank, because the bank paces the test cycles — and with 44% of banks behind on their own readiness, the queues get longer as November approaches.

The costs of not migrating are also real

Two show up in the published guidance. Advisory firm Redbridge raises the pointed question of whether banks will keep back-office teams to repair or enrich non-compliant files, "and if they do, at what cost" — repair fees for corporates who arrive at the deadline unprepared. And treasury vendor Kyriba flags potential additional bank charges for continued reliance on legacy formats. Add the hard one: from 14 November 2026, a payment message with a fully unstructured address is rejected outright, and your supplier finds out before you do.

What a fair quote looks like

Four tests, whoever you buy from. It separates the deadline work from the optional work, and tells you plainly that the November requirement alone can be met cheaply. It is priced per payment type you actually use, not for the full menu. It puts the clerical data work with your team if you have the capacity (with a format guide), rather than billing it at technical rates. And its acceptance criteria are the bank's own validated test files, so "done" is the bank's verdict, not the vendor's.

Tell us what this is costing you — we will publish the picture

Because no corporate-side benchmark exists, we are building one. If your company has been quoted for, budgeted, or completed an ISO 20022 / payment-file migration — whatever the vendor, whatever the bank — we would genuinely like to hear it: what was quoted, what was in scope, how the bank's testing went, what surprised you. We will aggregate and publish the results anonymised — no company names, no bank names, no vendor names — so the next finance director has a reference point that today does not exist. Share your experience through the short form here (a sentence or two is enough), and if you would like the compiled benchmark when it is ready, say so and we will send it to you first.

And if you are still working out what your own bank's letter actually requires, the plain-language explainer is here and our fixed-scope migration service is here.

Frequently Asked Questions

How much are banks spending on ISO 20022?

Analyst firm Celent estimated banks had invested over $100 billion in ISO 20022 preparations by early 2023. For the November 2026 requirements specifically, recent survey coverage puts typical individual bank spend around $20 million, with larger institutions above $30 million.

Why is there no published cost benchmark for corporates?

Corporate migrations vary enormously with scope: how many payment types, how many counterparty records, how many banks, and whether the work rides inside an ERP project. Vendors quote privately, corporates rarely disclose, and advisory coverage stays qualitative. That is why we are compiling an anonymised benchmark from real corporate experiences.

What is the cheapest compliant path for November 2026?

Structured or hybrid addresses in your payment files — town and country as discrete fields at minimum. For a mid-market ledger that is clerical work measured in days, and it satisfies the only hard deadline most corporates face. The certified new-format file build can usually follow on its own timeline.

What drives the cost of the certified file build?

The number of payment types you use (each carries its own mapping and its own bank test files), the state of your counterparty data, and the bank's certification calendar. The build effort is days; the bank-paced validation cycles are weeks — typically four to twelve weeks per bank end to end.

Can banks charge companies that do not migrate?

Published treasury guidance flags both possibilities: fees for banks repairing or enriching non-compliant files, and additional charges for continued reliance on legacy formats. The certain cost is operational: from 14 November 2026, payments with fully unstructured addresses are rejected outright.