International bank statement import (camt.053, MT940, CSV, Excel, PDF)

Typing bank payments in by hand is slow and error-prone. Importing the bank statement directly is faster and more accurate; the file your bank already produces becomes your collection record. Flatmine reads the international standard formats so you are not tied to one bank or country: camt.053 (ISO 20022 XML), MT940, CSV and Excel, and it can even read a receipt image or PDF with AI.

camt.053 (ISO 20022 XML) is the modern international standard, used by banks across Europe and beyond; it carries rich, structured detail (amounts, dates, counterparties, references); its siblings camt.052 (intraday account report) and camt.054 (debit/credit notification) are read the same way. MT940 is the long-established SWIFT statement format still common worldwide, with MT942 covering intraday movements. CSV and Excel (.xlsx) are the universal fallback; almost every bank can export them, and a column-mapping step adapts them to your data. And when all you have is a receipt (an image or a PDF) Flatmine can read it with AI and turn it into the same structured lines.

After import, each line is matched to the right unit or account automatically, using signals like the IBAN and payment reference. You stay in control: the system proposes the matches, an operator confirms them, and only then is the collection recorded. Multi-currency statements are handled, so cross-border communities work the same way.

Step by step: 1) Download the statement from your online banking; camt.053 or MT940 is ideal, CSV/Excel also works. 2) Upload the file to the bank import screen in Flatmine; the format is detected automatically. 3) The rows are read and suggested against units using previously learned IBAN matches. 4) Link an unmatched row once by hand; the system learns the counterparty IBAN and matches it automatically on the next statement. 5) Approve the suggestions: collections post to the ledger and you only deal with the exceptions.

Importing does not replace good records; it feeds them. Keep the original statement file, review unmatched lines instead of forcing them, and let the running balance update from confirmed entries. The result is faster month-ends, fewer typing mistakes, and a collection record that matches the bank line for line.