My bank only offers CSV downloads — here's how to use it in QuickBooks

First, decide which path you need

There are two ways to get bank CSV data into QuickBooks, and the right one depends on which product you run.

Path 1 — Direct CSV import. QuickBooks Online has a built-in CSV/Excel uploader. If you are on QBO and your file is small and clean, you may not need anything else. QuickBooks Desktop does not import raw CSV bank statements through the standard menus (its Excel import is for lists like customers and the chart of accounts, not bank transactions), so Desktop users almost always need Path 2.

Path 2 — Convert CSV to a QBO/OFX file. A .QBO (Web Connect) file is the same format your bank would have given you if it supported QuickBooks directly. It works for both QuickBooks Online and QuickBooks Desktop, it carries a unique ID per transaction so re-imports don't duplicate, and it sidesteps the column-mapping and file-size headaches of the direct CSV route. This is the more robust option, especially for Desktop or for large statements.

• Small, tidy CSV + QuickBooks Online → try the direct import first (Path 1).
• QuickBooks Desktop → you'll need a .QBO file (Path 2); Desktop can't import raw bank CSVs.
• Messy multi-column export, thousands of rows, or recurring monthly imports → convert to QBO (Path 2).

Path 1: Import the CSV directly into QuickBooks Online

QuickBooks Online accepts CSV (and Excel) bank uploads in one of two shapes. Get your file into one of these before you start:

Once your CSV matches one of those formats, here is the import flow inside QuickBooks Online:

Watch the limits. QuickBooks Online caps a single CSV upload at roughly 350 KB and around 1,000 to 1,500 transactions per import. If your statement is larger, split it by month or date range and import in batches. Also strip out running-balance columns, blank rows, currency symbols, and any header/footer text the bank tacked on — those are the most common reasons the uploader chokes or maps columns wrong.

• 3-column format: Date, Description, Amount — where money in is a positive number and money out is negative.
• 4-column format: Date, Description, Credit (money in), Debit (money out) — amounts as positive numbers in separate columns.
• In QuickBooks Online, go to Transactions > Bank transactions (older layouts: Bookkeeping > Transactions > Bank transactions).
• Select the account the transactions should land in, then open the Link account dropdown and choose Upload from file.
• Drag in your CSV (or browse to it), click Continue, and pick the target QuickBooks bank account.
• Map your columns: tell QuickBooks which column is the date, the description, and the amount(s).
• Set the date format explicitly (for example MM/DD/YYYY vs DD/MM/YYYY) — this is the single most common cause of wrong or rejected dates.
• Review the preview (confirm income shows positive and expenses negative), select the rows to import, and confirm. Transactions land in the For review tab to be categorized and matched.

Path 2: Convert your CSV to a QBO (Web Connect) file

If you are on QuickBooks Desktop, or the direct import is fighting you, convert the CSV into a .QBO file. A QBO file is built on OFX 1.0.2 — an SGML-based format (note: not XML; it uses SGML-style tags that often are not closed) wrapped with a few Intuit-specific extensions. For QuickBooks to accept it as a Web Connect file, it needs a valid INTU.BID (the Intuit Bank ID that identifies the financial institution) plus correctly structured account, statement, and transaction blocks, with dates in YYYYMMDD form. Hand-editing this is error-prone, which is exactly what converters automate.

To convert without sending your statements to a third-party server, drop your CSV (or Excel file) into LedgerBridge. It runs entirely in your browser — your data never leaves your computer — maps your columns to the OFX fields, writes a valid INTU.BID and a unique FITID for every transaction, and gives you back a .QBO (or .QFX/.OFX) file. It is free to try; a one-time $29 Pro unlock removes the row limit for large or recurring statements.

About FITID and duplicates: every transaction in a QBO file carries a FITID (Financial Institution Transaction ID), and QuickBooks uses it to deduplicate. Import the same file twice and matching FITIDs are silently skipped rather than doubled — so a generated FITID must be stable and unique per transaction. A good converter handles this; if you ever build files by hand, never reuse a FITID across different transactions, and never change the FITID for a transaction you have already imported.

• What a valid QBO file needs: an OFX 1.0.2 (SGML) header, a valid INTU.BID, account/statement blocks, dates as YYYYMMDD, and a unique FITID per transaction.
• Why QBO beats raw CSV for recurring imports: FITID dedup means re-downloading an overlapping month won't create duplicates.

Import the QBO file into QuickBooks Desktop

Once you have a .QBO file, QuickBooks Desktop reads it through Web Connect — the same channel a supported bank would use. Back up your company file first, since an import cannot be undone.

If Desktop says the file is not recognized or the bank is not supported, it is almost always the INTU.BID, the date format, or a malformed header rather than your actual transaction data. Regenerating the file with a converter that sets a valid bank ID usually clears it.

Importing a QBO into QuickBooks Online instead? Use the same Upload from file flow as Path 1, but choose your .QBO file. QBO online treats it as a bank file and skips the manual column mapping, since the fields are already defined inside the OFX structure.

• In QuickBooks Desktop, go to File > Utilities > Import > Web Connect Files (or Banking > Bank Feeds > Import Web Connect File).
• Browse to your .QBO file and open it.
• When prompted, choose Use an existing QuickBooks account and pick the right bank or credit card account (or create a new one). Map it carefully so transactions don't land in the wrong register.
• If the target account shows a yellow lightning/strike icon, it is connected to Online Services — disconnect it before importing a QBO file.
• QuickBooks processes the file and the transactions appear in the Bank Feeds Center for review, matching, and adding to the register.

Avoid the common failures

Most CSV-to-QuickBooks problems come down to a handful of fixable issues. Run through this checklist before you import.

If a direct CSV import keeps failing in QuickBooks Online despite clean data, that is a strong signal to switch to the QBO route instead — a properly formed Web Connect file removes the mapping and file-size variables entirely.

• Date format: pick one format and use it everywhere; tell QBO which one you're using, or use YYYYMMDD inside a QBO file.
• Amount signs: in 3-column format, deposits are positive and withdrawals negative — don't mix conventions.
• Extra junk: delete running-balance columns, blank rows, merged cells, summary/footer lines, currency symbols, and thousands separators (send plain numbers like 1234.56).
• Encoding: save plain CSV (UTF-8) rather than a styled spreadsheet, and strip unusual special characters.
• Size: keep QBO Online uploads under ~350 KB and ~1,000 to 1,500 rows per import; split big statements by month.
• Re-imports: rely on FITID dedup in a QBO file rather than re-uploading edited CSVs; for direct CSV imports there is no FITID, so avoid overlapping date ranges.

Frequently asked questions

Related guides

• How to convert a CSV to QBO (step by step)
• How to import bank transactions into QuickBooks Desktop
• How to import bank transactions into QuickBooks Online
• QuickBooks Web Connect discontinued by your bank? Here's the fix
• What is a QBO file?
• QBO vs QFX vs OFX