Convert a camt.053 ISO 20022 bank statement (.xml) to a clean CSV for Excel or Google Sheets, with a running balance checked against the booked opening and closing balances. Free up to 100 rows.
Only have a PDF statement? Use the PDF statement converter.
camt.053 is the ISO 20022 bank-to-customer statement many European banks now export next to, or instead of, MT940. It's XML: each Ntry is one booking, with an unsigned amount and a CRDT or DBIT mark, a booking date, and usually a counterparty name and remittance text. Excel shows the tags, not a table. Utilly reads every booked entry into a row, takes the creditor name when money goes out and the debtor name when money comes in, and checks that opening booked balance + entries = closing booked balance for every statement in the file.
.xml. Treasury and accounting systems (SAP, for example) store the same message.Ntry becomes a row. You don't need to rename the file, and you don't need to pick columns.The first entry in our sample camt.053 (a made-up Dutch business account):
<Ntry>
<Amt Ccy="EUR">1850.00</Amt>
<CdtDbtInd>DBIT</CdtDbtInd>
<BookgDt><Dt>2026-10-01</Dt></BookgDt>
<AcctSvcrRef>EX26100100001</AcctSvcrRef>
<RltdPties><Cdtr><Nm>Voorbeeld Vastgoed BV</Nm></Cdtr></RltdPties>
<RmtInf><Ustrd>Huur kantoor oktober 2026</Ustrd></RmtInf>
</Ntry>
is this row in the CSV:
Date,Description,Amount,Balance
2026-10-01,Voorbeeld Vastgoed BV - Huur kantoor oktober 2026,-1850.00,6562.65
| camt.053 field | CSV column |
|---|---|
BookgDt (booking date), then ValDt if there's no booking date | Date, written 2026-10-01. A datetime such as 2026-10-01T00:00:00+02:00 is read as that calendar day. |
Amt plus CdtDbtInd: CRDT or DBIT | Amount with a decimal point: credits positive, debits negative. camt stores the figure unsigned; the direction code supplies the sign. A reversal (RvslInd) keeps the sign the bank already put on CdtDbtInd. |
Counterparty Nm (the creditor when money goes out, the debtor when money comes in) and RmtInf/Ustrd remittance text | Description: the name, a dash, then the payment description. |
AddtlNtryInf (card payments, bank fees, and other free text) | Description, as one line, when there's no structured name and remittance. |
A batch Ntry with several TxDtls | One row per detail when every detail has its own amount and those amounts add up to the booked entry; otherwise the entry stays a single row. |
OPBD or PRCD opening booked balance, CLBD closing booked balance | Balance: a running balance from each statement's opening figure, filled in only when the statement ties. |
IBAN, BIC, message ids, end-to-end references marked NOTPROVIDED | Not in the CSV. Only the last 4 digits of the account (from the IBAN or Othr/Id) are kept, as the .QBO/OFX account ID. |
Every camt.053 element, including the ones that don't end up in the CSV (GrpHdr, Bal types, BkTxCd, TxDtls), is explained with this sample on camt.053 format explained.
A camt.053 statement usually carries its own proof: an opening booked balance and a closing booked balance. We add up the entries in between and compare. For the sample file:
| Statement | Opening | Entries | Closing (CLBD) | Ties? |
|---|---|---|---|---|
| 1–15 October 2026 (7 entries) | 8,412.65 | +1,067.96 | 9,480.61 | Yes |
| 16–31 October 2026 (6 entries) | 9,480.61 | +1,616.84 | 11,097.45 | Yes |
When a statement doesn't tie, the preview says how many do, the Balance column stays blank, and you know to download the period again before importing. A cut-off file, or a camt.052/054 notice that never included opening and closing balances, shows up here instead of later in your reconciliation.
Columns are separated by commas and decimals use a point (-1850.00), which Google Sheets, Numbers and most importers already expect. Excel whose region is set to the Netherlands, Germany or France often wants semicolons and decimal commas, so double-clicking the file can dump every column into one or treat the amounts as text. To load it cleanly:
Ntry entries. They often have no OPBD/CLBD balances, so the Balance column stays blank and the preview says the check is incomplete.Sts = PDNG) are left out. Free up to 100 rows per file; files up to 20,000 rows.| Problem | Fix |
|---|---|
Excel shows raw XML tags such as <Ntry> and <CdtDbtInd> | That's the camt.053 file itself. Convert it here and open the .csv instead. |
| "No booked entries (Ntry) found" | The statement covers a period with no bookings, or the XML is a different ISO 20022 message (a payment initiation, for example). Export a camt.053 for a period that has entries. |
| The balance check fails | Often a partial download, or a camt.052/054 file with no opening and closing balances. Download the full camt.053 period again. If a complete statement still fails, the file itself doesn't add up; ask the bank. |
| All amounts land in one column in Excel | Your Excel region expects semicolons. Use Data → From Text/CSV as described above. |
| A payroll or collection batch is one row | We only split a batch when every detail lists an amount and those amounts add up to the booked total. Otherwise the entry stays one row so the statement still ties. |
| It's an MT940 (.sta / .940) file | That's the older SWIFT text format. Use the MT940 to CSV converter. |
03/16/88 records), puts the decimal point back on amounts in cents and checks each day against the opening and closing ledger.:61:/:86: bookings with the same kind of balance check. We don't convert camt.053 into MT940.Free for files up to 100 transactions, which covers a typical month of activity. Larger files (a year of catch-up, a client's full history) use 1 credit from the same $9 pack of 5 as our PDF statement converter, or unlimited on Pro at $19/month. The preview is always free.
Yes for files up to 100 transactions: no sign-up, no watermark. Bigger files (multi-month catch-up work) use 1 credit from the same $9 / 5-credit pack as our PDF converter, and the preview is always free.
No. Files are processed in memory and deleted after 1 hour. We never use your data for AI training.
Yes. Click a sample button under the upload box. It opens a made-up export from a fictional bank in the same preview your own file gets, and every format is free to download, so you can test an import in a test or backup company file first. Don't import a sample into your real books.
A bank-to-customer account statement in the ISO 20022 XML format, the successor many European banks offer next to SWIFT MT940. A Document wraps one or more Stmt blocks: the account (often an IBAN), opening and closing booked balances (OPBD or PRCD, and CLBD), and Ntry entries. Each entry has an unsigned amount, a CRDT or DBIT mark, a booking date and usually a counterparty and remittance text. Banks save it as .xml.
Only as XML. Excel shows tags such as Ntry and CdtDbtInd, not a table of transactions. Convert it here and open the CSV instead: one row per booked entry with a real date, a signed amount and a running balance, ready to sort, filter or Save As .xlsx.
The booking date (BookgDt) when the entry has one, because that's the date on the statement; otherwise the value date (ValDt). A datetime is read as its calendar day.
CRDT is money in and positive; DBIT is money out and negative. camt stores the amount unsigned, so the direction code is what gives the CSV its sign. A reversal keeps the sign already on CdtDbtInd (a reversed debit comes through as a credit).
The counterparty name and the remittance text: the creditor when money goes out, the debtor when money comes in, then RmtInf/Ustrd (or a structured creditor reference). Card payments and bank fees that only have AddtlNtryInf keep that text as one line. IBANs and BICs are left out of the description.
Yes. For every statement we add the entries to the OPBD (or PRCD) opening booked balance and compare the result with the CLBD closing booked balance, and the preview says whether each one ties. When they all tie, the CSV gets a running Balance column; if one doesn't, Balance is left blank and the preview warns you.
Yes. Statements for the same account and currency are joined in order, so a month of daily statements becomes one CSV. Each different account gets its own tab in the preview, its own CSV and a combined CSV with an Account column. One credit covers the whole file.
No. We read camt.053 and write a spreadsheet (and, from the same preview, OFX, QBO, IIF, QIF or Xero CSV). We don't write SWIFT MT940 messages. If your file is already MT940, use the MT940 to CSV converter.
Yes when they list the same kind of Ntry entries. camt.052 is an intraday report and camt.054 is a debit or credit notification; they often have no opening and closing balances, so the Balance column stays blank and the preview says the check is incomplete.
Yes, from the same preview: Xero CSV, OFX, QuickBooks .QBO and .IIF and Quicken .QIF. The OFX and .QBO files carry the file's own currency (for example EUR), and their ending balance is the statement's closing booked balance when every statement ties. We don't write QFX.
Free converter →
Free converter →
Free converter →
Free converter →
Free converter →
Free converter →