Will your bank reject your payments after 14 November 2026? The ISO 20022 structured-address deadline, explained

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

If your company pays suppliers through a bank channel fed by your ERP or treasury system, there is a reasonable chance a letter from your bank about ISO 20022 is sitting in someone's inbox right now. The letters vary, but the core is the same: payment formats are changing, addresses must be structured, deadlines are quoted, and the finance director is left to work out how much of it is real, how much it will cost, and who is going to do the work.

The 30-second answer: one part of this has a hard deadline and one part does not. From 14 November 2026, under Swift's CBPR+ rules, payment messages carrying fully unstructured postal addresses are rejected outright, with no contingency period; the minimum mandatory elements are town name and country as discrete fields. That applies to the addresses inside your payment files, and it is the piece you cannot ignore. The move to the newer pain.001.001.09 file format, by contrast, mostly carries no published corporate deadline: several banks have confirmed in writing that older formats remain acceptable provided the addresses in them are structured. Banks often present both changes in one letter, which is how a small, containable compliance task gets quoted as a large migration project. Separate the two and the November question usually becomes much cheaper than the letter implied.

What actually changes on 14 November 2026

The change is to the address data inside payment messages, not to your banking relationship. Today, most ERP-generated payment files carry counterparty addresses as free text: one to four lines typed however the record was first keyed. From 14 November 2026, interbank payment messages must carry addresses as structured or hybrid data: discrete fields for town and country at minimum, ideally street name, building and post code as well. Fully unstructured addresses are rejected, not queued or repaired. The European Payments Council aligns SEPA schemes to the same November 2026 window, and UK banks' own ISO 20022 guidance says the same thing.

The practical consequence: every supplier and customer record that feeds a payment file needs its address split into the right fields before mid-November. For most mid-market companies that is hundreds of records, not tens of thousands, and it is methodical clerical work against a format guide, not a technical project. If your ERP already holds addresses in discrete fields, it may be close to a non-event; if your payment file is built from free-text address lines, the data work is the deadline-critical piece.

What is not changing in November

The newer payment file format, pain.001.001.09, is where most of the cost in your bank's letter actually sits, and it is the part with room to breathe. Banks would like corporates on it, and new implementations should certainly build straight to it rather than to the older version. But for existing connections, banks have generally committed to supporting current formats until they give notice, and have confirmed that structured addresses inside an older-format file satisfy the November requirement. Germany is the exception worth knowing about: the domestic DTAZV format is being retired in November 2026, so corporates paying through German banks face a forced format migration on the same date.

If your bank's letter reads as though the format migration itself is due by November, ask the direct question in writing: can we remain on our current format past 14 November 2026 if our addresses are structured? The answer shapes the size and urgency of everything else.

What a certified bank-format migration actually involves

When you do move to the new format, whether now or later, it is a bank interface project rather than a report change, and it is worth knowing the components before anyone prices it for you:

• Address data cleansing and capture. Splitting every payable and receivable counterparty address into structured fields, and changing the capture screens so new records are born structured.
• File generation to the bank's implementation guide. Each bank publishes its own profile of pain.001.001.09, typically on Swift MyStandards, and stock ERP output does not match it. Even large ERP platforms need format development for this; their user communities are full of corporates asking for exactly that.
• Status messages back. The bank returns pain.002 acknowledgements and rejections; handling them into your ledger is what turns a fire-and-forget file into a payment process your team can see.
• The secure channel. Host-to-host or API connectivity, with certificates and registration on the bank's side.
• Bank certification. Banks typically require registration on their standards portal and a minimum number of validated test files per payment type before production access.
• Testing on real payment runs before the old route is switched off.

Each payment type you use — domestic bulk, urgent domestic, international, SEPA — carries its own mapping rules and its own certification cycle, so the number of payment types you actually use is the biggest lever on cost. Scope to what you use, not to the full menu.

Why the calendar, not the effort, is the constraint

Treasury implementation practice puts corporate-to-bank connectivity at four to twelve weeks per bank, end to end. The reason is not the build effort: it is that the bank paces the process. Test cycles are scheduled with the bank's technical team, every format deviation discovered in testing requires a new cycle, and certification queues are shared with every other corporate migrating at the same time. That last point matters in 2026: the closer to November, the longer the queues. A migration started with months in hand runs at the fast end of the range; one started six weeks before a deadline does not get to choose.

The sensible sequencing follows from the two-part structure above. Do the structured-address work first, inside whatever data project is nearest to hand, because it alone keeps you compliant in November. Then take the format and channel build as a scoped project on its own timeline, ideally once, straight to the newest version, so you never migrate twice.

The best time to do this is during an ERP migration

If you are implementing or replacing an ERP in the next year, the economics change in your favour. The address cleansing folds into data migration work that is happening anyway; capture screens are configured structured from day one; and the payment interface is built once, against the new system, instead of being built against the old system and rebuilt a year later. A payment-format deadline landing mid-ERP-project feels like bad luck, but handled deliberately it removes an entire future project from your roadmap.

At Phlo Systems we run this migration both ways: embedded inside an opsPhlo or Acumatica ERP implementation, or standalone against the ERP you already run. We scope to the payment types you actually use, put the clerical address work with your team under our format guide where that is cheaper for you, and take the file build, the status handling and the bank certification cycles as fixed deliverables with the bank's test gates as the acceptance criteria. If you have received one of these letters and want a straight read on which parts apply to you and what they should cost, talk to us at finphlo.com — the first conversation is a scoping one, not a sales one.

Frequently Asked Questions

Is pain.001.001.09 mandatory by November 2026?

For most corporates, no. The hard 14 November 2026 requirement under Swift CBPR+ is structured or hybrid postal addresses in payment messages. Several banks have confirmed in writing that existing file formats remain acceptable after that date provided the addresses inside them are structured, and that notice will be given before older formats are retired. The exception is where a domestic format is being withdrawn outright, such as Germany's DTAZV in November 2026. Ask your bank the question in writing rather than inferring from a bundled letter.

What happens if I send a payment with an unstructured address after 14 November 2026?

Under CBPR+ the message is rejected outright; there is no contingency period. The minimum mandatory structured elements are town name and country as discrete fields. In practice, the payment does not leave, and your team finds out when the supplier chases.

What is the difference between a structured and a hybrid address?

A structured address carries each element — street, building, post code, town, country — in its own field. A hybrid address allows some free-text lines but still requires town and country as discrete structured fields. Both satisfy the November 2026 requirement; fully free-text addresses do not.

Does my ERP already produce compliant payment files?

Check rather than assume, on two levels. First, whether counterparty addresses are held as discrete fields or free text: that decides the data work. Second, whether the payment file your system emits matches your bank's published implementation guide for the format version your bank expects: stock output from even the largest ERP platforms generally needs format development to match a specific bank's profile, which is why banks require validated test files before production.

How long does bank certification take?

Corporate-to-bank connectivity projects typically run four to twelve weeks per bank end to end, because the bank paces the test and certification cycles: validated test files per payment type, scheduled joint testing, and a new cycle for every deviation found. The build inside that window is days of work; the calendar is the constraint, and certification queues lengthen as the November 2026 deadline approaches.

Can the migration be done as part of an ERP implementation?

Yes, and it is usually the cheapest place to do it: address cleansing folds into the data migration that is happening anyway, capture screens are configured structured from the start, and the bank interface is built once against the new system. If an ERP change is on your roadmap within a year, sequence the structured-address compliance work now and the certified format build into the implementation.