When a statement upload ends in an Import failed notification, work down a short list: make sure the file opens, check whether it is password protected, try the CSV or Excel version of the same statement, split a very long file, and retry. Some layouts may simply not parse perfectly.
Step one: does the file open on your device?
Open the statement on your own computer or phone. If it will not open, or shows a blank page, the file may be damaged or not fully downloaded. Download it again from your bank and upload the fresh copy. A file that cannot be opened by you cannot be read by an app either.
Step two: is it locked?
Many PDFs from banks ask for a password. A locked file can fail because the content cannot be read. Open it with your own password, save an unlocked copy, import that, and delete the copy afterwards. The related article on password-protected PDFs walks through this.
Step three: try another format
If the PDF keeps failing, download the same period as CSV or Excel. Machine-readable files are more reliable because they are already tables. If your portal only offers PDF, keep the PDF and move to the next step.
Step four: is the file very long?
A statement for a whole year, running to many pages, is harder to read in one go than a month. Download shorter periods, such as a month or a quarter, and import each. This also makes review easier.
Step five: retry once, calmly
After changing something, retry once. Then look at the import history, which shows a status for each upload, to confirm what happened. Avoid uploading the same failing file again and again; if the first attempt did partly save, you risk possible duplicates.
| Symptom | Likely cause | Try this |
|---|---|---|
| File will not open at all | Damaged or incomplete download | Download again |
| Asks for a password | Locked PDF | Open it yourself, save an unlocked copy |
| Fails only in PDF | Layout not read well | Download CSV or Excel |
| Fails on a long statement | Too many pages for one go | Split into shorter periods |
| Fails after all of the above | Unfamiliar layout | Add rows by hand or use the optional layout feature |
What if nothing works?
Be honest with yourself: not every layout will parse perfectly, especially from smaller banks or unusual card statements. SpendixAI has an optional feature for reading an unfamiliar layout, which processes the uploaded document, so use it only if you are comfortable with that. Otherwise you can add the transactions by hand, singly or several at a time.
A tidy routine after a failure
- Note which file failed and why you think it did.
- Delete any unlocked copy you made.
- Check the import history for partial saves before re-uploading.
- Do the balance proof on whatever did save: opening plus credits minus debits should equal closing.
- Fill any remaining gap by hand.
Give each fix a fair try before moving to the next, and change only one thing at a time, so you know which change worked.
What do I tell support?
If you reach a point where you want help, send the details that make the problem reproducible: the bank or card issuer, the format you tried, the period covered and whether the file is a PDF, CSV or Excel. Do not attach anything you would not want read, and remove account numbers where you can. Describe what you saw rather than what you think the cause is. A short, accurate description gets a quicker answer than a long guess, and it also helps you remember what you have already tried if you come back to it a day later.
A failed import is annoying, but it rarely loses anything. Your bank still has the statement, and you can always try a different format of the same period.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

