Reconciliation
Match bank transactions to expected cash flows with auto-matching, manual matching, and variance tracking.
Last updated March 2, 2026
Overview
Reconciliation in TreasuryPath is the process of matching actual bank transactions to your expected cash flows. This closes the loop between what you forecasted and what actually happened, giving you visibility into forecast accuracy, timing variances, and unplanned cash movements.
How Reconciliation Works
- Expected cash flows are created through the forecasting module (manually or from recurring templates)
- Bank transactions flow in from connected accounts (via Plaid, API, or manual entry)
- TreasuryPath attempts to match transactions to expected cash flows automatically
- Unmatched items surface for manual review
- You confirm, reject, or manually match remaining items
Match Types
Each reconciliation match is classified by how it was created:
| Match Type | Description |
|---|---|
| Auto | TreasuryPath automatically matched the transaction to an expected cash flow based on amount, date, and other criteria |
| Suggestion | The system identified a likely match but wants your confirmation before finalizing |
| Manual | You manually paired a transaction with an expected cash flow |
| Force Close | You closed an expected cash flow without a matching transaction (e.g., a forecasted flow that will not occur) |
| Unplanned | A bank transaction that does not correspond to any expected cash flow (an unexpected payment or receipt) |
Match Statuses
Each match goes through a review workflow:
| Status | What it means |
|---|---|
| Pending Review | The match has been created (auto or suggestion) and is awaiting your confirmation |
| Confirmed | You have confirmed the match is correct |
| Rejected | You have rejected the match as incorrect |
Expected Cash Flow Reconciliation Status
Each expected cash flow tracks its own reconciliation progress:
| Status | What it means |
|---|---|
| Open | No matches have been confirmed against this expected cash flow |
| Partial | Some portion of the expected amount has been matched, but the full amount remains outstanding |
| Fully Matched | The entire expected amount has been matched to confirmed transactions |
Match Sources
TreasuryPath uses multiple strategies to find matches. Each match records its source:
| Source | Description |
|---|---|
| Frozen History | Matched from a frozen (locked) forecast scenario |
| Live Primary | Matched from the live primary forecast scenario |
| Raw Base | Matched from base expected cash flow data |
| Ghost Rule | Generated by automated matching rules for items that should exist but were not explicitly forecasted |
| Manual | Created manually by a user |
| Global Search | Found by searching across all expected cash flows |
Immunity Locking
When an expected cash flow is fully matched and confirmed, it becomes immunity locked. This means:
- The expected cash flow cannot be modified or deleted
- It is excluded from future matching attempts
- It serves as a verified historical record
This prevents accidental changes to reconciled data and maintains audit integrity.
Variance Tracking
Each reconciliation match records variances between what was expected and what actually occurred:
- Variance days - The difference in days between the expected date and the actual transaction date. Positive values mean the transaction occurred later than expected.
- Variance amount - The difference between the expected amount and the matched transaction amount.
These variances feed into forecast accuracy metrics, helping you improve future forecasts.
Bulk Operations
For efficiency, TreasuryPath supports bulk reconciliation actions:
- Bulk Confirm - Confirm multiple pending matches at once
- Bulk Reject - Reject multiple pending matches at once
This is useful during periodic reconciliation reviews when you need to process many items quickly.
Frequently Asked Questions
What happens to unmatched transactions?
Unmatched bank transactions appear in the reconciliation queue as potential unplanned items. You can either match them manually to an existing expected cash flow or mark them as unplanned cash movements.
Can I undo a confirmed match?
Rejecting a previously confirmed match is possible as long as the expected cash flow has not been immunity locked as part of a broader reconciliation close. Check with your admin for your company’s reconciliation policies.
How does auto-matching work?
Auto-matching uses amount, date, counterparty, and account information to find likely pairs between transactions and expected cash flows. Matches with high confidence are auto-confirmed; lower-confidence matches are surfaced as suggestions for your review.
What is a ghost item?
Ghost items are expected cash flows generated by matching rules when the system detects a transaction that should have had a corresponding forecast entry. They are created with the origin type “materialized_ghost” to distinguish them from manually created or synced expected cash flows.
How does reconciliation connect to forecasting?
Reconciliation closes the feedback loop on your forecast. By matching actual transactions to expected cash flows, you can measure forecast accuracy and identify systematic biases (e.g., consistently overestimating revenue or underestimating payment timing).