Hi @Rich P 

you will find it on the IFS server (or FTP server of IFS if you are in cloud). You can control it via IFS connect.

It isn’t possible to export this file on you local path.

For example:

Hi, the difference is BACS and similar are text type files.   SEPA and ISO20022 are XML.   They follow different logic / program flows.  

Best regards

Hi

Is anyone successfully taking the ISO20022 SEPA xml and getting Lloyds bank to process it? We have tried again today and Lloyds won’t accept the file as it has ‘an error’.

We get no  further detail to identify what causes the problem

Regards Rich

Hi @Rich P 

ISO20022 and SEPA are two different files. For ISO20022 you need more settings than SEPA. SEPA is very easy. Both files export via IFS Connect. Are you in cloud or onprem?

Hi

We are using Apps 10 - we have selected the SEPA format ID as below:

Hi, 

A common problem with SEPA is that it’s no longer a fixed format as it was first intended. It has evolved such that differences exist between banks and countries. 

ISO2022 is a more modern format that is said be to be a replacement for SEPA.  I would suggest ISO20022. You have more options.    From a IFS R&D contact (a few years ago” SEPA - BAD  ISO20022 - good.    The downside of ISO20022 some banks have been “slow” to adapt to the newer format.  ISO20022 has only been around for nearly 20 years.

In dealing with banks / client's numerous times, I’m a bit surprised you can’t get a formal detailed error message.  Is it possible you're not contacting the “right” person?   I say this because often it has been reported to me that “the bank” did not provide that information, but when digging deeper, the bank really did / really can provide the details.   

Best regards