A QBO file not uploading to QuickBooks Online usually has one of four faults: an extension that doesn't match the contents, bank or account identifiers QuickBooks can't use, a card file sent to a bank account (or the reverse), or tags damaged during download. Find which screen the upload stopped on first, because that narrows it to one.
Where the QBO file upload stops in QuickBooks Online
The QBO upload in QuickBooks Online runs through a short series of screens: choose the file, choose the account, then review the transactions. The point where it stops tells you which part of the file to suspect.
A refusal on the first screen is about the file as a whole. A message after you pick an account is about the account. A review list with missing rows is about the lines inside.
Intuit's guide to manually uploading transactions sets the outer limits. It lists .csv, .txt, .qbo and .ofx as transaction files, says the file must be in English and 350 KB or less, and caps each upload at 1,000 lines. A QBO file over either cap fails before QuickBooks looks at a single transaction.
Use this map before you open the file:
| Where it stopped | What to suspect first |
|---|---|
| Selecting the file | Extension, size, line count, or a damaged file |
| After choosing the account | Account type in the file versus the account you picked |
| Review list is empty or short | Missing or broken transaction blocks |
| A message about a server or an update in progress | QuickBooks itself, not the file |
Write down the exact wording of any message. Two messages that sound alike can point to different causes, and the wording is what support will ask for.
Does the QBO file extension match what is inside?
A QBO file is a plain text file in the Open Financial Exchange layout, with the .qbo extension that tells QuickBooks to treat it as a Web Connect file. The extension only matters if the contents agree with it. A file renamed from .csv to .qbo still holds CSV rows, and the upload cannot read them as a QBO.
You can check this in a minute. Open the file in a plain text editor such as Notepad or TextEdit, not a spreadsheet. A real QBO file begins with a few header lines and then a run of angle-bracket tags such as <OFX>, <BANKMSGSRSV1> and <STMTTRN>. If you see commas between columns instead, someone renamed a CSV. If you see unreadable symbols, the file may be a PDF or a spreadsheet with the wrong extension.
Three renaming slips come up again and again:
- A CSV renamed to .qbo because someone heard QBO files need no column matching. Upload it as a CSV instead, or build a proper QBO file.
- A QFX file renamed to .qbo. The two formats share the same structure, so the contents may be fine. The question is whether the identifiers inside suit QuickBooks, which the next section covers.
- A hidden double extension, such as
statement.qbo.txt, when the computer hides known extensions. Turn on file extensions in your file manager and look again.
If the file is really a PDF statement, no rename will help. The upload in QuickBooks Online has its own statement option for PDF files, and the other route is to turn the statement into a real CSV or QBO file first.
Bank and account identifiers inside a QBO file
A QBO file names the bank and the account it came from before it lists a single transaction. The OFX 2.2 specification defines that block for bank accounts as <BANKACCTFROM>, holding a <BANKID> (the routing and transit number in the United States), an <ACCTID> with the account number and an <ACCTTYPE>.
These identifiers are why a file can open cleanly and still be refused. Text that looks fine to a person can carry a bank ID the receiving program does not accept, an account number that has been cut short, or no identifiers at all. Hand-made QBO files and files produced by older converters are the usual sources of these gaps.
Here is an annotated excerpt. Every value is an example:
<BANKMSGSRSV1>
<STMTTRNRS>
<STMTRS>
<CURDEF>USD
<BANKACCTFROM>
<BANKID>011000015 (example routing number)
<ACCTID>000123456789 (example account number)
<ACCTTYPE>CHECKING
</BANKACCTFROM>
<BANKTRANLIST>
<DTSTART>20260301
<DTEND>20260331
<STMTTRN>
<TRNTYPE>DEBIT
<DTPOSTED>20260304
<TRNAMT>-42.18
<FITID>20260304001
<NAME>HARDWARE STORE
</STMTTRN>
Check that each of the four header tags is present and holds a value. An empty <BANKID>, or an account number with letters or spaces in it, is worth fixing before anything else. If the file came straight from your bank's website, download it again rather than editing it. A fresh download replaces whatever went wrong the first time, and it keeps the transaction IDs the bank assigned.
QuickBooks Desktop reacts to the same problem with its own messages, and the Desktop side has a separate guide to a Web Connect file not opening in QuickBooks Desktop.
Card QBO file, bank account: the account type check
Every QBO file is either a bank file or a credit card file, and QuickBooks Online compares that against the account you choose on the second screen. When they disagree, Intuit's list of bank upload errors gives the message "The uploaded file is of a different type than these accounts."
The same Intuit article explains the two buttons. Cancel takes you back to choose the correct account. OK carries on with the upload into the account you already picked. Choose Cancel unless you are sure the account in QuickBooks was set up with the wrong type.
The file shows its type in its wrapper tags. A bank file uses <BANKMSGSRSV1> and <BANKACCTFROM>. A card file uses <CREDITCARDMSGSRSV1> and <CCACCTFROM>, and the OFX specification gives the card block no account type field at all. So if you downloaded from a card's page at the bank, expect a card file, and point it at a credit card account in QuickBooks.
Forcing a card file into a checking account causes trouble that outlasts the upload. Purchases and payments land with the wrong meaning, the account balance drifts, and reconciliation stops making sense. Clean-up then means deleting the lines and starting over.
Broken tags and cut-off QBO file downloads
A damaged QBO file is one whose structure no longer holds together. A tag opens and never closes, a transaction block is missing a field, or the file simply ends early. QuickBooks either refuses the whole file or brings in fewer transactions than you expected, without saying which ones are missing.
Look at the last lines of the file in a text editor. A complete file ends with closing tags such as </BANKTRANLIST>, a balance block and </OFX>. If the text stops in the middle of a transaction, the download was cut off. Delete the file and download it again, ideally on a steady connection and without opening it in a spreadsheet first. Spreadsheets can rewrite text files when they save, and a QBO file that has passed through one is rarely the same afterwards.
Inside a transaction block, the fields that matter most are the date, the amount and the transaction ID. A block missing its <FITID> gives QuickBooks nothing to identify the line by. A <TRNAMT> with a currency symbol or a thousands comma in it is not a plain number. A date written as 03/04/2026 instead of 20260304 does not follow the OFX date layout.
Editing tags by hand is possible, but it is easy to make a second fault while fixing the first. When the bank offers a fresh download, take that. When the file came from a converter, rebuild it from the source statement.
Is the QBO upload failure on the QuickBooks side?
Some upload failures have nothing to do with the QBO file, and editing it only wastes time. Intuit's bank upload error list includes messages that point at QuickBooks itself. The fix for those is to wait, try again later, or change which account you upload to.
Intuit's article names a daily Online Banking update in progress, a temporary server fault, an upload that timed out (often because the target is a subaccount, which uploads don't support) and a parent and subaccount both connected to online banking. The wording of each message and what to do about it is in the upload messages that mean QuickBooks Online is busy.
If none of these match and the file passes every check above, try a different file type. Many banks offer CSV next to QBO. A three-column CSV goes through the mapping screen instead, which shows you exactly which column QuickBooks is reading.
A QBO error code that comes from a bank connection, such as QuickBooks error OL-301 in Desktop bank downloads, is a different problem from a failed file upload. Those codes come from a live connection, not from a file you chose. A file upload is often the way around them.
A QBO upload checklist before you try again
Run through this list once, in order. The values in brackets are examples:
- Open the file in a text editor and confirm it starts with OFX tags, not commas.
- Check the size (under 350 KB) and count the transactions (no more than 1,000).
- Confirm
<BANKID>,<ACCTID>and, for a bank file,<ACCTTYPE>hold values (011000015,000123456789,CHECKING). - Match the wrapper to the account:
<BANKMSGSRSV1>goes to a bank account,<CREDITCARDMSGSRSV1>to a card account. - Check the file ends with
</OFX>. - Choose a main account in QuickBooks, not a subaccount.
- Make sure the dates don't overlap anything already in that account.
That last point matters most for people building a new company file. When you are entering history month by month, the guide to setting up QuickBooks Online from bank statements shows how to pick a start date and chain the files so nothing lands twice.
When the only thing your bank gives you is a PDF statement, SimpleBankConvert is being built to turn it into a CSV or QBO file QuickBooks Online can take. It isn't open yet; the get started page takes your details for an invitation.