How are you sending the payment file initially for the FTP process? Is the payment file saved on server first and moved from there? This is typically how we’d suggest setting it up to avoid anyone having access to the file. 

Because when repeat media output is performed, IFS doesn’t send it to the server, the file gets saved in the downloads folder of the user performing the action.

Hi Ieva

Yes we have done a customisation to the repeat media output job, the file is sent to the database ftp server and not downloaded to users local machine. I have spoken to our bank and they have informed me that they have a process to check for duplicate files based on number of transactions and total of debits and credits so that should prevent duplicate payments being made to our suppliers!!!

Cheers

GT

Hi, 

Typically, IFS creates the media file at crate payment order.   We “only” would use the repeat media file when we have a true payment issue / most commonly when testing.   Given this is a customization and maybe not using IFS in a typical way, we are seeing unanticipated issues.  Can you create an event at repeat media - that may block this if some data condition is true?  The other thing to consider is that after the payment process is completed - you can no longer use the same option.  

Best regards