When enabling journal batch approval for Payment Journals, the application behaves in a way that isn't useful for standard operations.
If you export a payment file from the journal, the Boolean "Exported to Payment File" is set to true on the journal line.
This is a change on the lines, and therefore the batch's status becomes 'Pending Approval' again, despite not needing another round of approval.
Please fix this issue so that exporting a payment file doesn't trigger a new round of approvals.
It doesn't make operational sense.
Reproduction steps can be found on this Microsoft Support case: 2501140050003186
Comments
It is a control flaw to allow updates after payment file has been extracted for Bank Payment.In 40 years as auditor, FD & systems expert I have not encountered such a weakness.When payment file is exported, journal should be auto-posted without opportunity for change or requiring additional redundant effort by finance team
Category: Financial Management
I agree that this functionality doesn't make sense in its current format. I can't imagine a scenario where you'd ever need a second authorisation if only thing on the journal that has changed, is 'Exported to Payment File' going from from false to true. Fixing this would be of great benefit to many users I'm sure!
Category: Financial Management
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