LedgerBridge

How to import bank transactions into QuickBooks Online

QuickBooks Online (QBO) is happiest when transactions flow in automatically through a connected bank feed. But feeds break: banks change their login security, switch aggregation providers, go down for maintenance, or simply stop syncing a single account while every other account keeps working. When that happens, you do not have to wait for support, you can import the transactions yourself in a few minutes.

This guide walks through every reliable way to get transactions into QuickBooks Online and QuickBooks Desktop: the built-in CSV upload, importing a bank-issued QBO (Web Connect) file, and the troubleshooting path when the live feed quietly fails. Along the way we cover the technical gotchas that trip people up, the per-file transaction limit, date-format mismatches, and how QuickBooks uses FITID and INTU.BID under the hood, so your import lands cleanly the first time. Where a converter genuinely saves you time (for example, turning a messy bank CSV into a QBO file QuickBooks will accept), we point to LedgerBridge, which runs entirely in your browser so your statement data never leaves your machine.

First, decide which import path you actually need

QuickBooks gives you three doors, and picking the right one before you start saves a lot of backtracking.

Manual CSV upload (QBO Online): Best when you can export a transaction list from your bank as CSV or Excel and you only need the basics (date, description, amount). QuickBooks Online accepts a simple 3-column or 4-column layout and maps it to a bank or credit-card account you have already set up.

QBO / Web Connect import: A .qbo file is the bank-issued format built on the OFX (Open Financial Exchange) standard. QuickBooks treats it as a richer, more reliable import than CSV because it carries a unique ID for every transaction and an institution identifier. If your bank offers a 'QuickBooks Web Connect (.QBO)' download, prefer it over CSV. If your bank only gives you CSV, you can convert that CSV into a .qbo file (more on that below).

Re-establish the live feed: If the goal is ongoing automation rather than a one-time catch-up, fixing the bank connection itself is the real fix. Use a manual import to plug the gap, then reconnect the feed so future transactions sync on their own.

  • Only need date/description/amount and your bank exports CSV: use the CSV upload (Method 1).
  • Your bank offers a .QBO/Web Connect download: import the QBO file directly (Method 2).
  • Bank only gives CSV but you want dedup and repeat imports: convert the CSV to QBO first.
  • You want ongoing automation: fix the live feed, and bridge the gap with a manual import.

Method 1: Upload a CSV or Excel file in QuickBooks Online

This is the fastest path when your bank only exports CSV or Excel and you do not need the extra metadata a QBO file carries.

QuickBooks Online accepts two column layouts. The 3-column format is Date, Description, Amount, where a single Amount column uses positive numbers for money in and negative numbers for money out. The 4-column format is Date, Description, Credit (money in), Debit (money out). Your first row must be headers, and every date in the file has to use one consistent format. A few cleanup rules from Intuit's own docs: remove currency symbols and thousands separators from amount columns, remove stray numbers from the Description column, and leave any amount cell that would just be 0 blank.

  • In QuickBooks Online, go to Transactions then Bank transactions (older accounts call this the Banking menu).
  • Select the bank or credit-card account you are importing into. If the account does not exist yet, create it first under your Chart of Accounts.
  • Click the dropdown next to Link account (or the Upload icon) and choose Upload from file.
  • Browse to your CSV or Excel file and click Continue.
  • Pick the QuickBooks account that the transactions belong to.
  • Map your file's columns to QuickBooks fields (Date, Description, Amount, or Credit/Debit). Confirm the date format here, MM/DD/YYYY versus DD/MM/YYYY is the single most common cause of a botched import.
  • Review the preview, deselect anything you do not want, and click Yes / Import.
  • Go to the For review tab to categorize and accept the new transactions into your books.

Method 2: Import a QBO (Web Connect) file

A .qbo file is QuickBooks' native bank-import format. Because it follows the OFX 1.0.2 specification (an SGML-based format, not modern XML), it carries two things a plain CSV cannot: an INTU.BID code that tells QuickBooks which financial institution the file is from, and a FITID (Financial Institution Transaction ID) on every single transaction. QuickBooks uses the FITID to deduplicate, so re-importing an overlapping date range will not create double entries as long as the IDs are stable.

In QuickBooks Online, importing a .qbo uses the same Upload from file flow as Method 1, just select the .qbo file instead of a CSV. In QuickBooks Desktop, the path is different and worth memorizing: File > Utilities > Import > Web Connect Files, then browse to the .qbo and choose to add it to an existing account or create a new one. Imported transactions land in the Bank Feeds center for review. One Desktop prerequisite: if the account shows a yellow strike icon it is still connected to Online Services, and you must disconnect it before a manual Web Connect import will go through.

Two errors are common here. If QuickBooks says it does not recognize the file or the financial institution, that is almost always an INTU.BID mismatch, the bank ID in the file does not line up with what QuickBooks expects for that account. If transactions look duplicated, the FITID values from your source were not unique or stable. Both are fixable when you generate the file yourself rather than relying on a hand-edited export.

  • QuickBooks Online: Upload from file under Bank transactions, then select the .qbo.
  • QuickBooks Desktop: File > Utilities > Import > Web Connect Files, then pick the .qbo.
  • Desktop only: disconnect the account from Online Services first if it shows a yellow strike icon.
  • Desktop accepts .QBO (Web Connect), .QFX (Quicken), and .OFX files through this same menu.

