The problem
Bank reconciliation is one of the most manual, error-prone recurring tasks in bookkeeping: matching hundreds of transactions by hand, and hoping two people don't accidentally act on the same transaction at the same time when more than one person has banking access.
How AccountDesq solves it
Statements import as transactions, and a matching-rules engine previews and applies suggested matches automatically based on rules you define. Reconciliation includes positive-pay verification, sweep rules, and watchlist screening. Every transaction-matching action is protected by row-level database locking, so concurrent match/unmatch actions from two users can't corrupt each other, and higher-risk banking actions route through the platform's maker-checker approval workflow rather than executing immediately.
How it works, step by step
Import your statement
Bring in transactions from a bank statement file.
Let matching rules do the work
Rules preview and suggest matches against existing ledger transactions; you review and apply them.
Reconcile with confidence
Positive-pay checks and watchlist screening catch discrepancies beyond a simple balance match.
Approve sensitive actions
Actions that warrant a second set of eyes route through maker-checker approval instead of executing immediately.
Connected to the rest of AccountDesq
Nothing here works in isolation - it posts through the same ledger as everything else.
In practice
A business with two people who have banking access - a bookkeeper and a controller - both open the reconciliation screen the same afternoon. Row-level locking on transaction matching means one person's in-progress match can't be silently overwritten by the other's action at the same moment, and a payment above the approval threshold routes to the controller for sign-off instead of posting immediately.
What this means for your business
- Far less manual line-by-line matching, because the rules engine handles the routine matches.
- Two people with banking access can't accidentally collide on the same transaction.
- Higher-risk banking actions get a second set of eyes automatically, without slowing down routine reconciliation.
Frequently asked questions
Does AccountDesq connect directly to my bank for live transaction feeds?
Not currently - banking works via statement import (CSV) plus a rules-based matching and reconciliation engine, not a live open-banking feed.
What is maker-checker approval in banking?
A workflow where certain banking actions require a second person's approval before they take effect, instead of one person being able to act alone.
Can two people safely work on reconciliation at the same time?
Yes - transaction-matching actions use row-level database locking so concurrent actions from different users can't corrupt each other.