Three things in QuickBooks are called bank connections and only one of them involves a file. Which one your bank supports decides whether converting a statement is even possible, and what to do when the connection stops working.
The three ways QuickBooks gets bank data
Web Connect is file-based. You log into your bank’s website, download a .qbo file, and import it into QuickBooks yourself. Nothing in QuickBooks holds your bank login, and nothing happens until you import the next file.
Direct Connect is a live link. QuickBooks Desktop talks to the bank’s OFX server directly, often with a separate PIN or login the bank issues for the purpose, and sometimes for a monthly fee. It is the only one of the three that is two-way, which is why it can also support bill payment and transfers from inside QuickBooks.
Express Web Connect is aggregation: Intuit’s service signs into the bank’s website with your ordinary online banking credentials and retrieves the transactions for you. It looks like a live connection from inside the product and behaves like one until the bank changes its website or its sign-in.
| Web Connect | Direct Connect | Express Web Connect | |
|---|---|---|---|
| How data arrives | You download a file and import it | QuickBooks queries the bank’s OFX server | Intuit’s service signs into online banking |
| File involved | Yes: .qbo for QuickBooks, .qfx for Quicken | No | No |
| Products | QuickBooks Desktop, QuickBooks Online, Quicken | QuickBooks Desktop, Quicken | Quicken and QuickBooks Online’s feeds; Desktop depends on the bank |
| Credentials | Only on the bank’s site | Often a separate PIN from the bank | Your online banking login |
| Typical failure | Wrong file or bank ID | Server or enrolment problem | Stops silently when the bank’s site changes |
All three end up in the same place, the bank feed, with the same matching and duplicate detection. The bank decides which ones it offers; Intuit’s help for QuickBooks Desktop describes setting up an account with Direct Connect where the bank supports it and falling back to Web Connect where it does not.
Where the bank supports Web Connect but only offers statements as PDFs for older periods, you can produce a Web Connect file from a statement PDF and import it the same way.
What is actually in the file
A Web Connect file is OFX 1.0.2, the SGML dialect, with Intuit’s bank ID tag added. It opens in any text editor and starts with a header block rather than markup:
OFXHEADER:100
DATA:OFXSGML
VERSION:102
SECURITY:NONE
ENCODING:USASCII
CHARSET:1252
COMPRESSION:NONE
OLDFILEUID:NONE
NEWFILEUID:NONE
<OFX>
<SIGNONMSGSRSV1><SONRS> ... <INTU.BID>12345 ... </SONRS></SIGNONMSGSRSV1>
<BANKMSGSRSV1><STMTTRNRS><STMTRS>
<CURDEF>USD
<BANKACCTFROM><BANKID>...<ACCTID>...<ACCTTYPE>CHECKING</BANKACCTFROM>
<BANKTRANLIST><DTSTART>20260301<DTEND>20260331 ... </BANKTRANLIST>
<LEDGERBAL><BALAMT>2410.55<DTASOF>20260331</LEDGERBAL>
</STMTRS></STMTTRNRS></BANKMSGSRSV1>
</OFX>Inside are the institution and its Intuit bank ID, the account the file belongs to, the period it covers, the transactions with their identifiers, and the closing balance. A credit card file has the same shape with card-specific blocks, CCSTMTRS and CCACCTFROM, in place of the bank ones. If you open a .qbo and see HTML, the download failed and the extension is the only correct thing about the file.
Importing one
- 1QuickBooks Desktop: File → Utilities → Import → Web Connect Files, then choose the .qbo.
- 2Desktop asks which account the transactions belong to. Choose your existing account rather than letting it create a new one, or the transactions land in a duplicate account.
- 3Review the transactions in Bank Feeds, match or add them, and reconcile.
- 4QuickBooks Online: Transactions → Bank transactions → Link account → Upload from file, then pick the account and review in the For review tab.
When your account is not in the list
In Desktop, an account already set up for a different connection, or linked to a different institution, may not be offered as a destination for the file. Intuit’s usual fix is to deactivate the account’s online services in its bank feed settings, then import again and link it.
Why it matters which one your bank offers
A bank enrolled in Web Connect has an Intuit bank ID, which means a QBO file for that bank can be produced, including from a PDF statement for a period the download no longer covers.
A bank not enrolled has no such ID, so no valid QBO can exist for it at all. That is not a converter limitation and no tool gets around it. CSV or plain OFX into QuickBooks Online, or IIF into Desktop, are the routes that remain.
The gap Web Connect leaves
Bank download windows are short, often ninety days, sometimes a year or two. Statements as PDFs usually go back several years. So the transactions you most often need, for a catch-up or a prior year, are precisely the ones the Web Connect download will not give you.
Converting the statement to a QBO with the correct bank ID closes that gap, and the file imports through the same menu as one the bank issued. Import the older periods before the ones the bank feed already holds, and stop the day before the feed’s first transaction.
Express Web Connect breaks quietly
Because aggregation depends on the bank’s website, it breaks when the bank changes that website or its authentication, and it breaks silently: the feed simply stops bringing anything in. Banks also change providers or withdraw from Intuit’s programmes entirely, and a connection that worked for years ends on a date announced in an email nobody read.
When a connection has quietly gone stale for a few weeks, the missing period is exactly what a Web Connect file, downloaded or converted from the statement, is for. Check the last date the feed brought in before importing, so the file and the feed do not overlap.
The extension is not the format
A file named .qbo is a Web Connect file only if its contents say so. Several things routinely arrive wearing that extension and are not.
- An HTML page. A bank portal whose session expired serves an error page, and the browser saves it under the name it was going to use.
- An OFX 2.x file. Valid OFX, wrong dialect for QuickBooks Desktop, and it opens in a browser as a tidy XML tree, which is the tell.
- A plain OFX renamed to .qbo. Everything looks right except that there is no INTU.BID line, and the import fails on the bank check.
- A .qfx renamed to .qbo. It carries the bank’s Quicken ID, which QuickBooks may not recognise.
Opening the file in a text editor, checking that the first line reads OFXHEADER:100 and that an INTU.BID line is present, takes thirty seconds and rules out a whole afternoon of theories.