34
Using the standard payment journal approval workflow there is currently a need for duplicate approval each time specifically when working with exporting payment files.
1) When the journal has been created (it has to be approved before it can be exported)
2) When the journal has been exported (this adds additional record restrictions even though the only thing has changed is that the file has been exported)
Ideally only 1 approval should be required, unless of course the user makes subsequent changes to the journal, other than just exporting the BACS file.
1) When the journal has been created (it has to be approved before it can be exported)
2) When the journal has been exported (this adds additional record restrictions even though the only thing has changed is that the file has been exported)
Ideally only 1 approval should be required, unless of course the user makes subsequent changes to the journal, other than just exporting the BACS file.
STATUS DETAILS
Needs Votes
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