How to import a QBO file into QuickBooks Online.

A .qbo file is a Web Connect bank-transaction file. It is not a QuickBooks company file such as .qbw, and renaming a CSV to .qbo does not convert its structure. Use a QBO file when your bank or another trusted source provides one and the transaction period belongs in the account you intend to update.

QuickBooks Online also has separate workflows for CSV transaction lists and, in some versions, statement images or PDFs. Those capabilities belong to QuickBooks Online. BankFileKit does not read or convert PDF statements, images, QFX, IIF, or QuickBooks company files.

Intuit's manual-upload guidance reviewed on September 4, 2026 says a transaction-list upload should be in English, no larger than 350 KB, and contain no more than 1,000 transaction lines. If a QBO file is larger, return to the source and request a shorter statement period instead of deleting arbitrary rows.

These are QuickBooks Online upload limits, not BankFileKit parser limits. A file that BankFileKit can preview locally may still exceed the separate limit enforced when you upload it to QuickBooks.

Open the Bank transactions area and note the account, the oldest and newest visible transaction dates, and whether transactions for the same statement period are already pending, matched, categorized, or reconciled. Preserve whatever export or recovery information your bookkeeping process requires before adding a historical file.

An upload can create duplicate work when its date range overlaps a connected bank feed or an earlier manual upload. BankFileKit can display possible duplicate rows inside one supported file, but it does not compare that file with the transactions already stored in your QuickBooks account.

In QuickBooks Online, open All apps, then Accounting, then Bank transactions. Select the tile for the intended bank or credit-card account when it is already present. Open the account-link dropdown and choose Upload from file; an unconnected account may instead show an option such as Or upload transactions manually. Intuit can change interface labels by plan or release, so use its current help article if your navigation differs.

Choose the QBO file you received from the bank or prepared for a controlled test, then continue. At this point the file is being submitted to QuickBooks Online under Intuit's service and privacy terms. BankFileKit is not part of that upload connection.

If you used BankFileKit only to inspect the file, that earlier preview happened in your browser memory. BankFileKit did not send the source QBO, filename, transaction descriptions, dates, amounts, or account details to its application server or analytics providers.

Use the QuickBooks account dropdown to select the bank or credit-card account that represents the statement. Do not choose an account only because its display name looks similar: confirm the account type, currency, statement period, and opening context used by your bookkeeping process.

If the account does not exist, QuickBooks may offer an option to create one. Creating a chart-of-accounts record is an accounting decision; BankFileKit cannot determine the correct account type, opening balance, tax treatment, or parent/subaccount structure for you.

Continue through the recognition or mapping step shown by your QuickBooks Online version. CSV uploads normally require explicit column mapping. A valid QBO file carries Web Connect fields, so the screens can differ, but you should still verify the visible dates, descriptions, amount direction, and target account before confirming.

Stop if deposits appear as spending, spending appears as income, dates use the wrong convention, the transaction count is unexpected, or the period overlaps transactions already waiting for review. Fix the source or account choice rather than accepting rows that you do not understand.

When QuickBooks displays a transaction selection screen, compare it with the source statement and select only the rows that belong in this upload. A useful verification is to compare the first date, last date, number of rows, representative descriptions, and signed totals with the source records available to you.

Use completely fictional data for a test account. For example, a safe two-row test could contain a Fictional Office Supply purchase and a Fictional Client Payment. Never send a real bank statement or transaction list to BankFileKit support for troubleshooting.

Complete the confirmation shown by QuickBooks and return to the bank-transactions list. Uploaded rows normally require further review; their appearance in the list does not mean they have been categorized correctly or reconciled.

Compare the resulting pending rows with the source before posting anything. If a row is missing, duplicated, assigned to the wrong account, or shown with the wrong amount direction, stop and investigate before continuing with the rest of the batch.

Match an uploaded bank transaction when the corresponding invoice, bill, receipt, check, transfer, or other record already exists in QuickBooks. Categorize it only when the workflow should create a new accounting record. Intuit warns that matching and categorizing have different effects, so review suggested matches instead of accepting them automatically.

After the review is complete, reconcile the account against the statement according to your normal bookkeeping process. BankFileKit does not assign categories, create accounting entries, verify suggested matches, provide tax advice, or confirm that reconciliation is correct.

Use the QBO to CSV converter to preview the supported transaction rows and available statement metadata in your browser. The audit CSV can help you compare dates, descriptions, signed amounts, and row counts without modifying the QBO source.

The preview is deliberately limited to fields BankFileKit supports. It does not prove that the file is complete, authentic, approved by a bank, compatible with every QuickBooks release, or safe to add to a particular set of books.

The BankFileKit CSV to QBO converter creates an experimental candidate Web Connect file in the browser. The writer has automated structure tests but has not passed a real QuickBooks Desktop import matrix. The output is not advertised as guaranteed compatible with QuickBooks Online or Desktop.

Test a generated candidate only with fictional transactions and a controlled, recoverable QuickBooks environment. A successful browser download is not evidence that QuickBooks accepted the file or represented every field as intended.

This guide was last checked against Intuit's current US manual-upload, matching, and categorization guidance on September 4, 2026. QuickBooks menus, limits, supported file types, and review labels can change. The linked Intuit articles control for the QuickBooks service; this page explains a cautious workflow and BankFileKit's separate local-processing boundary.