Open a QBO file in a text editor and you'll spot a strange tag buried inside every transaction: <FITID>. It looks like noise. It is actually the one field responsible for keeping your QuickBooks register free of duplicates.
What FITID Stands For, and Its One Real Job
FITID stands for Financial Institution Transaction ID. The OFX specification itself, the format QBO files are built on, states its purpose plainly. "An FI assigns an FITID to uniquely identify a transaction." Its purpose: letting a client detect duplicate responses.
In plain terms, a FITID is a label. QuickBooks reads that label on every transaction it imports. If it has seen that exact label on that exact account before, it treats the transaction as already imported. It skips it. That single mechanism is what stops duplicate transactions from piling up when you re-import an overlapping statement.
Why FITID Only Needs to Be Unique Per Account, Not Globally
A common assumption is that a FITID must be unique across your entire business, or even the whole world. The actual specification says otherwise. FITIDs "must be unique within the scope of the requested transactions, that is, within an account." They need not even be sequential.
That distinction matters in practice. Two different transactions, at two different bank accounts, can technically share the exact same FITID value with no problem. QuickBooks only checks for a matching FITID within one specific account's own history. It never checks across accounts.
What Happens When Two Banks Reuse the Same FITID
The specification goes further here, and it directly affects anyone converting statements from more than one bank. FITIDs "are not unique across FIs," meaning across different financial institutions. Two banks can independently generate the exact same FITID for two unrelated transactions.
QuickBooks handles this correctly as long as each transaction stays tied to its own account. The real risk only shows up if a conversion tool mixes transactions from two accounts into one file. It has to track which account each FITID belongs to. A well-built converter keeps that separation intact automatically. This stays a non-issue for anyone using one.
What Happens When a File Has No FITID at All
Not every source file starts with a usable FITID. A plain CSV export from online banking has no such field built in. Neither does a PDF statement, since it's a visual layout rather than structured data.
Something still has to fill in the <FITID> tag when a QBO file gets built from one of those sources. The format requires it on every transaction. The conversion tool generates that value itself. How it generates it determines whether a later re-import behaves correctly or creates duplicates.
qbosync generates each FITID as a deterministic hash. It's built from the account, the transaction date, the amount, and the description. Converting the exact same source row twice always produces the exact same FITID. QuickBooks correctly recognizes a genuine re-import of unchanged data as a duplicate. No extra tracking is needed on your end.
Why This Matters Even If You Never Touch a Raw QBO File
Most people who convert a bank statement never open the resulting QBO file directly. That's fine. The FITID mechanism works the same either way.
Where it actually matters is in choosing a conversion tool, and in understanding why duplicates sometimes appear anyway. A tool that generates random or timestamp-based FITIDs produces a different value every time. That happens even if nothing in the source data changed. Re-import that same file later, or one covering overlapping dates, and QuickBooks has no way to recognize the overlap. A tool that generates the same FITID for the same source data avoids that problem by design, not by luck.
FAQ
What does FITID actually stand for?
Financial Institution Transaction ID. It's a field inside a QBO or OFX file, attached to every transaction. Its entire purpose is letting QuickBooks detect a duplicate.
Does a FITID need to be unique across my whole business, or just one bank account?
Just one account. The OFX specification states FITIDs only need to be unique within one account's own transaction history. They don't need to be unique across your whole business.
Can two different banks use the same FITID for different transactions?
Yes, and the specification says this explicitly. FITIDs are not unique across financial institutions. QuickBooks handles this correctly as long as each transaction stays tied to its own account.
What happens if a QBO file has no FITID at all?
The file would be malformed, since the format requires one on every transaction. In practice this rarely comes up. Any tool converting a CSV, Excel, or PDF statement into QBO generates a FITID automatically.
Why does this matter if I'm just using a conversion tool instead of writing OFX files by hand?
Because the quality of that generated FITID decides what happens on your next import. A good one gets a real re-import correctly recognized. A poor one creates duplicate transactions in your books instead.