01

The problem I saw

A bank statement may look readable but still resist reconciliation. Dates, descriptions, deposits, withdrawals, and balances can sit in the wrong columns. A clean export can also hide a missing opening balance.

02

What I built

The public workspace loads a sample statement with three extracted rows. It separates date, description, withdrawal, deposit, balance, review state, and type. A review queue flags the missing opening balance. A person can edit values, show the source PDF, and export XLSX, CSV, DOCX, PDF, QBO, review JSON, or a ZIP review pack. In the static build, document parsing and optional caches run in the browser.

03

What I learned

A usable conversion has two outputs: the file and the reason to trust or review it. The sample makes the missing balance visible instead of calling the document finished.

PAIN POINTS

What the product addresses

  • Manual re-keying across file formats
  • Extraction tools that stop before usable output

DECISIONS

Decisions that shaped it

  • Keep money columns as numbers in spreadsheet exports.
  • Show a balance check and review state before download.
  • Let edits recalculate the balance trail immediately.
  • Provide diagnostic data without statement text, rows, or filenames.

LEFT OUT

What I deliberately did not build

  • A one-click export that hides uncertain rows and missing balances.

MEASURES

What I would measure

  • Documents that reach export without an unresolved critical flag.
  • Rows edited after comparison with the source page.
  • Balance trails that reconcile after review.
  • Files that need OCR or manual correction by source format.

EVIDENCE AND BOUNDARIES

What this note is based on

  • Visible on extractmint.iangoh.com on 21 July 2026: the three-row sample, balance check, review queue, source-PDF control, export options, local caches, and privacy-safe diagnostic description.
  • The first-party GitHub README describes this as a static prototype. I did not upload a private statement or verify OCR accuracy, financial accuracy, QuickBooks compatibility, or production security.

RELATED WORK

Explore the work connected to this note.

Explore related work