Import problems
What each import message means and how to fix it.
Rows with problems are skipped and listed by line number (line 1 is the header); the rest of the file still imports. For holdings, any problem stops the whole import.
Messages about a row
| Message | What to do |
|---|---|
Invalid date: "…" | Use 2026-06-28, 28/06/2026 or 28.06.2026. Two-digit years aren't recognised. Month-first dates are read day-first, so convert them first (why) |
Invalid amount: "…" | Remove currency codes and brackets from the amount column. €, $ and £ are fine |
Missing description | The row's description column is empty. Map a different column, or fill it in |
Missing required column: … | Map a column to Date, Amount and Description in the column step |
If the preview says No rows could be parsed with this mapping, the Date or Amount column is probably mapped to the wrong column.
Messages about the file
| Message | What to do |
|---|---|
| Choose a file smaller than 10 MB. | Export a shorter date range |
| This file has N rows. Import up to 10,000 at a time… | Split the export by date and import each part |
| Older Excel files (.xls) are not supported… | Open it in your spreadsheet app and save as .xlsx or CSV |
| The file needs a header row and at least one data row. | Make sure the first row holds column names |
| This file has statements for N accounts… | Export each account on its own and import each into its account |
| This XML file is not a CAMT.053 bank statement or OFX file… | Choose your bank's CAMT.053 or OFX export, or use CSV |
| Investment QIF files are not supported… | Export the account's transactions instead |
| This file type is not supported here… | Use one of the supported formats |
Wrong account?
If at least half the rows already exist in another account, Euporia asks you to check the file belongs to the account you chose. Pick the right account, or select Import anyway.
Names look garbled
You may see This file isn't UTF-8, so it was read as Western European text. Export the file again as UTF-8 and re-import; duplicates are skipped.
Dates look wrong after a QIF import
QIF dates are read as day/month. If they look swapped, check the export settings in the app that made the file.
Some transactions are missing
- Rows already in that account were skipped as duplicates. The summary says how many.
- CAMT.053 pending entries are left out until they're booked.
- Check the date filter on Transactions: it shows This month by default.
Nothing was saved
Import failed. Nothing was saved. means the whole import was cancelled, so it's safe to try again.
Last updated on