Hello IFS,

we have also received requests from some banks to prepaire ourselfs to switch to Pain.001.001.009 format.

What are the plans for introducing support of the format?

Hello IFS, 

We currently have a customer who’s bank will be updating their system to require Pain.001.001.009 from November 2023, Is there an update for introducing this within IFS? 

Thank you, 

Mish

Hi, 

Thinking it may be best to log a call center case. This could be another set of people who may see the inquiry.  FYI, I sent the link to a coworker, unfortunately due to the vacation season, my contact is out of the office. 

Best regards, 

Thomas

@Thomas Peterson

Most of the banks now advise Corporates to migrate to the latest Common Global Implementation (CGI) ISO 20022 version (pain.001.001.09 or V9) in order to benefit from a harmonized cross-border payment experience and the latest value-add services. Although this version is based on the ISO20022 2019-2023 release, the bank adoption is very new and some banks like Citi are going to support this version from 2023 onwards. Since IFS also follows the Common Global Implementation (CGI) releases, it is good to introduce pain.001.001.09 as a new XML transformer in IFS Core solution. However, pain.001.001.03 version should be continued until all the banks and clearing channels are completely moved to V9.

There are not a lot of differences between V3 and V9 versions from IFS perspective other than some points highlighted below.

1. Introduced additional attributes for postal addresses presentation
2. UETR - Unique End-to-end Transaction Reference (SWIFT gpi) to track the payment (added to PMTINF level)
3. LEI: Legal Entity Identifier to identify the payment initiating party (Initiating Party/Identification) 

In addition to the above some XML tag names have been changed. 

E.g. BIC ---> BICFI,

BICOrBEI --→ AnyBIC

I am looping @Chirantha who is managing the functional development of this area from IFS R&D side.

Hi,

Thank you Eranda for keeping me in the loop. As suggested by Thomas P., the best approach is to create a new legal request to R&D Finance in order to provide you a solution before the due date.

@agfsavovpla and @mishaelakleker would it be possible to send us a legal request having disucssed this with the relevent country represnettaive in your region.

Pleas do contact me if you need more details over the process of creating a new legal request.

Thank you.

Best Regards,

Chirantha.

Hi,

there was also a discussion in this post:
SEPA ISO20022 XML Transformer for Germany as of 2023 NOV | IFS Community
As per my understanding the “old” Format will be obsolete in 2025.

Regards
Ralph
 

Hello @Chirantha,

is there any information on a possible solution for this legal requirement and will it be available for App9 customers as well?

Thanks and best regards,
  Stefan
 

@Chirantha  is there any update on this? Will this be available for IFS 9 customers?

@Chirantha  is there any update on this? I have a customer in IFS Cloud 23R1, their bank also informed them about moving to iso20022 pain.001.001.009. This version is critical as it can handle foreign payment for Germany (to replace DTAZV format).

Hi All,

Apologies for the delay in getting back to you.

I'd like to update you that our R&D team is currently completing the investigation and will proceed with development as the next phase.

I want to clarify that this development won't be applicable for Apps 9 since R&D has ended support for Apps 9.

Regarding the cloud track for which this update will be accessible, I am not in a position to decide.

For further information on this matter, please reach out to Lena Borggren at lena.borggren@ifs.com.

Best Regards,
Chirantha.

Hi everyone!
Is there any update on the new payment format 001.001.009? Is anyone know in which release IFS Cloud and IFS10 will be delivered?

Regards, Agata

Hi,

here is an update on the upcoming Sepa Pain Versions:

New Pain Version for SEPADD : pain.008.001.08 - CustomerDirectDebitInitiationV08

New Pain Version for ISO20022 : pain.001.001.09 - CustomerCreditTransferInitiationV09

These Versions will be developed and available for 24R2, 25R1, Core 10_26

In addition upcoming CAMT versions:

New ISO 20022 Format for camt. 053. 001. 08

New ISO 20022 Format for camt. 054. 001. 08

These Versions will be developed and available for 24R2, 25R1, Core 10_26

Regards

Ralph

Hi,

Looking into 24R2 for new Pain Version for ISO20022 : pain.001.001.09.

When i look in to transformer IFS_ISO20022_TO_CORE_ISO20022, still pain.001.001.03 is used.

What transformer should be used for this version ?

Regards,

Thomas

Hi Thomas,

the development is not finished yet.

