ISO 20022 Migration in the UK: What's Changing (and What's Just Been Delayed)
The ISO 20022 migration is the biggest shift in payment messaging in a generation, and for UK finance teams, it has just become more confusing rather than less. The industry-wide deadline to stop accepting unstructured addresses in payment messages, originally targeted for November 2026, has been pushed back by both Swift and the Bank of England.
For UK businesses, three different payment rails, CHAPS, Bacs and Faster Payments, and cross-border Swift payments, are each on their own timeline. Treating them as one deadline is the single most common mistake we see finance teams make.
What is ISO 20022 migration?
ISO 20022 migration is the global banking industry's shift from the older MT payment messaging standard to ISO 20022, a structured, XML-based format that carries far richer payment data, including addresses broken into separate fields rather than free text.
Banks worldwide have been replacing MT with ISO 20022 for both payment instructions and account reporting. For UK businesses, the practical change shows up first in how beneficiary and debtor addresses are formatted: a single free-text line is no longer enough, addresses need to be broken into structured elements (building number, street, town, country) or, at minimum, a hybrid format where town and country sit in their own fields.
Why this is happening
Structured addresses improve data quality. They let banks screen payments for sanctions and financial crime more reliably, route them with fewer manual interventions, and reduce the investigation time when something goes wrong. It's an industry-wide move, driven by banks and payment schemes rather than by a single regulator, which is part of why the timeline varies so much by network, and by payment rail.
The Swift ISO 20022 migration timeline: what's confirmed, what's deferred
Swift's core MT-to-ISO 20022 messaging migration for cross-border payments (CBPR+) was completed in November 2025. Fully unstructured addresses were still tolerated at that stage. The next milestone, a hard requirement for fully structured or hybrid postal addresses, was due in November 2026.
This is the most important update for anyone tracking this topic: the structured address requirement that was due to take effect in November 2026 has been officially deferred, and no new date has been confirmed.
On 27 August 2026, Swift announced it was extending the deadline after industry-wide requests for more time, and will confirm a new timeline by December 2026 at the latest.
The Bank of England followed the same day. Its ISO 20022 page (last updated 27 August 2026) confirms that the November 2026 RTGS standards release, which included the removal of unstructured address fields for CHAPS, has been "deferred in its entirety." The Bank's current working expectation is a 12-month deferral, folding the change into the November 2027 release, though it stresses this "remains subject to confirmation."
One distinction worth being precise about: it's the address requirement that's deferred, not ISO 20022 itself. The underlying ISO 20022 messaging migration (the shift from MT to XML-based MX messages, pacs.008, pain.001 and so on) is already live and isn't going anywhere. What's been pushed back is specifically the rule that would have rejected messages still carrying a free-text-only <AdrLine> instead of structured fields like <TwnNm> (town name) and <Ctry> (country).
This also applies beyond Swift: the European Payments Council (EPC) runs a parallel, aligned structured-address requirement across all five SEPA scheme rulebooks, and its Payment Scheme Management Board also deferred that deadline on 9 September 2026, shortly after Swift's own announcement, with a new date expected in October 2026. So a UK business making SEPA payments into the eurozone is in the same position as one making Swift cross-border payments: the direction is confirmed, the date isn't.
Three UK payment rails, three different timelines
Payment rail | Scope | ISO 20022 status |
|---|---|---|
CHAPS | UK domestic, high-value sterling payments | Migrated to ISO 20022 messaging on 19 June 2023. The structured-address requirement, separate from the messaging migration itself, was aligned to November 2026 and has now been deferred, expected around November 2027, pending confirmation. |
Bacs & Faster Payments | UK domestic retail payments | No confirmed ISO 20022 structured-address deadline. The New Payments Architecture (NPA) programme that was meant to carry this forward has itself been restructured by the Payment Systems Regulator, with its own timeline under review. Businesses relying solely on Bacs or Faster Payments are not currently bound by a firm date. |
Swift cross-border (CBPR+) | Payments sent or received internationally via Swift | The structured-address requirement, originally set for November 2026, is the one Swift deferred on 27 August 2026. A revised date is expected by December 2026. This is the rail most UK businesses trading internationally should keep watching most closely. |
If your payments are purely domestic UK transfers, the pressure has eased considerably for now. If you regularly send or receive international payments via Swift, or your bank routes CHAPS payments with enhanced data, this is still very much live, it's just no longer pinned to a specific November 2026 date.
What to check on your side
Whatever your payment mix, a few checks are worth doing now rather than waiting for a firm date to reappear:
Check your file format. Confirm your ERP or accounting system can produce payment files your bank will accept once structured or hybrid addresses become mandatory.
Check your beneficiary data. Every payee record should hold town and country as separate fields, not merged into one address line.
Ask your bank directly. Deadlines vary by bank and by payment rail, and some banks may hold to earlier internal timelines regardless of the industry-wide extension.
Keep testing. Where your bank offers a validation option, send a sample payment with a structured address now.
What this means if you pay through Agicap
The answer depends on how your payments reach Agicap in the first place, and it's worth being precise about the difference between two separate things: formatting the payment message (Agicap's job) and cleaning the underlying address data (the customer's job, whichever route the payment takes).
- •
If you create your payments directly in Agicap, Agicap builds the correctly formatted ISO 20022 message on your behalf, rolling out the structured address format bank by bank ahead of each bank's own deadline, so most of that technical work happens behind the scenes. What Agicap can't do is invent data that isn't there: if a beneficiary's town and country were never captured as separate fields in the first place, Agicap has no source to pull structured data from. That's why the one thing worth checking is that city and country are stored as separate fields in your beneficiary data, not combined into a single address line, before the format is ever built.
- •
If your payments are created outside Agicap, in your ERP or accounting software, and then routed through Agicap, the same logic applies one step earlier: that system needs to export an ISO 20022-compliant file with structured or hybrid addresses already in place. Agicap routes the payment through to your bank, but it can't retroactively parse or restructure address data that arrives already flattened into free text.
Either way, the deferral doesn't remove the underlying task: fixing address data at the source is a master-data project.
How a clean payment setup pays off: Luminous Hotel Management
This case doesn't involve ISO 20022 structured-address compliance specifically, but it illustrates the underlying discipline this migration rewards: knowing exactly where your bank connections and payment data stand, entity by entity, bank by bank. Multi-bank complexity is often where format changes like this one cause the most friction, and it's worth seeing what that discipline looks like in practice.
Luminous Hotel Management, which manages 17 entities and 67 bank accounts, used to reconcile its accounts manually across all of them. After centralising banking connectivity and automating reconciliation through Agicap, the time spent on bank reconciliation dropped by 90%, down to under two hours a week, and the company avoided hiring a dedicated full-time employee for the task. "Before Agicap, we had no clear view of the net cash generated or consumed each month," says Neha Jadav, CEO and Co-founder.
The bottom line
The November 2026 deadline you may have read about elsewhere has moved, but the direction of travel hasn't changed. Structured payment data is still where the industry is heading, on CHAPS, on Swift, and eventually on UK domestic retail rails too. The businesses that keep cleaning up their beneficiary data and testing their file formats now won't be scrambling when the next date is confirmed, whenever that turns out to be.
If your payments run through multiple banks and systems, it's worth checking now whether your setup can handle a structured-address requirement before it's mandatory.
Explore how Agicap handles multi-bank connectivity and payment routing to see where the gaps might be.
Frequently asked questions about ISO 20022 migration
Is the ISO 20022 structured address requirement limited to cross-border Swift payments, or does it reach SEPA too?
It reaches SEPA as well, on its own aligned timeline. The European Payments Council (EPC) runs a separate structured-address requirement across all five SEPA scheme rulebooks (SEPA Credit Transfer, SEPA Instant Credit Transfer, SEPA Direct Debit Core and B2B, and One-Leg Out Instant Credit Transfer), originally set for 15 November 2026 to align with Swift's own date.
Following Swift's 27 August 2026 deferral, the EPC's Payment Scheme Management Board decided on 9 September 2026 to delay its own SEPA deadline as well, with a new date expected at its October 2026 meeting. CHAPS is affected for a similar reason: the Bank of England chose to align its own structured-address timeline with Swift's, not because Swift's CBPR+ rules apply to CHAPS directly.
Does a hybrid ISO 20022 address need more than just the country field?
Yes. A hybrid address requires both town/city and country as separate, structured fields, a country code on its own doesn't meet the minimum bar, even under the more lenient hybrid format.
My bank has already flagged structured address changes to me, does the Swift deferral cancel that?
Not necessarily. Banks can enforce parts of the structured-address requirement ahead of, or independently from, the industry-wide Swift/CBPR+ timeline. Confirm the exact date and scope your bank referenced rather than assuming the recent deferral automatically applies to your own banking relationship.
Is CHAPS affected by the ISO 20022 migration timeline?
CHAPS itself migrated to ISO 20022 messaging on 19 June 2023. A separate, later requirement to phase out unstructured addresses was aligned with the November 2026 Swift deadline and has been deferred alongside it, with the Bank of England currently expecting around November 2027, subject to confirmation.
Do Bacs and Faster Payments have a confirmed ISO 20022 deadline?
Not currently. The New Payments Architecture programme meant to bring Bacs and Faster Payments onto ISO 20022 has been restructured, and no firm structured-address deadline applies to these domestic retail rails at this time.
