Use of Data Source Schemes (previously called Issuer Codes) in ISO 15022 Compliant Messages:
The data source scheme, [4!c[4c]], consists of two sub-fields:
data source issuer code - where the purpose is to identify the institution issuing a proprietary code
data source issuer sub-code - where the purpose is to explicitly identify the proprietary code in the case where a single institution issues more than one proprietary code for the same business purpose, for example, two codes for identification of parties.
An initial list of valid data source schemes, assigned on a field-by-field basis, has been agreed with ISO.
Updates to this list will be agreed between the ISO 15022 Registration Authority (RA) and the ISO 15022 Registration Management Group (RMG).
The following principles have been agreed and will be applied:
Generic fields for which there is agreement that no current need exists for a data source scheme.
If an institution or market organisation requires the use of additional (proprietary) codes in one of these fields, they either have to request the RA to register new codes in the Data Dictionary, or they have to request a data source scheme from the RA. Such a request will need to be accompanied by a business justification of why they cannot use the standard codes. It is not the intention that every bank or institution should obtain a data source scheme. In case of appeal, the final decision will be taken by the Registration Management Group.
Example fields: Account, Balance, Date/Time, Place, Rate, Status Code, Number Identification
Note: For the number identification field, it is recommended to use the ISO standard for the transmission of certificate numbers (ISO 8532, Securities - Format for transmission of certificate numbers). If the ISO standard is followed, no data source scheme must be used. A data source scheme may only be used when an institution or market organisation wants to transmit proprietary certificate numbers.
Generic fields for which there is agreement that an institution or market organisation may need to specify their proprietary scheme(s).
In this case the RA will assign a data source scheme to each institution or market organisation requesting a data source scheme, that is, the assignment will be less restricted than for the previously listed fields.
However, if an institution requests to register new codes in the Data Dictionary, the RA will not register the proprietary codes of each institution, but will translate and register any new business codes not already catered for within the ISO 15022 Standard.
Example fields: Indicator, Reason Code, Type of Financial Instrument
Generic fields for which there is agreement that the proprietary schemes for a specific list of institutions and market organisations may be used.
Example fields: Party
SWIFT is also reviewing the possibility of validating the data source scheme, that is, use of an invalid data source issuer code or issuer sub-code would cause the message to be NAKed.
The list of institutions or market organisations have already been assigned a data source scheme, only to be used with the indicated field as specified in the Data source Scheme list.
Consult www.swift.com or www.iso15022.org for the latest list.
Any additional Data Source Schemes or updates to the existing Data Source Schemes should be submitted for approval to the ISO 15022 Registration Authority. The official Data Source Scheme request form (Request for a new Data Source Scheme) can be found on the ISO 15022 web site (www.iso15022.org).
If you have any questions, contact the ISO 15022 Registration Authority Administrator:
E-mail: iso15022ra@iso15022.org
