Free Reference

QBO Import Errors, Explained

QuickBooks rejected your file? Find the error below, learn what it actually means, and fix the file — not your books.

Test with sample files

Download a clean file and a broken file, run them through the checkers, and see exactly what each report looks like — before you touch your real books.

Then check your own file: QBO File Checker for structure and balances, QBO Duplicate Finder for duplicates. Both are free with no account.

Bank-grade security — Free reference · Sample files only, nothing uploaded

Free to use

Scan free, QBO downloads on Pro

Files never stored

How it works

How to diagnose a rejected QBO file

Note the exact error

Write down what QuickBooks says and which file it refuses — the message points at the row below.

Find it in the table

Match your error to a row in the decoder table and read what it actually means.

Fix the file, not the books

Fix the file with the cleanup checker (or a careful text edit for one or two rows) — never force the import and fix the books afterwards.

Verify before re-importing

Run the fixed file through the QBO checker. A clean report means the re-import should go through.

The decoder table

QuickBooks error messages describe the file, not your books — and the fix is almost always in the file. Work through the table from the top: fix the file, verify it with a checker, and only then re-import.

Error	What it actually means	How to fix it
Duplicate transaction ID (FITID)	Two or more rows share one FITID. QuickBooks treats a repeated ID as already imported and skips or rejects the later rows, so real transactions go missing.	Run the file through the QBO Duplicate Finder and download the cleaned QBO (Pro): exact duplicates are dropped and missing or repeated IDs are regenerated. For a single row, change its FITID to a unique value by hand.
Ledger-balance mismatch	The file's closing balance (LEDGERBAL) disagrees with the transactions in the file, or with the balance QuickBooks already holds for that account.	Compare the file's closing balance with the statement's closing balance, and confirm you are importing into the correct account. If the file is yours, regenerate it from the statement rather than editing the balance.
Missing closing balance	The file has no LEDGERBAL block. Some imports accept this; others warn or refuse, and reconciliation has no target to aim at.	Regenerate the file from a converter that embeds the closing balance, or add the statement's closing balance as the LEDGERBAL with the statement's end date.
Invalid or missing transaction date	A row's DTPOSTED is empty, malformed, or outside the statement period. QuickBooks cannot place the transaction, so the import stops or the row is dropped.	Find the row in the cleanup report, correct its date to the statement date, and make sure every date falls inside the file's DTSTART–DTEND period.
Missing statement period	The file declares no DTSTART or DTEND, so QuickBooks cannot tell which month the transactions belong to and may treat them as already imported.	Regenerate the file with the statement's start and end dates, or add DTSTART and DTEND matching the statement period.
Duplicate transactions, different IDs	The same date, amount, and payee appear twice with different FITIDs — a double export or a typed-twice entry. QuickBooks imports both, and the account is overstated.	The cleanup checker flags these as exact matches (not FITID duplicates). Delete one copy from the file — or from QuickBooks if it already imported — and check the statement to be sure it is really one transaction.
Not a valid Web Connect file	QuickBooks expects OFX 1.02 with a .qbo extension and USD currency (for US accounts). A renamed .ofx or .qfx file, or a non-USD currency tag, is refused outright.	Re-export as QBO from a QuickBooks-targeted converter and confirm the extension is .qbo before importing. Do not just rename another format's file.
Corrupt or truncated file	The file ends mid-transaction, has a broken tag, or is not OFX at all (for example, a CSV saved with a .qbo extension). The parser fails before any row is read.	Re-download or regenerate the file. If you edited it by hand, restore the original and use the cleanup checker instead of editing tags directly.

Still stuck after fixing the file? The Reconciliation Difference Finder compares a statement against a QuickBooks export and shows exactly which entries do not line up — and our QuickBooks cleanup service takes the whole mess off your hands with a free assessment first.

Free tools