as part of the ISO 20022 alignment I see there is more and more (mandatory) requirements to populate your payment files with (semi) structured beneficiary address fields.
in our current setup for example it is fully unstructured … all data merged into address line.
How are you guys progressing with changing this ?
And can you confirm this is a global requirement to change this ? (Will payments be rejected if not complying to it?)
And will this be per Nov 2025 or Nov 2026 as I am hearing a lot of mixed communications.
This is a great GenAI use case. Ask AI e.g. to structure a specific Malaysian address into JSON format that is compatible with the ISO20022 address structure, including the building number and unit reference tags.
One needs to specify country, the format, and the required tags to get the best possible response. To do this in scale some programming skills will help. Happy to have a call to chat more on this.
unstructured, in 1 field not ok anymore. Separate field for street, postal code, city, country. Judges are still struggling with double addresses, buildings and floors.
as of 2025 semi structured is possible already.
it is required for certain payment types (international and sepa outside EEA).
for exact details you bank knows best as every bank is further in THEIR implementation as well
One major bank just today told us that payment files will not be rejected, if still unstructured by Nov 2025 / 2026, even for International and SEPA outside EU.
The only requirement for structured (and rejections) is for POBO debtor information and for DD collections for the debtor information, but not for any creditor information.
Then other banks, do say it is mandatory in their ISO pitchbooks (for debtor and creditor details) or they will reject the payment files.
.
