When a PDF statement will not import, the cause is almost always one of seven things: the file is locked, it is a photo of a statement rather than text, the upload was cut short, the layout is unusual, the date range overlaps an earlier import, the file is not the statement at all, or the rows did import but you are looking at the wrong account. Work through them in that order and you will usually find the culprit in a few minutes.
Start with what the app actually says
Most trackers tell you something even when the import fails. Look for an import history screen, a status next to the file, or a failure notification. A status such as failed, partly imported or waiting for review points you to different fixes, so note the exact wording before you try anything else. In SpendixAI, for example, there is an import history with a status per upload and an Import failed notification, and rows are shown for review before they are saved, so a file that looks like it vanished may simply be waiting for you to confirm it.
Which problems are about the file, not the app?
- Locked file. Many bank PDFs open only with a password set by the bank. Open it on your device with your own password, then save an unlocked copy for yourself if your bank allows it. Never type that password into anything except the PDF viewer on your own device.
- Scanned or photographed pages. If you cannot select a single word with your cursor, the file is a picture. Download the statement again in the text version your bank offers, or ask for a CSV or Excel copy instead.
- Incomplete download. A file of a few kilobytes for a full month is suspicious. Download it again on a stable connection and open it before uploading.
- Wrong document. Account summaries, interest certificates and mini-statements are not the same as a full transaction statement. Check that the pages list one row per transaction.
- Strange layout. Some statements put narration on several lines, repeat headers on every page, or split debit and credit into separate columns. Tools differ in how well they cope, and no tracker can promise every layout will read perfectly.
Should you try CSV or Excel instead of PDF?
Yes, whenever your bank offers it. A PDF is built for printing, so a tool has to guess where one column ends and the next begins. A CSV or Excel file already has columns. SpendixAI accepts PDF, CSV and Excel, so switching the file type does not mean switching tools. If only a PDF is available, upload it anyway and read the review screen carefully before saving.
How do you check that every row came in?
Rows can be missing without any error message, so reconcile. Take the opening balance, add the credits, subtract the debits and compare with the closing balance printed on the statement. Say a statement shows an opening balance of ₹48,200, total credits of ₹52,000, total debits of ₹60,550 and a closing balance of ₹39,650. Check it: 48,200 + 52,000 - 60,550 = 39,650, so the statement is consistent.
Now suppose your tracker shows debits of ₹58,300 for that month. The gap is 60,550 - 58,300 = ₹2,250, so some debit rows are missing or sitting in another account. Sort the statement by amount, tick each row against the tracker, and the missing ones will show up. Typical suspects are rows near a page break and rows with a long, wrapped narration.
| Symptom | Likely cause | What to try |
|---|---|---|
| Nothing uploads at all | Locked or unsupported file | Open it locally, save an unlocked copy, retry |
| Zero rows found | Scanned image | Download the text version or a CSV |
| Some rows missing | Page breaks or wrapped lines | Reconcile totals and add missing rows by hand |
| Everything flagged as duplicate | Same period imported before | Check import history before re-uploading |
| Rows appear under a different account | Wrong account picked first | Pick the right account before the next import |
What if the app flags duplicates?
A duplicate warning is not a failure. It usually means the same transactions were already imported, often because two statements overlap by a day or two. Compare the import history dates before deleting anything. If you did upload the same month twice, remove the second batch rather than individual rows.
A short checklist before you upload again
- Open the file yourself and confirm you can select text.
- Confirm the period and the account name on page one.
- Choose the correct account in the tracker first, since each transaction keeps its account.
- Keep the original file untouched in a folder named by month.
- After saving, reconcile totals against the closing balance.
If a particular bank layout keeps failing after all this, ask your bank for the CSV or Excel version rather than fighting the PDF. It is the quickest fix more often than not.
Useful ideas start with a clearer picture of your own spending.
Explore your reports
