AuditbenchFor accounting and audit firms
Reconstruct the year from the bank statements.
Auditbench reads a client’s bank statements, rebuilds what actually happened, classifies every line with a reason you can defend, and shows you where the client’s own ledger disagrees. Built for the engagements where the records are incomplete.
Nigerian banks first — naira, stamp duty, NIP and COT charges recognised out of the box — with multi-currency engagements supported from the first migration.
March statement — 248 lines
Balance chain closed14 MarNIP/ADEBAYO VENTURES/INV-2291Trade receipts1,450,000.00
0.96
14 MarCOT CHARGEBank charges3,625.00
0.99
15 MarPOS TOTAL ENERGIES IKEJAMotor running42,000.00
0.81
16 MarTRF TO SUNDRY / NO REFERENCEUnclassified870,000.00
0.34
One line below threshold — held for review, not guessed
Illustrative rows. Confidence and category come from the engine; anything under the threshold waits for a person.
What it does
Every figure traces back to a line on a statement.
Statements in, transactions out
PDF, Excel or CSV. The running balance has to close and the declared totals have to agree before a single row is saved, so a statement that does not reconcile leaves no trace beyond the error you see. Re-importing the same file adds nothing.
Classification you can defend
Every classification carries the reason it was made — which rule or keyword fired, and how confident it was. Nothing applies itself below the threshold; those go to a person. A correction teaches the next statement, at that client only.
Ledger validation
Import the client's general ledger and see where it disagrees: movements the ledger never recorded, journals with no bank behind them, amounts that differ, duplicates, and timing differences told apart from genuine gaps.
Working papers, not exports
Excel and PDF schedules that name the client, the period and who prepared them, list what is still outstanding rather than omitting it, and carry the figures as numbers a column can total.
How it is built
The parts an auditor would ask about.
Evidence first
Each transaction links to the statement it came from, and the statement records a checksum of its own bytes. If the file behind a figure is ever replaced, the figure stops being trusted rather than quietly changing.
An append-only trail
Every change records who made it and what the row looked like before. Updates and deletes to the trail are refused by the database itself, not by convention. Retention and erasure go through one attributed path that records itself.
Clients stay separate
A pattern learned at one client applies there and nowhere else until someone senior promotes it deliberately. Between firms, isolation is structural: the database has no key that would let one firm's row reference another's.
Where it is
Bank statement analysis and ledger validation work today.
Accounts preparation and financial statements are the next two releases. Scanned statements are refused rather than guessed at — ask the client for the file their bank issues. We would rather tell you that now than after you have signed something.
Talk to usAccounts are created by your firm; there is no self-service sign-up.