ISO 20022 structured addresses for corporates — stop payment rejections before November 2026
From 14 November 2026, your banks need at least structured Town and Country at payment initiation, or your cross-border payments can be rejected. ioNova resolves the free-text supplier and counterparty addresses in your ERP into full ISO 20022 structured addresses — across 246 countries and 50+ scripts — so payments clear the first time, on every channel.
AI-native coverage / rules-engine determinism / 30+ years of payments compliance experience.
See how corporates deploy ioNovaPlot 47, near City Mall, Andheri East
Mumbai 400069, India
The runway to structured-address payment initiation
From 14 November 2026, your banks can reject cross-border instructions that arrive without structured Town and Country. The obligation sits upstream — in your ERP and treasury master data, not with the bank. Standardising counterparty data now is what keeps the November payables run clean.
Three pressures on corporate payables — before 14 November 2026
The mandate reaches into your ERP, your bank relationships, and every payment you initiate. Here's where the address requirement actually bites for a corporate treasury.
Your ERP data is free text
Supplier and counterparty addresses live as unstructured strings in your ERP and treasury systems.
- Most ERP and treasury platforms store addresses in free-text or semi-structured fields.
- From 14 November 2026, banks require at least structured Town and Country at payment initiation.
- You must source, store, and supply creditor address data through your own channels.
- The cleanup spans every counterparty record, not just a handful of payees.
Payments get rejected
Addresses that don't meet CBPR+ rules mean delayed, returned, or repaired payments.
- Banks NAK or hold cross-border instructions that arrive without structured Town and Country.
- Applies across MT101 SCORE, pain.001 SCORE+, and proprietary bank channels alike.
- Returned payments mean late settlements, supplier friction, and manual rework.
- The requirement covers all payment types — trade, FX, funds, and securities included.
Every channel needs it
There's no single switch — each bank relationship and channel expects compliant data.
- Address requirements apply regardless of which bank or channel you use.
- Multi-bank corporates must standardize data once and feed it everywhere.
- Manual remediation per-bank doesn't scale to a global payables run.
- ioNova structures addresses once, at the source, for every downstream payment.
A common misreading is that banks will structure addresses for their clients. Under the CBPR+ change, the originator must source and supply at least structured Town and Country at payment initiation — SWIFT and the PMPG place the obligation upstream, in the ERP. Banks can reject instructions that arrive unstructured; they cannot create address data you have not provided.
Your payables run, before and after ioNova
What changes for a corporate treasury when free-text counterparty addresses become structured ISO 20022 data at the source.
| For your payables | Status quo | With ioNova ARS |
|---|---|---|
| Counterparty address data | Free text in ERP / treasury | Structured ISO 20022 at the source |
| Payment acceptance (14 Nov 2026) | Rejection / hold risk | Passes CBPR+ at initiation |
| Country & script coverage | Gaps in non-Latin markets | 246 countries, 50+ scripts |
| Multi-bank channels | Remediate per bank | Standardize once, feed everywhere |
| Settlement reliability | Returns and late payments | Fewer exceptions, on-time settlement |
| Time to production | Manual project per system | API integration in 2–4 weeks |
What corporates ask about ISO 20022 and address intelligence
What does the November 2026 ISO 20022 mandate require corporates to do?
Will my cross-border payments be rejected if addresses aren't structured?
How does ioNova fit into our ERP or treasury workflow?
We pay suppliers in many countries and scripts — can ioNova handle that?
Should we wait for our banks to handle this for us?
Keep every payment flowing.
Through the November 2026 cut-over.
ioNova structures your counterparty data once, for every bank and channel. 246 countries, 50+ scripts. Live in 2–4 weeks.