statement.work for bookkeepers
For bookkeepers, statement.work turns the statements clients send (PDFs, scans or photos from any bank) into categorized transactions with consistent columns, so month-end and catch-up work starts with clean data instead of retyping.
Where bookkeeping time really goes
Bookkeeping software is good at handling transactions once it has them. The slow part is getting them in when a bank feed isn’t available, has gaps, or a client has only paper or PDF statements. Then the job becomes copying, retyping and fixing columns, statement by statement, before any categorizing or reconciling can begin.
statement.work removes that step. You give it the statements; it gives you transactions.
A month-end routine with statement.work
- Gather the month’s statements for each account, in whatever form the client sends them.
- Convert them together. Every transaction comes out with date, description, amount, running balance and a category.
- Check the balances. Opening balance plus money in minus money out equals the closing balance.
- Export CSV and import it into your bookkeeping software, using the same column mapping every month.
- Reconcile against the books. Our reconciliation guide has a fast routine.
- Review flagged items: duplicate charges, fee spikes and unusual transactions.
Catch-up and clean-up jobs
Catch-up work is where manual entry hurts most: a new client arrives with eight months of unfiled statements from two banks. Converting them in one batch gives you a single, consistent dataset to work from. Because every statement produces the same columns, the months stack straight into one spreadsheet, ready to sort, categorize and import.
Categories that save a pass
Automatic categorization (payroll, rent, subscriptions and so on) means you start from a first draft rather than a blank column. You still decide how categories map to the client’s chart of accounts, but the bulk of obvious transactions are already grouped. For building a category list that stays consistent across clients, see how to categorize bank transactions.
Questions without spreadsheets
Clients ask questions like “How much did we spend on software this quarter?” or “Did that supplier charge us twice?” With statement.work you can ask those questions in plain words and get an answer built from the actual transactions, without building a pivot table first.
What it doesn’t do
statement.work doesn’t post transactions into your accounting software for you, and it doesn’t claim built-in integrations with specific products. It produces clean CSV, Excel or JSON that you import using your software’s own bank-statement import. The CSV import guide covers the general steps.
Getting started
statement.work is onboarding a first group of bookkeepers. A good test is your messiest client: the one with scans, multiple banks and a backlog.
Questions
Can I use statement.work when a client's bank feed is missing or broken?
Yes. When transactions are not coming through a feed, converting the PDF statement to CSV gives you the same data to import, in a consistent layout.
Does statement.work categorize transactions?
Yes. Transactions are categorized automatically, for example payroll, rent and subscriptions, and you can map those categories to the client's chart of accounts.
Can I convert a whole year of statements for a catch-up job?
Yes. You can upload several statements in one go, and each comes out in the same format, so a year of months stacks into one sheet.