“One file contains several accounts”
Downloading everything at once seems efficient until the import. Most software imports into one account at a time, so a combined file either lands entirely in the wrong place or is refused for containing more than expected.
Symptoms
Every transaction lands in a single account regardless of origin The importer asks which account to use and offers only one choice The file contains more transactions than any one account should have
What actually causes it
The importer targets one account
Most import routes ask for a destination and send everything there. A file spanning three accounts becomes three accounts' worth of transactions in whichever one you picked.
Multiple statement blocks in one OFX
OFX can hold several statement responses, each with its own account. Software that reads only the first silently ignores the rest, so part of your data disappears without any error.
A CSV with an account column
Combined CSV exports distinguish accounts by a column, which importers ignore. Every row is treated as belonging to the destination you chose.
How to fix it
- Drop the file into the fixer below to see how many transactions it holds — a count far above what one account should have confirms the diagnosis.
- Re-download per account where the bank allows it; that is faster and safer than splitting the file by hand.
- If you must split a CSV, filter by the account column and save each part separately, then re-check each file before importing.
- Import one account at a time, choosing the destination deliberately for each.
Related import problems
Skip the manual edit — fix it automatically
The transaction count is what reveals a combined file before you import it into a single account and have to unpick it afterwards. Free, no signup, no upload.
Open the fixer