“The statement file is password protected”
Some banks encrypt statement downloads, usually PDFs but occasionally other formats. Finance software has no way to open them, and unlike most import failures this one cannot be repaired — it has to be worked around.
Symptoms
Opening the file asks for a password The importer refuses it as corrupt or unreadable The password works in a PDF reader but nowhere else
What actually causes it
The file is an encrypted PDF
Password-protected statements are almost always PDFs, and a PDF carries no importable transaction data even unencrypted. It is a picture of your statement, not the statement itself.
Encryption applied to an archive
Where the bank sends a protected ZIP, the file inside may be perfectly importable once extracted with the password.
The password is not what you expect
Banks commonly derive it from a date of birth, a postcode or the last digits of an account number, and send the rule separately from the file.
How to fix it
- Check whether it is a ZIP rather than a PDF; if so, extract it with the password and the contents may import directly.
- Drop any extracted file into the fixer below — it identifies the real format from the content, which matters when extraction strips the extension.
- If it is genuinely an encrypted PDF, look for a machine-readable export in the transaction list rather than the statements archive; those are rarely encrypted.
- Ask the bank for CSV or OFX access. Requests do influence what gets offered, and PDF conversion is data entry rather than import.
Related import problems
Skip the manual edit — fix it automatically
The fixer works on OFX, QFX, QBO, QIF and CSV, and tells you plainly when a file is not one of them rather than pretending otherwise. Free, no signup, no upload.
Open the fixer