ISO 20022-3:2013
Financial services — Universal financial industry message scheme — Part 3: Modelling
ISO 20022-3:2013 describes the modelling workflow, complementing ISO 20022-1:2013 and ISO 20022-2:2013. The modelling workflow describes the required steps a modeller follows in order to develop and maintain standardized BusinessTransactions and MessageSets.
ISO 20022-3:2013 is not intended to describe what will be the permissible artefacts and/or documents to be submitted to the Registration Authority (this information is contained in ISO 20022-7).
Examples are provided only to illustrate the modelling methodology and are not normative.
| Get this standard | Prices exclude GST | |
|---|---|---|
| PDF ( Single user document) |
$256.00 NZD
|
|
| HardCopy |
$303.00 NZD
|
|
| Networkable PDF |
Price varies
|
1 Scope
2 Normative references
3 Terms and definitions
4 Workflow activities overview
5 Scope level
5.1 General
5.1.1 Purpose
5.1.2 Key topics
5.1.3 Main activities
5.1.4 Deliverables
5.2 Activities
5.2.1 Define business context
5.2.2 Define BusinessProcesses
5.3 Guidelines
6 Conceptual level
6.1 General
6.1.1 Purpose
6.1.2 Key topics
6.1.3 Main activities
6.1.4 Deliverables
6.2 Activities
6.2.1 Define business model
6.2.2 Define BusinessTransactions
6.2.2.1 Overview
6.2.2.2 Define BusinessProcessTrace
6.2.2.3 Define MessageTransportMode
6.2.2.4 Define Participants
6.2.2.4.1 Establish whether there is a central system
6.2.2.5 Define BusinessRoleTraces
6.2.2.6 Define MessageTransmission(s)
6.3 Guidelines
7 Logical level
7.1 General
7.1.1 Purpose
7.1.2 Key topics
7.1.3 Main activities
7.1.4 Deliverables
7.2 Activities
7.2.1 Define the MessageSet
7.2.2 Compose MessageDefinition
7.2.2.1 Overview
7.2.2.2 Create a MessageDefinition
7.2.2.3 Define MessageComponentTypes
7.2.2.4 Define DataTypes
7.2.2.5 Mapping between the Business Layer and the Message Layer
7.3 Constraints
7.3.1 Inheritance
7.3.2 Normalized MessageDefinitions
7.3.3 Normalization
7.3.4 Non-Constraint preference
7.3.5 Sibling constraints
7.3.6 Value derivation
7.3.7 Versions versus flavours
7.3.8 Modelling associations between MessageComponent Types.
7.4 Guidelines
7.4.1 BusinessTransactions
7.4.2 MessageInstance style
7.4.3 Party Neutral MessageInstance
7.4.4 MessageInstance granularity
7.4.5 How to handle bi-directional relations
7.4.6 Factorize
7.4.7 How to define an ExternalSchema
7.4.8 How to enforce canonical form for date or time related user-defined DataTypes
8 Physical level
8.1 General
8.1.1 Purpose
8.1.2 Key topics
8.1.3 Main activities
8.1.4 Deliverables
8.2 Activities
8.2.1 Create syntax scheme
9 Conventions
9.1 Constraints
9.2 Naming
9.2.1 General
9.2.2 Generic rules applicable to all Repository Concepts
Keep me up-to-date
Sign up to receive updates when there are changes to this standard
Related Information
Similar Standards
-
BS 6601:1985
Specification for mail payment orders
-
BS 7896:1997
Securities. Specification for the format and structure of names and addresses used in securities transactions for the business of registrars
-
BS 8453:2011
Compliance framework for regulated financial services firms. Specification
-
BS 8577:2012
Framework for the provision of financial advice and planning services. Specification
1 Scope
2 Normative references
3 Terms and definitions
4 Workflow activities overview
5 Scope level
5.1 General
5.1.1 Purpose
5.1.2 Key topics
5.1.3 Main activities
5.1.4 Deliverables
5.2 Activities
5.2.1 Define business context
5.2.2 Define BusinessProcesses
5.3 Guidelines
6 Conceptual level
6.1 General
6.1.1 Purpose
6.1.2 Key topics
6.1.3 Main activities
6.1.4 Deliverables
6.2 Activities
6.2.1 Define business model
6.2.2 Define BusinessTransactions
6.2.2.1 Overview
6.2.2.2 Define BusinessProcessTrace
6.2.2.3 Define MessageTransportMode
6.2.2.4 Define Participants
6.2.2.4.1 Establish whether there is a central system
6.2.2.5 Define BusinessRoleTraces
6.2.2.6 Define MessageTransmission(s)
6.3 Guidelines
7 Logical level
7.1 General
7.1.1 Purpose
7.1.2 Key topics
7.1.3 Main activities
7.1.4 Deliverables
7.2 Activities
7.2.1 Define the MessageSet
7.2.2 Compose MessageDefinition
7.2.2.1 Overview
7.2.2.2 Create a MessageDefinition
7.2.2.3 Define MessageComponentTypes
7.2.2.4 Define DataTypes
7.2.2.5 Mapping between the Business Layer and the Message Layer
7.3 Constraints
7.3.1 Inheritance
7.3.2 Normalized MessageDefinitions
7.3.3 Normalization
7.3.4 Non-Constraint preference
7.3.5 Sibling constraints
7.3.6 Value derivation
7.3.7 Versions versus flavours
7.3.8 Modelling associations between MessageComponent Types.
7.4 Guidelines
7.4.1 BusinessTransactions
7.4.2 MessageInstance style
7.4.3 Party Neutral MessageInstance
7.4.4 MessageInstance granularity
7.4.5 How to handle bi-directional relations
7.4.6 Factorize
7.4.7 How to define an ExternalSchema
7.4.8 How to enforce canonical form for date or time related user-defined DataTypes
8 Physical level
8.1 General
8.1.1 Purpose
8.1.2 Key topics
8.1.3 Main activities
8.1.4 Deliverables
8.2 Activities
8.2.1 Create syntax scheme
9 Conventions
9.1 Constraints
9.2 Naming
9.2.1 General
9.2.2 Generic rules applicable to all Repository Concepts