Formatwerk
camt053 to csv
Parses camt.052, camt.053 and camt.054 in the 2009 (.02) and 2019 (.08) versions and later compatible versions with fast-xml-parser. One row per transaction detail (batch entries are split) or per entry: booking and value date, amount with sign from CdtDbtInd, reversal flag, status, counterparty name/IBAN/BIC chosen by direction (payer for credits, payee for debits, swapped for reversals), remittance text, end-to-end id (EREF), mandate id (MREF), KREF and CRED from SEPA keywords in the.
POST https://format.halowerk.com/v1/camt053-to-csvInputs
| Field | Type | Required | Description |
|---|---|---|---|
| xml | string | Yes | camt.052, camt.053 or camt.054 XML document. |
| level | string | No | transaction = one row per TxDtls (batches split), entry = one row per Ntry. |
| format | string | No | Output format. |
| delimiter | string | No | CSV delimiter. |
| decimal_separator | string | No | Decimal separator for amounts in the CSV. |
Show full input schema
{
"type": "object",
"additionalProperties": false,
"required": [
"xml"
],
"properties": {
"xml": {
"type": "string",
"minLength": 20,
"maxLength": 10000000,
"description": "camt.052, camt.053 or camt.054 XML document."
},
"level": {
"type": "string",
"enum": [
"transaction",
"entry"
],
"default": "transaction",
"description": "transaction = one row per TxDtls (batches split), entry = one row per Ntry."
},
"format": {
"type": "string",
"enum": [
"json",
"csv",
"both"
],
"default": "both",
"description": "Output format."
},
"delimiter": {
"type": "string",
"enum": [
";",
",",
"\t"
],
"default": ";",
"description": "CSV delimiter."
},
"decimal_separator": {
"type": "string",
"enum": [
".",
","
],
"default": ".",
"description": "Decimal separator for amounts in the CSV."
}
}
}Published input example
{
"xml": "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<Document xmlns=\"urn:iso:std:iso:20022:tech:xsd:camt.052.001.08\"><BkToCstmrAcctRpt><GrpHdr><MsgId>C52-1</MsgId><CreDtTm>2026-11-02T11:00:00Z</CreDtTm></GrpHdr>\n<Rpt><Id>RPT-1</Id><Acct><Id><IBAN>DE79000000001234567890</IBAN></Id></Acct>\n<Ntry><Amt Ccy=\"EUR\">75.25</Amt><CdtDbtInd>DBIT</CdtDbtInd><Sts><Cd>PDNG</Cd></Sts><BookgDt><Dt>2026-11-02</Dt></BookgDt><ValDt><Dt>2026-11-03</Dt></ValDt>\n<NtryDtls><TxDtls><Refs><EndToEndId>KARTE-77</EndToEndId></Refs><Amt Ccy=\"EUR\">75.25</Amt><CdtDbtInd>DBIT</CdtDbtInd><RltdPties><Cdtr><Pty><Nm>Probe Tankstelle</Nm></Pty></Cdtr></RltdPties><RmtInf><Ustrd>KREF+K-4711 SVWZ+Tankung</Ustrd></RmtInf></TxDtls></NtryDtls></Ntry>\n</Rpt></BkToCstmrAcctRpt></Document>",
"level": "transaction",
"format": "json"
}Result & documentation
Machine-readable documentation of this hub
Source of this page: the published HALOWERK catalog. Updated: 2026-11-17 UTC.
More endpoints in this hub
- Formatwerk0.004 USDC
accounting csv unify
POSThttps://format.halowerk.com/v1/accounting-csv-unifyDATEV booking batch files (EXTF/DTVF, category 21) are read by their documented field positions: amount and S/H become a signed amount relative to the account, Belegdatum TTMM is resolved within the fiscal year from the header. Other export
- Formatwerk0.005 USDC
avv checklist
POSThttps://format.halowerk.com/v1/avv-checklistChecklist after Art. 28 GDPR (Regulation (EU) 2016/679 Art. 28 (GDPR), https://eur-lex.europa.eu/eli/reg/2016/679/oj, German and English text retrieved from the EU Publications Office 2026-11-01): Art. 28(3) sentence 1 (subject-matter, dura
- Formatwerk0.004 USDC
bagit package
POSThttps://format.halowerk.com/v1/bagit-packageCreate: files go to data/, manifest-<alg>.txt and tagmanifest-<alg>.txt are written for SHA-256 (default), SHA-512 or legacy SHA-1/MD5, bag-info.txt gets your metadata plus Bagging-Date, Bag-Size and Payload-Oxum; paths are checked (no abso