← ISO 20022: integration and operational fundamentals
02 / 6 · 35 MIN

Messages, headers, and states

Identify each message’s purpose and the evidence it actually provides.

Concept and mechanism

Message families help locate functions, but the full type and profile remain necessary. pain.001 supports customer credit-transfer initiation; pacs.008 represents an inter-institution customer transfer; pacs.002 reports inter-institution status. camt.052, camt.053, and camt.054 support account reporting, statements, and debit or credit notifications. Receiving a status report does not automatically mean a completed payment: interpret content, reported scope, and correlation with the instruction. A statement is also not an instruction to initiate another payment. Versions listed in the global catalogue can differ from versions adopted by a particular community.

Guided application

The Business Application Header gathers metadata such as sender, recipient, and message identity independently of filename or network. The Business Message Envelope can bundle header and document in a technical container; usage depends on the contract. Design should identify which component validates each layer and which identifiers connect stages. Do not copy one identifier into every field without analyzing semantics and profile rules. For troubleshooting, collect full type, version, header, relevant status, and correlation references while respecting institutional access controls. Separating technical receipt, functional interpretation, and business effect prevents support closing a case on insufficient evidence.

IN PRACTICE

Example: a statement is resent during technical recovery. Its consumer should apply the reporting and correlation contract rather than treating redelivery as new payment authorization.

Common pitfalls

pacs.002 treated as universal success; camt treated as payment instruction; header treated as complete document; container validated against inner schema.

Related topics: Semantics and contract documentation · Layered validation · Mapping and data integrity

Take this idea with you

Identify function, layer, and state before deciding a message’s effect.

Create account

Reference: Payment message definitions · DR ISO20022 fundamentals professional assessment2026.10