April 24, 2026 · 8 min read
Bank statements for divorce discovery: converting opposing-counsel PDFs without silent errors
How to turn a discovery packet full of scanned bank statements into a reconciled spreadsheet you can stand behind in front of a judge. Practical notes for family-law attorneys and the forensic accountants they work with.
A discovery response in a contested divorce almost always arrives the same way: a PDF with every monthly bank statement for the last 24 months, scanned at 150 dpi from a printout, sometimes with a cover letter and sometimes with a cert-of-service stapled on. You need to sum every deposit, trace every wire, and map every recurring payment against the alleged budget in the financial-disclosure declaration. You have a week. The PDF has no text layer.
Traditionally this has meant one of two paths. Path one: hand the packet to a paralegal who retypes every transaction into Excel, burning 8-10 hours per account. Path two: run the file through a generic OCR tool, import the output, and spend the next month discovering transcription errors during deposition prep — sign flips, missing wire transfers, duplicated lines, and the occasional hallucinated $3,400 ACH that never happened. Neither path produces an exhibit you'd willingly attach to a Request for Admission.
What actually goes wrong with OCR on discovery packets
Discovery packets are scanned, not downloaded from bank portals, which means the usual failure mode of OCR — poor layout reconstruction — compounds with a second failure mode specific to scanned bank statements: the running-balance column gets mis-aligned with the transaction rows. Split-section layouts (Bank of America breaks its transactions across "Deposits," "Withdrawals," and "Checks" blocks, each sorted independently) survive OCR as three disconnected lists that a naive merge gets wrong in subtle ways. Chase's per-day running balance (only the last row of each day shows the balance) routinely gets interpreted as a per-row balance, which then makes every internal consistency check pass falsely.
The result in both cases is a spreadsheet that looks accurate — the dates are right, the descriptions are right, the amounts are even right individually — but the totals don't match the ending balance the bank printed on page one. Which means: there's a transcription error somewhere, and you won't find it without doing the math by hand. Which is the thing the tool was supposed to save you from.
The reconciliation check as a discovery guardrail
The thing every bank statement carries on its first page is a summary block: beginning balance, plus deposits, minus withdrawals, minus fees, equals ending balance. Those five numbers are arithmetically linked to every transaction row in the detail section. If your extracted rows don't sum to ending balance minus beginning balance within a penny, something is wrong. That's the entire premise of pdftoexcel: we run the check on every export, and we show you a Verified badge only when it closes.
For divorce-discovery work specifically, this changes the workflow in a useful way. Instead of a paralegal retyping rows and a second paralegal reviewing them, you upload the discovery packet, get a Verified XLSX per statement month, and spend your review time on what actually matters — identifying the suspicious transfers, the unreported deposits, the timing of withdrawals that preceded the separation. The math is guaranteed; you focus on the narrative.
Handling scanned, password-locked, and multi-account PDFs in one flow
The three PDF variants you actually encounter in discovery are: (1) scanned monthly statements from paper records; (2) digital PDFs downloaded fresh from the bank during discovery negotiation, sometimes password-protected with the last-4 of the account holder's SSN; (3) combined multi-account PDFs where checking, savings, and a credit card all appear in one file. pdftoexcel handles all three automatically — scanned PDFs route through a vision model, password-protected files prompt for the password inline, multi-account PDFs produce one sheet per account in the XLSX export. The reconciliation check runs on each account independently, so a Verified result means every account closed its own math.
Files above 20 MB — common for scanned 24-month archives — upload via Gemini's Files API transport, so you don't have to split them manually. A 200-page combined scan that used to require hand-splitting into 10 chunks now uploads as a single file and comes back with 10 reconciled sheets in the downloadable ZIP.
What you can do with the output — and what you still need to verify
A Verified export tells you the arithmetic is internally consistent with what the bank printed. It does not tell you that the bank's printed summary is accurate, that no statements are missing from the packet, that the account numbers haven't been redacted inconsistently, or that the opposing party hasn't opened accounts the packet doesn't mention. Reconciliation is a necessary condition for a trustworthy export; it isn't the whole trustworthiness check.
The discovery-specific work that still requires human review: matching statement cycles (look for gaps in the months — a missing January 2024 statement may be accidental or may be the month of a big deposit); cross-referencing with the financial-disclosure affidavit (unexplained deposits that don't appear on the W-2 are the single most common finding in contested divorces); and flagging large outbound transfers to unfamiliar accounts (the typical "mattress fund" pattern is four $9,500 cash withdrawals spread across six weeks — specifically under the $10,000 CTR threshold).
A short workflow for family-law attorneys
One version of the workflow we've seen work well: (1) on receipt of the discovery packet, upload every bank-statement PDF immediately, so the reconciliation check runs within minutes and you know on day one which statements extract cleanly and which need a hand-conversion. (2) For any file that comes back unverified, flag it in your discovery-tracking log — this is the signal that the packet page itself may be damaged, cropped, or missing rows, and you may have a Request-for-Correction ready. (3) Download the Verified exports as a single ZIP and hand them to the forensic accountant with the reconciliation certificate already attached. Their job shrinks from "type and reconcile" to "analyse and flag," which is what you're paying them for anyway.