A working reference for Intuit Web Connect files: QBO versus QFX, the exact import path in QuickBooks Desktop and in Quicken, the five reasons an import is rejected, and what to do when your bank only publishes 90 days. Have older statements as PDFs? Upload them and export CSV, Excel or OFX.
Upload your bank statement
Drop file here or click to upload
PDF, JPG, PNG, BMP, HEIC, TIFF
Uploading...
A Web Connect file is a bank statement download written in Intuit's OFX based format, saved as .QBO for QuickBooks Desktop or .QFX for Quicken. Both hold the same transaction structure, plus Intuit identifiers (chiefly INTU.BID) that the software validates before it reads a single transaction. QuickBooks Desktop imports one through Banking, then Bank Feeds, then Import Web Connect Files, and .QBO is the only file type Web Connect reads. Because each product validates its own flavor, a QFX file will not import into QuickBooks Desktop and a QBO file will not import into Quicken, and renaming the extension changes nothing.
Web Connect looks like a plain file transfer and behaves like a licensing check. The transaction data is ordinary OFX that any parser can read, but the identifiers wrapped around it decide whether the import runs at all, and the error messages rarely name the real cause.
QuickBooks Desktop reads .QBO and Quicken reads .QFX. Both are OFX with Intuit tags, but each product validates its own flavor, so handing QuickBooks a QFX file fails even though the transactions inside are perfectly formed.
Quicken and QuickBooks read the FI block and the INTU.BID identifier first, and check them before touching the transaction list. When the value is missing or is not a registered institution, you get an inability to verify the financial institution rather than a useful message about the file.
If the QuickBooks Desktop account already has a bank feed attached, shown by the lightning icon in Lists, then Chart of Accounts, the Web Connect import is refused until the feed is deactivated on that account.
Every account and transaction inside a Web Connect file carries a unique identifier, so QuickBooks blocks a repeat import of the same .QBO to prevent duplicates. Helpful most of the time, and genuinely confusing when a first attempt imported only part of the file.
Opening a .QBO in a text editor to correct a date or an amount usually ends the import. Intuit's guidance is to download the file and import it without editing, because the structure and the identifiers have to arrive exactly as the bank wrote them.
Web Connect downloads are commonly capped between 90 days and 18 months depending on the institution, while PDF statements stay available for years. The history you actually need for a catch up or an audit usually sits past the edge of the download.
A genuine Web Connect file can only come from an institution that participates in the Intuit program, so when the account is closed, the window has passed, or the bank simply does not offer one, the practical route is to rebuild the transactions from the statement PDF and use each product's file import instead of its bank feed.
Export the transactions as CSV and map them to the layout the target expects: three or four columns for QuickBooks Online, the Quicken Windows column order, or the Mint style CSV that Quicken for Mac reads.
Software that reads the open OFX standard rather than the Intuit variant, including Xero, NetSuite, Sage Intacct, MS Money and Banktivity, takes the OFX export directly, with a FITID on every transaction and a LEDGERBAL closing balance.
Export XLSX when you need to check the extraction against the printed statement, split debits and credits into separate columns, or trim a file down to the rows a single upload will accept.
Upload up to 50 statements at a time and merge them into a single extraction, which is how a multi year catch up gets done without repeating the same download 24 times.
Every extracted transaction is shown against the source statement before export, so a misread amount is corrected on screen rather than inside an accounting file that has already posted.
Statements that arrive locked are handled without stripping them by hand, which matters when a year of downloads all carry the same bank applied password.
Drop in the PDF or scanned statements covering the period you need. Multiple files can go in together and be merged into one extraction.
Tip: Scans and photos work; the text does not have to be selectable.
Check the extracted dates, descriptions, amounts and running balance against the printed statement, and correct anything the page rendered oddly.
Tip: Check the closing balance first, since it validates every row above it.
Choose CSV for Quicken or QuickBooks Online file upload, OFX for software that reads the open standard, or XLSX for review and manual work.
Tip: Match the column layout to the importer before you upload, not after it errors.
Run the import through the file upload path rather than the bank feed, then reconcile against the statement closing balance to confirm nothing was dropped or doubled.
Tip: Import one account per file, and one period at a time.
A Web Connect file is a bank statement download in Intuit's OFX based format, saved as .QBO for QuickBooks Desktop or .QFX for Quicken. It contains the account details, a list of transactions each carrying a unique FITID, and a closing balance, wrapped in Intuit identifiers the software checks before importing.
In QuickBooks Desktop, a Web Connect file is the .QBO file you download from your bank and import by hand instead of using a live bank feed. Intuit states that .QBO is the only file type Web Connect can read, so a CSV, an OFX or a QFX renamed to .QBO will not work.
Download the .QBO file from your bank, then in QuickBooks go to Banking, select Bank Feeds, and select Import Web Connect Files. Pick the file and select Open, then choose an existing QuickBooks account or create a new one, select Continue, and review the transactions in the Bank Feeds Center.
It is Open Financial Exchange with Intuit extensions. Most files use OFX 1.x SGML syntax: colon delimited header lines such as OFXHEADER:100 and DATA:OFXSGML, then a signon block carrying INTU.BID, an account block, a BANKTRANLIST of STMTTRN transactions with dates as YYYYMMDD, and a LEDGERBAL closing balance.
They are the same design aimed at different products. QBO is the QuickBooks flavor, QFX is the Quicken flavor, and each application validates its own Intuit identifiers. The transaction structure is identical, so the files look interchangeable, but neither product accepts the other's file and renaming the extension does not convert it.
The usual causes are a file that is not truly in Web Connect format, such as a CSV or QFX renamed to .QBO, a bank identifier QuickBooks cannot verify, an account that still has a live bank feed attached and needs it deactivated first, or a repeat import of a file whose unique identifiers QuickBooks has already seen.
Web Connect is Intuit's manual download method: you sign in to your bank, download a .QBO file, and import it into QuickBooks yourself. It is the alternative to Direct Connect and Express Web Connect, which pull transactions automatically, and it is the fallback when a bank cannot be connected or you need more history than a feed offers.
Direct Connect is a two way link that pulls transactions automatically and can support bill pay, usually enabled by the bank and sometimes for a fee. Web Connect is one way and manual: you download a file and import it. Web Connect works wherever a bank publishes a QFX or QBO download, which is why it keeps working after a feed is retired.
Yes, both .QBO and .QFX are plain text, so any text editor will show the contents, and the FI block near the top holds the ORG, FID and INTU.BID values worth checking when an import fails. Do not save changes, because Intuit advises importing the file exactly as the bank produced it.
You can rebuild the transactions, but not the Intuit licensing identifiers, which only a participating institution can issue. The practical route is to convert the PDF to CSV and use the file upload path in QuickBooks Online or Quicken, or to export OFX for software outside the Intuit ecosystem such as Xero, NetSuite or Sage Intacct.
Yes. Recent QuickBooks Desktop releases ask you to sign in to your Intuit account inside the program before a .QBO import will run, so an import that used to work can start failing after a version update or on a machine where nobody has signed in.
It depends entirely on the institution, and the common range is 90 days to about 18 months. PDF statements are usually kept far longer, often seven years, which is why older periods are rebuilt from statements rather than downloaded.
The Quicken flavor in detail, including the INTU.BID tag.
The open specification both Web Connect flavors are built on.
The CSV layouts and limits QuickBooks accepts on upload.
The full route from a PDF statement to the Quicken register.
Diagnose the numbered CC and OL error codes.
Convert years of statements in a single pass.
Get started converting bank statements to OFX.
USD
per month
per month
$288 charged today
Choose speed vs accuracy when extracting
| Base AI Faster | 2,500 pages |
| Pro AI Best accuracy | 500 pages |
Scale statement conversion across your team with automation.
USD
per month
per month
$888 charged today
Choose speed vs accuracy when extracting
| Base AI Faster | 10,000 pages |
| Pro AI Best accuracy | 2,000 pages |
Enterprise-grade bank statement conversion and controls.
USD
per month
per month
$ charged today
Choose speed vs accuracy when extracting
| Base AI Faster | pages |
| Pro AI Best accuracy | pages |
