Notifies an account owner about one or more debit or credit entries, often promptly or with transaction-level detail for a bulk booking. It reports entries already booked or advised; it does not move value.
DIRECTION: Sent by an account servicing institution to the account owner or authorised recipient when the agreed notification trigger occurs.
Version + profile: camt.054 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 near-real-time notification that the corporate account was debited. SYNTHETIC / TRAINING ONLY; illustrative unvalidated.
crc32:5a173137Initiation, customer and interbank status, payment, notification, intraday report, and statement.
crc32:705aa0afField correspondence, transformation treatment, and data-loss notes for Single debit advice compared with a structured bank-to-customer debit/credit notification.
crc32:96b16a98Field correspondence, transformation treatment, and data-loss notes for Single credit advice compared with a structured bank-to-customer debit/credit notification.
crc32:baee9a30Curated field requirements, contexts, operational meaning, and implementation cautions.
crc32:25aa6ef8Positive 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 message supports multiple notifications, entries, and detailed underlying transactions; the trigger, status usage, and level of detail are contracted service choices.
| FIELD | NAME | PRESENCE | WHAT IT MEANS |
|---|---|---|---|
GrpHdr/MsgId | Message identification | MANDATORY | Unique reference for the notification message. |
Ntfctn/Id | Notification identification | MANDATORY | Identifier assigned to this notification. |
Ntfctn/Acct/Id | Account identification | MANDATORY | The account on which the entry was reported. |
Ntfctn/Ntry/Amt | Entry amount | MANDATORY | Amount of the debit or credit notification. |
Ntfctn/Ntry/CdtDbtInd | Credit or debit indicator | MANDATORY | Whether the account was credited or debited. |
Ntfctn/Ntry/Sts | Entry status | MANDATORY | Whether the entry is booked, pending, or carries another supported status. |
Ntfctn/Ntry/NtryDtls/TxDtls/Refs/EndToEndId | End-to-end reference | OPTIONAL | Customer payment reference used to match the notification. |
Ntfctn/Ntry/NtryDtls/TxDtls/RmtInf | Remittance information | OPTIONAL | Structured or unstructured information explaining the underlying transaction. |
The whole camt.054 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.BkToCstmrDbtCdtNtfctn—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-CAMT054-001MandatoryUnique reference for the notification message.DEMO-PACS008-001CreDtTm2026-07-18T09:01:00ZMandatoryCreation date and time — when this message was created (a UTC timestamp), separate from when the payment is executed.2026-07-12T09:01:00ZNtfctn—IdchoiceDEMO-NOTIFICATION-001MandatoryIdentifier assigned to this notification.Acct—Idchoice—MandatoryThe account on which the entry was reported.IBANDE02120300000000202051International Bank Account Number — the standardised account identifier used across SEPA and beyond.DE02120300000000202051Ntry—Amt1250.00Ccy=EURMandatoryAmount of the debit or credit notification.CdtDbtIndDBITMandatoryWhether the account was credited or debited.Sts—MandatoryWhether the entry is booked, pending, or carries another supported status.CdBOOKCode — a value taken from a defined code list.NtryDtls—TxDtls—Refs—EndToEndIdDEMO-E2E-001OptionalCustomer payment reference used to match the notification.DEMO-E2E-001RmtInf—OptionalStructured or unstructured information explaining the underlying transaction.UstrdDEMO INVOICE 1001Unstructured — free-text remittance information (e.g. an invoice note); readable but not machine-parseable.<Ustrd>DEMO INVOICE 1001</Ustrd>ISO 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.054 BankToCustomerDebitCreditNotification 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.054 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: One entry is shown; notification triggers and bulk-detail conventions vary.
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…