1. Introduction
Welcome to the Proposed Auto-Matching user guide. This feature allows users to define matching passes, each resulting in either a full match or a suggested/proposed match. The matching engine operates based on the defined passes, and users can subsequently approve or reject proposed matches, providing flexibility and control over the matching process.
Use this feature to set specific match rules for potential matches as this will help improve the reconciler's experience in locating potential matches manually and remove the time and effort. If users are constantly approving the same pass rules this can potentially be moved to full automatch in the future thus further reducing the time spent clearing breaks.
2. Getting Started
2.1 Prerequisites
Ensure that you have the necessary access rights to configure matching passes and review proposed matches and the ability to create matches if you wish to approve them.
2.2 Defining Matching Passes
- Log in to the system with your administrative credentials.
- Navigate to "Multi-pass" of the particular process you wish to configure these on.
- Define each matching pass, specifying whether it results in a full match or a proposed match with the simple switch of a button.
3. Matching Engine Operation
The matching engine processes transactions based on the defined passes:
- Full Match (As per Current Capability)
- Transactions are fully matched according to the existing matching capabilities.
- Write-offs and other relevant actions are executed.
- Proposed Match
- Transactions that you wish for users to review before the match rule is complete will go to the pending change queue and be greyed out in the results view.
- Users can use the action bar to approve or reject each proposed match.
4. Approving or rejecting
- Reviewing, approving or rejecting matches in the Pending Changes queue
- Navigate to the "Pending change”queue section to view, approve or reject transactions with suggested matches.
- Reviewing, approving or rejecting matches in the results UI
- Users can review details of each suggested match in the workflow buckets only once a pending match has been selected using the tick selection on the left of the screen
- Approve the match if it meets the criteria or reject it if necessary.
- Users can use the action bar to approve or reject
Option 1 - Pending change page
The Pending change page allows you to view only the pending approval requests. Including those that were approved or rejected.
Option 2 - New columns in results view
The ability to filter through ‘Pending change ID’ and ‘Change type’ allows you to approve or reject actions more easily.
5. Pass Re-validation
- Re-validation Process
- Each matching run re-validates transactions in the Proposed Match queue.
- Transactions may move from the Proposed matched queue to Auto- Match if new data arrives and fits a higher priority pass.
- Rejected matches by users will automatically be included in future runs in case there is a better match rule that applies.
6. Troubleshooting
6.1 Common Issues
- Issue: Transactions not moving from Auto-match to Full Match.
- Solution: Check the matching pass priorities and ensure that the relevant data has been updated.
- Issue: Unable to access the Proposed Match queue.
- Solution: Confirm that user permissions include access to the Proposed Match queue.
- Issue: Proposed match option in multi-pass settings “greyed out”
- Solution: Find matches within roll-ups and "Generate proposed matches" can not be both enabled at the same time in the process.
7. Conclusion
By following this user guide, users can effectively configure and utilise the Proposed Auto-Matching feature, providing a flexible and controlled approach to the matching process and significantly increase the automation of managing exceptions.