Why QuickBooks says “The uploaded file isn’t a valid Web Connect file”
QuickBooks Online gives this one message for different faults and doesn’t say which. We imported test files into a QuickBooks Online sandbox company (US, October 2026), and two things in a file brought it up:
- No closing balance. A file without the
<LEDGERBAL>block was refused, even with every transaction in it right. The OFX standard requires the block, and some converters leave it out when they don’t know the balance. - A UTF-8 header. A file whose header said
ENCODING:UTF-8was refused too. The fixed copy saysENCODING:USASCII, which QuickBooks Online took.
Some files can’t be read at all, and the checker looks for those too: a download that didn’t finish (the file stops before </OFX>), a web page saved in place of the file (often the bank’s sign-in page), a PDF or CSV renamed to .qbo, and transactions without a date or an amount.
For QuickBooks Desktop, Intuit’s help page on fixing Web Connect import errors says a .qbo file is the only type Web Connect can read, puts other failures down to incomplete files, changes at the bank or a setting in the company file, and suggests importing into a test company to tell them apart. A file that passes every check here can still be refused for those reasons.
How to open a QFX or QBO file without Quicken or QuickBooks
Drop it above: you get the account, the period, the money in and out, the closing balance and every transaction in a table. A .qfx or .qbo file is plain text, so a text editor opens it too, but you see the OFX tags (<STMTTRN>, <TRNAMT>…) rather than a table. Excel doesn’t open these files; to work with the rows in a spreadsheet, use Convert to Excel or CSV under the table.
Save a QFX or QBO file as a PDF
Open the file above and choose Print or save as PDF. The printout has the account summary and the transactions, without the rest of the page. In the print dialog, pick Save as PDF as the printer.
What the fixed copy changes, and what it keeps
The fixed copy is written by the same code as our converters’ QBO, QFX and OFX files, which imported cleanly in our QuickBooks Online tests:
- The standard OFX 1.02 header, saying
ENCODING:USASCII. - A closing balance: the file’s own, or the one you type. With none, it writes 0.00, which QuickBooks shows as the bank balance.
- Plain ASCII text: in our tests QuickBooks Online showed every accented letter or curly quote as “?”, so Café becomes Cafe.
- An ID on every transaction: kept where the bank gave one, made from the date, amount and description where it didn’t, and made unique where two different transactions shared one.
- Names over 32 characters (the OFX limit) cut to 32, with the whole text in the memo; a bare “&” written as
&.
Every transaction’s date, amount and description stays as it was. It can’t fix a file that was cut short or a bank’s error message, and it never makes up an Intuit bank ID.
What the checks are based on
Each finding says where it comes from. “Seen in our QuickBooks Online tests” means we imported such a file into a QuickBooks Online sandbox company and saw what happened. “OFX standard” means it breaks a rule of the format, without our having seen what QuickBooks does about it. We haven’t tested QuickBooks Desktop or Quicken.
Related
What a QBO file is · Importing bank statements into QuickBooks Online · QBO to Excel · QFX to QBO · CSV to QBO · PDF bank statement to QBO