Parsing bank-statement PDFs in the browser: text layer, tables, and a balance check

Description and use

Step‑by‑step process for extracting data from bank statement PDFs that ensures accurate balances and preserves confidentiality by checking for a text layer, using table‑aware extractors, and row‑by‑row reconciliation.

Problem

Generic PDF‑to‑Excel converters produce incorrect ledgers when processing bank statements, causing column drift, repeated headers, wrapped descriptions, and balance mismatches.

Outcome

The workflow yields accurate, reconciled bank statement spreadsheets while keeping sensitive data local and avoiding OCR pitfalls.

Workflow

• Confirm the PDF has a real text layer by selecting a transaction line; if not, OCR is required.
• If a text layer exists, use a table‑aware extractor such as Excel’s "Get Data → From PDF" or Tabula to export the transaction table.
• Prefer the bank’s native CSV/Excel export when available; use the PDF route only if no spreadsheet is provided.
• Reconcile each row by walking the ledger: previous_balance ± amount == new_balance; flag any mismatches.
• Keep the PDF on the device and perform parsing client‑side (e.g., with pdf.js) to avoid uploading sensitive data.

Evidence

Generic "PDF to Excel" converters are great until you feed them a bank statement. Columns drift, page headers repeat mid-table, wrapped descriptions become extra rows, and the closing balance no longer matches the opening balance plus the sum of amounts.

Source

After extraction, start from the opening balance and walk each row: previous_balance ± amount == new_balance

Source

Keep the file on the device. Bank statements are high‑sensitivity documents. Uploading them to a random converter is a privacy decision, not just a convenience one.

Source