20
It would be great if the Bank Code Field in the Purchase Invoice could be filled automatically when the QR-IBAN or IBAN from the QR-Bill file matches the IBAN/QR-IBAN in the Vendor Bank Account, i.e, when there is a match, the field could be filled automatically.

This way the user will save time when paying these invoices, for example, and not having to manually enter the Vendor Bank Account in the Payment Journal, which can be filled automatically when using the Suggest Vendor Payments.

Thank you.
STATUS DETAILS
Needs Votes
Ideas Administrator

Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team

Comments

L

Part 3 due to character limitation:Problem 2 - it is not user friendlyAs Laeticia Cunah already mentioned, it's absolutely a waste of time if user has to set it manually. Additionally, it would prevent user errors due to selecting wrong bank code manually. In my opinion a modern ERP-System should support users instead burdening additional work. SolutionAs already mentioned Dynamics should try to set bank code automatically in pruchase invoice if a QR-Bill is scanned and therefore IBAN is known. If on vendor a corresponding bank code with that specific IBAN is missing, bank code should be empty and an info message should be shown. Preferred bank account should only be used if there is no IBAN provided!

Category: Geographies and Localization

L

Part 2 due to characater limitation:Problem 1 - Preferred bank account code is always usedWe can set a preferred bank account code on a vendor. When we scan a QR-Bill, IBAN is set correctly in purchase invoice. But instead to set the correct corresponding bank code, it sets the preferred bank account code. Effect: user does not recognize a wrong bank code is used and payment is done on wrong IBAN. This has already led to problems with vendors. As i mentioned above - with this functionality Dynamics supports/produces actively failures! To be honest, in my opinion this problem is more a bug than anything else and it would be easely fixable when it would automatically set corresponding bank code or throw an info message if no corresponding bank account code is defined on vendor. Futhermore, i do not understand why it should work when using "purchasing entry journal" - but it does not when using "purchase invoice". It's somehow inconsistent functionality inside Dynamics itself. I would really appreciate if there is a clarification about that behavior. Do you know about that problem?

Category: Geographies and Localization

L

Part 1 due do characate limitations:IntroductionOur Version: CH Business Central 24.3 (Plattform 24.0.23002.0 + Anwendung 24.3.21374.21517)I found this post because we have same issue. Futhermore, it leads to failures in accounting (i will explain it more detail below). In my opinion an ERP-System should be interested to not implement functionality what leads to failures in accounting. To be said: mabye our system is somehow wrong configured, but our implementation partner gave us the information that this functionality is not supported. Here is what we got as answer from our implementation partner (translated from german to english):We have analyzed the situation. The standard solution is that only the preferred bank code is always taken into account on the purchase invoice screen. If none preferred bank account code is stored for the vendor, it is not filled and the invoice is posted without a bank code if it is not entered manually.However, if you enter the invoice in the purchase entry journal, the bank details from the QR code are taken into account, regardless of what is in the preferred bank account code.As you see, he told us we should use "Purchasing entry journal" (i dont know the correct name of it in english) instead, because there it seems to work that Dynamics automatically sets correct bank code. Due to the fact (regarding our implementation partner) "purchasing entry journal" does not support an approval process, we can not use that way.

Category: Geographies and Localization