Skip to main content

camt.053

camt.053 is the ISO 20022 bank-to-customer statement message used for end-of-day account reporting.

Overviewโ€‹

camt.053 (BankToCustomerStatement) is an account statement message sent by a bank to its customer, typically end-of-day or intraday statement cut. It provides booked balance and entry details for reconciliation and accounting.

Primary Use Casesโ€‹

  • Daily account statement delivery to corporate treasury
  • Automated bank reconciliation against ERP/AP/AR ledgers
  • Audit trail for debits, credits, fees, and interest postings
  • Position and cash forecasting

Structure (High Level)โ€‹

camt.053
โ”œโ”€โ”€ GrpHdr
โ””โ”€โ”€ Stmt (1..n account statements)
โ”œโ”€โ”€ Id / CreDtTm / FrToDt
โ”œโ”€โ”€ Acct (account identification)
โ”œโ”€โ”€ Bal (opening, interim, closing)
โ””โ”€โ”€ Ntry (entries)
โ”œโ”€โ”€ CdtDbtInd
โ”œโ”€โ”€ Amt / Ccy
โ”œโ”€โ”€ BookgDt / ValDt
โ””โ”€โ”€ NtryDtls / TxDtls (references, remittance, counterparties)

camt.053 vs camt.054โ€‹

  • camt.053: statement-oriented periodic summary with detailed entries
  • camt.054: event/notification-oriented credit/debit advice

Organizations often consume both: camt.054 for near-real-time updates and camt.053 for official day-close reconciliation.

Operational Considerationsโ€‹

  • Statement generation cut-off times must be deterministic
  • Missing entries or duplicate entries cause reconciliation breaks
  • Balance type semantics (opening/closing/booked/available) must be documented
  • Statement IDs and sequence numbers should support replay-safe ingestion

Integration Tipsโ€‹

  • Map Ntry and TxDtls into internal transaction model
  • Keep full reference chain (EndToEndId, bank refs, scheme refs)
  • Validate total movements against internal ledger snapshots
  • Use idempotent import by (statement_id, entry_ref) keys