Direct answer
camt.053 is an ISO 20022 bank-to-customer statement in XML. Spreadsheets want rows. F20 FinanceOps flattens camt.053 by element name, keeps references, and checks opening and closing balances against the transactions. StatementBridge is stronger if your job is MT940 into camt.053 for a European package rather than XML into Excel. Browser tools such as ZZP Pulse and TreasuryEase describe local camt-to-CSV conversion; we have not tested them. There is no ISO-issued official converter.
European banks have spent years moving customer reporting from MT940 to camt.053. The XML is self-describing, versioned, and full of parties and remittance that a SWIFT tag cannot hold cleanly. It is also unreadable in Excel. Controllers then paste the file into the first Google result and hope the namespaces match.
F20 walks the tree by element name rather than pinning one namespace version, because banks ship .02, .04, .08 and house dialects. That is an engineering choice documented in the catalog, not a claim that every dialect on earth parses.
What camt.053 conversion has to preserve
Booked entries, not just header balances. Related account servicer references. End-to-end and payment-information identifiers when present. Debit/credit indicator. Currency on every amount so a multi-currency statement cannot be summed into a fantasy total.
camt.052 is intraday. camt.054 is a credit/debit notification. A converter that silently accepts those as if they were a daily statement will wreck a recon. F20's tool is the statement converter. If you have 052/054, do not pretend they are 053.
F20 FinanceOps
Flatten to one row per transaction, references intact, opening and closing checked against the movements. CSV or XLSX. Free, not stored, no account. Then quality-score or reconcile.
F20 does not write MT940 back out from camt.053. Some ERPs still want MT940. ValidateFin describes a camt-to-MT940 browser tool; we have not tested it. If your problem is 'XML in, legacy importer', that is a different job from 'XML in, spreadsheet out'.
StatementBridge and EU specialists
StatementBridge's documented direction on the page we read is MT940 toward camt.053 and spreadsheets. That helps teams whose bank is late to ISO 20022 while the accounting package has already moved. F20's documented direction is camt.053 toward rows. Opposite arrows. Both can be correct.
Browser converters and libraries
Several free pages claim 100% local camt.053 to CSV. Privacy copy is easy to write. Parser quality is not. We list them as a category, not as a ranked set, because we did not put a multi-namespace fixture through each. The camt053 Python suite on PyPI is for developers who want a typed document model and an Excel writer package. That is not a controller UI.
Comparison table
Direction of conversion matters more than brand.
| Direction | F20 | StatementBridge |
|---|---|---|
| camt.053 → CSV/Excel | Yes | Excel/CSV among outputs on their MT940 page |
| MT940 → camt.053 | No | Yes |
| Balance check | Yes | Review of balances described |
| Price | No charge | NOT VERIFIED |
Pricing, privacy, limitations
F20: no charge, in-memory, not stored. Others: read their pages. F20 will not fix a truncated XML file. It will not invent entries the bank omitted. It will not convert a PDF that happens to contain the letters 'camt'.
What usually goes wrong in a camt.053 conversion
Namespaces: a parser compiled against one schema version rejects a perfectly ordinary bank file because the xmlns string moved. F20's element-name walk is there to reduce that class of failure. It is not a promise that a bank's proprietary wrapper with a different root element will parse.
Batch statements: one XML document, several accounts, several statement periods. A converter that emits one sheet without an account column will recon the wrong population. Check that the account identifier survived before you sum anything.
Reversals and return codes: camt entries can carry return reason codes. Flattening them to a signed amount without keeping the code makes a later investigation harder. If the download looks fine but a controller cannot see why money moved backwards, the converter threw away the plot.
Multi-currency: ISO 20022 is explicit about currency on amounts. A spreadsheet that concatenates EUR and USD into one total is a bug even if every row parsed. F20 does not invent an FX rate. Neither should you in the CSV.
When you should not convert camt.053 at all
If the ERP already ingests camt.053 natively, converting to Excel so you can re-key is a step backwards. Use the native importer, then use F20 only when that importer fails or when you need an independent tie-out on the same file.
If the file is camt.054 notifications mixed into a folder with 053 statements, splitting them by eye is safer than hoping a converter's autodetect is bored enough to be correct. Name the files. Do not rely on .xml meaning statement.
If you actually needed camt.052 intraday positions for treasury, flattening yesterday's 053 will not invent intra-day movements. Ask the bank for the message you mean.
Methodology
Official pages, 8 September 2026. Textbook explainer remains /learn/bank-files/what-is-camt053. Pairwise: /compare/formats/mt940-vs-camt053. We did not run a multi-bank camt fixture through StatementBridge or the free browser tools.
Where F20 FinanceOps is a better fit
- You received camt.053 and need rows plus a balance tie-out, then a recon, for free, without storing the file.
- You do not need to emit MT940 or CODA.
Where another camt.053 tool is a better fit
- You have MT940 and the package now demands camt.053: StatementBridge documents that direction.
- You need a library inside an application: use a parser suite, not a website.
- You have a scan of a statement that was never XML: OCR, not a camt converter.
FAQ
Ask the bank what they actually send. Many corporates receive both during migration. F20 converts either to rows.
It walks by element name rather than one pinned namespace. House dialects can still surprise you. Read the issues list after the run.
Yes. /samples/camt053. Synthetic, not customer data.
053 is the statement this converter is for. 052 is an account report, often intraday. Do not substitute them in a period recon.
Best fit for free XML-to-rows plus recon. Not best for MT940 emission or package-specific XML profiles we have not implemented.
Sources
- F20 FinanceOps policies — F20 FinanceOps. Verified. Uploaded files are processed in memory and dropped when the response is sent. There is no charge to run a tool. Output is not professional advice.
- MT940 Converter | StatementBridge — StatementBridge. Verified. StatementBridge converts MT940 to camt.053, CSV, Excel, OFX and CODA, aimed at Dutch and European accounting packages.
Convert camt.053 to CSV or Excel — Check the balance issues before you import the rows into anything that posts.