If a password-protected bank statement PDF will not import, the usual causes are that the file is locked, the layout is unusual, or the file is a scan. Try, in this order: a CSV or Excel version of the same statement from your bank, then the import screen's own prompts, then hand entry for the few rows that matter. Never share your bank password or OTP with anyone to get a statement.
Why do banks lock statement PDFs?
Statements hold account numbers, balances and spending, so many banks send them locked, and the password is usually built from details you already know, like part of a date of birth or a customer ID. The exact rule differs by bank and sometimes by account, so read the email or the note that came with the statement rather than guessing. A note on the PDF's download page often says what it is.
What should I check first?
- Open the PDF yourself, on your own device, with the password. If it will not open, the issue is the password, not the app.
- Check the file is a real statement and not a screenshot saved as a PDF; text you cannot select is likely an image.
- Confirm you chose the right account before importing.
- Look at the import history for the status, and any Import failed notification, which tells you the file did not go through.
- Try the file once more, in case the first upload timed out.
SpendixAI accepts statements in PDF, CSV or Excel, shows the rows for review before saving, and keeps an import history with a status per file. No tool can promise that every locked PDF will open, so treat a failure as a prompt to try another format rather than a bug you must fix.
Is there a safer format than the PDF?
Often yes. Many banks let you download a statement as CSV or Excel for a chosen date range; where to find it is something to check in your own banking app or website, because menus change. A spreadsheet file has no password in most cases and gives software clean columns instead of a layout to interpret. Download it from your own banking session, and keep it on your own device.
A worked check on a partial import
Say your statement shows 58 transactions with debits of ₹46,210 and credits of ₹62,000. After the import preview you see 55 rows. Count and compare.
| Check | Statement | Preview | Action |
|---|---|---|---|
| Row count | 58 | 55 | Find the 3 missing rows |
| Debits (₹) | 46,210 | 45,010 | Gap of 1,200: check three small debits |
| Credits (₹) | 62,000 | 62,000 | Matches |
The gap of 46,210 minus 45,010 is ₹1,200. If three missing rows are ₹500, ₹450 and ₹250, they add up to exactly ₹1,200, which finds them. Add those three by hand, then compare again before saving.
When should I add rows by hand?
If a statement fails and a CSV is not available, entering the missing transactions manually is slower but safe. The tracker allows several expenses at once, which suits a short list. Do it for a month at a time, and keep the PDF until the totals match.
A quick list before you give up
- Does the password open the file in a normal PDF reader?
- Is there a CSV or Excel download for the same period?
- Is the right account chosen in the import?
- Did the import history show a failure or a partial result?
- Can the missing rows be added by hand?
If none of that works, ask your bank for a fresh statement and say which format you need.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

