Microsoft Dynamics 365
on 5/6/2019 11:32:00 AM
Thank you for your feedback. This is a great suggestion! We will consider this in our roadmap.
Good afternoon :)
We have just gone live with D365 Finance and Operations and we are experiencing the same issue with native vendor bank details workflow only working on new bank details configured in form VendTable control name TabPayment.
Any follow-on changes made to form VendBankAccounts control name TabGeneral bypass workflow completely and there is no native workflow to control changes - it is free to edit and save.
To access form VendBankAccounts control name TabGeneral
1. Go to Modules/Purchase ledger/Suppliers/All Suppliers
2. Open any supplier account, then from the Supplier top menu banner select Setup>Bank accounts
3. This opens form VendBankAccounts
4. Any bank account, routing number or other changes made here completely bypass workflow
The business impact is:
5. The form cannot be locked down to e.g. senior Finance managers since it creates a segregation of duty issue - same people making changes would be approving other workflow changes.
6. Junior staff members entering the bank details changes could make changes that would go unnoticed until a vendor queries payment - creates opportunity for fraud.
This requires a manual workaround to validate all bank details outside D365 before approving supplier payment proposals.
Do we have any update on bringing in the vendor bank account fields workflow?
This is a very common scenario for our customers as well. We are looking forward to when it will be released.
I agree this will be a very useful feature, audit log also helps.
Vendor bank account changes approval workflow is a great feature that helps many customers.
Sorry, my previous post was incorrectly made to this idea. This applied to vendor bank account workflow.
This has been introduced in version 8.1 and is a very nice feature. It would be great if was made possible to add all vendor fields to be tracked by workflow, not a limited set. Another improvement would be if the workflow kicks in directly when creating a new customer or vendor. Currently (version 8.1) it only works on change.
I also agree, since for some reason I can't vote for the idea I will just say it in a comment. This should work as an addition to the vendor change workflow that has been introduced in version 8.1.
Financial** Sorry but I cannot edit my last post.. that be handy too :)
please see below the flaws, if you cannot fix them then please a workflow for vendor add/ edit / bank edits. This is a KEY IT / Finicla Risk control - this could limit D365 being installed unless the client spends extra for something custom which wouldn't be ideal. We need to reduce the amount of customization to allow seamless upgrade and Cloud experiences :)
We do have the same issue. The proposed vendor changes workflow that has been introduced only covers changing the default bank account on the vendor master sheet but it doesn't pick up when details are changed on an existing bank account or a new bank account that isn't the default one is being added.
We found the following ways to bypass it:
Ways to bypass it:
1.) Change default bank account on supplier account, then change bank details after workflow has been approved
2.) Have a bank account on the supplier that defaults into transaction approved by workflow (PO header, vendor invoice journal line, general journal line) and change it to another, unapproved bank account on the transaction before posting
3.) Have a bank account on the supplier that defaults into transaction approved by workflow (PO header, vendor invoice journal line, general journal line) and change it to another, unapproved bank account on the open supplier transaction
4.) Change the supplier bank account on the payment journal/payment proposal to an unapproved bank account record on the same supplier
Therefore the need to provide a control for creditor bank accounts continues to be addressed by cumbersome workarounds only.