Provides the booked statement for an account, normally covering a completed reporting period with opening and closing balances plus the entries booked during that period.
DIRECTION: Sent by an account servicing institution to the account owner or an authorised recipient, commonly at end of day.
Version + profile: camt.053 is a message-family identifier, not a complete version. The numeric .001.xx definition and field rules depend on the scheme, service, usage guideline, and implementation version named in each context; sample namespaces show only the illustrated version.
EVIDENCE AT ARM'S REACH
Start with the exact message version, then apply the scheme or network profile that governs your implementation.
An XSD checks XML structure. A usage guideline adds profile rules, conditional fields, code restrictions, and business controls. XSD-valid does not mean scheme-compliant.
Choose the exact message definition in the official catalogue. The base XSD checks XML structure; it does not prove compliance with a scheme profile.
The network profile that restricts how ISO 20022 payment and reporting messages are used for cross-border traffic.
Adds the November 2026 validation and structured-address changes; implement against the final SR2026 usage guidelines.
Final usage guidelines are published through MyStandards; the public release page gives the implementation timeline.
Open version sourceNon-binding market practice for structured party data, cover payments, investigations, and the transition between MT and ISO 20022 reporting.
The ECB release library for T2 RTGS and central-liquidity messaging, including public user specifications, business validation rules, and binding schemas.
A fictional end-of-day statement containing the payment debit. SYNTHETIC / TRAINING ONLY; illustrative unvalidated.
crc32:52085b13Initiation, customer and interbank status, payment, notification, intraday report, and statement.
crc32:705aa0afField correspondence, transformation treatment, and data-loss notes for Customer statement migration from compact FIN lines to structured ISO 20022 entries.
crc32:6bcf9eecField correspondence, transformation treatment, and data-loss notes for Interbank statement migration to a structured bank-to-customer statement.
crc32:5c7c7b44Curated field requirements, contexts, operational meaning, and implementation cautions.
crc32:57cb37c0Positive and negative test cases across validation, rejection, return, recall, reversal, investigation, reconciliation, migration, instant payments, and screening.
crc32:98c48cc7Verified profile constraints with versioned evidence and explicit operating conditions.
crc32:ce355754Positive and negative lifecycle tests linked to verified profile rules.
crc32:52175ca5Discovery, controls, testing and operational-readiness checks for the profile.
crc32:dabcc15dOutcome-focused profile acceptance criteria with honest release gates.
crc32:90dc18baVersion, transformation, cutover and reconciliation controls.
crc32:90393a22Evidence that must be obtained from the owner before production readiness can be claimed.
crc32:581e94a5Generated mapping, field-matrix, test, checklist, acceptance-criteria, migration, manifest, checksum, and source-inventory bundle.
crc32:9d2559edGenerated mapping, field-matrix, test, checklist, acceptance-criteria, migration, manifest, checksum, and source-inventory bundle.
crc32:39e4ef6dGenerated mapping, field-matrix, test, checklist, acceptance-criteria, migration, manifest, checksum, and source-inventory bundle.
crc32:458732a2Generated mapping, field-matrix, test, checklist, acceptance-criteria, migration, manifest, checksum, and source-inventory bundle.
crc32:02c424d8Generated mapping, field-matrix, test, checklist, acceptance-criteria, migration, manifest, checksum, and source-inventory bundle.
crc32:4e9cc3dbCurated teaching subset. The full statement supports balances, entries, transaction details, parties, charges, rates, remittance, pagination, and supplementary data; requirements depend on the service guideline.
| FIELD | NAME | PRESENCE | WHAT IT MEANS |
|---|---|---|---|
GrpHdr/MsgId | Message identification | MANDATORY | Unique reference for this statement message. |
Stmt/Id | Statement identification | MANDATORY | Identifier assigned to this account statement. |
Stmt/ElctrncSeqNb | Electronic sequence number | OPTIONAL | Sequence used to detect missing or duplicate statements. |
Stmt/Acct/Id | Account identification | MANDATORY | The account covered by the statement. |
Stmt/Bal | Opening and closing balances | CONDITIONAL | Balances that frame the reporting period and make completeness testable. |
Stmt/Ntry/Amt | Entry amount | OPTIONAL | Amount of each booked debit or credit. |
Stmt/Ntry/CdtDbtInd | Credit or debit indicator | OPTIONAL | Whether the entry increased or reduced the account balance. |
Stmt/Ntry/NtryDtls/TxDtls/Refs/EndToEndId | End-to-end reference | OPTIONAL | Reference that ties a statement entry back to the originating customer payment. |
The whole camt.053 laid out as a parent-child tree: every field in its nesting, with a sample value and what it means. Expand a branch to drill in. Values are fictional (SYNTHETIC / TRAINING ONLY); this is a curated practitioner view, not the full schema.
Document—The root of an ISO 20022 message — the business payload, which a Business Application Header (head.001) accompanies as a separate document.BkToCstmrStmt—GrpHdr—Group header — data that applies to the whole message: its identity, when it was created, how many transactions it carries, and shared settlement data.MsgIdDEMO-CAMT053-001MandatoryUnique reference for this statement message.DEMO-PACS008-001CreDtTm2026-07-18T23:55:00ZMandatoryCreation date and time — when this message was created (a UTC timestamp), separate from when the payment is executed.2026-07-12T09:01:00ZStmt—IdchoiceDEMO-STATEMENT-001MandatoryIdentifier assigned to this account statement.ElctrncSeqNb198OptionalSequence used to detect missing or duplicate statements.Acct—Idchoice—MandatoryThe account covered by the statement.IBANDE02120300000000202051International Bank Account Number — the standardised account identifier used across SEPA and beyond.DE02120300000000202051Bal—ConditionalBalances that frame the reporting period and make completeness testable.Tp—Type — qualifies what kind of reference or code this is.CdOrPrtrychoice—Code or Proprietary — a choice between a standard code and a proprietary value.CdOPBDCode — a value taken from a defined code list.Amt50000.00Ccy=EURAmount — the money being moved, as either an instructed amount or an equivalent amount.CdtDbtIndCRDTCredit/Debit Indicator — says whether an amount or entry is a credit (CRDT) or debit (DBIT) on the reported account.Ntry—Amt1250.00Ccy=EUROptionalAmount of each booked debit or credit.CdtDbtIndDBITOptionalWhether the entry increased or reduced the account balance.BookgDt—Dt2026-07-18Date — a calendar date value.NtryDtls—TxDtls—Refs—EndToEndIdDEMO-E2E-001OptionalReference that ties a statement entry back to the originating customer payment.DEMO-E2E-001ISO 20022 Catalogue of messages ↗ — ISO 20022 Registration Authority · pain/pacs/camt message-definition elements
Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.
Cross-Border Payments and Reporting Plus (CBPR+) usage guidelines ↗ — Swift (CBPR+ working group) · cross-border agent chain and structured-data usage
Full guidelines require MyStandards access. Public guidance states that after 14 November 2026 fully unstructured addresses are removed for in-scope CBPR+ traffic, with explicit message exceptions including admi.024, camt.025, camt.052, camt.053, camt.054 and camt.060.
Swift Standards MT (annual standards releases) ↗ — Swift · FIN block structure
Full field-level specifications live in the Swift Knowledge Centre User Handbook behind a swift.com login. Coexistence for in-scope FI-to-FI payment instructions ended on 22 November 2025, but treatment differs by MT: some instructions are NAKed and selected messages can enter temporary, chargeable contingency conversion. Reporting, initiation, investigations and correspondence follow separate roadmaps.
Payments Signal editorial teaching models — Payments Signal
What this simplifies: One-line plain-language descriptions of the commonly-populated elements — a practitioner view, not the authoritative ISO 20022 / MT schema, which defines many more optional elements.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.
ISO 20022 Catalogue of messages ↗ — ISO 20022 Registration Authority · camt.053 BankToCustomerStatement message definition
Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.
Cross-Border Payments and Reporting Plus (CBPR+) usage guidelines ↗ — Swift (CBPR+ working group) · camt.053 usage guideline
Full guidelines require MyStandards access. Public guidance states that after 14 November 2026 fully unstructured addresses are removed for in-scope CBPR+ traffic, with explicit message exceptions including admi.024, camt.025, camt.052, camt.053, camt.054 and camt.060.
Payments Signal editorial teaching models — Payments Signal
What this simplifies: The reference focuses on one booked statement and omits advanced entry and tax detail.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.
Share an operational observation or ask a concrete payments question. Your name and message are public; your email remains private.
Loading the discussion…