A statement import failed

Import errors protect existing banking data from duplicates, overlaps and files that cannot be interpreted safely.

Wrong file type or format

Confirm that you selected the correct bank and importer and that every file uses an accepted extension. A valid extension is not enough if the file headers, XML structure, dates, currency or required fields do not match the bank format.

Duplicate file

Flinq compares file-content hashes across the system. If the content was imported before—even with a different filename or in another office—the new import is blocked. Open the conflicting statement shown by Flinq and confirm whether it already contains the required data.

Conflicting or overlapping data

An account and date may already have a balance entry, or a file may contain duplicate rows. Compare the bank, office, account, date and value in the error with the existing statement. Do not remove applied statement history solely to force a replacement import.

Incomplete or multi-page statement

Upload related pages together where possible. Flinq groups sequence-aware files, orders them and checks for the closing information required by the format. A statement can remain Incomplete while additional pages or a final closing balance are missing.

Missing or unsupported values

Check for missing account identifiers, dates, currencies, balances, headers or transactions required by the importer. The error message normally identifies the affected row or account.

A larger upload was interrupted

Keep the original file. Return to Banking > Statements > Import larger files, choose the same bank and importer, and select the same original file. Flinq verifies the parts already received and continues from the last completed part, so this retry is safe.

If your session expired, sign in again before following the same steps. If Flinq says the selected file differs, choose the exact original file rather than a renamed, edited or regenerated copy.

The statement format changed during upload

If Flinq reports that the selected statement format changed, do not resume the earlier upload. Start a new upload with the current importer configuration. Preserve the original file until the new import has completed.

Resuming a verified upload does not bypass statement duplicate protection. If the same statement content was already imported, Flinq still blocks the duplicate and points you to the existing statement.

Escalate safely

Preserve the original file and error details. Contact Flinq support with the bank, importer, office, import time and error text. Use your approved secure transfer method if the original bank file is required for investigation.