Articles / Learning brief
The ISO 20022 message model
Your notes
In simple terms / 01
What this means in plain language
ISO 20022 is an international standard that organises financial messages around business areas, reusable data components, and a shared dictionary, giving families such as pacs, pain, and camt a common structured XML foundation.
ISO 20022 (International Organization for Standardization standard 20022) is not a single message format but a method for describing financial messages. It begins with a central data dictionary that defines each business concept once, an amount, a party, an account, a date, so the same building block can be reused everywhere. Messages are grouped into business areas identified by a four-letter code: pain for payment initiation, pacs for interbank clearing and settlement, and camt for cash management and reporting. Each message is expressed in structured Extensible Markup Language (XML), where every piece of information sits inside a labelled tag rather than a free-text line. Because the model separates the business meaning from the way it is written down, the same definition can be validated automatically and shared across institutions. The result is consistency: two banks reading the same message interpret each field in exactly the same way.
Complete lesson / 02
Understand the full idea, step by step
Fill in a delivery form online — name, street, city, postal code, country, each in its own box — and a warehouse anywhere can read it the same way you meant it. Now picture every bank inventing its own form, its own boxes, its own word for amount and address. The agreement that stops that is ISO 20022. Let us see what it actually is, because it is not, as people often say, just XML.
You may be wondering: isn't a message standard just a fixed layout that everyone agrees to fill in?
That is the part you can see, but it is not where ISO 20022 starts. It starts one level higher — as a method for describing financial business and a shared repository of definitions. The layouts you fill in are assembled from that repository. Get the definitions agreed once, and every message built from them already means the same thing to both sides.
ISO 20022 — International Organization for Standardization standard 20022
ISO 20022 is three things at once: a methodology for modelling financial business, a central repository — a shared data dictionary that defines each concept once — and a set of message definitions built from that dictionary. A monetary amount, a party, a postal address, an account each have one agreed definition, with a name, a data type, and rules. Message definitions are then assembled from those reusable pieces, the way a document is built from shared paragraphs. Calling it a file format misses the point: the format is only the last step.
Three layers, kept apart on purpose
The repository separates the standard into three layers. The business model describes processes and the roles that take part — who initiates a payment, who receives it. The logical message model defines the message as reusable components, independent of how it is written down. The physical syntax is how the message is finally rendered — most often XML, but the standard does not require XML. Keeping these apart means the meaning stays stable even when the way it travels changes, and software can check any message against its definition automatically instead of a person eyeballing it.
Reading a message identifier
- Example
- pacs.008.001.08
- Business area
- pacs — payments clearing and settlement (between banks)
- Message number
- 008 — which message within that area
- Variant
- 001 — a specific flavour of the definition
- Version
- 08 — rises each time the definition is revised
Why one shared dictionary earns its keep
Because every definition lives in one place, the same concept never has to be reinvented: an amount means the same thing in a payment initiation as in a statement. A receiving system can read the four-letter area code and the identifier before it parses the body — enough to route the message and pick the right schema to validate it against. And because each piece sits in its own labelled element, a creditor's town, postal code, and country are separate fields, not four free-text lines that a screening or reconciliation system has to guess at. Precision entered early and preserved end to end is what the model rewards.
COMMON CONFUSION
“ISO 20022 is just XML — a new file format banks are switching to.”
XML is only one syntax the standard can be written in; the meaning lives in the repository of definitions, not in the angle brackets. Two messages could share XML and still mean nothing to each other. ISO 20022 is the methodology and dictionary that make the fields mean the same thing to both banks — and, as always, the message carries the instruction, never the money itself.
STRICTLY SPEAKING
Strictly speaking, ISO 20022 is syntax-independent by design. The logical model can be rendered in XML or in other syntaxes, and the standard is maintained by a registration process with published catalogues that add and revise definitions over time. So the safe way to name a message is by its identifier and to check the current catalogue for the version in force, rather than assuming the one you learned is still the latest.
FOR NOW, REMEMBER
- ISO 20022 is a methodology, a shared repository of definitions, and the message definitions built from them — not merely XML.
- It separates three layers: business model, logical message model, and physical syntax, so meaning survives changes in how a message is written.
- One agreed dictionary means a concept like
amountis defined once and reused across pain, pacs, and camt. - The message identifier — area, number, variant, version — lets a system route and validate before reading the body.
TRY IT YOURSELF
Nordbank's gateway receives a message tagged `pacs.008.001.08` and has not yet parsed the body. What can it already do, and why?
You now know the message inside. But how does a network know who sent it, who it is for, and that it has not seen it before? That job belongs to a small standard envelope — the Business Application Header.
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
ISO 20022 defines a shared data dictionary so each business concept is described once and reused across many messages.
- 02
A four-letter business area code, pain, pacs, or camt, signals what job a message does.
- 03
Structured XML tags replace free-text lines, letting institutions validate and interpret every field the same way.
Practical use cases / 04
Where you would use this
Standards teams at a bank map internal payment data to ISO 20022 components so outgoing messages validate against the published schema.
Correspondent banks rely on the shared dictionary to interpret a counterparty's message fields without bilateral agreements.
Market infrastructures publish usage guidelines that constrain the base standard for a specific clearing or settlement service.
Worked example / 05
Put the idea into a real situation
Illustrative example: a fictional bank, Meridian Trust, sends an interbank customer credit transfer using message pacs.008.001.08. Reading the identifier left to right: pacs names the business area (payments clearing and settlement), 008 is the message number, 001 is the variant, and 08 is the version. The message carries a settlement amount of EUR 48,250.00 inside a labelled amount tag with a currency attribute, a structured creditor address split into street, town, and country, and a 140-character structured remittance block. A second fictional bank, Kestrel Union Bank, validates the XML against the published schema in under 1 second and books the payment without manual repair, because every field arrived in its expected place.
Evidence & review / 07
Evidence & review
ISO 20022 methodology and repository generally; identifier example uses pacs.008 for illustration only.
What this brief simplifies: Presents the three modelling layers and identifier anatomy as a teaching model; the full registration process, business-area catalogue, and non-XML syntaxes are summarised rather than enumerated.
Sources for this brief2
- Official requirement
ISO 20022 Catalogue of messages ↗ — ISO 20022 Registration Authority · Methodology, repository, message identifier structure
Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
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.