QuickBooks will not re-import a Web Connect file
The symptom is specific and confusing: you deleted some transactions, imported the same .QBO file again to get them back, QuickBooks reported a successful import, and the transactions did not reappear. Nothing is broken. QuickBooks is doing this on purpose.
What is actually happening
Every transaction inside a Web Connect file carries a unique id called a FITID. QuickBooks stores the FITID of everything it imports, and when it meets one it has seen before it skips that transaction silently — no warning, no error, no mention in the import summary. An Intuit support agent put it plainly in their community forum:
"Every account and transaction inside of a WebConnect file has a unique identifier which is why QuickBooks won't allow you to re-import the same .qbo file more than once to prevent duplicate entries."
— Intuit support, Re: import web connect file issue, QuickBooks Community
This is a sensible default. It is the mechanism that stops you doubling up your books when two statement exports overlap by a few days. It only becomes a problem when skipping is precisely what you do not want.
When you hit it
- You deleted transactions, by accident or to redo a messy import, and want them back.
- You imported with the wrong dates, amount signs or account, fixed the CSV, and need to import the corrected version.
- You imported into the wrong company file or the wrong bank account.
- You are re-doing a reconciliation and want a clean set of transactions to work from.
In all of these the file you want to import contains transactions QuickBooks has already seen, so by default almost nothing will come in.
The fix: new transaction ids
Because the skipping is driven entirely by the FITID, the way through is to give the transactions ids QuickBooks has never encountered. The transactions themselves are unchanged — same dates, same amounts, same descriptions — only their ids are new, so QuickBooks treats them as fresh and imports them.
Intuit's manual workaround
The approach circulated in Intuit's own community is to edit the file by hand: open the .QBO in a plain-text editor, find every <FITID> and replace it with <FITID>1, which prefixes every id with a 1 and makes them all new. It works. It also means hand-editing a financial data file in Notepad, remembering to use a different prefix on each attempt, and not saving it as .txt by mistake.
The one-click version
QBOKit converts your original CSV again with a fresh set of ids. In the converter, open "Re-importing a statement QuickBooks has already seen?" and tick Force a re-import. Every transaction gets a brand-new id, generated from the conversion time plus a random component, so two conversions a second apart still produce different ids and a second attempt does not fail the same way.
🔒 Convert your CSV with new ids — free, runs in your browser, nothing uploaded.
Leave it off for normal imports
Only tick this when you are deliberately re-importing. With the box off, QBOKit derives each id from the transaction's own date, amount and description, so the same statement always produces the same ids — which is what stops overlapping exports from duplicating your transactions. Forcing new ids throws that protection away for that one file: if you import a statement twice with the box ticked, you will get duplicates.
The rule of thumb: box off for your monthly import, box on only when you have deleted something and want it back.
If you already have duplicates
Forcing a re-import does not clean up after itself. If a previous attempt left duplicate transactions sitting in QuickBooks, remove those first — in QuickBooks Online, transactions still waiting in the For review tab can be ticked and excluded, which moves them out of your way without touching your books. Do that before importing a file with new ids, or you will be reconciling against both copies.
A note on QuickBooks Online
Web Connect import is a QuickBooks Desktop feature. If you are on QuickBooks Online you do not need a .QBO file at all — use the cleaned-CSV output instead and see the CSV format requirements. QuickBooks Online does its own duplicate checking on upload, which is a different mechanism from the FITID one described here.
Sources
- Re: import web connect file issue — QuickBooks Community, containing the Intuit support explanation quoted above.