StatementForge
Convert a statement
A review-first conversion workflow

From statement PDF toclean, reviewable rows.

StatementForge reads the file inside your browser, shows the transactions it found, and waits for your review before generating an export.

Convert a statement Run the safe sample
Statement contents stay local Review before export No bank connection required
The workflow at a glance
  1. 01Choose the source file
  2. 02Read the statement locally
  3. 03Build transaction rows
  4. 04Review before export
  5. 05Generate the file

Conversion data remains in the current browser workspace.

Five deliberate steps

Automation handles the repetitive work. You keep the final say.

Statement layouts differ, and scanned text can be imperfect. The workflow is designed to expose the result before it becomes an accounting or spreadsheet file.

  1. 01

    Choose the source file

    Open one bank statement PDF, add a supported batch on a paid plan, or use pasted statement text as a fallback.

    The selected statement stays in the browser workspace.
  2. 02

    Read the statement locally

    Text-based PDFs are read in the browser. A scanned PDF can use local image-to-text on its first eight pages.

    OCR output varies with scan quality and always needs review.
  3. 03

    Build transaction rows

    StatementForge looks for dates, descriptions, amounts, withdrawals, deposits, and running balances.

    Unusual layouts can produce warnings or rows that need correction.
  4. 04

    Review before export

    Search the extracted rows, compare totals, and correct transaction fields before creating the destination file.

    The review table remains the source of truth for the export.
  5. 05

    Generate the file

    Create CSV, XLSX, JSON, QBO, OFX, or QIF from the reviewed rows and save the result from the browser.

    Accounting applications can still require their own import review.
What "local" means

The document is processed in the browser tab.

StatementForge does not send the PDF, extracted statement text, transaction rows, or generated export contents to its backend for conversion. Your browser still downloads the application and any worker assets needed to perform that work.

  • PDF text extraction runs in the browser
  • Scanned-page OCR runs locally
  • Generated files are saved from your device
Read the complete data boundary
The review that matters

Check the financial meaning, not only the row count.

A parser can find likely rows without understanding every institution-specific layout. Compare the export with the source statement before posting transactions.

Before you export

  • Dates match the source statement
  • Deposits and withdrawals use the correct direction
  • Descriptions are complete enough to recognize
  • Running balances agree where the statement provides them
  • The destination application accepts the selected file format

Scanned statements and unusual layouts deserve extra review.

See the result before the export

Try the workflow with a safe sample or your own statement.

Your statement contents remain in the browser conversion workspace.

Open the converter Explore file tools