The problem
Manually matching every bank transaction against your books line by line is slow and error-prone, and gets riskier when more than one person has banking access - two people acting on the same transaction at once can silently corrupt the reconciliation.
How AccountDesq solves it
Statement import brings transactions in; a matching-rules engine previews and applies suggested matches based on rules you define, cutting down the manual matching load. Positive-pay checks and watchlist screening catch discrepancies a simple balance match would miss. Row-level database locking on transaction-matching actions prevents two users from colliding on the same transaction, and higher-risk actions route through maker-checker approval instead of executing immediately.
How it works, step by step
Import the statement
Bring in bank transactions from a statement file.
Apply rules-based matches
The matching engine suggests and applies matches automatically.
Catch discrepancies
Positive-pay and watchlist screening flag what a simple balance check would miss.
Approve sensitive actions
Higher-risk banking actions require a second person's sign-off.
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 a bookkeeper and a controller both handling banking imports a large batch of transactions after a busy week. The matching engine auto-applies the routine matches, leaving only the genuinely ambiguous ones for manual review, and row-level locking means the bookkeeper and controller can't accidentally overwrite each other's work on the same transaction.
What this means for your business
- Far less manual line-by-line matching, since routine matches are handled automatically.
- Discrepancy detection beyond a simple balance check.
- Safe for more than one person to reconcile at once, without risking data corruption.
Frequently asked questions
Does AccountDesq connect live to my bank?
Not currently - reconciliation works from imported bank statements plus a rules-based matching engine, not a live open-banking feed.
What is maker-checker approval in reconciliation?
Certain banking actions require a second person's approval before taking effect, adding a safety check beyond a single user acting alone.