“The import said it worked but nothing appeared”
A successful import with nothing to show for it is the most disorienting outcome, because the one thing you can normally rely on — an error message — is absent. The transactions went somewhere, or were never there.
Symptoms
The import finishes cleanly and the register is unchanged No error, no warning, no imported count The file clearly contains transactions when opened
What actually causes it
They went into a different account
Where the account selection defaulted to something else, the import genuinely succeeded — into a ledger you are not looking at. Check every account before assuming nothing happened.
They were filtered as duplicates
Re-importing an overlapping period leaves nothing new to add. The importer reports success because it did its job; the result is indistinguishable from a failure.
A register filter is hiding them
Date-range and category filters left over from earlier work hide new entries that fall outside them, and the register looks unchanged while the data is there.
The file has no transactions the importer recognises
A CSV whose rows never matched the expected shape yields zero rows without failing, which is reported as success with nothing imported.
How to fix it
- Drop the file into the checker below first: it tells you how many transactions it actually contains, which decides whether to look at the file or the app.
- Clear every filter in the register and widen the date range before concluding the entries are missing.
- Check other accounts, especially any created recently by an import.
- If the file genuinely has zero recognisable rows, the checker says so explicitly rather than leaving you guessing.
Related import problems
Skip the manual edit — fix it automatically
A transaction count from the file turns "nothing happened" into a specific question about where they went. Free, no signup, no upload.
Open the fixer