Open finance skill
Which bank transactions do not match the ledger?
Compare two synthetic transaction lists, identify exact matches, and surface unresolved items for human review.
Guided synthetic example
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.
| Source | Reference | Date | Amount |
|---|---|---|---|
| Bank | Deposit B-104 | Jul 8 | $12,480 |
| Ledger | Receipt L-221 | Jul 8 | $12,840 |
Match reference, date, and amount. Flag any amount variance greater than $1.
Needs review
$360 mismatch between the bank deposit and ledger receipt.
At 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.
A Level finance professional validates the source evidence, challenges the AI-assisted analysis, and decides which explanation is supported.
Inspect the deposit support and customer remittance before closing the account.
Financial Systems Field Tests
These are repeatable Level Operating Rule tests using invented records only. They identify a control boundary and a refusal condition. They do not establish vendor behavior or replace review of your actual configuration.
FST-015 · LOR-004 · LOR-006 · LOR-042
Test: Trace one pay run from register through journal, liabilities, cash settlement, bank match, and job-cost allocation.
Expected: A suspected duplicate is classified before any mapping change or deletion.
Refuse when: Missing pay-run evidence, Unclear source authority.
Use this system
MCP preview
run_synthetic_example {"slug":"reconcile-account"}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.
Use it yourself, or bring us the messy part
Tell us where the records stop making sense. We will reply with the first check to run, the records it needs, and the decision that still needs human finance judgment.
Install the free skills yourself