When your bank only gives you CSV (converting to QBO)

Plenty of banks, especially smaller credit unions and non-US institutions, have dropped or never offered a QuickBooks Web Connect download. You are left with a CSV that QuickBooks Online will accept for a basic upload but that lacks the FITID-based dedup and institution metadata of a real .qbo file. For one-off imports the CSV route is fine; for repeated imports into the same account, a proper QBO file is far more reliable.

This is exactly the gap a converter fills. Drop your CSV (or Excel) into LedgerBridge, map your columns once, and it produces a standards-compliant QBO/QFX/OFX file with valid FITID values and the right institution identifier, so QuickBooks recognizes it and dedupes correctly. The whole conversion happens in your browser, nothing is uploaded to a server, which matters when the file is a full bank statement. It is free to try, with a one-time $29 Pro unlock for unlimited rows if you are processing large statements.

  • Export your transactions from the bank as CSV or Excel.
  • Open LedgerBridge in your browser and drop the file in.
  • Map Date, Description, and Amount (or Credit/Debit) columns, and confirm the date format.
  • Download the generated .qbo file.
  • Import it via File > Utilities > Import > Web Connect Files in Desktop, or Upload from file in QuickBooks Online.

Limits, duplicates, and other gotchas to plan around

QuickBooks Online caps a single CSV upload at around 1,000 lines (one transaction per line) and roughly 350 KB per file. If your statement is larger, the import can truncate or reject it. Split the data into multiple files by date range, or generate a QBO file, which handles larger volumes more gracefully than CSV.

Be aware of two timing issues too. QuickBooks generally cannot pull bank-fed transactions older than 90 days, so genuinely old history almost always has to come in by manual CSV or QBO import. And if you import to cover a gap and then the live feed comes back online, you can end up with duplicates for the overlapping dates, with a real QBO file the FITID dedup protects you, but with plain CSV you may need to delete the doubled entries.

Finally, remember that an import only adds transactions to the For review queue. They do not affect your registers, reports, or reconciliations until you categorize and accept them, so the job is not finished at the upload step.

  • About 1,000 lines and ~350 KB maximum per CSV upload, split larger statements or use a QBO file.
  • No currency symbols or commas in amount fields; keep one consistent date format throughout.
  • Bank feeds usually cannot fetch transactions older than 90 days, import those manually.
  • Overlapping ranges are safe with a real QBO file (FITID dedup) but will duplicate with plain CSV.
  • Imported items sit in For review until you categorize and accept them.

Convert your CSV now →

Frequently asked questions

My bank feed stopped updating but everything looks connected. What should I do?

Bank feeds fail quietly when a bank changes its login security, enables new multi-factor authentication, or switches aggregation providers. First, go to Bank transactions and click Update to force a refresh, and check for any banner asking you to re-authenticate. If that does not work, disconnect and reconnect the account, and confirm the username and password QuickBooks has on file match your bank's website exactly. To fill the gap in the meantime, export the missing transactions from your bank and import them manually as CSV or QBO so your books stay current while the live feed is restored.

What is the difference between uploading a CSV and importing a QBO file?

A CSV is a plain spreadsheet with date, description, and amount, QuickBooks reads it but has no way to uniquely identify each transaction. A QBO (Web Connect) file follows the OFX standard and includes a FITID on every transaction plus an INTU.BID institution code. That lets QuickBooks deduplicate automatically and recognize the source bank. For a quick one-off, CSV is fine; for repeated imports into the same account, a QBO file prevents duplicates and is more reliable.

How do I import a QBO file into QuickBooks Desktop?

In QuickBooks Desktop, open your company file and go to File > Utilities > Import > Web Connect Files. Browse to your .qbo file, then choose to add it to an existing account or create a new one, and click Continue. The transactions appear in the Bank Feeds center for you to review and match. If the account shows a yellow strike icon it is still connected to Online Services and you must disconnect it first. In QuickBooks Online the path is different, you use the Upload from file option under Bank transactions and select the .qbo there.

Why does QuickBooks say it does not recognize my QBO file or financial institution?

That error is almost always an INTU.BID mismatch, the bank identifier embedded in the .qbo file does not match what QuickBooks expects for that account. It can also happen if the file's OFX structure is malformed from manual editing. Generating the file with a converter that writes a valid INTU.BID and well-formed OFX, rather than hand-editing one, resolves this. We cover the recognition error in more depth in our file-not-recognized guide.

My statement has more than 1,000 transactions. How do I import all of them?

QuickBooks Online limits a single CSV upload to roughly 1,000 lines and about 350 KB. You have two options: split the CSV into multiple files by date range and import them one at a time, or convert the data into a QBO file, which handles larger transaction counts more gracefully. A converter like LedgerBridge can produce the QBO file in your browser, and with the one-time Pro unlock there is no row cap on the conversion itself.

Related guides

Not affiliated with Intuit/QuickBooks/Quicken/Xero. LedgerBridge is a file-conversion utility, not financial advice.