Who statement.work is for

statement.work is for anyone who has to get transactions out of bank statements and into a spreadsheet or accounting system: accountants, bookkeepers, small business owners and people preparing taxes.

Last updated

The common problem

The people on these pages do different jobs, but they hit the same wall. Bank data arrives as statements: PDFs exported from online banking, scans of paper copies, or photos taken on a phone. The work that follows needs rows and columns. Closing the gap by hand means copying, pasting, retyping and checking, and it gets slower with every client, account and month.

statement.work reads the statement and returns every transaction with its date, description, amount and running balance, categorized and in one consistent format, whichever bank it came from. From there you can export CSV, Excel or JSON, or ask a question about the data in plain words.

Pick your role

What stays the same for everyone

  • Any bank, any layout. No templates to set up per bank. See the bank pages for layout notes.
  • Every input type. Digital PDFs, scanned statements and phone photos go through the same way.
  • Same columns every time. Consistent exports make it easy to combine statements from different banks.
  • Careful data handling. Statements are encrypted in transit and at rest, deleted after processing on a retention window you control, and never used to train models. Details are on the security page.

statement.work is currently in early access for accountants, bookkeepers and small businesses.

Get your afternoons back.

We're onboarding a first group of accountants, bookkeepers and small businesses. Add your email to get early access.

You're on the list. We'll email you when it's your turn.

No spam. One email when it's your turn.