Your bank portal produced a camt.053 file, and opening it got you a thousand lines of nested XML: Ntry, BkToCstmrStmt, CdtDbtInd, amounts buried four levels deep. CAMT.053 is the ISO 20022 bank-to-customer statement, the format European banking is standardizing on, and it was designed for ERPs, not eyes. Our converter reads the file and gives you a clean spreadsheet: one row per transaction with dates, descriptions, amounts, and running balances in columns.
The reliability part matters more than it looks. CAMT.053 files state their own opening and closing balances, and Ledger Tome checks its output against them: running balances are reconstructed from the statement's opening balance, and if the result doesn't land exactly on the stated closing balance, you get a warning instead of a spreadsheet with silently wrong numbers.
This page explains what's inside a CAMT.053 file, why "it's XML, Excel can open XML" doesn't survive contact with reality, and how to get analysis-ready data out.
Why You Can't Just Open a CAMT.053 File
It's XML, so it looks approachable. Then you try:
Deeply nested structure
A transaction's date, amount, direction, and description live at different depths under different parents. Flattening that into rows is the entire problem.
Excel's XML import produces a maze
Mapping the schema by hand in Excel yields dozens of half-empty columns and split rows, not a transaction table.
Signs live in a separate field
Amounts are unsigned; direction comes from CdtDbtInd elements. Miss that and every debit becomes a credit.
Versions and namespaces vary
Banks ship different camt.053.001.0x versions with different namespace prefixes. A parser that only knows one bank's flavor breaks on the next.
The data is complete, precise, and structured. It just was never meant for human eyes.
What Is a CAMT.053 File?
CAMT.053 is the ISO 20022 bank-to-customer statement: the XML message European banks use to deliver end-of-day account statements, and the designated successor to SWIFT MT940.
You typically end up holding one because a Swiss, German, or Nordic bank portal exports it (in Switzerland, CAMT is already the standard), an ERP integration delivered it, or a migration away from MT940 switched the format under you. Ledger Tome reads any camt.053.001.0x version, whatever the namespace prefix, including extensionless downloads identified by content.
What's inside a CAMT.053 file:
<Ntry>
<Amt Ccy="EUR">42.50</Amt>
<CdtDbtInd>DBIT</CdtDbtInd>
<Sts>BOOK</Sts>
<BookgDt><Dt>2026-01-15</Dt></BookgDt>
<NtryDtls><TxDtls><RmtInf>
<Ustrd>Invoice 2026-014</Ustrd>
</RmtInf></TxDtls></NtryDtls>
</Ntry>
Statement in SWIFT MT940 instead? See MT940 to Excel . Need to produce CAMT.053 rather than read it? See PDF to CAMT.053 .
Common Ways to Read a CAMT.053 File
Open It in a Browser or Editor
Pretty-printed XML you can scroll forever. Confirms what it is; analysis impossible.
Excel's XML Import
Hours of schema mapping producing fragmented columns and duplicated rows. The nesting defeats it.
Import Into an ERP, Then Export
Works if you have the ERP and the configuration; a long detour if you just need the transactions.
Automated CAMT.053 Conversion
Parses any version natively, flattens the nesting, applies the direction signs, and verifies balances against the statement's own numbers. Free to start.
CAMT.053 to Excel: Method Comparison
| Method | Time Required | Accuracy | Best For | Cost |
|---|---|---|---|---|
| Text editor / browser | Instant | Read-only scrolling | Confirming file contents | Free |
| Excel XML import | 1-2 hours per schema | Fragmented output | The very determined | Free |
| ERP round-trip | Hours, if configured | Depends | Existing ERP users | Varies |
| Ledger Tome | Under a minute | Balance-verified | Any camt.053, any bank | Free to start |
Why automated conversion wins: ISO 20022's nesting rules are exactly the kind of thing software should know so you don't have to.
How Ledger Tome Converts CAMT.053 to Excel
Ledger Tome parses ISO 20022 statement files natively and turns them into clean spreadsheets.
Upload
Upload your camt.053 file
Native Parsing
Any version and namespace handled; amounts, directions, and nested descriptions flattened into rows
Balance Check
Running balances reconstructed from the statement's opening balance and verified against its closing balance
Download Excel or CSV
One row per transaction, ready for analysis
If the reconstructed balances don't land exactly on the statement's stated closing balance, Ledger Tome warns you rather than showing numbers that look right and aren't.
From Nested XML to a Clean Spreadsheet
Before: Raw CAMT.053
After: Spreadsheet columns
Use Cases for CAMT.053 to Excel Conversion
Treasury Reviews
Reading multi-account CAMT deliveries without an ERP in the loop.
Audit and Workpapers
Balance-verified transaction listings straight from source files.
Swiss Administration
CAMT is the Swiss standard already; spreadsheets are still where analysis happens.
Post-Migration Surprises
The bank switched you from MT940 to CAMT and your old workflow broke.
Client Sent an XML Statement
Bookkeepers receiving whatever the client's bank portal produced.
Just Opening the File
Sometimes you only need to see what is in it. That counts too.
Who CAMT.053 to Excel Conversion Is For
This type of conversion is commonly used by:
Treasury & Finance Teams
Reviewing statement deliveries outside the ERP.
Accountants & Bookkeepers
Swiss, German, and Nordic practices reading client files.
Auditors
Independent listings with verified balances from source statements.
Financial Analysts
Getting bank activity into Excel where the work happens.
Developers & Consultants
Inspecting CAMT deliveries during integrations, without writing an ISO 20022 parser.
Anyone Handed a camt.053 File
If you didn't choose the format, you shouldn't need to learn it.
Related Converters
Ledger Tome supports multiple input and output formats. Choose the one that fits your workflow:
The SWIFT-format sibling of this page.
The other direction: statements into ISO 20022.
Migrating SWIFT statements to ISO 20022.
The anglosphere equivalent: OFX downloads into spreadsheets.
PDF statements into Excel.
What Ledger Tome Does Not Do
For clarity and transparency, Ledger Tome does not:
- Access bank accounts directly
- Initiate or modify transactions
- File taxes or submit reports
- Replace accounting software
- Categorize transactions automatically
It focuses solely on converting statement data into structured, readable formats.
Security & Privacy
Your Financial Data is Protected
We take statement security seriously. Here's how we protect your data:
-
Encrypted Transmission
All uploads use 256-bit SSL encryption (the same security banks use)
-
Secure Processing
Files are processed in isolated, secure environments with no human access
-
Automatic Deletion
All uploaded files are permanently deleted after 7 days (or immediately upon request)
-
No Training Data
Your statements are never used to train AI models or shared with third parties
-
No Account Access
We never access your bank account directly or store your banking credentials
-
GDPR Compliant
Full compliance with data protection regulations
-
No Permanent Storage
We don't maintain a database of your financial information
Privacy First: We process your data solely for conversion purposes. No marketing, no data selling, no third-party sharing.
Frequently Asked Questions
How do I open a CAMT.053 file?
Can I get CSV instead of Excel?
Which camt.053 versions are supported?
Are the balances in the output reliable?
Where do the descriptions come from?
How are debits and credits handled?
My file contains several statements. What happens?
What columns does the output contain?
Is XML parsing safe with sensitive bank data?
Can I convert the CAMT.053 into another import format instead?
How much does it cost?
Troubleshooting Common Issues
A balance warning appeared
The statement's entries don't add up to its stated closing balance, which happens with truncated exports. Transactions are still parsed; only the running balances are withheld. Check the source file is complete.
File isn't recognized
Confirm it's actually CAMT.053: it should contain a BkToCstmrStmt element. Banks also export camt.052 (intraday) and camt.054 (notifications), which are different messages.
Some entries were skipped
Entries without a parseable amount or date are skipped with a warning stating how many. Check the source if the count surprises you.
Descriptions look sparse
Some banks put minimal remittance info in the file. The parser shows what the bank encoded; there's nothing hidden to recover.
Need the data in accounting software, not Excel
Export MT940, OFX, or QBO from the same preview instead, or see the related converters above.
Summary
CAMT.053 files carry complete, precise statement data in XML built for ERPs. Browsers scroll it, Excel's XML import fragments it, and hand-flattening risks exactly the sign and balance errors that make financial data worthless. Automated conversion parses any version natively and proves its own output: balances reconstructed from the statement and verified against it.
If you have a camt.053 file you need to actually read, Ledger Tome converts it in under a minute.
Ready to Read Your CAMT.053 File?
Stop scrolling nested XML. Convert your first CAMT.053 file to Excel in minutes.
Used by treasury teams, accountants, auditors, and analysts