Bank statement conversion for audit and forensic review
Audit and forensic work needs the full population, not a sample of what someone typed up. Structured statement data is the difference between testing every transaction and testing the ones that happened to be transcribed.
Convert a statement for review
Drop your PDF statement here
or click to browse · 10MB max · nothing is stored
Completeness before analysis
The first test is arithmetic: opening balance plus the sum of transactions equals closing balance, and each period's closing figure equals the next period's opening figure. A break in that chain is either a missing statement or an altered one, and both matter.
What structured data enables
Once the population is in a sheet, standard procedures become quick:
- Benford analysis on leading digits across the year
- Round-number and just-below-threshold transaction searches
- Duplicate payment detection on amount and payee
- Weekend, holiday and out-of-hours posting patterns
- Counterparty concentration and previously unseen payees
Working across accounts
Fraud rarely lives in one account. Convert each account, tag with an entity and account column, then match debits against credits by date and amount to trace movements between related parties.
Evidence handling
The converted file is a working paper. The original PDF, with its metadata and provenance, is the evidence. Keep both, and record the verification check that ties one to the other.
Frequently asked questions
+Is the output suitable as audit evidence?
It is a working paper. The source statement remains the evidence and should be retained with it.
+Can it detect an altered statement?
It surfaces arithmetic inconsistencies, such as transactions that do not sum to the printed balance, which are strong indicators worth investigating.
+Does it handle very large statements?
Files are capped at 10MB. Long statements are better split into shorter periods, which also keeps each result independently verifiable.