The ISO 20022 message model

IN ONE LINE

Analogy: think of ISO 20022 as a dictionary plus a grammar, not a pile of ready-made sentences.

The dictionary defines reusable parts — "debtor", "amount", "account" — once, each with a precise meaning.

Every message type is a sentence pattern assembled from those shared parts, which is why the same concept looks identical wherever it appears.

And like a letter, each message travels inside an envelope: the Business Application Header is the address label on the outside, saying who sent it, who should receive it, and what kind of document is inside — so the postal system can route and sort the letter without having to open and read it.

WHAT IT ACTUALLY IS

The standard has layers.

At the top sits the business model: definitions of parties, accounts, amounts, and the relationships between them, held in a central repository.

Message definitions are assembled from those shared components, which is why a debtor block looks the same in a customer initiation message as in an interbank transfer.

The wire format is XML, validated against a published schema.

Names follow area.number.variant.version: in pacs.008.001.xx, pacs is the business area, 008 the message number, 001 the variant, and the final part a version that changes as the standard evolves.

Networks and schemes pin the specific versions they accept, so version numbers matter operationally, not just editorially.

HOW IT WORKS

The Business Application Header — message definition head.001 — is a separate small document that travels with the payload rather than inside it.

It identifies the sender and receiver at business level, names the message definition of the payload, and can carry a business service identifier telling the receiver which usage guideline the message claims to follow.

Practically, validation happens in layers: schema validation checks the XML against the base definition; guideline validation applies the tighter rules of the specific scheme or service; business validation — does the account exist, is a party sanctioned — happens in the bank's own systems.

A message can pass the first layer and still fail the others, and institutions differ in where each layer runs.

THE WORDS

Business Application Header

The standard ISO 20022 header (head.001) that travels with a message and carries sender, receiver, message identification, and routing data.

READ FIRST

• Why ISO 20022 exists

CONNECTED TO

• pacs.008 pacs.008 — FI to FI Customer Credit Transfer
• CHECKPOINT ISO 20022 model checkpoint

SOURCES

• ISO 20022 Catalogue of messages — ISO 20022 Registration Authority
• Business application header (BAH) — ISO 20022 Registration Authority
• Payments Signal editorial teaching models — Payments Signal