Tickmark: bank statements to spreadsheets, checked to the cent, without uploading them
Description and use
Tickmark converts bank statement PDFs to spreadsheets locally, verifies each row against the printed running balance, flags mismatches, and exports to multiple accounting formats—all without uploading data.
Problem
Bookkeepers and accountants routinely retype bank statement PDFs into spreadsheets, risking data loss and errors because converters upload files to unknown servers and may misread figures.
Outcome
Tickmark converts bank PDFs to spreadsheets locally, verifies each row against the printed running balance, flags mismatches, and exports to multiple accounting formats—all without uploading data.
Workflow
- Open the Tickmark web page
- Drop or open a PDF statement
- Tickmark parses the PDF text layer or runs Gemma 4 on scanned images
- It groups text into lines and cells, identifies columns, and extracts dates, amounts and balances
- It calculates a running balance and compares it to the printed balance
- Rows that match are ticked; mismatches are ringed in red with gap details
- The ledger is displayed and can be exported to various formats
- No external requests are made; the page shows a zero request count
Evidence
Tickmark copies every transaction into a ledger and adds it to the running balance. A row gets a tick only when the balance the bank printed agrees to the cent; a row that does not agree is ringed in red, with the gap and the place to look.
Scanned statements, which have no text to copy, are read by Gemma 4 running on your own graphics card through WebGPU.
Nothing is uploaded. The page counts every request it makes to another site and shows the number at the bottom.
On the scanned sample (three pages, 64 transactions) Gemma 4 reads every row correctly in about two minutes, and all 64 tie.
- Record date: 2026-10-15T13:41:01.166Z