Quicken / QuickBooks / YNAB

“Some transactions are missing after import”

The import reports success, yet the account is short a few transactions. Nothing failed loudly — the importer simply decided some records were duplicates it had already seen. The mechanism behind this is the FITID.

Symptoms

  • Import completes without errors but the balance is off
  • Two similar transactions on the same day — only one shows up
  • Re-importing the same file never brings in the missing rows

What actually causes it

Cause 1

Duplicate FITIDs in the file

The FITID is each transaction's unique fingerprint; importers skip any FITID they have seen before. When a bank assigns the same FITID to two genuinely different transactions (a recurring subscription charged twice in one day is the classic case), the second one is silently dropped.

Cause 2

FITIDs reused across statement periods

Some banks reset their FITID sequence, so this month's IDs collide with last month's. The importer "remembers" the old IDs and skips the new transactions.

Cause 3

Transactions with empty FITIDs

A transaction whose id field is present but blank has nothing for the importer to key on. Rather than reporting a problem, most apps quietly skip the record — so the import succeeds, the count is short, and nothing in the log explains which entries went missing.

How to fix it

  1. Drop the file into the fixer below — it lists every duplicate and missing FITID (processed locally, never uploaded).
  2. Apply the repair: duplicates get a numeric suffix, missing IDs get a deterministic generated value.
  3. Delete the partial import in your app (or restore from backup), then import the repaired file.
  4. Note for the "reused across months" case: the collision is with IDs your app already stored, not inside the file — there the fix is renaming FITIDs in the new file before import, which the duplicate repair also accomplishes.

Skip the manual edit — fix it automatically

The fixer makes every FITID in the file unique and deterministic, which resolves both in-file duplicates and cross-statement collisions. Free, no signup, no upload.

Open the fixer

Your file never leaves your browser.