Steps

Load the camt.053 XML and validate it against the official ISO 20022 camt.053.001.08 (or .06/.02 depending on the bank's version) XSD schema before processing
Parse the statement at three levels: BkToCstmrStmt (envelope), Stmt (per-account statement with opening/closing balance), and Ntry (individual entries); each Ntry can contain multiple NtryDtls > TxDtls sub-entries
For each entry, extract: ValDt (value date for interest calculations), BookgDt (booking date for GL posting), Amt + CdtDbtInd (credit/debit), and the BkTxCd (bank transaction code) for categorization
Drill into TxDtls to find the EndToEndId, InstrId, or Refs/TxId that matches your internal payment reference; use these to match against your payment ledger
For unmatched entries, apply secondary matching rules: match on Amt + ValDt + counterparty name (RltdPties/Cdtr or Dbtr) + last-4 of account number
Reconcile closing balance: sum your matched and unmatched entries against the statement's closing balance (ClosgBal); any discrepancy indicates missing entries or a parsing error

Known gotchas

camt.053 versions differ significantly across banks (v2 through v8 are all in active use); parse the namespace URI from the root element to determine the version and load the correct XSD — do not assume a single schema will work for all bank feeds
A single Ntry with multiple NtryDtls sub-entries (batch booking) is common for ACH files; if you only parse at the Ntry level you will see one lumped entry instead of individual transactions — always recurse into NtryDtls
ValDt and BookgDt can differ, sometimes by days (e.g., weekend value dating); use ValDt for interest accrual and BookgDt for GL posting date — conflating them causes incorrect interest calculations

iso20022.org · 6 steps · unrated

Build a transaction-code crosswalk between BAI2 type codes and ISO 20022 camt.053 Bank Transaction Codes for unified reconciliation, given that no single official standard mapping exists

iso20022.org · 5 steps · unrated

Integrate BAI2 and camt.053 statement ingestion with a Treasury Management System via SFTP and normalize transaction codes across both formats

moderntreasury.com · 6 steps · unrated

Give your agent this knowledge — and 15,600+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Parse a camt.053 ISO 20022 bank statement XML file and reconcile entries against internal payment records

Steps

Known gotchas

Related routes

Give your agent this knowledge — and 15,600+ more routes

Need this verified for your stack — or a route we don't have yet?