Why Your QBO File Won't Import into QuickBooks (And How to Fix It)

Step 1: Open the QBO file in a text editor

A QBO file is plain XML. Open it in Notepad, TextEdit, or VS Code before attempting any fix. You should see a structure that starts with OFXHEADER:100 (for legacy OFX format) or an XML declaration. If the file is blank, truncated, or shows garbled text, the file itself is corrupt. Re-download or regenerate it.

If the file looks like valid XML, read on. The problem is likely in the content, not the file itself.

Problem 1: Invalid XML structure

QuickBooks rejects QBO files with malformed XML. Common causes:

• Special characters in transaction descriptions (ampersands, angle brackets) that were not escaped as XML entities (&amp; instead of &, &lt; instead of <).
• Unclosed XML tags.
• Extra content before the OFXHEADER line.
• Encoding issues from conversion tools that output wrong character encoding.

Fix: if you generated the QBO file from a conversion tool, re-run the conversion. Most modern tools handle XML escaping automatically. If you built the file manually, run it through an XML validator online to find the malformed section.

Problem 2: Wrong date format

QBO files require dates in YYYYMMDD format (for example: 20260315 for March 15, 2026). If the DTPOSTED field in your QBO contains dates formatted as MM/DD/YYYY or DD-MM-YYYY, QuickBooks will reject the file or import with wrong dates.

Fix: open the QBO file in a text editor and check the DTPOSTED fields. They should look like 20260315, not 03/15/2026. If your conversion tool created wrong date formats, regenerate the file or manually replace all date strings using find-and-replace in a text editor.

Problem 3: Duplicate or missing FITIDs

Every transaction in a QBO file must have a unique FITID (financial transaction ID). QuickBooks uses FITIDs to detect duplicates. If two transactions share the same FITID, QuickBooks skips the second one. If FITIDs are missing entirely, QuickBooks may reject the file or fail to import correctly.

Fix: regenerate the QBO file using a conversion tool that automatically assigns unique FITIDs. Do not try to assign FITIDs manually unless you are certain they are unique within the file.

Problem 4: Wrong financial institution ID (QuickBooks Desktop only)

QuickBooks Desktop matches QBO imports to bank accounts using the FID (financial institution ID) inside the QBO file. If the FID does not match the bank ID configured in Desktop for that account, QuickBooks Desktop will show an "account not found" error.

Fix: check the FID value inside your QBO file (look for the FI > FID tag). Then check what FID QuickBooks Desktop expects for that bank account (this is in the account setup under online banking settings). Either update the QBO file to use the expected FID, or reconfigure the Desktop account to accept the FID in your file.

Problem 5: File too large (QuickBooks Desktop)

QuickBooks Desktop has a practical file size limit for QBO imports. Files covering more than two years of transactions, or accounts with very high transaction frequency, can exceed this limit. The import either fails silently or imports only a partial date range without warning.

Fix: split the QBO file into 6-month chunks and import each chunk separately. Most conversion tools let you specify a date range for the output file.

Problem 6: Overlapping import with wrong transaction signs

This is not strictly an import error, but it looks like one. If debits and credits are swapped in the QBO file (positive values where there should be negative), QuickBooks imports the transactions but the amounts are wrong. Check the TRNAMT fields in the XML. Debits (money out) should be negative numbers.

When none of the above fixes it

If the QBO file looks correct but QuickBooks still rejects it, try importing a very small test file with just 5 transactions to isolate whether the problem is with the file structure or with a specific transaction. If the test file imports, add transactions back in batches of 50 until you find the problematic row.

For the full QBO import process from scratch, see our step-by-step QBO import guide.

FAQ

Can I validate a QBO file before importing?

Yes. Run the QBO file through an online XML validator. A valid QBO file is valid XML. Any XML error will show up in the validator before you attempt the QuickBooks import.

QuickBooks says the import succeeded but I cannot find the transactions. Where are they?

In QuickBooks Online, imported transactions go to the For Review tab under Banking, not to the register automatically. In QuickBooks Desktop, they go directly to the register. Check both locations.

My QBO file imports in QuickBooks Online but not Desktop. Why?

QuickBooks Desktop is stricter about the financial institution ID and account matching. QuickBooks Online is more tolerant of QBO files without valid FIDs. Check Problem 4 above for the Desktop-specific fix.