A digital statement reads in about two seconds on the server once it is warm, so a matter of thirty statements is on screen in about a minute. Scans take longer, because every image page is read by OCR at 300 dpi, page by page, and that is most of the runtime: about five minutes for sixty scanned pages. The progress card shows the file being read and, on a scan, the page it is on. You can leave the page. The address bar carries the link back to the matter, and if you give an email address the matter mails you the same link when it is done. The link opens on the browser that started the matter, and on no other.
A matter takes up to 200 files, 300 pages per file, 40 MB per file, and 120 pages of OCR. Nothing over a cap is refused. A file past the cap is entered in the register with its name, size and SHA-256, marked as examined and not read, with the reason in plain words, and the exhibit says so. A statement that arrives in ten monthly PDFs is ten files; a year in one PDF is one.
Bank and card statement PDFs are read, digital or scanned. QuickBooks and Xero exports, and PayPal, Venmo and Cash App activity exports, are read as sheets; PayPal and Cash App statement PDFs are read as statements. A password-protected PDF opens when you type the password into the field on the upload form; it is held for the run and then released.
Everything else gets an entry and nothing more. A photograph of a statement as a JPG or PNG, a Word file, a spreadsheet that is not a ledger export: each is recorded by name, size and hash, listed in the exhibit as not read, and the checks that could not run on it are named. If you hold a statement only as an image, print it to PDF first; the scan path will then read it.
The statement is still held to its own printed opening and closing balance. Rows that could be read are proven against those figures; if they do not tie, the exhibit shows the first row where the running balance breaks and by how much, and the pages that could not be read are listed in the register as unread rather than skipped in silence. The register names every file with OCR-read pages and which pages they were. Those pages sit outside the row-accuracy credit, and the exhibit's last section says why: on a scanned page a misread digit is caught only where it breaks the arithmetic, and a misread name is not caught at all.
Two things help more than anything else. Redact inside the PDF, by drawing boxes in the file as it came from the bank, rather than printing and rescanning, because a rescan erases the file structure the authenticity checks read. And if the same statement exists as a digital download, send that one; a scan of it adds nothing the digital file does not already prove.
Amounts are read as numbers with the currency symbol stripped, so dollar, euro, pound, rupee and Singapore dollar figures read, and European decimal commas are recognised. Day-first and month-first dates are told apart from the statement itself; where a statement has too few rows to be sure, the read is not guessed. Every statement is proven against its own printed balances whatever its currency.
Nothing is converted between currencies, and the tracing step matches transfers on amount and date without looking at the currency. Keep one currency per matter: a set that mixes them would match a transfer across the two. The regression corpus that gates every release is built from US bank and card statements; a layout that will not read is added within one business day for a digital statement downloaded from the bank.
The first matter needs no account. Drop the set in, read the register and the proof on screen, and decide. The exhibit and the schedules are the product, paid once per matter; the same files run again at no charge for ninety days, a missed statement or two included.
The register and the proof are free on screen, no account needed for the first matter. Start a matter · Read the sample exhibit