Duplicate Transactions in Transaction Matching Module
SummaryIs there a way to avoid duplicate transactions loading into the system
Presently, if the transactions are already loaded for the day, than in case there is an unintentional run of the process, the transactions are reloaded and duplicate transactions also start appearing in the system. Resulting which there is an increase in number of duplicate unmatched transactions in the system.
Can we avoid loading of duplicate unmatched transactions into the application ?