Most bank statement files uploaded to Chatter, fetched via Bank Feed, or automatically polled from file servers, are extracted by ProcessingHub Jobs and inserted as a Transaction Set record with one or more Transaction records.
This is a multi-step reconciliation process with two main stages:
- File extraction and matching on ProcessingHub
- ProcessingHub validates and extracts file content.
- Automated matching is executed where applicable.
- Reconciliation through Guided Matching
- Guided Matching rules may be triggered on Transaction records to improve matching rates and further enrich Salesforce data.
If extraction and record creation complete successfully, you’ll see both the Transaction Set and related Transaction records. However, if some Transactions are in a Failed state, this indicates an issue that requires further investigation.
The troubleshooting steps depend on whether the issue occurred during the extraction job or within the Transaction records themselves.
You uploaded a file to the File Exchange Chatter Group, expecting to see Transactions created under a parent Transaction Set. However, after some time, no transactions appear.
In this case, you should check the extraction process in ProcessingHub Manager.
- Open ProcessingHub Manager and review the jobs related to file extraction. Check if any other failed jobs are blocking queued extract jobs.
- If the extraction task itself failed, the error message usually indicates which data or element in the file caused the problem.
- Some tasks execute queries or insert operations as data load jobs. If you see an error in one of these steps, expand the details to review the error message.
- If the issue is clear and you can take corrective action (e.g., update data), go ahead and fix it.
- If not, an admin user should review the error details and handle the failure.
- For admins: Some extract operations are handled as data load jobs. If an error refers to a Bulk Data Load Job, use the Bulk Data Load Job ID link to navigate directly to Salesforce Setup > Bulk Data Load Jobs for deeper investigation and troubleshooting.
Once a file is extracted into a transaction set with transactions, processing of individual Transactions may fail.
To troubleshoot failed transactions:
- From the Transactions Set record, you can see the full list of related Transaction records. If a transaction has the status Failed.
- Check the following fields on the failed record for further details:
- Last Status Reason
- Guided Matching Error
- Guided Matching Log
- Check the Guided Matching Progress component for additional error information. Below is a summary of common reconciliation issues and resolutions.
| Problem | Resolution |
|---|---|
| Exceeding Governor Limits During Custom Guided Matching Queries | If you see an error such as “Too many query rows: 50001,” your custom Query Rule in the Guided Matching Setup is returning too many records. Refine your query by adding additional filters and ensure the most restrictive filter appears first in the WHERE clause |
| Governor Limits from High-Volume Batches | When Guided Matching runs on a large batch of transactions with many active rules, the process can hit governor limits. Reduce the Job size in the Guided Matching Setup settings to process smaller batches. |
| Inactive Guided Matching Setup for the Target | If the Guided Matching Progress component shows no visible rules and no actions occur, the related Guided Matching Setup may be inactive or not correctly linked. |
|
| Validation Rules Blocking Record Creation or Updates | A validation rule on a related object might block Guided Matching from creating or updating records. Review the data being processed and ensure it complies with your custom validation rules. |
| Incorrect Rule Order in Guided Matching Setup | If rules are not executed in a logical sequence, processing may fail. Review and reorder the Guided Matching Rules to ensure dependencies and priorities are handled correctly. |
After resolving the root cause of a failed transaction, you can restart reconciliation in a few ways:
- Click Retry All Rules in the Guided Matching Progress component on the Transaction record.
- Click Retry Unmatched Transactions on the Transaction Set Progress component.
- Perform a bulk update on the Transaction records with the following field values:
- Start Guided Matching = TRUE
- Guided Matching Installment Processed = FALSE
- Guided Matching Nr of Rules Processed = 0