CSVQBO / Practical guide

Import CSV to QBO: choose Online upload or a Desktop workflow

Resolve the meaning of QBO first, then choose a supported route without confusing file conversion with ledger posting.

Resolve the two meanings of QBO

To import CSV to QBO, first decide whether QBO means QuickBooks Online or a Web Connect .qbo file. Online commonly has a manual bank-transaction upload that accepts mapped CSV data. A .qbo file is structured bank-statement data read by QuickBooks Desktop's Web Connect import, and Intuit's US help also lists .qbo among the files QuickBooks Online's Upload from file accepts. You do not create it by saving a spreadsheet with a new suffix. Write down the intended destination and account before changing the source. If Online accepts your CSV directly, a separate conversion service may add no value to this task.

Prepare an Online bank upload

Keep the original bank export and a backup of any working spreadsheet. Prepare a single account and currency; Intuit's US help asks for an English file of 350 KB or less, up to 1,000 lines, with either 3 columns (Date, Description, Amount) or 4 columns (Date, Description, Credit, Debit). In Bank transactions, open the Link account menu, choose Upload from file, pick the file and the target account, then match the columns; labels can vary by subscription and region. Review the incoming list before adding entries. Avoid overlapping already imported dates where possible. This is a banking transaction workflow; importing a supplier list, sales invoices or a complete company database is a different job with different fields.

Use the right Desktop route

Desktop's Web Connect file import accepts .qbo only; CSV, QFX, OFX and QIF do not enter through that route. Windows Pro and Premier lack built-in CSV transaction import. Enterprise and Accountant can paste spreadsheet rows into bank or credit-card registers with Batch Enter Transactions. QuickBooks Desktop for Mac, which Intuit no longer sells to new customers, can import checks, deposits and other supported transaction types from a spreadsheet arranged in its own template through File > Import > Transactions. Choose the workflow supported by your edition and check the fields it requests. The 2024 release was the last annual Desktop version. File format alone does not prove that a bank-feed service is available for your software and institution.

Check transaction conventions before any route

Confirm numeric date order from the bank rather than guessing from an ambiguous day. Inspect which direction purchases and payments move the account balance. With separate debit and credit columns, verify that each row uses the intended side. A running balance is different from an amount and must not be mapped as a transaction value. Do not remove repeated rows merely because their dates, descriptions and amounts match; two real payments can share those fields. Keep source references in a working copy even if the destination accepts only three columns.

Verify the posting result

Compare source and destination counts for the selected period, then inspect a deposit, withdrawal, refund and the first and last dates. Review duplicate warnings and any omitted entries before finalizing. A successful upload message establishes that the file was accepted, not that mapping and signs were correct. When a Web Connect file is necessary, obtain authorized institution identifiers and the actual balance at the latest included date before conversion. A bank's native QBO export is preferable when available, since it avoids manually reconstructing institution metadata from a spreadsheet.

Prepare a destination-only CSV copy

The review workbook and the Online upload file serve different purposes. Keep source row numbers, printed dates and your checking notes in the workbook. In the upload copy, retain only the supported transaction columns and use one consistent date convention. If the source exceeds the documented line or size limit, divide it into nonoverlapping periods, retaining a manifest of which transactions belong to each file. Do not split a quoted record by cutting physical text lines. Read every part back as CSV and compare its record count and amount sum with the corresponding source subset before using the upload action.

Separate upload from adding transactions

Once Online reads the file, verify the matched columns and the selected transactions before adding them. A successful file selection is not a posted ledger result. Check a known withdrawal, deposit and refund in the incoming list, then review what the destination actually records. If you chose the wrong account or signs, investigate that result before retrying the entire file. Track which period and rows were already accepted so a correction does not accidentally introduce a second copy. Keep the original bank export available for any duplicate or missing-transaction investigation instead of relying only on the shortened upload copy.

Where CSVQBO fits

CSVQBO's normalized CSV carries audit columns; for Online upload, make a separate copy containing only Date, Description and Amount, within Intuit's limits. The service itself accepts one-account CSV or one-sheet XLSX up to 15 MiB and 3,000 transactions. Generating QBO, QFX or OFX additionally requires bank ID, account ID, FID, organization, authorized Intuit BID, currency, account type and actual balance at the latest included date. It does not post transactions or connect to QuickBooks. The account trial downloads the first ten transactions without a card; longer files need a fresh paid upload for complete output. Results expire within 24 hours.

Try a real free conversion See one-time packs

Written by Zijian Xiao. Examples are synthetic. Review all extracted results against your original source file.