When transactions go missing after an import, the cause is almost always one of four things: the file did not contain them, some rows were skipped as unreadable or duplicate, the date range was shorter than you assumed, or the rows landed in a different account. Count the rows in your file, count the rows in the app for that account and period, and the difference tells you which case you are in.
First, check the file itself
Open the statement you uploaded and look at the first and last dates. Banks often let you pick a range, and a custom range ending on the 28th will never contain the 29th to 31st. A multi-page PDF may also have been saved with only the first few pages.
- First and last transaction date in the file.
- Whether pages or sheets are missing from the file.
- Whether the file shows a single account or several accounts together.
- Whether the file is a summary rather than a transaction-level statement.
Did the import skip or reject rows?
Look at the import history. SpendixAI keeps a history with a status for each upload and sends an Import failed notification when something goes wrong. Rows are shown for review before saving, so rows you removed during review will not appear later. Possible duplicates are flagged, and if you chose to leave them out, that explains a short count.
Is it sitting in a different account?
Each transaction keeps the account chosen before import. If you uploaded a credit card file while the savings account was selected, the rows exist but sit under the wrong account. Look across all accounts and search for a known merchant or amount to find them, then correct the account or import again properly.
A quick row-count example
Say your savings statement for September has 86 rows, and the app shows 79 for that account. Seven rows are missing. Search the app for the amount of the largest missing row. If it appears under your card account, you uploaded to the wrong account. If it appears nowhere, compare dates: perhaps all seven fall on 29 and 30 September, which means the file ended early.
| What you see | Likely reason | Fix |
|---|---|---|
| Missing rows all at the end of the month | File range was cut short | Download a full-month statement and import it |
| Missing rows scattered through the month | Skipped as duplicate or removed in review | Check the review step and the duplicate flags |
| Rows exist but under another account | Wrong account selected | Correct the account or import again with the right one |
| Whole file shows nothing | Unreadable layout or failed import | Check import history; try CSV or Excel from the bank |
Should I just import the file again?
Yes, but carefully. Re-importing the same period can create duplicates, so use the duplicate flags and the Possible duplicate charges report, which lists the same amount to the same merchant within two days. Better still, import only the missing date range so the overlap is small.
A short recovery checklist
- Write down the file's first date, last date and row count.
- Filter the app by that account and period and count rows.
- Search for one missing amount across all accounts.
- Fix the cause: range, account or review selection.
- Import again for just the gap, then re-count.
- Compare the closing balance with the statement to confirm.
Why rows vanish at the edges of a statement
Statements are cut by date, and transactions that post late can land on the next statement. A purchase made on the 30th may show with the 2nd as its posting date. If you import October and November separately, you may think a row is lost when it simply belongs to the other file. Check the posting date column rather than the date you remember paying.
Also check whether the file lists credits and debits in separate sheets or columns. If only one set came through, totals will look lopsided and a whole class of rows, such as salary credits, will seem to be missing.
If the numbers still do not agree, the bank's own statement is the source of truth. Ask them for a fresh copy rather than guessing which rows might be absent.
Useful ideas start with a clearer picture of your own spending.
Explore your reports
