Import: what to do when it fails

The file is refused or nothing is recognised

• Accepted files: .csv, .xml (SEPA camt.053), .ofx and .qfx. Excel files are accepted for broker trades, not for bank statements; export CSV from the bank instead.
• PDF: not parsed directly. Open the PDF, copy the text and use the “Paste text” tab.
• Zero transactions found: the bank chosen in the dialog and the file do not match, or the file is a summary rather than a transaction list. Choose the bank again, or leave detection on automatic. The structure of the file decides before the bank choice: a camt.053 file is parsed as camt.053 even if a CSV bank is selected.

Czech characters look wrong

The file is read as UTF-8 first; if that fails, as Windows-1250 (Air Bank and most Czech banks), then ISO-8859-2. If the preview still shows wrong characters, the bank exported in yet another encoding. Re-export the statement, preferring UTF-8 if the bank offers a choice.

Columns are assigned wrongly

Smart detection recognises columns by content, not by header names. When it is unsure, the dialog shows the columns and lets you assign date, amount, description and counterparty by hand. You can also let the AI propose the mapping from the header and a few rows; the mapping is then saved with the bank, so the next import does not ask again. The whole statement is never sent to the AI.

Numbers with a comma as the decimal separator and dates in d. m. yyyy are handled; if amounts come out multiplied by 100 or 1000, the thousands separator was read as a decimal point, which the manual mapping’s number-format option fixes.

Everything is marked as duplicate

The preview compares each row with what the account already holds: by the bank’s transaction code when the file has one, otherwise by date, amount and description. If you already imported the same period, all rows are duplicates and skipping them is correct. If you imported into a different account by mistake, remove that import first (below) and import again.

”This account is synced with Wallet”

An account that receives Wallet by BudgetBakers sync refuses CSV imports, because the two sources identify the same movement differently and would create duplicates and wrong balances. Import into a separate account, or disconnect Wallet in Settings and remove its transactions from the account first.

The monthly limit

The Free plan imports up to 500 transactions per calendar month; the count is shown in the import dialog. Premium and Max have no limit. Rows skipped as duplicates do not count.

Balance looks wrong after import

The account balance is recalculated from its transactions after every import. A transfer between two of your accounts is detected and paired; when the two accounts have different currencies, only the source side is adjusted, because the bank’s exchange rate is unknown. Check that transfers were not imported twice from both accounts’ statements with different descriptions; if so, delete one side.

Undoing an import

Every import has a batch id. Open the account, choose “Clean up data” and select the import batch or the source (CSV import, Wallet sync, manual) to remove. Rules and categories are not affected.

Large statements

Import runs in batches on the server. A very large file can take a while; the dialog shows progress and reports a timeout as a message rather than a crash. If it happens, split the statement by period and import in parts; duplicates from the overlap are skipped.