Release Notes

Running changelog for StatementLock. Newest changes on top. I'll edit this post as updates ship and add a comment when new notes land.

July 25, 2026

Statement verification. Bank and credit-card statements print their own control totals — beginning/ending balances, total deposits and withdrawals, or on cards, New Charges and Payments/Credits. StatementLock now parses those totals locally and reconciles the extracted transactions against them, deterministically, on your device. Every statement in your Files tab gets an honest badge:

• Verified — the extracted transactions tie to the statement's own printed totals (the badge names exactly which checks ran, e.g. "balance replay clean" for checking, "charges tie, payments tie" for cards).
• Review totals — the statement's summary layout wasn't recognized, so the app shows its computed totals next to a link to the source PDF, and you accept or reject them yourself.
• Accepted by you — you reviewed and accepted (clearly labeled as your call, never called "verified").
• Doesn't reconcile — the numbers genuinely don't tie. The app tells you which check failed instead of quietly showing data it can't stand behind.

If a statement is missing or duplicating a transaction, this catches it. All of it runs in your browser — same as parsing and categorization.

Filter by statement. The Transactions tab now has a Statements filter alongside Accounts — view one statement's transactions in isolation, with its verification badge in the list. Statement periods now show in the Files tab and export as a column in the Transactions CSV.

Rename accounts. The pencil icon now properly renames an account (your name becomes the primary display, with the auto-detected name kept visible underneath).

Issuer detection improvements. Detection is now anchored to the statement's page-1 letterhead, so a bank mentioned in a transfer line can't be mistaken for the issuer. Added recognition for more issuers, including PNC and Navy Federal.

Better bug reports. In-app bug reports now include a scrubbed diagnostic trace (timings, counts, parse results — filenames replaced with aliases, run through the same PII filter used before any AI analysis). If a statement won't load right, your report now carries the evidence.

Demo fix. The sign-up buttons at the end of the demo tour now work (previously the tour overlay blocked the highlighted button).

Public guide. The full user guide is now public at statementlock.com/guide — setup, categorization rules, the AI report, privacy, and troubleshooting.

As always: statements are parsed in your browser, files stay in your local folder, and only de-identified text is sent to the AI for extraction and reports — categories are assigned locally by your rules and built-in patterns. Details in the transparency post. Found something off? Report a Bug (top-left, every tab) or comment here.