Free camt.053 viewer & ISO 20022 statement validator
Read any camt.053, account by account.
Open an ISO 20022 bank statement (camt.053), intraday report (camt.052) or notification (camt.054) to see balances, entries, codes and counterparties — with the roll-forward checked. Everything happens in your browser; no data is sent to any server.
- Balances & entries per account
- Every code explained
- Roll-forward & totals checked
Drag & drop a camt file hereOpen a camt file
Or click to browse. Reads camt.053, camt.052 and camt.054 XML, versions .02 to .13
More samples:
100% in-browser.
Your file never leaves this device.
Parsed on your device
JavaScript on this page reads the file. Nothing is uploaded, stored or transmitted.
No account, no cost
Every tool is free to use. No sign-up, no paywall, ever.
Open about usage
Our public analytics show exactly what we count — never what your files contain.
Anatomy of a camt.053 entry
Tags, codes and references, decoded.
A statement is XML: abbreviated tags (CdtDbtInd, AcctSvcrRef, SubFmlyCd) wrapped around values. The viewer names every tag, explains every code and checks every value.
- Accounts & IDs
- Amounts
- Dates
- Names & text
- Codes
- Reserved
Lines 107–182 · one entry
A booked credit, field by field
- 1Amount
12500.0012,500.00 GBP — never negative; the indicator gives the direction - 2Credit/debit
CRDTMoney in. DBIT is money out - 3Status
BOOKBooked: part of the closing balance. PDNG and INFO are not - 4Booking date
2026-10-28When it hit the account; the value date can differ - 5Account servicer reference
NW261028000101The bank’s own reference for the entry - 6Bank transaction code
PMNT · RCDT · DMCTPayments · Received credit transfers · Domestic credit transfer - 7End-to-end id
INV-2026-1043Set by the payer and carried unchanged: the key for reconciliation - 8Counterparty
Contoso LtdThe debtor of a credit entry (the creditor of a debit)
A short camt primer
Three messages, one account story.
Banks report to their corporate customers with three camt messages. All of them group entries by account, and all of them use the same balance types and bank transaction codes.
- camt.053Bank-to-customer statementThe end-of-day statement: opening and closing booked balances and every entry booked in the period. Replaces MT940.
- camt.052Account reportIntraday (or interim) report: balances so far and entries booked or pending today. Replaces MT942.
- camt.054Debit/credit notificationAdvice of single debits or credits, often the detail behind one batch entry on the statement.
Balance types you will meet
- OPBD
- Opening booked. Book balance at the start of the reporting period: the closing booked balance of the previous statement.
- CLBD
- Closing booked. Book balance at the end of the reporting period: the opening booked balance plus or minus every entry booked in the period.
- CLAV
- Closing available. Closing balance of funds the account owner can use at the end of the period (booked balance adjusted for float and holds).
- ITBD
- Interim booked. Book balance calculated during the business day, at the time given; it can still change before the day closes.
- PRCD
- Previously closed booked. Closing booked balance of the previous statement, as reported then. Some banks send it instead of (or as well as) OPBD.
- FWAV
- Forward available. Balance that will be available on a future date (Dt), taking value-dated entries into account.
Amounts are never negative
CdtDbtIndsays which way money moved:CRDTin,DBITout. A reversal (RvslInd) keeps the direction of the booking itself.Booked is what counts
Opening booked + booked entries = closing booked. Pending (
PDNG) and information entries are reported but not in the balance; the viewer checks the roll-forward for you.Codes classify every entry
Bank transaction codes nest domain → family → sub-family (
PMNT/RCDT/ESCTis a received SEPA credit transfer). Banks may add their own underPrtry.Versions differ in the details
.001.02writes<Sts>BOOK</Sts>andBIC;.001.08writes<Sts><Cd>BOOK</Cd></Sts>andBICFI. The viewer reads .02 to .13.
Every code list, the MT940 field mapping and the message family are in the ISO 20022 reference.
What it shows
From raw XML to a readable statement.
Every view shares one selection: pick an entry in the statement and its XML lines, its place in the tree and its values follow.
No. 01
Statement
Per account: IBAN or account id, owner, servicer, period and sequence numbers, every balance with its code explained, credits, debits and net, and the entries with references, counterparties and remittance.
No. 02
Entry detail
Open any entry for everything it carries: bank transaction code in words, batch details, each transaction’s end-to-end id, UETR, parties, agents, remittance and return reason.
No. 03
Structure & XML
The message as a tree, and the raw XML with line numbers, values coloured by what they hold and an inspector that decodes codes, amounts, IBANs and BICs.
No. 04
Validation
Roll-forward, transaction summary, batch totals, IBAN check digits, BIC format, currency decimals, dates and duplicate references — each with its line and the rule behind it.
Related tools
More free tools for payment files.
The same private, in-browser approach for payment initiation files and SWIFT statements — and an API and MCP server for agents.
pain.001 · pain.008 · pain.002
Payment File Viewer
Credit transfer and direct debit files checked before they go to the bank: control totals, IBANs, BICs, decimals and SEPA rules. Status reports with every reason code explained.
.xml
- Converter
SWIFT MT940 · MT942
MT940 Viewer
Every :61: statement line decoded, structured :86: details read, balances rolled forward — and the whole file converted to camt.053.001.08.
.sta · .940 · .mt940 · .txt