Error when loading external payment file for CAMT.053 in 25R1

UPDATE:

In the original file from the bank the message codes are located as follows:

I know that if I add <Fmly><Cd> oraz</Cd> </Fmly> into my file IFS can recognize the message codes correctly:

Does anyone know if it is possible for IFSCloud to fetch the message codes from <Domn><Cd></Cd></Domn> ? Or there have to be additional level? 

We are experiencing errors with CAMT053 aswell. Have you reported this to IFS? Got any answers?

Thanks!

UPDATE:

In the original file from the bank the message codes are located as follows:

I know that if I add <Fmly><Cd> oraz</Cd> </Fmly> into my file IFS can recognize the message codes correctly:

 

Does anyone know if it is possible for IFSCloud to fetch the message codes from <Domn><Cd></Cd></Domn> ? Or there have to be additional level? 

Cześć. 

As per format description shared by mbank, transaction codes used could be domain code, family code or subdomain code  :
 

I think current IFS solution reads Family codes, while your bank is sending Domain codes only.  

it means for this bank you should customize your CAMT message transformer to reach to Domain code in absence or instead of Family code. It is not so complex for person knowing xsl/xml. 

Following thread could help as well

Hi,

Please check whether ‘Use Prepared References’ is yes for the relevant message code. In CAMP054 file we had the same issue and when we make this yes and then error disappear and information correctly read to the system. During my investigation I noted that this particular column in the table has data related to payer/payee, ledger item id, ledger series id. Try that

Hello ​@Aleksandra W. ,

The standard CAMT transformer expects: 

<BkTxCd>

  <Domn>

      <Fmly>

        <CD>

However, it is quite easy to adjust the transformer and upload the xsl file and re-upload it. 

I believe , it has change in 25R1 that it no longer handled by a projection but by PLSQL

We have been using ING format, but as of 25R1, IFS expects one statement at a time, which was not the case before.

Regards,

Kajetan Guzy Polska