Abbreviation guide

Understand bank statement abbreviations

Banks shorten transaction descriptions in different ways. StatementForge preserves those descriptions in exports so you can review and clean them.

Bank statement abbreviation guide
Descriptions Transfers Fees

Preserve source wording

Exports keep transaction descriptions so you can decide what each label means.

Review bank-specific labels

Abbreviations can differ by bank, country, card network, and payment method.

Clean after export

Use CSV or XLSX when you want to normalize labels manually.

1
Choose bank statement PDF step

Choose the statement

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

2
Parse transactions from a bank statement step

Extract transactions

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

3
Review extracted statement rows step

Review rows

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

4
Export bank statement data step

Export the file

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

Statement descriptions mapped into rows
Browser-only Descriptions

Useful for

Bookkeeping notesClarify transaction descriptions before categorizing expenses in another tool.Transfer reviewIdentify internal transfers, e-Transfers, online banking payments, and fees.Statement cleanupKeep raw labels in one column and add your own notes after export.

Before you export

  • This page is a practical guide, not financial, legal, tax, or accounting advice.
  • Bank statement labels vary by bank, country, card network, and merchant processor.
  • Use the converter output as a reviewable starting point, then confirm against the source statement.

Does StatementForge decode every abbreviation?

No. It preserves the source description and lets you review or edit it.

Why do abbreviations differ?

Banks, card processors, and payment networks use different transaction description formats.

Should I remove confirmation codes?

Only if your own workflow requires it. Keep the original export if you need a source trail.

Can I edit descriptions before export?

Yes. You can edit extracted descriptions in the table.

Convert statement descriptions into rows.Convert now