LedgerBridge

QuickBooks Web Connect discontinued by your bank? Here's the fix

If your bank just dropped support for QuickBooks Web Connect (the .QBO download) or Direct Connect, you are not alone. Banks have been quietly retiring these older connection methods, and Intuit is sunsetting Desktop bank feeds on a rolling three-year schedule (2022 editions lost them in May 2025, 2023 editions in May 2026). The result is the same for you: the "Download to QuickBooks" button is gone and you are left with a plain CSV, Excel, or PDF statement.

The frustrating part is that QuickBooks Desktop and QuickBooks Online still happily import a .QBO file the moment you have one. The bank just stopped generating it. This guide explains exactly what changed, why a CSV download is not a dead end, and how to rebuild a valid .QBO (Web Connect) file from the data your bank still gives you. The fastest fix is to convert your CSV or Excel export into a proper OFX-format .QBO file and import it the way you always did. You can do that locally in your browser with LedgerBridge by dropping your CSV into the converter, but the underlying mechanics matter, so we cover those first.

What "Web Connect discontinued" actually means

Web Connect is the method where you log into your bank's website, click a "Download to QuickBooks (.QBO)" button, and import that file by hand. It is different from Direct Connect (a paid, two-way link inside QuickBooks) and from Express Web Connect (the automated bank feed in QuickBooks Online that relies on Intuit's aggregator). When people say Web Connect was "discontinued," one of three things has usually happened.

First, your bank removed the .QBO / QuickBooks download option entirely and now offers only CSV, Excel (.xlsx), or PDF. Second, your bank discontinued Direct Connect (Bank of America did exactly this) or your Desktop version aged past Intuit's three-year bank-feed support window, so the automated feed stopped and you are told to import files manually. Third, the connection still exists but breaks, because the .QBO files banks generate use an aging format and Intuit periodically tightens what it accepts.

The good news in every case: QuickBooks itself has not removed .QBO import. The format is the same OFX 1.0.2 (SGML) standard it has always been. If you can produce a well-formed .QBO file, QuickBooks Desktop and QuickBooks Online will import it. The only thing you lost is the bank pressing the button for you.

Why a .QBO file is just OFX in disguise (and why that helps you)

A .QBO file is not a proprietary binary. Open one in a text editor and you will see a readable OFX document. The header is plain SGML key-value pairs (OFXHEADER:100, DATA:OFXSGML, VERSION:102), and the body is tagged transaction data. That is why it is reconstructible from a CSV: every field QuickBooks needs is something your bank statement already contains.

Two pieces of metadata make a .QBO file specifically a QuickBooks file rather than a generic OFX file. The first is INTU.BID, the Intuit Bank ID that tells QuickBooks which financial institution the file belongs to; without a recognized value, Desktop can throw an "unable to verify the financial institution" error. The second is FITID, a unique Financial Institution Transaction ID on every transaction. QuickBooks uses FITID for deduplication: import the same transaction twice and matching FITIDs are skipped rather than double-counted, which is exactly what you want when you reimport an overlapping date range.

Because the format is open, a converter can read your CSV columns (date, description, amount) and emit a valid OFX 1.0.2 body with stable, deterministic FITIDs and the correct header. That is the entire job.

  • OFXHEADER:100 / DATA:OFXSGML / VERSION:102 — the SGML header lines QuickBooks expects; a wrong version number or missing line triggers import failure.
  • INTU.BID — the Intuit Bank ID; QuickBooks rejects or cannot verify files without a recognized value.
  • FITID — one unique ID per transaction; QuickBooks dedups on it, so stable IDs prevent duplicates on reimport.

Step 1: Download whatever your bank still offers

Log into your bank's website (not QuickBooks) and export your transactions in whatever format remains available. Pick the widest date range you can; FITID deduplication means overlapping imports are safe to redo later. In rough order of usefulness for conversion:

  • CSV is ideal — structured, machine-readable, and it contains the date, description, and amount columns a converter needs.
  • Excel (.xlsx or .xls) works just as well; most converters read it directly.
  • OFX or QFX, if still offered, can often be rebranded into .QBO with minimal effort.
  • PDF is the worst case: it is unstructured, so you may need to copy the transaction table into a spreadsheet first.

Step 2: Convert the CSV into a valid .QBO file

This is where you replace the button your bank removed. A converter maps your spreadsheet columns to OFX fields and writes a compliant .QBO file. With LedgerBridge, drop your CSV or Excel file into the converter in your browser; nothing is uploaded to a server, so your bank data never leaves your machine. You map the date, description, and amount columns once, confirm the account type (bank or credit card), and export.

