Finance / Reconciliation Live
Bank Transaction Matching
Match bank transactions to ledger entries and leave the genuinely unmatched genuinely unmatched — no forcing, no plugging the difference to make the reconciliation close.
- Runs on a schedule
- ~7 credits per run
- v1.0.0
What does Bank Transaction Matching do?
Bank Transaction Matching is a production AI agent in the finance section of the Leverge agent store, built for the reconciliation process. Match bank transactions to ledger entries and leave the genuinely unmatched genuinely unmatched — no forcing, no plugging the difference to make the reconciliation close. It runs on a schedule (every weekday at 08:00), works through 4 steps and returns 4 outputs, including does it reconcile.
What it needs
-
Bank statement
-
Ledger entries
-
Matching rules
What it does
- Reading the bank statement
- Reading the ledger
- Matching transactions
- Writing the reconciliation note
What you get back
- Does it reconcile
- Reconciliation note
- Unmatched both ways
- Bank line to ledger entry
After each run it asks: “Does this reconciliation hold?”
When it runs
Runs on a schedule — Every weekday at 08:00.
Oversight
Runs under scoped, least-privilege credentials with every action written to an audit log. Anything that moves money, alters a contract or reaches a customer requires human approval before it executes.
Reconciliation
Other agents in reconciliation
Close, reconciliation, payables and treasury, with an audit trail
-
Transaction Classification
Classify bank transactions to the right account and cash flow category from what the narrative actually supports — and route the ambiguous ones to a person instead of defaulting them to sundry.
-
Account Risk Classification
Rank balance sheet accounts by how much could be wrong and nobody would notice — driven by reconciliation quality and manual-entry exposure, not by size alone.
-
Annual Plan Review
Review a draft annual plan before it is signed off — whether the growth is built on named actions or on a percentage, and which assumptions the whole plan depends on.
-
Audit Preparation
Work through the auditor's request list before they arrive — what exists, what does not, and which items will turn into a finding rather than a question.
-
Budget Variance Analysis
Explain variance against budget by cause rather than by size — separating timing from overspend, and price from volume, so the explanations mean something.
-
Capital Expenditure Monitoring
Track capital projects against their approved case — spend, stage and the benefit that justified them, including the projects quietly costing more than the approval allowed.
Next Step
Deploy Bank Transaction Matching, or adapt it
It runs as-is against the inputs above. Most deployments diverge — a different source system, a different tolerance, a different approval path. A 30-minute technical call establishes which.