QBO to CSV Converter

Convert QBO to CSV when you have a QuickBooks Web Connect download and want to read the transactions in Excel, Google Sheets or another app. A .qbo file is an Open Financial Exchange (OFX) statement with a QuickBooks header, so its transactions sit in standard STMTTRN blocks. This QBO to CSV converter reads those blocks and writes one row per transaction.

How to use the QBO to CSV converter

1. Choose the .qbo file from your bank. Plain .ofx files work too.
2. Leave Input encoding on auto; older files that show odd accents usually need windows-1252.
3. Select Process files, or press Try an example for a one-transaction fictional file.
4. Check the rows and download the CSV.

What a QBO file holds

The OFX specification groups a bank statement as STMTRS, with the account in BANKACCTFROM and the transactions in BANKTRANLIST. Each STMTTRN has a type such as DEBIT or CHECK, a posted date (DTPOSTED), a signed amount (TRNAMT), a unique ID (FITID) and usually a NAME and MEMO. The QuickBooks-specific header and sign-on details are not transactions, so they are not exported.

The QBO to CSV output has seven columns: account, id, date, type, amount, payee and memo. Both the old SGML style, where tags such as <TRNAMT>-12.50 have no closing tag, and the newer XML style are read.

Worked example: one debit

<STMTTRN>
<TRNTYPE>DEBIT
<DTPOSTED>20260105
<TRNAMT>-12.50
<FITID>demo1
<NAME>Cafe
</STMTTRN>

Inside the sample file this becomes one row: account EXAMPLE123, ID demo1, date 20260105, type DEBIT, amount -12.50 and payee Cafe. The date stays in the OFX YYYYMMDD form so nothing is lost to a time zone guess; format the column as a date in your spreadsheet if you need to.

Why keep the FITID column

The OFX specification calls FITID the unique ID of a transaction, and accounting apps use it to skip rows they already imported. Keep it in your CSV, and format the column as text so leading zeroes survive. If you run the QBO to CSV converter on two overlapping downloads, matching IDs show you which rows repeat.

Files with several different accounts are rejected so no row gets the wrong account label. Investment statements, splits and loan details are outside this bank-statement profile.

Common QBO to CSV errors

• No supported bank transactions found. The file has no STMTTRN blocks, holds more than one account, or is a saved web page.
• Use a decimal amount with no currency symbol and at most two decimal places. A TRNAMT value has a currency sign or extra decimals.
• Wrong characters in payee names. Choose the encoding by hand.

Privacy: your bank file stays in your browser

The QBO to CSV converter runs with JavaScript in a background worker on this page. We checked the tool code: the statement is read from your device into browser memory, nothing is sent to a FileFix or Calcenzo server, and the only network requests the tool makes are for its own static files. Your file stays in your browser. The download is built in memory too. Bank files carry account numbers and balances, so on a shared computer clear the selection or close the tab when you are done.

For plain OFX or QFX files use the OFX to CSV converter. To go the other way, the CSV to OFX converter and the CSV to QIF converter build import files from a spreadsheet.

Sources

The QBO to CSV converter follows these specifications and format guides:

• Financial Data Exchange: OFX specifications
• The National Archives (PRONOM): Open Financial Exchange 1.02

Questions about this tool