30

Dynamic Transaction Code for EFT exports

on 6/30/2021 12:29:38 PM
Currently the transaction code of "22" is hard coded in the data definition for EFT exports and there is nowhere on the vendor bank account to state what type of account it is (checking, savings, debit, etc.). It would be great to be able to note what type of bank account it is on the vendor bank card and have that drive the transaction code on the data definition.
Category: Purchasing
STATUS DETAILS
Needs Votes
Ideas Administrator

Business Central Team (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

RE: Dynamic Transaction Code for EFT exports

Angel Walker on 8/22/2023 2:19:24 PM

I feel that this is a very important feature to have, as we have many customers who are using a savings account and every week we have to manually update those files. And if we forget or make an error, it does cause issue's. Please make this a required field on the vendor card. This was an option on Microsoft GP, so I am surprised it isn't on Microsoft BC.

Category: Purchasing

RE: Dynamic Transaction Code for EFT exports

Tressa Dorn on 11/2/2022 2:37:15 PM

This would be a huge help for us, as we have quite a few personal reimbursments and we have quite a few people that put it in their savings accounts, and we get rejection notices from their bank becuase the "Transaction Code" is incorrect. This is a required field per the NACHA File format based on the type of account being deposited to and I don't believe that we should have to alter the file every time to get this correct.

Category: Purchasing