Open a QBO File in Excel: Export Transactions Without Losing IDs

Read a QBO bank file as a spreadsheet with dates, amounts, payees, memos and transaction IDs. This guide follows the actual controls and output of CSV2QBO, so you can distinguish a completed file conversion from a verified import.

Prepare the right source

Choose the original .qbo file from the bank. A QuickBooks company file, report PDF or a downloaded web page renamed to .qbo is not a transaction statement.

Work with a copy covering one account and a known date range. An export from a bank or finance application is preferable to a manually reconstructed table because it gives you an original to compare. Never rename a PDF or a company backup to a different extension and expect its contents to become transaction data.

Convert and review

1. Open the QBO to CSV Converter. Use Download sample file or the sample button first if you want to inspect the workflow with fictional data.
2. Choose the original qbo file. The converter reads it locally. Keep an untouched copy for comparing counts and values later.
3. Review the parsed transactions. For QIF or IIF, set the source date order explicitly; OFX-family files already contain structured dates.
4. Inspect the preview and resolve any errors. Read and acknowledge format limitations when they appear, then download the csv output.
5. Compare the downloaded file with the original before importing it into your destination software.

What changes in this format

The spreadsheet retains one row per STMTTRN and separate columns for payee, memo, type, check number and FITID. An account containing two equal purchases still produces two rows when the source IDs differ.

Worked example: verify the meaning, not just the extension

An OFX NAME of Example supplies and a MEMO of Office materials should appear in different spreadsheet columns. The -42.50 amount remains numeric. The source FITID DEMO-TXN-2 should remain attached to that row even if you sort the spreadsheet by amount instead of date. A missing memo is an empty cell, not a reason to drop the row.

Set up the destination

For CSV output, open the result as a table and keep all columns together when sorting. Spreadsheet programs may reinterpret identifiers or dates, so import those columns as text when exact values matter. Text that could be interpreted as a formula receives an apostrophe prefix; this is a deliberate spreadsheet safety measure, not a financial adjustment.

Common mistakes to avoid

Treat account numbers and FITIDs as text in your spreadsheet. Sorting is safe only when entire rows move together. The CSV is an inspection artifact, not a complete export of customers, bills or the QuickBooks company.

An invalid date or amount blocks export rather than quietly removing a transaction. If an error names a record or source row, correct that record in a copy of the source and load it again. A date that is valid in two different orders still needs your explicit choice. Check a date whose day is greater than twelve to confirm the source convention when such a row is available.

A final comparison before import

Compare the first and last transaction dates, the number of main transactions, the total money in and the total money out. Inspect at least one refund or reversal when the source has one. A matching net total alone is insufficient: two errors with opposite signs can cancel each other. Keep the source and output together until the destination has been checked.

The local file limit is 5 MB, and supported financial inputs are bounded to 50,000 records. The destination software may allow less. Files remain in your browser; no account is needed, and no conversion file is stored on CSV2QBO servers.

Use QBO to CSV Converter or explore the other converters. For a related workflow, prepare a CSV for QuickBooks.