Until November 2025 the already existing formats will fade out.

Means they still can be used.

KR
Ralph

Hi Ralph,

Any date when new Sepa Pain Versions will be released ?

Kind regards,

Thomas

Hi,

the PAIN Format  ISO20022 001.001.09  is availabe for the following versions:

24.2.4 - 24R2 SU4

25.1E.0 - 25R1 EA

APP10UPD27

Kind regards

Ralph

Hello,

Is the new format also available in a Service Update of 24R1?

Regards,

Robin

Hi Robin,
it is only available from 24R2 SU4 onwards.
Regards,
Ralph

Additional Information regarding SEPA CT Pain.001.001.09 version.

If a user needs to process SEPA payment with the latest pain version, this can be done the same via ISO20022 by selecting SEPA as the service level code. Follow below steps to do so.

01. Navigate to window: Application Base Setup > Enterprise > Supplier > Supplier and search for the supplier that you need to do the payment with SEPA CT Pain.001.001.09

02. Go to Payment Tab > Add ISO 20022 as a Payment Method > RMD Payment Method Line ISO20022 > Click on Electronic Payment Address

03. Add a new line and fill the details > In the Payment Instructions field > Under Service Level Code > Make sure to add the Code: as SEPA

This will result the payment file to be created with SEPA CT Pain.001.001.09.

Hi All,

I have question regarding to the employee payment. (IFS_EMP_ISO20022_TO_CORE_ISO20022.xsl)

IFS Cloud 25R1 has Pain.001.001.03 the customer Bank  BNP Paribas is using the Pain.001.001.11

One of the error which not allow me to import Employee Expenses payment is missing XML Dt tag is has been introduced later than Pain.001.001.03.  Do we have any plan to update the our IFS_EMP_ISO20022_TO_CORE_ISO20022.xsl  transformer to include the lattes version Pain.001.001.11 or Pain.001.001.12? 

​@Les I believe there may be a misunderstanding. The most recent payment initiation file version 9 has been accepted by the SWIFT CGI group, which includes most major global banks and financial institutions.

While ISO 20022 payment messages evolve annually with new versions, actual adoption by banks does not always keep pace. For example, BNP Paribas has clearly communicated in their latest newsletter that they currently support pain.001.001.09, which dates back to 2019.

Which country is your customer located in? It is better to double-check this again with the bank. 

FYAI: It is not possible to handle the version change via the transformer only, since there are some new XML elements added and required to fetch data from the application.

​@Eranda 

I hope this message finds you well.

The follow up on the BNP Paribas Bank template from Poalnd, specifically regarding XML V2 domestic transfers (page 49). I've attached both the template and an XML example for your reference.

When you open the XML example, you'll notice the namespace xmlns:urn1="urn:iso:std:iso:20022:tech:xsd:pain.001.001.11".

To get employee expense payments accepted by the bank, I've customized the IFS_EMP_ISO20022_TO_CORE_ISO20022.xsl file. I added the missing <Dt> element within <ReqdExctnDt>, as shown below:

XML

<ReqdExctnDt>
    <Dt> <xsl:value-of select="$Vvar22_RESULTOF_substring"/> </Dt>
</ReqdExctnDt>

This change has successfully enabled the bank to accept employee expense payments.

While this workaround is effective, I'd prefer an official core version developed by IFS. As you mentioned, there could be numerous new XML tags (100 or more) that might be useful in the future. Could you please direct me to the person responsible for this development in the core system?

I'm a bit confused as to why only supplier payments were updated to Pain.001.001.09, while employee payments still use Pain.001.001.03. It seems logical that the same changes applied to supplier payments should also be incorporated for employee payments.

​@Ralph Gericke 

As ​@Les wrote:

I'm a bit confused as to why only supplier payments were updated to Pain.001.001.09, while employee payments still use Pain.001.001.03. It seems logical that the same changes applied to supplier payments should also be incorporated for employee payments.

I share his opinion. Is there a way to make Pain.001.001.09 available for employee payments as well? The employees of our customer would like to get paid, not very surprisingly...

Hi ​@Ralph Gericke  

I followed your steps in 24R2 (24.2.5) I am in the below window but I can’t see the field which you mentioned below.

“ 03. Add a new line and fill the details > In the Payment Instructions field > Under Service Level Code > Make sure to add the Code: as SEPA”
 

Also do we need to change anything in the format specific information per institute window?