“The bank gave me a ZIP file”
Some banks compress exports, particularly for long date ranges or when several accounts are downloaded together. No importer reads a ZIP directly, and the interesting question is what the archive turns out to contain.
Symptoms
The downloaded file ends in .zip and the importer refuses it Extracting produces several files with unfamiliar names The extracted file has no extension at all
What actually causes it
Multiple accounts in one download
Requesting all accounts at once produces one file per account inside an archive. Each must be imported separately into its own ledger, which the single download button rather hides.
Compression for a long date range
Multi-year exports are compressed to keep the download manageable, so the archive contains a single ordinary file that just needed unpacking.
The extension is missing after extraction
Files extracted without an extension are refused by importers that filter by name, even when the contents are a perfectly valid statement.
How to fix it
- Extract the archive and look at what is inside before anything else — the number of files tells you whether this is one account or several.
- Drop each extracted file into the fixer below: it identifies the real format from the content, so a file with no extension is no obstacle.
- Rename each file to match what it actually is (.ofx, .qfx, .csv) so your importer will offer it.
- Import one account at a time, choosing the destination deliberately for each.
Related import problems
Skip the manual edit — fix it automatically
Identifying the format from content rather than filename is exactly what an extracted, extensionless file needs. Free, no signup, no upload.
Open the fixer