Sometimes incorrect or irrelevant transactions appear in the source data, cluttering unmatched results and making it more difficult to focus on genuine breaks. They can add noise to investigations and proofing.
With this new functionality, you now have the ability to manage them directly:
- Close transactions you don’t need – Move unwanted unmatched transactions into a new workflow bucket called “Closed.” This keeps your results clean and ensures proofing only reflects what matters, as the transaction will no longer be deemed unreconciled.
- Re-open if needed – If you’ve closed a transaction by mistake, you can easily re-include it at any time.
- Automate with rules – Apply the “Close” action manually or automate it through workflow rules after pre-processing and matching. Just update your Exceptions workflow settings to enable it.
This new workflow action helps you reduce noise, streamline investigations, and stay focused on the transactions that actually matter.
Key features
The new functionality includes the following key features:
- New workflow actions: You can now “Close” and “Open” transactions
- New workflow state: Closed transactions will appear under a separate bucket called “Closed”
- New Exceptions workflow setting: This will allow you to enable/disable the functionality at a process level
Access and permissions
The new workflow action doesn’t need any separate permissions. It can be used by anyone with “Viewer” and with an “Operator” or “Investigator” role.
If you have any further questions or encounter issues, please submit a support ticket or review the release notes from September 2025.