Guided Matching is an essential part of the bank statement reconciliation process. With Guided Matching, reconciliation can be improved in many ways, including:
- High automated matching percentage
- Reduced time and errors per transaction review through guided manual review
- Use all data from bank statement files to improve automation and create personalized customer journeys
- Insight into how bank statement files are enriched, processed and matched to improve payment processing on Salesforce
- Reduced time to process bank statement files
The Guided Matching solution consists of the following components:
- Salesforce native rule engine that automatically processes each transaction record extracted from a bank statement file
- Guided manual review that follows the same rules as the automated rule processing
- Various general purpose and FinDock-specific rule types
- Easy setup with automatic rule execution order calculation
- Option to define a rule set per target
- Multi-agent support
Throughout our documentation, we use the following key terms:
- Matching: Finding the corresponding installment for a transaction.
- Guided Review: A transaction is in guided review if a user/agent needs to perform a manual action to continue the process.
- Enrichment: Adding more data to the Transaction records using guided matching rules.
If you are using the Enhanced Online Experience with FinDock's Payment API v2, Guided Matching takes on a broader role in handling inbound payment data. For further information, please see Processing and reconciling online payments
High-level technical reconciliation flow
The overall technical flow of reconciliation, including guided matching, consists of five main steps as illustrated below.
- The flow is started by placing a bank statement file (CAMT.053, CAMT.054, MT940, CODA, etc.) in the Chatter group designated for file exchange.
- ProcessingHub picks up the file from Chatter and extracts all transaction sets and transactions from the file. It pushes the extracted transaction sets and transactions as records into Transaction Set and Transaction.
- ProcessingHub does a first round of matching where it tries to find the corresponding installment based on payment reference or end-to-end-Id. If it finds a match, the transaction record status is set to ‘Matched.’ If no match is found, the status is set to ‘No Match.’
- Update transaction records triggers Guided Matching.
- Guided matching completes the matching work in the reconciliation process.
Central role of the transaction record
Guided Matching revolves around the transaction record. It processes each transaction record according to the following rules.
Enrichment adds more data to the transaction records using guided matching rules. The type of the returned field must be the same as the transaction field. For instance, you cannot enrich a currency field with a text field. The main enrichment methods are:
- Extract a value from another Transaction field using regular expression matching. The most common fields to use this on are: Payment Reference and Raw XML Entry which contains the full raw CAMT, MT940, etc. content for that specific transaction.
- Example: Extract campaign code from payment reference.
- Perform a query against the Salesforce database using another Transaction field as the query parameter.
- Example: Query Campaign by the just extracted campaign code.
- Add a constant value to a transaction field.
- Example: If no campaign code was, use campaign code “DEFAULT_CAMPAIGN” as default.
Matching is a special form of enrichment. The goal is to find the correct Contact, Payment Profile and Installment related to the Transaction record. This information is crucial in processing the transaction and related installment.
After the transaction is fully enriched, all that data can be used to modify Salesforce data by creating or updating records.
The last step is always to process an Installment. In this step, FinDock uses internal business logic to close transactions, move installments to a new status and create payments.
Sometimes automatic matching fails and manual review is needed. In this case, the transaction is put into guided matching. Using the Guided Review component on the transaction detail page, a user can provide the required input and trigger the automated process by clicking Retry & Continue.