Local conversionNo statement uploadEditable reviewCorrect rows before exportScanned-page fallbackLocal OCR on the first 8 pages
Built around a visible result
What bulk mode changes
StatementForge does not hide extraction behind a black box. The transaction table, warnings, totals, and destination format stay visible so you can decide whether the result is usable.
Up to twelve PDFs can be queued in one paid batch
Each file has its own progress, warnings, row totals, and review tab
Combined CSV and XLSX exports retain the source statement name
The XLSX workbook adds per-statement sheets when multiple files are loaded
A review-first workflow
From source document to a file you can inspect.
01
Choose
Select a statement PDF or use the safe sample.
02
Extract
Read its text layer or run limited local OCR.
03
Review
Check and correct the transaction table.
04
Export
Generate XLSX from the reviewed rows.
Honest operating limits
Financial files still deserve a human check.
Bulk limits depend on your plan and the file size/page limits shown inside the app.
Review each statement tab before relying on the combined export.
Scanned PDFs can take longer because image-to-text runs locally and is limited to the first 8 scanned pages.
Where this workflow fits
Use the converter for a defined job.
Year-end cleanup
Load a full year of monthly PDFs and export a combined table.
Bookkeeper batches
Process several client statements in one session.
Account comparisons
Combine rows from multiple statements while preserving the statement name column.
Practical questions
Bulk conversion questions
Can I add multiple statements at once?
Yes. Bulk batches are supported according to your plan limits.
Does the export keep statement names?
Yes. Exports include a statement name column so rows can be traced back to the source file.