CAMT.053 is an ISO 20022 bank-statement message. Our export creates a camt.053.001.02 XML document from the extracted PDF data. Confirm that exact version and your destination's implementation rules before using it: support for a different CAMT.053 version does not establish support for this one.
Choose the correct import route
If your bank provides an electronic statement that already matches your ERP's requirements, use it directly. PDF conversion is useful when the historical data is only available as a statement PDF, but it cannot recreate identifiers or structured details missing from that document.
SAP's bank-statement processing documentation lists CAMT.053 version 2 among its import formats. Check the configuration and documentation for your actual system and release before choosing a file type or posting rule.
Generate the XML file
- Open the PDF to CAMT.053 tool.
- Upload a readable, unlocked PDF of up to 25 MB, keeping one account and currency per conversion.
- Select Convert My Statement, then download Excel to review the extracted fields.
- Open More formats and select CAMT.053 under Bank standards.
- Save the .xml file and retain the PDF and review workbook for comparison.
The export contains one statement with one entry per extracted transaction. It does not create separate statement objects for multiple accounts in a combined PDF. Editing the downloaded workbook does not update the XML produced from the stored extraction.
Understand the XML structure
| Element or value | What this exporter writes |
|---|---|
| Document namespace | urn:iso:std:iso:20022:tech:xsd:camt.053.001.02 |
| BkToCstmrStmt / Stmt | One statement and its account information |
| Acct / Id / Othr / Id | Account identifier; not a dedicated IBAN element |
| Bal with OPBD or CLBD | Opening and closing booked balances |
| Ntry / Amt and CdtDbtInd | Two-decimal amount and CRDT or DBIT direction |
| BookgDt and ValDt | The same extracted transaction date |
| BkTxCd | Generic proprietary code NMSC |
| RmtInf / Ustrd | Shortened description |
Amounts and direction are separate. For an outgoing payment of 40, the entry amount is 40.00 and the direction is DBIT. Do not make the amount negative a second time when mapping that entry into another format. Check both an incoming and outgoing row in the import preview.
Check references and defaults
Message and statement IDs are generated anew on each download. Entry references and EndToEndId values are generated from extracted content and row position; they are not original payment-network identifiers. Re-downloading or reordering data is not a reliable duplicate-prevention method.
Missing currency defaults to USD, missing balances to zero, and missing dates to 1970-01-01. Missing account or owner information receives placeholder text. Review the Excel Summary or JSON output for null values before importing XML that contains these defaults.
Narratives are shortened, and the exporter does not restore detailed counterparties, original end-to-end payment references, or separate booking and value dates. Retain the PDF when you need those details for matching or investigation.
Validate before posting
Have your integration process check that the file parses as XML, validate it against the required version's XSD, and apply your destination's business rules. Those are separate checks. The converter does not currently run an XSD validator, so an XML download is not a schema-validation certificate.
Use a test import or preview before posting. Confirm account mapping, currency, dates, entry count, opening and closing balances, and duplicate handling. If validation fails, retain the error location and original file for investigation rather than changing the namespace to a different version.
For a system expecting a tagged text statement, see the MT940 guide. If you need a transaction table to inspect first, use the CSV guide.