Statement import problems

If a bank statement will not import, the cause is usually the file, the column mapping, or duplicates. The basics are in Import a bank statement.

The file is rejected

• Kontala accepts CSV and OFX files up to 5 MB - nothing else.
• A CSV needs a header row and at least one transaction row, or you will see "the CSV file is empty".
• If the file cannot be read at all, re-export it from your online banking rather than editing the old one.

Rows are flagged in the preview

On the Check the columns step, any row Kontala cannot read is flagged with the reason - a missing date, a date that does not match the selected Date format, a missing description, or an amount that is not a number.

Fix the mapping rather than the file: change the dropdowns and the Preview re-reads your rows immediately. Common culprits are the wrong Date format and mixing up One amount column with Separate money-in / money-out columns. Statement import formats lists exactly what each column accepts.

Rows skipped as duplicates

The Import complete summary counts rows "skipped (already imported)". Kontala matches on date, amount, and description, so re-importing an overlapping export is safe and expected.

One edge case: if a genuinely separate, identical payment (same day, same amount, same description) arrives in a different file, it is skipped too. Add that one with Add a transaction manually.

No Upload statement button

Importing needs the Banking permission level or above. Ask an owner or admin to check your level in Users.