Many clients have issue with the ACH not being able to void at the point where you have Generated the .txt file. However, after reviewing and thinking about Security I think that is valid. So here is what I would like to see as the process to make this functionality easier.
Current Process
1. When you choose Bank/Export it assigns and sends if configured the Remittance Advice
2. When you choose Actions/Functions/Generate EFT File/Generate EFT file it creates the .txt file
3. Then you post the payment journal
4. If you have already created the .txt file and find an error you must continue to post the journal and then go to the bank account and do a void and unapply. Then redo the ACH run. This sends a second remittance advice
Better Process
1. When you choose Bank/Export assign the remittance advice but do not send the remittance advice at this time. Hold it in a buffer
2. When you choose Generate EFT file and create the file somehow grouping these with some code in case there is a problem. Also train the client to NOT put the .txt file up on the bank site until the payment journal has been posted in case there is an issue.
3. If you find there is a problem with the .txt file after Generate, the user will continue and post the journal. Then with the group code the user will go to the Bank Account Card and do the Void and Unapply using that group code so it will void and unapply the entire batch run rather than doing it one by one
4. If there was a problem with the .txt file when you post the journal prompt to ask if you want to send the Remittance advice. No will not send them. Yes will send them all as it does now. This would eliminate the customer getting multiple remittance advice emails if there was an issue and eliminate the vendor remittance advice getting mailed too soon in the process. Thanks