Preventing Duplicate Bank Transactions in Transaction Matching
We are currently using ARCS transaction matching for matching cash transactions in the GL to bank statements and are using EPM Automate to upload and import bank files daily using the standard BAI & MT940 adapters in Data Management. Occasionally we are seeing duplicated bank transactions/bank statement files imported into ARCS due to various upstream issues. While these duplicate transactions can be deleted, it becomes tedious to find and delete them one-by-one, especially when larger statements are duplicated that contain multiple accounts and thousands of transactions.
This duplication doesn't cause issues in other systems receiving these same bank statements as those systems have built-in or customized functionality to identify and ignore duplicate bank transactions. We have been able to implement a custom report in ARCS to identify potentially duplicated transactions, however we are looking for something more robust that can prevent these transactions from importing. While I know the root cause lies in upstream processes, I'm hoping that ARCS may have some capability to prevent these duplicated transactions from being imported through either Data Management, ARCS itself, or some other custom approach.