WoluTools
Find a tool

Finance & Accounting

Convert OFX, QFX or QBO transactions to CSV

Upload an OFX, QFX or QBO file. You get a CSV with date, amount, payee, memo and transaction ID for each supported transaction. Balances are not included.

or drop it here

OFX, QFX, QBO · Up to 100,000 transactions
Free account needed for your 3 free jobs a day

No file at hand? See the prepared example

Standard toolIncluded · 3 free jobs a dayFree: 3 jobs a dayPro: up to 200 jobs a day · €12.99/month or €89.99/year
  • OFX / QFX / QBO
  • Up to 100,000 transactions
Prepared result preview · fictional sample dataFictional OFX/QFX Transaction Extractor fixture
Source
1 prepared source file · 111 bytes
Verified package preview
  • Transactions: 1
  • Artifacts reopened: 3

transactions.csv · findings.csv · manifest.json

BringOFX, QFX, QBO
GetTransaction CSV, parser findings and manifest
PrivacyEncrypted source · 24-hour result

One clear job, from source to download

  1. 1

    Add the source

    Supported formats and limits are visible before the upload.

  2. 2

    Confirm the settings

    Review the exact source, options, units and access before processing.

  3. 3

    Inspect and download

    Check the preview and warnings, then unlock the complete package.

Turning OFX, QFX and QBO files into a transaction CSV

Which bank files work and how large

You upload one OFX, QFX or QBO file as exported by your bank or accounting software. A single job handles up to 100,000 transactions. There are no settings to fill in. The tool reads the transaction blocks in the file and nothing else. If the file is too large or not one of these formats, it is refused before processing, so you never receive a half-converted export that looks complete.

What the CSV and findings show

You get transactions.csv with one row per supported transaction: FITID, date, amount, name and memo. Values are not renamed or reshaped beyond what a CSV row needs. FITID is the ID your bank assigns, and it helps you spot duplicates when the same period is imported twice. findings.csv lists anything the tool left alone. manifest.json records the source file so you can match the CSV to it later.

What is left out on purpose

Account balances and other account-level details are not included. Many banks add their own custom tags to OFX files. The tool does not try to interpret them. They are named in the findings so you can decide whether they matter for your books. The CSV is a starting point for import or review. Check it against your bank statement before you import it.

Questions before you run it

Which fields does the converted CSV contain?

FITID, date, amount, name and memo, taken from supported STMTTRN blocks. Values are not renamed or reshaped beyond what writing a CSV row requires.

Why is FITID kept in the export?

FITID is the transaction identifier the institution assigns, and it is what lets you spot duplicates when the same period gets imported twice. It stays in the file rather than being dropped as noise.

Does the export include account balances?

No. Ledger and available balances, along with account-level elements, sit outside scope. The job converts transaction blocks and nothing else.

My bank adds custom tags to its OFX. What happens to them?

Institution extensions and unsupported elements are not interpreted. They are preserved rather than guessed at, and the findings name what was left alone so you can decide whether it mattered.

Is a QBO file from QuickBooks accepted?

QBO is accepted alongside OFX and QFX, up to 100,000 transactions per job.