Preserve source wording
Exports keep transaction descriptions so you can decide what each label means.
Banks shorten transaction descriptions in different ways. StatementForge preserves those descriptions in exports so you can review and clean them.
Exports keep transaction descriptions so you can decide what each label means.
Abbreviations can differ by bank, country, card network, and payment method.
Use CSV or XLSX when you want to normalize labels manually.

Choose a text-based bank statement PDF, add a batch on bulk plans, or paste statement text when a PDF is locked.

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

Check and edit the transaction table before exporting, especially for unusual layouts or rows that need manual review.

Download CSV, XLSX, JSON, QBO, OFX, or QIF depending on the workflow you need.

No. It preserves the source description and lets you review or edit it.
Banks, card processors, and payment networks use different transaction description formats.
Only if your own workflow requires it. Keep the original export if you need a source trail.
Yes. You can edit extracted descriptions in the table.
Start with the format, privacy setup, or statement type that matches the file in front of you. Each guide opens the same converter with a more focused workflow.
Use these when you want clean rows for spreadsheets, bookkeeping cleanup, or analysis.
Create reviewed files for accounting tools that accept QBO, QIF, OFX, or CSV imports.
Parse, review, analyze, and batch-convert sensitive statement files in the browser.
Start from a bank-specific or statement-review workflow, then convert the downloaded PDF.