New Payment Format iso20022 pain.001.001.009

We have followed the steps and when trying to create the payment we had the below error.

Then we entered the whole account number in Account Number field and it worked. My question is that, is that correct to do it like that?

Hello ​@Ralph Gericke ,

Actually we’ve IFS App10 UPD27 and I know that the format ISO20022 pain.001.001.09 is available, and what about the SEPADD pain.008.001.08, can it also be available to IFS App10?

Thanks & Regards,
André Lima

Hi,

We are currently looking into implementing this in Employee Payments as well.

I will get back with firm timelines in the future, but the current plan is to deliver this for 26R2 and evaluate the impact for supported tracks including apps 10. 

Best regards,
Sahan Wijerama

Hi All,
as you know, the effective November 14, 2026, financial institutions and corporates sending cross-border payments that include addresses over Swift Cross-Border Payments and Reporting Plus (CBPR+) or key Payment Market Infrastructures (PMIs) must use hybrid or fully structured addresses. If using MT messages, senders must include structured Town Name and Country address elements (F-Option). This requirement also impacts domestic payments with a cross-border payment leg. Unstructured postal addresses will be removed after November 14, 2026.

At this moment, IFS is able to create supplier payments with ISO20022 CORE 001.001.009 xml schema.
When the supplier’s payment address is set TRUE for Detailed Postal Address, then the xml file contains the Town Name  <TwnNm> and country <Ctry>, but does not contain the Building No <BldgNb>. The street name <StrtNm> contains the building No.
When the supplier’s payment address is set TRUE for Detailed Postal Address, then the xml file contains only the old address lines <AdrLine> which will be retired.
How we can manage the standard supplier payments file created by ISO20022 CORE 001.001.009 xml schema? We are using Cloud 26R1.
The IFS can not create hybrid format.

What is the current situation with that at IFS? Does it mean, that customers need to create their own transformers?

Any feedback is appreciated, thanks

ISO 20022 Core 09 format is now available in below tracks and onwards.
 

 As per July 2026 SU release schedule, the fix was released in these specific SU versions:

Plus 26R2 EA will contain this new format and Apps 10  fix was delivered via https://ifsdev.atlassian.net/browse/HRZ-20962 (CS0542920 )

Hi All,

We are using IFS CLOUD 26R1 SU2. I’ve created the ISO20022 file but I think the file structure is not correct:

I’ve downloaded the related transformer from RnD core environment (26R1 SU4) and put our environment to try the new payment file. The result was the same.

If I don’t enable the detailed address I get this non-structured xml:

I would like to ask please add more information about setups and solution!

Many thanks for helping

Hi,

This new transformer is applicable only with the newly introduced ISO CORE 09 format only. So customers don’t need to reimport the transformer if they are already in 26.1.2

Also the intended behavior is to enable the structured address only when the detailed postal address is enabled.  (This flexibility was provided in case if customers want to continue with old way)

There will be news presentations released with 26R2 EA. But if you need any help before that, reach out to IFS support team.
Also we are working on some supplementary fixes received by customers while they test. Those will be released with OCT SU (unless OOB is requested)