For accountants
Close faster on data you can defend.
Rebuild a full year from statement PDFs in an afternoon: every month reconciled against its own printed balances, every figure traceable back to the line it was read from.
50 free page credits · No card · Cancel anytime
- Balance-validated parses
- Full-year reconstruction
- Source traceability
Add statements
50 free pagesYear-end starts with a stack of PDFs and a deadline.
The books are incomplete, the bank feed only reaches back ninety days, and what the client actually hands you is twelve months of statement PDFs. Retyping them is days of work carrying no professional value, and the time is not even the real risk. A transposed figure or a page that never got scanned becomes a discrepancy you will spend longer hunting than you spent typing, and you will find it late, in a total, with no way back to the document it came from.
How it works
Twelve months, in the order you would do them
- 01
Load the whole year in one go
Every statement at once: scanned, multi-page, and password-protected PDFs included, up to 50 MB each. Nothing is read until you confirm the batch and how warnings should be counted.
The queued files and the warning policy are both settled before a single transaction is extracted. - 02
Watch each one reconcile
A statement is read, its transactions extracted, its bank detected, its rows categorized, and its opening and closing balances checked against the total it printed. A month that does not tie says so here, not in a year-end figure.
Each upload reports the stage it is on and the seconds elapsed as it moves through the queue. - 03
Take the flags before the totals
Anything the parse could not settle is counted on the statement itself. Work those rows against the page they came from, and record the treatment you decided on.
Every figure sits beside the printed line it was read from, which is what makes it defensible later. - 04
Classify, and make it stick
Categories and subcategories apply automatically and are refined with rules, but a classification you set by hand is protected from every later automated run, so a considered treatment is never quietly reversed.
A category opened to the rules behind it and the transactions they caught. - 05
Produce the outputs, and the evidence
Monthly totals, category distribution, and per-merchant detail: exported to Excel or CSV for the working papers, or to OFX/QBO for QuickBooks. Every row still carries the statement and account it was read from.
Excel selected, the columns chosen and ordered, and the rows previewed before the file is written.
The parts that make it defensible
Reconciliation at intake
Every statement's own opening and closing balances are checked against the extracted rows, so completeness is verified before classification begins.
Traceable to source
Each transaction records the statement and account it came from, so any figure in a total can be traced back to the document it was read from.
Fast interrogation
Narration search plus filters for date range, min/max amount, category, credit versus debit, and account, for when a review question needs an answer in seconds.
Judgement calls that stick
Manual categorizations are protected from subsequent automated changes, and tags like #tax-deductible or #review carry through filters and exports.
Analysis, not just totals
Monthly income versus expense, category distribution, merchant rankings, and a money-flow view: the context that turns a compliance job into advisory conversation.
Every output format
Filter-scoped exports as CSV or Excel for working papers, or OFX/QBO for QuickBooks Online and Desktop.
FAQ
Common questions
How far back can I reconstruct records?
As far back as the client has statement PDFs. Unlike a bank feed, there is no ninety-day or twelve-month window. You upload the documents you have.
How do I know nothing was missed in the parse?
Each statement's extracted rows are reconciled against its own stated opening and closing balances, and anything that does not agree is flagged for review rather than passed through silently.
Can I trace a number back to the statement?
Yes. Every transaction carries its source statement and account, so a category total can be decomposed back to the individual rows and the documents they came from.
Will automated categorization override my classifications?
No. Any category you set by hand is protected from automated and rule-driven changes, so a considered treatment is not quietly reversed by a later run.
Does it handle scanned or password-protected statements?
Yes: scanned PDFs, multi-page statements, and password-protected files, up to 50 MB each, alongside CSV, XLSX, and JSON.
Where can I read about data handling?
The security page covers how documents are stored and handled, and a DPA is available for client-data engagements.
Keep exploring
For Bookkeepers
Speed up monthly reconciliation and recurring client work.
For Accounting Firms
Standardize statement intake across every client account.
Live example
A real Bank of America statement read into transactions you can trace back to the page.
Bank Statement → Excel
Download a clean XLSX of every parsed transaction.
Bank Statement → QuickBooks
Categorize first, then export an OFX/QBO QuickBooks imports.
Spend year-end on judgement, not typing.
Load a year of statements and see how much of the reconstruction is already done for you.