“Two-factor authentication stops my statement download”
Additional security has removed some download routes that worked for years, particularly automatic connections from desktop finance software. The data is still exportable; the path to it has moved, and knowing which path broke saves a long argument with support.
Symptoms
Direct connection from your finance software fails after a security change The export is interrupted by a verification prompt and returns nothing Downloading works in the browser but not from within your software
What actually causes it
Stored credentials no longer suffice
Desktop software that logs in with a saved password cannot complete a step that requires a code sent to your phone. The connection fails at that point, and the error usually blames the credentials rather than the missing step.
The session expired while you chose a date range
Verification often starts a short session. Spending time selecting accounts and dates can exhaust it, and the export then returns the login page or an empty file under the expected file name.
App passwords exist but are not offered
Some banks issue a separate access code for finance software, distinct from your login. It usually has to be requested, and its absence looks identical to a broken connection from the software side.
How to fix it
- Download manually in the browser and import the file, rather than relying on a direct connection the bank has restricted.
- Complete verification first, then go straight to the export screen without pausing over settings.
- Ask the bank specifically whether an application password or dedicated access code exists for finance software.
- Verify each manual download with the tool below, since an expired session returns a plausible-looking file that contains nothing.
Related import problems
Skip the manual edit — fix it automatically
The checker distinguishes a genuine export from the empty or login-page file an expired session leaves behind under the same name. Free, no signup, no upload.
Open the fixer