What is a QuickBooks Web Connect file?
Two 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.
Web Connect and Direct Connect are different things
Direct Connect is a live link. QuickBooks talks to the bank’s servers directly, usually for a monthly fee, and pulls transactions on demand.
Web Connect is file-based. You log into your bank’s website, download a .qbo file, and import it into QuickBooks by hand. No live connection, usually no fee.
Both go through the same banking feed once inside QuickBooks, with the same matching and duplicate detection. The difference is entirely in how the data arrives.
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.x 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:102Inside are the account it belongs to, the period it covers, and the transactions with their identifiers. If you open a .qbo and see HTML, the download failed and the extension is the only correct thing about the file.
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 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. Statements as PDFs go back much further. 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.
Express Web Connect is a third thing
Alongside Direct Connect and Web Connect there is Express Web Connect, where Intuit logs into the bank’s website on your behalf and retrieves the data. It looks like a live connection from inside QuickBooks and behaves like scraping, because that is broadly what it is.
It matters here for one reason: it breaks when the bank changes its website or its authentication, and it breaks silently — the feed simply stops bringing anything in. When a connection has quietly gone stale for a few weeks, the missing period is exactly what a converted statement is for.
The extension is not the format
A file named .qbo is a Web Connect file only if its contents say so. Two 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, and it opens in a browser as a tidy XML tree — which is the tell.
Opening the file in a text editor and checking that the first line reads OFXHEADER:100 takes five seconds and rules out a whole afternoon of theories.
Related
What is INTU.BID, and why does QuickBooks check it?
One tag inside a .qbo file decides whether QuickBooks accepts it. What the number is, where to find yours, and what to do when your bank has none.
ReadQBO vs QFX vs OFX vs QIF: which one does your software need?
Four formats, three of them nearly the same file with different requirements. What separates them, and which your accounting package will actually accept.
ReadQuickBooks error OL-301: what causes it, and how to fix it
OL-301 reads like a connection failure and usually is not. What the error actually means, the four causes in order of likelihood, and how to fix each.
Read