If a statement import seems stuck on processing, do not upload the same file again straight away. First open the import history and look at the status, then check the file itself: its format, size, whether it is password protected or scanned. Re-uploading too early is how duplicates and confusion start.
What should you look at first?
- Open the import history and find your file. Note its status, such as processing, completed or failed.
- Check your notifications. SpendixAI sends an Import failed notification when an import does not go through.
- Refresh the page or reopen the app once. A screen can look stuck when the work has finished.
- Wait a little. A large PDF or several files in one batch take longer. We cannot give a standard waiting time, so use judgement and look again after a while.
Is the file the problem?
| Check | Why it matters | What to do |
|---|---|---|
| Format | Only PDF, CSV or Excel are accepted | Save or export in one of those |
| Password | A protected PDF cannot be read without opening it | Open it with the password you were given and follow your tool's guidance |
| Scanned image | A photo of a statement has no text to read | Ask the bank for a digital copy |
| Size or pages | A very large file may be slow | Split by month and upload one at a time |
| Wrong file | Receipts or screenshots are not statements | Upload the statement itself |
A worked example: proving what saved
Say you uploaded three monthly files in one batch. The history shows two completed and one stuck. Your own counts from the statements are 64, 71 and 58 rows. After the two completed imports you check the transactions and find 64 and 71 rows, so 135 saved. The stuck file would have added 58 more, so the full total should be 193. Because you know the expected counts, you can tell exactly what is missing, instead of guessing.
How do you retry safely?
- If the status is failed, upload again after fixing the cause, ideally just that one file.
- If it is still processing after a long time, wait, then check again before retrying.
- If you must re-upload, do it alone, not in a batch with files that already finished.
- After saving, look for flagged possible duplicates and clear them.
When should you ask for help?
If a file stays stuck and you have checked the format, size and password, note the file name, the account, the time you uploaded it and the status shown. Use the help or FAQ pages to reach support with those details, rather than uploading the same file five times. As a workaround, try the same statement as CSV or Excel if your bank offers it, or split a large PDF into months.
What if only some rows appear?
A partial import is worse than a failed one, because it looks finished. Compare the count of rows in the tracker with the count on the statement, using a filter on the account and date range. If rows are missing, note the date of the last row that did appear. That tells you where the file stopped. Upload the missing period again as a separate, smaller file, and the duplicate flag will help you spot any rows that overlap.
How can you prevent it next time?
- Upload one account and one month at a time while you learn what is normal.
- Choose the account before you upload.
- Keep the original statements in a folder.
- Look at the import history after each upload.
- Do not close the app mid-upload on a weak connection; wait for confirmation.
These steps apply to most statement tools, not just one. If your upload still will not complete, entering the month's transactions by hand, several at once, is a fallback that keeps your tracking going while the issue is sorted.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

