Electronic Payment file ISO20022 GB error when generating a payment

(0) Share

Report

Posted on by Community Member

Hello all

I'm having a problem after loading the payment file 'ISO20022 - GB' from the Microsoft repository.

After loading an applying to method of payment, I get the following error when I try to generate a payment. the following message appears..

Payment generation process information

Evaluating expression for path 'CreditorAgent/$ClrSysIdCode'.

Evaluating expression for path 'RoutingNumberType'.

Enums/RoutingNumberType/SC

Element of the configuration 3 - 'SC' is not found

Property 'Enabled' of the format component 'ISO20022CTReports/XMLHeader/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/CdtrAgt/FinInstnId/ClrSysMmbId/ClrSysId' is evaluated.

An error occurred during the 'Format mapping' run. For more information, contact your system administrator.

Property 'Enabled' of the format component 'ISO20022CTReports/XMLHeader/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/CdtrAgt/FinInstnId/ClrSysMmbId/ClrSysId' is evaluated.

Error while evaluating expression for path 'CreditorAgent/$ClrSysIdCode'.

Error while evaluating expression for path 'RoutingNumberType'.

Element of the configuration 3 - 'SC' is not found

The payments cannot be generated

I've checked the vendor bank account and the field 'routing number type' has SC chosen. I also checked the bank account and that also has SC.

I'm at my wits end - can anyone advise what I'm doing wrong?

Thanking you in advance

David

I have the same question (0)

All responses (10)

Answers (2)

greengrimms 1,400 on at

Like (0)

Report
Copy link

Link copied!

Hi David,

When you obtained the ER format from the MS repository, did you happen to see which version was it? Did it worked before?

Was this reply helpful? Yes No
Suggested answer

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hello David,

Can you check your vendor bank details and also your company's bank account detail for the SC type?

If things are completely setup then get into contact with the MS support to ensure that this behavior is not the result of a bug.

Best regards,

Ludwig

Was this reply helpful? Yes No
Suggested answer

Elsa Guo Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hello David,

From internal research ,seems that we already fixed this bug on 10.0.20.

LCS link Details for issue 571394 (dynamics.com)

Thanks.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

thank you everyone

I can confirm..

SC is on the vendor bank detail

SC is on the Bank

when downloaded from MS repository, the version number is 43.56.11

I was told by my team that it worked in a previous environment however I checked in there and it doesn't work.

Could it be the formula definitions within the mapping in formula designer?

thanks

David

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

just wanted to add further information...

if I add a swift code and iban code into the supplier bank account, the file is now being produced however, when trying to load to the bank, the bank is pointing to the Swift / Iban fields.

As this is a GBR generated payment for a GBR supplier, only sort code and account number is used...

I checked the formula from...'ISO20022CTReports/XMLHeader/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/CdtrAgt/FinInstnId/ClrSysMmbId/ClrSysId' is evaluated.

Error while evaluating expression for path 'CreditorAgent/$ClrSysIdCod

it is the following...- $ClrSysIdCode: Calculated field = CASE(model.Payments.CreditorAgent.RoutingNumberType, RoutingNumberType.None, "", RoutingNumberType.AT, "ATBLZ", RoutingNumberType.BL, "DEBLZ", RoutingNumberType.CC, "CACPA", RoutingNumberType.CH, "CHBCC", RoutingNumberType.CP, "USPID", RoutingNumberType.FW, "USABA", RoutingNumberType.SC, "GBDSC", ""): String

if you look at the last line, RoutingNumberType.SC, "GBDSC"

not sure if that's a red herring or not

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (0)

Report
Copy link

Link copied!

Hi

I had the exact same issue and logged this with Microsoft. They replied its a known issue which they will resolve but the attached provides a workaround. Just manually update Payment model 80 and 82 as per the attached. Let me know if this helps,TrackingID_2300_2106180050000788.docx please. Thx

Was this reply helpful? Yes No
Community Member on at

Like (1)

Report
Copy link

Link copied!

hi

thanks for the reply - i've checked in the MS repository and 80 /81 are not there - any ideas?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

and we're on version .18

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (0)

Report
Copy link

Link copied!

so log into ER and click on the Microsoft Repository. Global > Open >

Look for the payment model.

I should have checked first however - I'm using 10.0.16 - What version are you on as it needs to be this maybe or later

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

thank you for your help - it now works!

Was this reply helpful? Yes No