One counterpart has the same normalized reference and exact cent amount.
- Ledger
- L-101 · $120,000.00
- Feed
- F-201 · $120,000.00
- Owner
- Reconciliation reviewer
Retain the paired source IDs as evidence; reviewer still owns close.
Ledger Match / fictional walkthrough
Choose an invented batch and follow the comparison from source rows to matched pairs and human-owned exceptions.
Go to the demoExplore the matching workflow
Switch between two invented batches and inspect the comparison. Each open item retains its source IDs, reason, proposed owner, and next human action.
Reference and exact cents drive the sample results. Reviewers can inspect every pair and exception below.
Ready to replay the fictional matching response.
One counterpart has the same normalized reference and exact cent amount.
Retain the paired source IDs as evidence; reviewer still owns close.
One counterpart has the same normalized reference and exact cent amount.
Retain the paired source IDs as evidence; reviewer still owns close.
Reference and exact cents drive the sample results. Reviewers can inspect every pair and exception below.
Ready to replay the fictional matching response.
One counterpart has the same normalized reference and exact cent amount.
Retain the paired source IDs as evidence; reviewer still owns close.
The reference agrees, but the amounts differ by an exact-cent comparison.
Investigate the source values and document the variance before close.
More than one record shares this reference; an amount match cannot choose the correct counterpart.
Confirm the source records and resolve the duplicate before matching.
No operations-feed row has this reference. Equal amounts under other references are not auto-matched.
Check timing and source completeness; do not create an adjustment from this demo.
This feed row has no ledger reference, even if its amount equals another open item.
Confirm whether the feed item belongs in this period and ledger scope.
All rows are newly written fictional fixtures. Matching rules run when the static site is built; the browser replays their fixed results. No client data, model, live integration, journal entry, or automatic close is involved.