EU Bank Statement Reader — Open camt.053 and MT940 Files and Convert to CSV

Open a camt.053 or MT940 bank statement and check it adds up

Paste or drop a camt.053 (XML) or MT940 statement to see each account, its opening and closing balance and every entry as a table, check that opening balance plus entries equals the closing balance, catch duplicated references and gaps between statements, and download the entries as CSV.

The file is read in this browser tab and never leaves your device. Account numbers are masked to their last four characters unless you tick the box. Independent of SWIFT, ISO and every bank. The layouts are read from memory of the public ISO 20022 and SWIFT documents; no real bank file or bank validator was available when this was built.

1. Your statement file

A .xml (camt.053) or .sta, .mt940, .txt (MT940) download from your bank's business portal. The format is detected from the first character.

Choose a statement file …or paste the file text

Show full account numbers in the CSV (off: masked to the last four characters)

Choose a file or paste the text, then click Read and check.

Result

Statements

Statement	Account	Currency	Opening	Closing	Entries

Entries

Line	Booked	Counterparty	Reference	Text	Amount

The model, and what it leaves out

camt.053 / 052 / 054: each Stmt, Rpt or Ntfctn is one statement with Acct, Bal (OPBD opening, CLBD closing) and Ntry entries. Credits are positive, debits negative, and a reversal indicator flips the sign. Entries whose status is not BOOK are listed but left out of the balance check.
MT940: :20: starts a statement, :25: is the account, :60F:/:60M: the opening balance, :61: an entry (C credit, D debit, RC/RD reversals) with its :86: text, :62F:/:62M: the closing balance. Amounts use a comma. A SWIFT {4: envelope is stripped. German-style ?20/?32 subfields give the remittance text and counterparty.
Balance check: opening + booked entries must equal closing, in whole minor units with no floating point. A difference is an error and names the amount.
Continuity: consecutive statements of one account should join: one statement's closing is the next one's opening.
Other checks: account IBAN length and mod-97 check digits, impossible dates, amounts with too many decimals, a missing indicator, duplicate references, entries in a different currency to the statement.
Not checked: that the file matches your bank's online statement or your books, bank-specific variants and private codes, statements with several currencies, digital signatures, and anything that needs the bank's own records.

Common questions

How do I open a camt.053 file?

Paste the XML or drop the file onto this page. It reads each statement's account, opening and closing balance and every entry, and shows them as a table with a CSV download, so you can see what is in the file without an XML editor.

How do I convert an MT940 file to CSV or Excel?

Load the MT940 and press Download transactions as CSV. Each :61: statement line becomes a row with booking and value date, signed amount, currency, counterparty, reference, bank reference and the :86: text, ready for Excel, Google Sheets or an import template.

What is the difference between camt.053 and MT940?

Both carry a bank statement. MT940 is the older SWIFT text format with tagged lines such as :60F: for the opening balance and :61: for each entry. camt.053 is the ISO 20022 XML successor. Banks are replacing MT940 with camt.053, and many accounting tools still read only one of them.

Why does my bookkeeping software reject the statement?

Common causes are a closing balance that no longer equals the opening balance plus the entries after an edit or a missing line, an impossible date, an amount with the wrong number of decimals, duplicated entries, or a gap between two statements. The report lists each with its line number.

How does the balance check work?

For each statement it adds the signed booked entries to the opening balance and compares the result with the closing balance. If they differ it says by how much, because a single missing, duplicated or edited entry of exactly that amount usually explains it. Pending and informational entries are left out.

Does this check my IBAN?

If the account is an IBAN it checks the length for the country and the mod-97 check digits, and warns when they fail. An MT940 account field that is a bank code and account number instead of an IBAN is not checked.

Is it safe to put bank statement data into a web page?

The page runs in your browser, the file is read locally and nothing is uploaded; a test in the code asserts there are no network calls. Account numbers are masked in the report and the CSV unless you choose otherwise. Your own policies still decide whether you may open bank data in a browser.

What does this not check?

Whether the file agrees with your bank's online statement or your books, bank-specific variants and private codes, camt files with several currencies on one statement, and signatures or envelopes. A clean result means the file is consistent, nothing more.