camt.053 Viewer & Excel / CSV Converter

What it reads. The three ISO 20022 account-reporting messages: camt.053 (statement, usually end of day), camt.052 (intraday account report) and camt.054 (debit/credit notification). Versions .02, .04 and .08 are read with the same mapping, including the differences between them: BIC or BICFI for banks, a status text or Sts/Cd for entries, and Dbtr/Nm or Dbtr/Pty/Nm for parties. A version the tool has not been checked against is still read, with a warning, so you can see what the file contains.

What you see. For every statement: the account (IBAN, holder, bank), the period, the opening and closing balances (OPBD, CLBD and others) with their dates, and then each entry with booking date, value date, credit or debit, amount, currency, counterparty with IBAN and BIC where the file has them, the end-to-end reference, the payment reference or free text, the bank transaction code (for example "Payments / Received credit transfer / SEPA credit transfer") and the bank's own reference. A batch entry, where the bank books several payments as one line, is shown as one row with its total, and its individual payments are available in the export.

Excel and CSV. The Excel file has three sheets: Entries, Balances and Details. Dates are real Excel dates, amounts are numbers (debits negative), and the header row is frozen with a filter. The CSV export lets you choose the delimiter (semicolon is the default for German-language Excel), uses a decimal comma if you want one, starts with a byte order mark so umlauts open correctly, and prefixes cells that start with = + - or @ with an apostrophe so a spreadsheet cannot run them as formulas. If a ZIP file holds several camt files, all of them are read and listed together.

Checking your work. The signed amounts of the entries are what you add to the opening balance to reach the closing balance; compare that with the closing balance shown. A camt.054 notification or a camt.052 report may cover only part of the day, so its balances need not match a full statement.

XML files of the types camt.052, camt.053 and camt.054 (versions .02, .04 and .08 checked; others are tried with a warning), up to 40 MB, or a ZIP file with up to 60 such XML files. Output: XLSX and CSV. Not supported: MT940 and MT942 text statements, CAMT.053 files from a format other than ISO 20022 XML, and encrypted or signed envelopes around the XML.

1. Drop the camt XML file (or a ZIP of several) onto the box. The file is read in your browser.
2. Check the account, period and balances at the top, then look through the transactions. Use the filter to find a name, a reference or an amount.
3. Choose the CSV delimiter and decimal mark if you want a CSV, or press the Excel button.
4. Open the download in Excel, LibreOffice or your bookkeeping program.

• Looking at a statement the bank sent as XML without importing it into accounting software
• Matching incoming payments to invoices by end-to-end reference or structured reference
• Sending an accountant an Excel version of one day's or one month's entries
• Checking what a bank's camt export contains before configuring an import
• Comparing a camt.052 intraday report with the camt.053 that follows it

The viewer shows what the XML says, using the generic ISO 20022 element names. Banks add their own implementation rules and codes (Swiss, German, Nordic and SEPA guides differ), so a field can mean something slightly different for your bank, and compatibility with every bank's variant is not claimed. Bank transaction codes are explained only for the common generic codes; others are shown as written.

It does not check the file against the XSD or against your bank's rules, does not reconcile accounts and does not verify that the statement is genuine. Very large files (tens of megabytes) take a moment to parse because the browser has to read the whole XML. Check the totals against your bank's own statement before you rely on an export.