A correct conversion produces a file with the proper OFX 1.0.2 SGML header, an INTU.BID value QuickBooks will accept, your account identifiers, and one FITID per transaction. Stable FITIDs are the detail that separates a good converter from a sloppy one: if a tool regenerates random IDs on every export, reimporting the same month creates duplicates. LedgerBridge derives FITIDs deterministically from the transaction data so re-runs stay clean.

Watch the sign convention while you map columns. Withdrawals and debits must be negative; deposits positive. If every transaction lands on the wrong side of the ledger, the amount column or its sign mapping is reversed. If your CSV uses separate Debit and Credit columns, map both.

  • Map Date, Description, and Amount (or Debit/Credit) columns to the OFX fields.
  • Confirm the account type: checking/savings (bank) vs. credit card — they use different OFX statement blocks.
  • Verify the sign convention: debits negative, deposits positive.
  • Export and keep the file; reimporting it is harmless thanks to FITID dedup.

Step 3: Import the .QBO into QuickBooks

In QuickBooks Desktop, go to File > Utilities > Import > Web Connect Files, then select your converted .QBO (you can also reach it via Banking > Bank Feeds > Import Web Connect Files). Desktop routes the transactions to the matching account, or prompts you to create or link one on first import. Review the items in the Bank Feeds Center, then add or match them to your register. Desktop does not enforce a 90-day limit, so older history loads fine here.

In QuickBooks Online, go to Transactions > Bank transactions, choose the account, click Upload from file (or drag and drop), and pick the .QBO. Mind QBO's upload constraints: a single manual upload is capped at 1,000 transactions and the file must be 350 KB or less. Although manual uploads are not bound by the 90-day automatic-feed window, large or historical statements should be split by date range to stay under the row and size limits. After upload, rows land in the For review tab where you categorize and accept them.

If QuickBooks says the file is unrecognized or the institution cannot be verified, the header or INTU.BID is the usual culprit; reconvert with a tool that writes a known-good header. If transactions look duplicated, your FITIDs are not stable across exports.

  • Desktop: File > Utilities > Import > Web Connect Files (or Banking > Bank Feeds > Import Web Connect Files).
  • Online: Transactions > Bank transactions > Upload from file; max 1,000 rows and 350 KB per upload.
  • Split large/historical files by date range before uploading to QBO.
  • Unrecognized file = header/INTU.BID issue; duplicates = unstable FITIDs.

Convert your CSV now →

Frequently asked questions

Did Intuit remove Web Connect import from QuickBooks?

No. QuickBooks Desktop still imports .QBO files via File > Utilities > Import > Web Connect Files, and QuickBooks Online still accepts .QBO uploads on the Bank transactions screen. What changed is that many banks stopped offering the .QBO download or discontinued Direct Connect, and Intuit sunsets Desktop bank feeds three years after each version's release. The import feature itself is intact, so once you produce a valid .QBO file from your CSV, the normal workflow works again.

My bank only gives me CSV now. Can I still get transactions into QuickBooks?

Yes. A CSV contains the same date, description, and amount data a .QBO file does, just in a different layout. Convert the CSV into an OFX-format .QBO file with the proper header, INTU.BID, and per-transaction FITIDs, then import it normally. LedgerBridge does this conversion in your browser, so your bank data stays on your device and is never uploaded.

Why does QuickBooks say it can't verify my financial institution?

That error almost always means the INTU.BID (Intuit Bank ID) or the OFX header in the file is missing, malformed, or not recognized. Banks' own exports occasionally trip this after Intuit tightens validation. Reconverting the file with a tool that writes a known-good OFX 1.0.2 header and a valid INTU.BID typically clears it.

Will reimporting overlapping dates create duplicate transactions?

Not if the file uses stable FITIDs. QuickBooks deduplicates on the FITID (Financial Institution Transaction ID), so transactions it has already seen are skipped on reimport. Problems arise only when a converter assigns random FITIDs on each export, making the same transaction look new. Use a converter that derives FITIDs deterministically from the transaction data.

Are there limits when uploading a .QBO file to QuickBooks Online?

Yes. QuickBooks Online caps a single manual upload at 1,000 transactions and 350 KB. The automatic bank feed only pulls about 90 days of history, but manual .QBO/CSV uploads are not bound by that window, so you can load older transactions as long as you split large statements into smaller date ranges. QuickBooks Desktop does not enforce these limits, making it easier for bulk historical loads.

Related guides

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