Mastering ISO 20022 in Practice
ISO Repository Overview
The Central Blueprint
Since ISO 20022 is a methodology, not just a set of message formats, it needs a central library to keep everything organised. This is the ISO 20022 Repository. Think of it as the single source of truth for the entire standard, ensuring that a payment instruction in Japan means the exact same thing as one in Germany.
The repository contains all the models, message definitions, and the methodology itself. It’s a public, open resource that allows financial institutions, developers, and market infrastructures to access the same blueprints. This prevents the fragmentation and ambiguity that plagued older messaging standards.
Inside the Repository
The repository isn't just a big folder of files; it's a structured system with three core components that work together. They move from the abstract business need to the specific technical detail.
Business Process Catalogue: This describes the 'why'. It contains models of financial business activities, like cross-border payments or securities trades. It defines the participants, their roles, and the flow of information required to complete a process.
Data Dictionary: This is the universal vocabulary, defining the 'what'. It contains all the business concepts and their associated data types, like 'Amount', 'Creditor', or 'Currency'. Each element is defined once and reused across all messages, ensuring consistency.
Message Definition Report (MDR): This provides the detailed 'how'. It documents the structure of each message, specifying which elements from the Data Dictionary are included, in what order, and how they relate. This is the final blueprint used to build the actual XML message.
This layered approach is key. By separating the business logic from the data definitions and message structure, the standard remains flexible and adaptable. If a new business process emerges, a new message can be built using existing, well-defined data elements, ensuring interoperability from day one.
The Gatekeepers
A standard this critical can't be a free-for-all. Two key groups manage the repository's integrity and evolution: the and the Standards Evaluation Groups.
The Registration Authority (RA) handles the day-to-day management. It reviews submissions for completeness and quality, registers new message definitions, and publishes updates to the repository. They are the administrators making sure the process runs smoothly.
The (SEGs), on the other hand, are the subject matter experts. Each SEG is responsible for a specific business domain, like Payments, Securities, or Foreign Exchange. When a change or a new message is proposed, the relevant SEG evaluates it from a business perspective. They ensure the proposal is valid, doesn't duplicate existing functionality, and aligns with global business practices.
The Lifecycle of a Message
How does a new message get into the repository? It follows a structured lifecycle.
| Step | Action | Key Players |
|---|---|---|
| 1. Submission | An organisation (like a central bank or industry group) submits a business case for a new message or a change to an existing one. | Submitting Organisation |
| 2. RA Review | The Registration Authority checks the submission for quality and completeness. | Registration Authority (RA) |
| 3. SEG Evaluation | The relevant Standards Evaluation Group reviews the business justification. Is it needed? Does it fit the standard? | Standards Evaluation Group (SEG) |
| 4. Development | If approved, technical experts model the message using repository components. | Submitting Organisation, RA, SEG Experts |
| 5. Publication | The RA publishes the new message definition in the repository for public use. | Registration Authority (RA) |
This rigorous process ensures that every part of the ISO 20022 standard is well-vetted, globally relevant, and technically sound before it becomes part of the official canon. It balances the need for innovation with the demand for stability, preventing the standard from becoming chaotic or obsolete.
It uses XML syntax to carry detailed, structured data—far more than older standards like ISO 8583 or SWIFT MT messages
The repository is the engine that makes ISO 20022 work. By providing a shared, open, and meticulously managed set of tools, it allows the global financial industry to build a truly interoperable communication network.
What is the primary function of the ISO 20022 Repository?
Which group is responsible for the day-to-day administrative management of the repository, such as reviewing submissions for completeness and publishing updates?