The import history is a list of every statement you have uploaded and what happened to it. Read it as a ledger: one line per file, matched to a month and an account, with a status that tells you whether the upload finished, failed or never reached review.
What the history is for
Over a year you may upload a dozen files for several accounts. Memory alone will not tell you whether the October card file went in. SpendixAI keeps an import history with a status for each upload, and it sends a notification if an import fails, so the list can answer that question.
How do I match files to months?
Write down the months you expect, then go down the list and tick each one off. A simple grid keeps it clear.
| Month | Savings account | Credit card |
|---|---|---|
| April | Imported | Imported |
| May | Imported | Missing |
| June | Failed | Imported |
| July | Imported | Imported |
In this example May's card file is not in the history at all, and June's savings file failed. Those are the two things to fix. Without the grid, both would be easy to miss.
Spotting a missing month
A missing month shows up as a gap in the date sequence, or a month with no file listed. Look also at the transactions themselves: if March has a hundred rows and April has none, April was never imported. A quiet month on the dashboard is a clue as well, because spending of zero is almost always a data gap rather than a frugal month.
Finding an upload that never reached review
Sometimes a file is uploaded but you never finished the review step, so nothing was saved. The history will show the upload, and its status will tell you it is not complete. If you see an upload that has no matching transactions, open it and continue the review or start again.
- A file listed but with no rows saved: the review was never confirmed.
- A file listed twice: it was uploaded more than once, so watch for duplicates.
- A file listed with a failure: retry it in another format.
- A file you remember uploading but cannot find: it may not have been sent in the first place.
What does stuck mean?
A stuck upload is one that stays in a processing state much longer than the others. Give it a few minutes first, since a long PDF takes longer than a small CSV. If it does not move, leave the page, come back and check again before uploading it a second time. A second copy risks duplicates, and the app flags possible duplicates, but it is better not to create them.
A monthly habit
- After each import, open the history and confirm the status.
- Tick the month off against your grid.
- Run the balance proof on the account.
- Note the last date imported, so the next file starts the day after.
Think of each line as a receipt for a file. If you cannot match a line to a month and an account in a few seconds, name your files more clearly next time, because the history is only as readable as the names you give. A good name carries the account and the period, for instance card-2026-02, which tells you everything at a glance and sorts neatly.
Using the history at year end
At the end of the financial year, the history becomes an audit trail. Before you export anything for your accountant or review your annual reports, scan the list once more. Twelve months and each account should be present, from April to March, with nothing failed and nothing left unreviewed. Count your files against your grid, and if the numbers differ, trace the gap to the month before you trust any total. Ten minutes at this stage can save an embarrassing correction after a report has already been shared with someone else.
A few seconds with the history each month keeps your records honest, and it makes a yearly review much less of a puzzle.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


