Open finance skill
Bank-to-ledger reconciliation
Which bank transactions do not match the ledger?
Compare two synthetic transaction lists, identify exact matches, and surface unresolved items for human review.
Inputs
- ✓Bank transactions
- ✓Ledger transactions
- ✓Date and amount tolerances
Outputs
- ✓Matched transactions
- ✓Unmatched bank items
- ✓Unmatched ledger items
Checks performed
- ✓Exact reference match
- ✓Amount and date tolerance match
- ✓Duplicate candidate warning
Guided synthetic example
See the check from input to decision
A customer payment appears in the bank, but the amount recorded in the ledger is different.
This is the operating model we use at Level. The percentages are estimated shares of the work in a typical review. Actual effort varies with data quality, complexity, and the issue found.
Start with the source records
About 15% of work| Source | Reference | Date | Amount |
|---|---|---|---|
| Bank | Deposit B-104 | Jul 8 | $12,480 |
| Ledger | Receipt L-221 | Jul 8 | $12,840 |
Run the deterministic check
About 20% of workMatch reference, date, and amount. Flag any amount variance greater than $1.
Surface the flagged result
About 10% of workNeeds review
$360 mismatch between the bank deposit and ledger receipt.
Use recorded finance judgment to analyze possible reasons
About 25% of workAt Level, we record the review logic, known explanations, and questions our finance professionals use in this situation. AI applies that documented human judgment to organize the most plausible reasons, without pretending it knows which reason is true.
Possible reasons to investigate
The difference could be a posting error, processing fee, partial payment, or a transposed amount. The check cannot choose among them.
Make the final human judgment
About 20% of workA Level finance professional validates the source evidence, challenges the AI-assisted analysis, and decides which explanation is supported.
Make the operating decision
About 10% of workInspect the deposit support and customer remittance before closing the account.
Use this system
Start with the example, then inspect the structure
- Download the invented input and expected output.
- Replace one field at a time with a safe test value.
- Compare the result with the expected structure.
- Have a finance professional review every exception before acting.
MCP preview
run_synthetic_example {"slug":"reconcile-account"}Human review is part of the system
This check organizes evidence and surfaces exceptions. A person with finance domain expertise still needs to interpret the result, validate the source records, and discuss the operating decision.
Open source does not mean open client data. We publish reusable finance tools, checks, templates, and playbooks. Client records, workpapers, credentials, communications, and private configurations remain confidential.