Choose a CAMT statement
Select a UTF-8 camt.053.001.02 or camt.053.001.08 XML file up to 2 MB.
Make CAMT statement data readable.
CAMT Statement Viewer
Inspect CAMT.053 XML bank statements locally. Review accounts, balances and debit or credit entries, then download Excel, CSV or structured JSON.
CAMT Statement ViewerYOUR WORKSPACE
CAMT.053.001.02 and CAMT.053.001.08 XML. PDF statements, other message versions and MT940 export are not supported.
Processed privately in your browserNo uploadNo signup
A simple workflow
Three steps. One less thing to do.
Review entries and balances
Inspect account information, statement periods, dates, directions, references and transaction details.
Download your data
Save all tables as Excel, one row per entry as CSV, or the normalized document as JSON.
Made for the everyday
A useful part of your workflow.
Bank export inspection
Read structured CAMT files without navigating XML.
Entry-level review
Keep credited and debited entry amounts separate from underlying transaction details.
Spreadsheet preparation
Export exact source strings, including references and account identifiers, for your own checks.
Good to know
A few useful answers.
The details that matter before you use CAMT Statement Viewer.
Which versions are supported?
This milestone reads CAMT.053.001.02 and CAMT.053.001.08 BankToCustomerStatement documents only. Other CAMT versions, payment messages, PDF statements and MT940 inputs are not supported.
How are batched entries handled?
CSV has one row per bank entry. The Excel transaction-details sheet links details to the statement and entry position. Missing detail amounts remain blank rather than repeating the entry total.
Are amounts signed or converted?
No. Source amount strings and explicit CRDT/DBIT direction are preserved separately. Currency is taken from each amount. No exchange conversion, balancing or inferred transaction amount is performed.
Can I export MT940?
No. This milestone does not claim a complete mapping from CAMT details to MT940. Use Excel, CSV or JSON for supported exports.
What does validation mean?
The viewer checks XML safety, supported version and required entry fields. It does not certify a bank-specific schema profile, verify balances or confirm that a transaction settled.
Do bank details leave my device?
No. Parsing and export are local. Account numbers, names, filenames, amounts, references and remittance text are excluded from analytics and the control database.
What are the limits?
Files must be UTF-8 XML up to 2 MB, with at most 50 statements, 5,000 entries, 30,000 XML elements and 64 nesting levels. DTD, entity definitions and external inclusions are rejected.
What do the downloads contain?
Excel includes entries, statement metadata, balances and transaction details. CSV includes entries only. JSON retains the normalized model and missing or invalid field states. XLSX cells are text, and CSV formula-like values receive an apostrophe.