Finance | Project Operations, Human Resources, ...

Error message when populating IBAN vendor bank number

(0) Share

Report

Posted on by ZvikaR

168

I am getting a strange error message when trying to create a vendor bank record, and populate the IBAN field.

When I create the record, and populate ANY IBAN number (e.g. AD12 0001 2030 2003 5910 0100, but I tested multiple IBAN numbers from multiple countries) I get the following error message: "IBAN routing number does not match bank routing number; IBAN: 00012030 Bank:"

Needless to say, populating the bank account field does not make the error message go away.

the workaround is to make the IBAN invalid (in this case, add 2 "xx" in the end) - so the error message changes:

then after restoring the proper IBAN format, the error goes away.

Now, WTF ?!? anyone has a thought how to not have to go through such detour in order to perform something simple as setting up vendor bank account?

I tried it and got the exact same results in 2 very different environments (difference legal entity, country, different version etc. - both recent D365 F&O versions)

I have the same question (0)

All responses (6)

Answers (0)

Suggested answer

André Arnaud de Cal... 300,896 Super User 2025 Season 2 on at

Like (0)

Report

Hi Zvika,

For some unclear reason, the application is checking for the bank account number field to be filled in with the "legacy" bank account number, before IBAN was introduced. Is this IBAN a real existing value? The error message tells you which part of the IBAN should be placed in the field Bank account number.

Was this reply helpful? Yes No
ZvikaR 168 on at

Like (0)

Report

yes, I tried it with (several) real IBAN numbers.

No, trying to follow the instructions for populating the account number does not make the error go away (just result with error about populating the routing number).

I can't believe not more people running into the same issue...

Was this reply helpful? Yes No
Suggested answer

Ludwig Reinhard Microsoft Employee on at

Like (1)

Report

Hello Zvika,

What has been setup in the iban structure form in the cash and management module?

Can you check the setup made there?

Best regards,

Ludwig

Was this reply helpful? Yes No
ZvikaR 168 on at

Like (0)

Report

Thanks Dr Ludwig.

You definitely send me in the right direction. I did not know about the existence of this table.

To your question:

I am testing with 4-5 IBAN different numbers - each from a different country - all giving the same error, each of them has a matching row in the "IBAN Structure" form with values.

For example:

IBAN: AT61 1904 3002 3457 3201

table setting:

I checked few of the examples I used (the one I put at the first message, and the following: BR97 0036 0305 0000 1000 9795 493P 1 etc)

as far as I can see the "setting" in this table is correct (length of bank account number, start point etc.)

Per an article of Microsoft I found now, once I set all the settings in the country specific row in IBAN Structure to 0, I no longer gets the error message I reported.

Note that even after I remove this validation Dynamics still do some kind of validation on the IBAN number (I assume it is the check digit validation)

Should I conclude that Microsoft "validation" dependent on this "IBAN structure" is broken and I should just always clear that table to avoid issues?

Was this reply helpful? Yes No
Suggested answer

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

Good morning Zvika,

Personally, I often disregard the warning messages but rather double check IBAN and SWIFT with external banking tools that are available. That is because a pure structural check of the number does not guarantee that the IBAN (and SWIFT) are correct. Sometimes banks merge or close divisions and then there are changes in the numbers, which is why I personally prefer to double check things with external banking tools/calculators that are freely available on the web.

... thinking about this makes we wonder whether it might be worth for you creating a PowerApp or something alike that checks the complete validity and existence of the number and the bank before you enter it in D365. I did something similar for the check of tax exempt numbers in the EU in the past and it might be useful to have a similar check for the IBAN/SWIFT numbers?!

Hope this helps.

Cheers,

Ludwig

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Zvika,

We have the exact same problem. Most of my clients ignore the warning or validate the number via third party software. Nonetheless not a good experience as you mentioned.

Was this reply helpful? Yes No