QBO spreadsheet review

Open a QBO file in Excel or Google Sheets without treating it as a spreadsheet.

A QBO Web Connect statement is structured financial text, not a ready-made worksheet. Create a local audit CSV first, then decide where you want to review that exported copy.

Updated July 25, 2026 · Examples use fictional data.

Use the next step nowRead the QBO locally and export supported fields for a spreadsheet review copy.
Convert QBO to an audit CSV

Why a QBO file does not open as useful rows

A QBO file is a QuickBooks Web Connect statement in the OFX family. Opening it as plain text can show tags, but it does not turn transaction blocks and statement headers into readable spreadsheet columns.

1. Keep the original QBO unchanged

Store the original statement separately and work from a downloaded review copy. Do not edit tags in the original file to make it look like CSV; that can change the structure needed by a later import test.

2. Create a local audit CSV

Use the QBO to CSV converter. It reads supported QBO transaction blocks in the browser and produces an audit CSV. The source QBO does not leave the browser during that conversion.

3. Review the exported columns

Column groupWhat it helps you inspect
Date, Description, AmountReadable transaction rows, dates, and signed values.
FITID, Memo, CheckNumberSupported identifiers and reference fields when present in the source statement.
Account and statement metadataAvailable account type, account/bank IDs, statement range, and financial-institution tags.
SourceFormatMarks the export as a QBO-derived audit CSV, not a QuickBooks upload file.

4. Open the audit CSV in a spreadsheet app

Open or import the downloaded CSV using the spreadsheet app's normal CSV-import flow, then verify the delimiter and columns before sorting or filtering. Treat any edits as edits to a review copy, not as a replacement QBO file.

5. Understand the Google Sheets privacy choice

BankFileKit's conversion is local. Uploading the resulting CSV into Google Sheets is a separate action that may send the exported data to Google. If the statement is sensitive, keep the audit CSV in a local spreadsheet application or use a fully fictional test file.

6. Use the audit CSV to validate, not to promise an import

Check transaction count, dates, amounts, and possible duplicates before a QuickBooks test. A readable CSV does not guarantee that the original QBO will import successfully into any QuickBooks product or account state.

What this tool does not do

It does not open QBW company files, create a full accounting export, repair a rejected Web Connect file, or turn the audit CSV back into a validated QBO import file.