QuickBooks Desktop import checklist: prepare and test a transaction file

Check your downloaded records, account identity, dates, signs, overlapping periods and statement balance before testing a Desktop import.

Last checked: November 9, 2026

Choose a supported Desktop route

Intuit describes Web Connect as a bank-website .qbo download; QFX and QIF are not accepted in that route. Direct Connect is a configured connection and is a separate workflow. Confirm what your bank and installed Desktop edition support. A QuickBooks Online integration does not establish Desktop file support, and conversion cannot restore a discontinued bank connection.

Prepare the transaction source

Keep an untouched original and work with one account and currency. A native CSV is preferable to extracting a PDF when it covers the period. If only PDF is available, first extract or transcribe its transaction rows and compare them with the document. Excel’s PDF connector can detect tables where installed; Tabula can select and preview regions of text PDFs but cannot handle scans. For a scan, verify OCR output against the image. CSVQBO accepts CSV or values-only single-sheet XLSX, not PDF or legacy XLS.

Check dates, signs and the closing balance

Confirm date order and decimal separators using unambiguous source values. Inspect withdrawals, deposits, refunds and card payments. If both Amount and split Debit/Credit fields exist, CSVQBO uses Amount first; split values use credit minus debit. Remove headings and summary totals from the transaction set. Reconcile opening balance plus signed activity against the actual closing ledger balance and check source rows even if the arithmetic agrees. A partial-period trial needs the real balance for its included period.

Compare overlap with entries already recorded

Before importing another file, compare its transactions with entries already recorded in Desktop. CSVQBO cannot inspect your company file, and duplicate prevention must be checked in the destination software. Keep an import log of accounts, source files and date ranges. Review overlapping periods and genuine repeated payments before removing rows. Optional exact-row deduplication of the uploaded file does not establish that those transactions are absent from Desktop.

Supply the real account details and test a small import

For generated QBO, QFX or OFX, supply your bank/account identifiers, FID, organization, authorized Intuit BID, currency, account type and actual ledger balance at the latest included date. Back up the company file before an import. Start with a small, non-overlapping period, choose the correct destination account and inspect the imported dates, signs, count and balances before continuing. Acceptance depends on the bank and software and has not been verified in a live importer; generation is not Intuit certification.

Where CSVQBO fits

CSVQBO normalizes CSV/XLSX and generates QBO, QFX or OFX as a separate step. Sign up for a first-10-transaction trial with preview and downloads, no card. A longer file requires a fresh paid upload for full output. Limits are 15 MiB and 3,000 transactions; formulas and legacy XLS are unsupported. See pricing and FAQ.

Pricing · FAQ

Try a real free conversion See one-time packs FAQ

Written by Zijian Xiao; verify the bank-by-bank sources and your original records before using an export.