Payments External Code Lists
The ISO 20022 Payment messages use 19 'external code lists' which are validated and approved by the Payments SEG.
The listed code values can be used in specific elements of the payments messages as indicated in the documents below. Unlike other ISO 20022 code lists, the code values are not included in the XML message schema with the message element they type. The purpose of externalising these code values is to be able to update the code lists (e.g. add new code values) without impacting the message themselves and, hence, without requiring the development of a new version of the messages that use these code lists.
The code lists are published in two sets of documents:
- 16 external code lists are published in a spreadsheet which is versioned at three levels: the spreadsheet itself has a publication date, each list within the spreadsheet has a publication date (see 'CodeInventory' sheet) and each individual code value has a date of last update ('status date').
Download the Payments External Code Lists spreadsheet - dated 3 February 2010
- 3 code lists which are combined to form the 'Bank Transaction Code' are described separately:
Download the Bank Transaction Code lists description - dated 16 June 2009
Download the possible Bank Transaction Code combinations - dated 24 June 2009
Requests for updates to External Code lists (addition of a new code value, clarification of an existing definition, deactivation of an existing code value) must be submitted to the ISO 20022 RA, using the "Change Request for update of an External Code list" template. Change requests received by end of March, end of June, end of September and end of December are evaluated on a quarterly basis and approved updates are published respectively by end of May, end of August, end of November and end of February.
Data Source Schemes (DSS)
A Data Source Scheme (DSS) is a mechanism which allows an industry body to specify the use a proprietary code list that is not owned nor managed by ISO 20022, and that replaces a standard code list (either a specific ISO 20022 managed code list or another ISO standard code list, e.g. BICs or ISINs) in specific ISO 20022 Message Components, where the use of such DSS has been approved.
The DSS consists of the following parts:
- a mandatory 'data source issuer' which identifies the institution or organiztion issuing the proprietary code list,
- an optional 'data source scheme name' which identifies the code list in case a data source issuer issues more than one code list for the same business purpose, e.g., two code schemes for identification of parties, and
- the actual proprietary code value.
The RA maintains the list of all ISO 20022 Data Source Schemes as well as the specific Message Components in which they can be used. The list gives the following information:
- which ISO 20022 Message Components support which DSSs,
- the data source issuer information: description, country of issuer,
- the data source scheme name(s), if any.
It does not include the list of proprietary code values, which are maintained separately by the data source scheme issuers.
Download the Data Source Schemes (DSS) List - dated 19 May 2010
Requests for updates to the Data Source Schemes List (creation of a new DSS or use of an existing DSS in a new Message Component) must be submitted to the ISO 20022 RA, using the "Request for ISO 20022 Data Source Scheme (DSS) registration" template.
Supplementary Data
Some ISO 20022 messages include a 'SupplementaryData' component that can be used by communities of users to add information to a message that is not catered for by other components of the message. The information in the SupplementaryData component must be ISO 20022 compliant: it requires development of a compliant model and its components must be registered in the ISO 20022 Data Dictionary.
Use of the SupplementaryData component is subject to the approval of the SEG in charge of the message. Two use cases can be considered by the SEG:
- the need to transport the additional information is too urgent to undertake the formal ISO 20022 maintenance process. The additional information will be included in the SupplementaryData component until specific components are created within the body of the messages at the occasion of the next maintenance;
- the supplementary data is too specific or too volatile to deserve specific components within the body of the message itself. Use of the SupplementaryData will avoid impacting the entire user base.
The SupplementaryData component is made of two elements:
- an optional location element, allowing the supplementary data to be targeted at a specific point in the message, if required
- a mandatory structured data element, which allows the identification of a separate ISO 20022 compliant schema and the inclusion of data that conforms to that schema.
Request for use of the SupplementaryData must be introduced to the ISO 20022 RA using the usual Change Request template. The change request must completely detail the various items of additional information (description, data type, cardinality, related ISO 20022 Business Component), the targeted community of users and the reason why use of the SupplementaryData is deemed to be necessary for each of these items. It must also indicate which organisation will develop the ISO 20022 compliant model including the business data required in the SupplementaryData.
If use of the SupplementaryData is approved by the SEG, a candidate ISO 20022 model of the contents of the SupplementaryData component must be submitted to the ISO 20022 RA for compliance checking and registration. Registered SupplementaryData extensions will be published in the Catalogue of ISO 20022 messages.
