You import a bank statement into QuickBooks, and a week later you import an updated one from the same bank. Suddenly half your transactions show up twice. This happens more often than you'd expect, and it has a specific, fixable cause.
Why Duplicate Transactions Happen After a Bank Import
QuickBooks does not compare transactions by date and amount alone. It relies on a hidden identifier attached to each transaction inside the QBO file itself. When that identifier is missing or reused incorrectly, QuickBooks can't tell a new transaction from one it already has. The result is the same real-world purchase showing up as two separate entries in your register.
How QuickBooks Actually Detects a Duplicate: FITID
Every transaction inside a QBO file can carry a Financial Institution Transaction ID, known as a FITID. A full breakdown of what a FITID actually is, and its exact uniqueness rules covers the mechanics in more depth than this guide needs. QuickBooks tracks these IDs per bank account, and uses them specifically to recognize a transaction it has already imported.
The catch is that a FITID only works if it is truly unique. Not just unique within one file, but unique across every file ever imported for that account. ProperSoft's own support documentation confirms this directly. Some banks generate IDs that only distinguish transactions inside a single export, not across separate exports. Import two files with that kind of ID scheme, and QuickBooks has no reliable way to spot the overlap.
The Overlapping Date Range Mistake
The single most common cause of duplicates is a simple one. You download a statement covering January 1 through January 31. A week later, you download another one covering January 15 through February 15, to catch up on February. Both files include the transactions from January 15 through January 31. If the FITIDs on those overlapping transactions aren't reliably unique, they import a second time.
The fix is straightforward once you know to look for it. Always check the actual date range of a new export against every file you've already imported for that account. Overlap is the trigger, not the tool doing the conversion.
Why Deleting a Duplicate Doesn't Always Fix It
Deleting a duplicate transaction from your register feels like it should reset the slate. It doesn't, according to the same ProperSoft documentation. QuickBooks keeps its own internal record of already-imported transactions. That record stays even after you delete them from the register.
Re-import the same file again later, expecting a clean slate. QuickBooks may still recognize those transactions as already seen. In some cases it skips them entirely, even when you actually did want them re-added.
That makes the safer approach a different one. If you need to redo a specific date range cleanly, delete the existing transactions for that range first. Then re-import the full range as one file. Don't delete and hope a partial re-import lines back up correctly on its own.
When Your Bank Doesn't Provide a Real Transaction ID
Not every bank statement export includes a usable FITID. A CSV export from online banking almost never does. Neither does a PDF statement, since it's a visual layout, not structured transaction data. Converting either one into a QBO file means the conversion tool must generate its own transaction IDs. Every bank formats its own export differently in the first place, which is exactly why this generation step can't assume one fixed layout.
qbosync generates its own transaction IDs during conversion, built directly from the transaction's account, date, amount, and description. Converting the same source data twice produces the exact same IDs both times. QuickBooks correctly recognizes a genuine re-import as already-seen, as a direct result. That is a property of the conversion step itself, not something QuickBooks does automatically for a plain CSV or PDF.
How to Safely Re-Import a Statement Without Creating Duplicates
A few habits keep this problem from ever showing up in your books.
Track exactly which date ranges you've already imported, per account. A simple note next to each bank profile, listing the last imported date, prevents most overlap mistakes before they happen.
Never split one month into two overlapping exports. Download and convert a clean, non-overlapping range each time. Wait a few extra days for the full period to close if you need to.
If you must redo a range, delete first, then re-import the whole thing. A partial re-import over transactions QuickBooks already has on file is where most real duplicate problems start.
Review the import summary QuickBooks shows before confirming. Most import flows list how many transactions were recognized as duplicates and skipped. That summary appears right before you finalize the import, and it's worth reading, not clicking past.
FAQ
Why do the same bank transactions show up twice after importing a QBO file?
The transaction IDs inside the file, called FITIDs, weren't unique enough. QuickBooks couldn't recognize that the second file covered some of the same ground as the first. This usually happens when two exports have overlapping date ranges.
How does QuickBooks actually detect a duplicate transaction?
QuickBooks checks each transaction's FITID against the ones it has already imported for that bank account. A matching FITID gets treated as already-seen and is not re-added.
What happens if I re-import a date range I already imported before?
If the FITIDs are consistent, QuickBooks correctly skips the overlapping transactions. If they aren't, the overlapping transactions get added a second time as duplicates.
Can deleting a duplicate transaction cause it to get skipped or re-flagged later?
Yes. QuickBooks keeps its own record of already-imported transactions, even after you delete them from the register. A later re-import of the same data may not behave the way you expect.
What if my bank's CSV or PDF doesn't include a real transaction ID at all?
The conversion tool generates its own IDs from the transaction's date, amount, and description. A tool that generates consistent IDs, like qbosync does, lets QuickBooks correctly recognize a genuine re-import.