QBO File Won't Import Into QuickBooks? How to Fix It
Convert a PDF bank statement to a QuickBooks file
Drop in a PDF statement and get a QBO (Web Connect) or IIF file you can import into QuickBooks Online or Desktop.
Short answer
A QBO file that will not import into QuickBooks almost always fails for one of five reasons: the file is not really a valid .qbo, QuickBooks thinks the transactions are duplicates, you are importing into the wrong account, QuickBooks Desktop is out of date, or the original PDF was read badly so the file is malformed. Work through them in that order and most imports go through. If the file itself is broken, re-convert it from the PDF and import the fresh QBO.
You converted a PDF statement, you have a .qbo file ready, and QuickBooks still will not take it. Maybe it shows "We can't read this file," maybe it accepts the file but nothing appears, or maybe Desktop throws a Web Connect error. The good news is that QBO import problems come from a short list of causes, and each has a clean fix. Here is how to diagnose which one you are hitting and get your transactions in. If your file does import but you want the exact click path, see our step-by-step guide to importing a QBO file into QuickBooks Desktop and Online.
Why QuickBooks won't import your QBO file
A QBO file is QuickBooks Web Connect, a flavor of the OFX standard. If your problem is the Web Connector app throwing an error rather than the file itself, see our fix for the QuickBooks Web Connect import error QBWC1039. It is plain structured text with a header and one block per transaction. QuickBooks is strict about that structure, the account it maps to, and whether it has seen those transactions before. When an import fails, the cause is usually one of these:
| What you see | Likely cause | Fix |
|---|---|---|
| "We can't read this file" or "not a recognized format" | The file is corrupted, renamed from another format, or not a true QBO | Re-download or re-convert; confirm the extension is really .qbo |
| Import finishes but nothing new appears | QuickBooks flagged the transactions as duplicates of ones already there | Check the register and date range; remove the earlier import or adjust dates |
| Balances go negative or look reversed | The QBO went into the wrong account type (bank vs credit card) | Import into the matching account; a card QBO belongs in a credit card account |
| Web Connect error on QuickBooks Desktop | Desktop is out of date, or the bank feed is not set to Web Connect | Update QuickBooks, then import through Bank Feeds, Import Web Connect File |
| Some lines missing or amounts garbled | The PDF was read poorly, so the QBO is incomplete or malformed | Re-convert the PDF with a tool that lets you review before export |
How to fix a QBO file that won't import
Go through these steps in order. Stop as soon as the import succeeds.
- Confirm the file is really a QBO. Open it in a plain text editor. A valid file starts with OFX header tags and contains STMTTRN blocks. If you see a PDF header or HTML, the file never converted and that is your whole problem.
- Import into the correct account. In QuickBooks Online, open Transactions, then Bank transactions, pick the exact account, use the Link account dropdown, and choose Upload from file. Map the QBO to the account it belongs to. A credit card statement must go into a credit card account, not a checking account.
- Check for a date or duplicate clash. If the import says it worked but you see nothing, the transactions probably already exist from an earlier upload or a live feed. Look in the register for the statement's date range before assuming the file failed.
- Watch the file size. The manual upload path tops out around 1,000 lines per file. For a heavy month, split the statement or convert it in smaller batches.
- Re-convert if the file is malformed. If the QBO is incomplete or the amounts look wrong, the PDF was read badly. Convert it again with a tool that shows the transactions for review before it builds the file.
QuickBooks Desktop: fix Web Connect import errors
Desktop is fussier than Online because Web Connect ties a QBO to a registered financial institution. If Desktop refuses the file, try this:
- Update first. Go to Help, then Update QuickBooks Desktop, install the update, and restart. Old versions reject files current ones accept.
- Import the right way. Use Banking, then Bank Feeds, then Import Web Connect File, and pick the matching account. Double clicking the file does not always route it correctly.
- Set the account to Web Connect. If the account was never enabled for Bank Feeds, set it up and choose Web Connect rather than Direct Connect.
- Fall back to IIF. When a stubborn QBO still will not load, an IIF file imports through File, Utilities, Import, IIF Files and sidesteps Web Connect entirely.
When the file itself is the problem, re-convert from the PDF
If you traced the failure to a bad QBO, the cleanest fix is to rebuild it from the source PDF with a converter that lets you review every line before export, so you catch a misread amount or a dropped transaction before it ever reaches QuickBooks. Our PDF bank statement to QuickBooks converter does exactly that, and the credit card statement to QuickBooks version keeps card charges on the correct side so they import into a credit card account without flipping your balances. For a refresher on which format your QuickBooks version needs, see the QuickBooks Online QBO import guide.
A few related tasks call for a different tool rather than a QBO. If you only need the statement numbers in a spreadsheet instead of inside QuickBooks, skip the QBO format and convert the statement straight to a worksheet with a PDF to Excel converter. If the PDF is a scan or a phone photo and the text will not read at all, run it through a dedicated document OCR tool first so the characters become real text. And if what you are actually trying to import is a stack of vendor bills rather than a statement, those need an invoice OCR tool built to read line items, not a bank converter.
Why does QuickBooks say it can't read my QBO file?
That message means QuickBooks could not parse the file as valid Web Connect. The usual culprits are a corrupted download, a file that was renamed to .qbo but is really a PDF or CSV, or a QBO built by a tool that wrote a broken header. Open the file in a text editor to confirm it starts with OFX tags. If it does not, re-convert the original PDF and import the new file.
Why did nothing import after I uploaded the QBO file?
When the upload completes but no transactions show up, QuickBooks almost always matched them to entries already in the account and skipped them as duplicates. Check the register for the statement's date range. If a live feed or an earlier import already pulled those dates, the file did its job and there is nothing new to add. If the dates are genuinely missing, the file may have the wrong account mapped.
Can I convert a QBO file to IIF if it won't import?
Yes, and it is a common workaround for QuickBooks Desktop. IIF is a tab delimited format that imports through File, Utilities, Import, IIF Files and does not depend on Web Connect's institution matching. The simplest path is to convert the original PDF statement straight to IIF instead of QBO, so you skip the format that was failing and import a file Desktop accepts.
Does the QBO file need to match the right account?
It does. A QBO carries transactions, but you choose which account they land in at import time. Send a checking statement to a bank account and a credit card statement to a credit card account. Mapping a card file to a bank account, or the reverse, flips the sign on purchases and payments and throws your balances off, which is why the import looks wrong even though the file is fine.