When generating a SEPA file, if there is a lot of payment notice to be generated, the system will generate the SEPA file first which will be deposited on the server and then once the SEPA file generation is done it will automatically go and generate the payment advices.
The issue is if the volume is high for the files to be generated and that this process is running on the client's session, if ever there is a termination of the session before the end of the generation of all the payment advises,
the status of the journal won't be updated while the initial SEPA file would have already been generated, this means that the user can launch the payment generation again without knowing that one SEPA file has already been deposited on the server.
In our case, we would have a duplication of SEPA files on the second run and if by mistake we don't intercept it, then this can lead to a double payment to vendors.
For the moment, what we had to do is to force the use of batch mode on this process in order for it to always run on the server, thus eliminating the risk of any interception during the process.
I think we could optimize this process technically in order to separate the SEPA file generation and the payment advice in order to have a better status management of this process to prevent cases where the user would be able to generate a duplication of SEPA files.