Changelog

1. 19 September 2026 Pricing

   Launch offer: ten free pages a day

   For a limited time after launch, the free tier goes from three pages a day to ten, with or without an account and with no card. Most monthly statements are four to eight pages, so one fits inside a single day's allowance, balance check and every export format included.

   • When the offer ends, the free tier returns to three pages a day. Credits you buy are not affected: they never expire.
2. 17 September 2026 Privacy and security

   Every provider and the operator, named

   The security page, the privacy policy and the data processing agreement now name the company whose model reads your statement: Anthropic, whose Claude model does the reading through Anthropic's commercial API. Its commitments are linked from those pages.

   • The legal pages name the person who operates StatementTable, and the footer carries the same line.
   • The privacy policy and the data processing agreement state the one exception to Anthropic's 30-day deletion: a request its automated safety systems flag under its usage policy.
3. 15 September 2026 Exports and the balance check

   One review workbook, then every format from what you confirmed

   A conversion now gives you a review workbook. You fix the rows it marks, fill in the statement details your accounting software needs, upload it, and every format is produced from what you confirmed.

   • The review workbook (.xlsx) carries every row with a Check column and a Note column naming what to look at, and a Statement details sheet with account type, currency, opening and closing balance, account number and bank identifier, already filled from the statement where it printed them.
   • Uploading the workbook checks it: a blank required field or a date that cannot be read is listed with its row or cell, and you upload again once it is fixed. Uploading uses no pages.
   • Excel, CSV, CSV for import, QBO, OFX, QFX and QIF are produced from the confirmed workbook and carry only your data: no marks, no notes. The opening balance is entered on the workbook, not on the screen.
   • A statement that prints no balance beside its rows is checked on its printed totals: previous balance plus money out minus money in against the new balance, and the printed totals for money out and money in against the rows.
   • A date that falls outside the statement's own sequence is marked for review. A cell the reader could not make out is marked with the cell named, and a doubt about an amount that the printed balances confirm is no longer marked.
   • A scanned page that carries a text layer under the picture, the way copiers and scanning apps produce them, is read as the picture at full resolution.
   • The navigation menus no longer overlap when the pointer moves from one to the next.
4. 15 September 2026 Conversion and the balance check

   Scans and photos are read at full resolution, and the check repairs what it can

   A scanned or photographed page now reaches the reader at its full resolution instead of a reduced rendering, and the balance check has moved from marking rows to putting them right where the arithmetic allows.

   • A scanned PDF page is read as the picture it contains, at the reader's full resolution. A phone photo is sized in your browser to that same resolution before upload.
   • A debit read as a credit, or a running balance misread on one line while the amounts around it agree, is corrected from the printed balances and shown as Matched with a note beside the tick.
   • A page whose chain still breaks is read a second time, and a row from the second reading replaces the first only when it makes the printed balances tie. Wording that differs between the two readings no longer marks a row for review.
   • "Rows to review" in the workbook summary now counts the rows the Check column marks, once each.
   • A page with more transactions than can be read in one answer is refused by name, with the page number, instead of failing as an error.
   • Pages are read six at a time, and the time estimate shown during a conversion is drawn from measured runs on full-resolution pages.
5. 9 September 2026 Policy and limits

   You can now read exactly how long each thing is kept

   The privacy policy answers the retention question in one schedule instead of in prose, which is the answer a client or a compliance reviewer asks you for first.

   • Every category of data now has a stated retention period in a single schedule, each sub-processor is described by category with its country and safeguards, and the provider is named on request.
   • Storage wording is now precise: your file exists only while the conversion runs and is deleted right after, in every case within one hour. The hour is the outer ceiling, not the usual case.
   • Terms cover accounts and monthly plans, and the refund policy now extends to plans as well as packs.
   • Photo uploads are capped at 10 per statement, so a long paper statement is split across two conversions.
   • Site content is in English. Turkish statements are read as before.
6. 8 September 2026 First release

   Convert a statement, and see the arithmetic tie

   The first release does one job end to end: it reads a statement and shows you, row by row, that what came out matches the balances the bank printed.

   • PDF, scanned PDF and phone-photo bank statements convert to XLSX, CSV, QBO, OFX, QFX, QIF and JSON.
   • Every conversion is balance-checked. The running balance is rebuilt from the extracted rows, compared line by line and then against the closing balance, and rows that break the chain are flagged with the difference.
   • Statements printed newest first are detected by running the check both ways, and exported in date order.
   • Credit-card statements flip the sign convention and exclude subtotal rows. Where the statement prints no running balance on each line, the check reports what it could tie rather than passing.
   • A native PDF that fails the check is read again with a stronger pass, automatically.
   • Three pages a day are free with no account. Page packs are $9 for 60, $29 for 300 and $79 for 1,000, and credits never expire.
   • Every release is validated against a fixed test corpus. How we test.

These entries describe work that has shipped. Planned work is on the roadmap, and how particular statements and export formats behave is documented in the help center.