static data business requirements - european central bank

Target2-Securities Project Team

TARGET2-SECURITIES

TECHNICAL GROUP 4 ON STATIC DATA

STATIC DATA BUSINESS REQUIREMENTS

Reference: T2S-07-0250

Date: 18 September 2007

Version: 0.1

Status: Draft

Target2-Securities Technical Group 4 on Static Data

Static Data Business Requirements

i

TABLE OF CONTENTS

1 Introduction..................................................................................................................... 2 2 Glossary of Frequently Used Terms.............................................................................. 4 3 General Principles........................................................................................................... 6

3.1 Static Data Identifier Requirements.......................................................................... 6 3.2 Static Data Status Information Requirements........................................................... 7 3.3 Data Revision and Data History ............................................................................... 9 3.4 Static Data Management ......................................................................................... 12

4 Configuration Requirements ....................................................................................... 19 4.1 Business Date.......................................................................................................... 19 4.2 Daily Processing Schedule...................................................................................... 20 4.3 System Entity Configuration Requirements ........................................................... 20 4.4 Closing Day Calendar ............................................................................................. 25 4.5 Authentication and Authorization........................................................................... 26 4.6 Authentication Parameters ...................................................................................... 32 4.7 Roles and Privileges for Authorisation ................................................................... 33

5 Currency Data............................................................................................................... 44 6 Securities Reference Data Model................................................................................. 46

6.1 Securities................................................................................................................. 47 6.2 Securities Name ...................................................................................................... 48 6.3 Securities Code ....................................................................................................... 49



Version: 0.1 Page: 2 of 53 Status: Draft

1 Introduction

The aim of this document is to describe the complete static data user requirements for T2S.




2 Glossary of Frequently Used Terms This section provides a glossary of terms, frequently used in the documents of T2S Technical Group

4, but that are not included in the officially approved T2S glossary.

Term Definition

Attribute An attribute defines a characteristic of an entity. For example, the type of security is an attribute of the entity security static data.

Authentication Authentication is a security mechanism for verifying the identity of an individual or process.

CSD in T2S A CSD in T2S is a central securities depository that 1) has entered into a contractual relationship to operate on the Target2-Securities platform, 2) fulfils Article 10 of the Settlement Finality Directive 3) settles in at least one T2S eligible currency and 4) settles in a central bank money.

CSD Participant

A CSD Participant is a legal entity that has a legal or contractual relationship with a central securities depository for the purpose of holding and transferring securities.

Entity In conceptual modelling terms, an entity is a collection of attributes used to define a person, place, event, object or thing that an information system needs to operate or about which an organisation collects data. Although an entity is conceptual, its physical implementation is one or more database tables.

Occurrence An occurrence is an individual element belonging to an entity. It would be a record in a database table or file in terms of physical implementation.

T2S Party A T2S party is the term used to define a legal entity using T2S or a participant of a legal entity using T2S. A T2S party is an occurrence in the T2S party static data and can be the T2S operator, a national central bank in T2S, a CSD in T2S or a participant of a CSD in T2S.

Party Type The party type classifies a T2S party into the T2S operator, a CSD in T2S, a participant of a CSD in T2S and a national central bank.

Privilege A privilege is right, either granted or denied, to execute certain functions within an application or to access and/or update certain data.

Role A role consists of a set of related privileges. The functions that a user performs to fulfil her/his responsibilities within an organisation define a role.




Term Definition

System Entity A system entity in T2S is the T2S operator or a central securities depository for which a segregation of processing capabilities and data is required.

T2S System User

A T2S system user is an individual or application that can log on to Target2-Securities with a login name and password. For example, a user may be an individual, who has an interactive access to T2S online functions; or an application programme, which requests services from T2S.




3 General Principles

General principles define the overall requirements pertaining to the management of all static data in T2S. The section Static Data Identifier Requirements specifies the requirements for uniquely identifying static data objects in T2S and avoiding the use of mnemonics as primary keys for static data. The Static Data Status Information Requirements sections details the standardised tracking of states for static data management in T2S. The section Data Revision and Data History provides the list of requirements for ensuring a full audit trail and history of static data. Static Data Management documents the standards applicable to the change management functions for all static data entities.

3.1 Static Data Identifier Requirements

3.1.1 Technical Identifier Requirement TG4.GP.1.1

Traceability Principles 20

Traceability Proposals 1, 11, 65

Occurrences in static data entities require a unique sequence as primary identifier. The allocation of

this primary identifier shall occur sequentially from a database counter. It shall be the object

identifier, used to identify the occurrence of a static or transactional data entity. When a user or

application appends a new occurrence in an entity, the application programme shall assign the current

value of the counter as the technical identifier to that occurrence, and increment the counter by one

for assignment to the next occurrence. The database administrator shall configure a counter for

exclusive use as a primary identifier for a static data entity. For example, security static data will use

a different counter as technical identifier than T2S party data.

3.1.2 Revision Number Requirement TG4.GP.1.2



The revision number is the counter within a technical identifier of an occurrence of static data that is

incremented by one when a user or application updates an attribute of that occurrence. Its primary

use is to ensure the uniqueness of an occurrence when there are several revisions to that occurrence.




3.2 Static Data Status Information Requirements Requirement TG4.GP.2


Traceability Proposals -

Status information is required to define the technical state of a static data occurrence and any updates

to that occurrence in T2S. Every static data entity shall include status information. These status

attributes are not included in the attribute requirements for entities in the subsequent sections to avoid

repetitiveness.

3.2.1 Deletion Status Requirement TG4.GP.2.1



Every occurrence in static data shall have an attribute, which defines if it is active or deleted, i.e.

whether it is available for use by processing functions and applications.

3.2.1.1 Active Setting

Requirement TG4.GP.2.4



The active status shall specify that an occurrence of static data is available for processing. For

example, T2S shall accept and process settlement instructions only when the deletion status of the

security and the account are active. Otherwise, T2S shall reject them.




3.2.1.2 Deleted Setting

Requirement TG4.GP.2.3


Traceability Proposals 65

The deleted status shall specify that an occurrence of static data is no longer available for processing:

it shall define a record as deleted for further use in T2S. When an application or user logically deletes

an occurrence, the user must be able to use the occurrence of static data for historic queries and

information requests (e.g. a backdated position query on a deleted account). However, T2S shall

reject new settlement instructions for a logically deleted record. Neither must it be possible for a user

to amend logically deleted data.

3.2.2 Approval Status Requirement TG4.GP.2.4



Every occurrence of static data shall have an approval status to define whether the user has approved

or rejected changes in attribute values of that occurrence, or if the update is awaiting approval by the

user.

3.2.2.1 Awaiting Approval Setting

Requirement TG4.GP.2.4.1



“Awaiting approval” shall define any change to static data that has been input and requires

confirmation by a second user, but approval by a second user is outstanding. T2S processes and

applications must not use unapproved changes.

3.2.2.2 Approved Setting







“Approved” shall define any change to static data, entered by a user or an application into T2S, that

requires confirmation by a second user, and confirmed to be correct by a second user.

3.2.2.3 Rejected Setting




“Rejected” shall define any change to static data, entered by a user or an application into T2S,

requiring confirmation by a second user, but cancelled by a second user as incorrect.

3.3 Data Revision and Data History Requirement TG4.GP.3



T2S shall undertake a differentiation of static data between data revision and data history. Data

revision shall define any update to static data, which is not a result of chronological record keeping.

Data history shall define the chronological record of changes to reference data, subject to change in

its lifetime, but that remains valid for a specified period.

For example, T2S shall keep a chronological record, i.e. data history, for legal addresses for account

relationships in T2S, since the owner of the account may move corporate headquarters and legal

jurisdiction. Even though the new address and jurisdiction are in effect, the previous jurisdiction

remains valid for backdated regulatory reporting. Additionally, the address will require data revision.

If an application or user makes a correction to the address due to an erroneous input, it needs to

generate a revision to identify the modified data, the application or user that undertook the change and

the date and time of the change.

3.3.1 Data Revision Requirement TG4.GP.3.1



T2S shall store data revisions in its physical static data model. T2S shall not simply log changes to a

text file and the text file archived as is the case in many applications today.




3.3.1.1 Data Revision Implementation

Requirement GP.3.1.1



Storing data revisions in the database requires replicating all static data structures with their attributes

as revision tables. A current static data entity shall store only the occurrences that are currently valid

for processing in T2S. Therefore, the technical identifier shall uniquely identify each record in the

table. All previous states of the record, which include both approved and rejected changes, as well as

entered, but yet unapproved changes, shall be stored in the corresponding static data revision entity.

Since many records may exist for an occurrence in the revision table, the technical identifier in

combination with a sequential revision number shall uniquely identify each record. This shall ensure

uniqueness of occurrences in the revision table. The following figure provides an example of revision

for instrument static data.

Figure 1 - Instrument Static Data - A Revision Example

05/07/07 5

Instrument Static Data – An Example

Instrument Static Data

Security Identifier <pk>

Security Revision

Authorisation Status

Technical Status

Security Status

User Identification <fk>

Maintenance Stamp

. . .

Instrument Static Data Revision

Security Identifier <pk>

Security Revision <fk>

Authorisation Status

Technical Status

Security Status

User Identification <fk>

Maintenance Stamp

. . .

The current table stores the active record.

The revision table stores all previous changes as well as rejected and unapproved changes.

The current record is always identified by a unique sequential identifier.

The revision record is identified by the combination of the unique sequential identifier of the current table and a sequential revision number.

The user and the timestamp is documented in every record.

The Authorisation Status specifies the update status of a record, i.e. is the data in the record approved, unapproved (ready for approval) or rejected).

The Technical Status specifies whether the record is active or logically deleted.

This attribute defines market status of an instrument (e.g. “when issued” or “matured”.




3.3.1.2 Audit Trail




Each data revision shall document the modified data on attribute level, the user performing the

change and the timestamp of the change. Every static data entity shall include the audit trail

attributes.

Table 1 - Audit Trail Attribute Requirements

Attribute Definition

User Every static data entity shall include the technical identification of the user who updated an occurrence (record). It must be possible to identify explicitly the individual or application that changed the data by linking the technical identifier to the user name in the authentication application.

Time Stamp Every static data entity shall include the date and time to document when a user updated an occurrence (record). The time stamp is a snapshot of the operating system date and time when a change is committed.

Approval Status Every static data entity shall include the approval status to document whether processing status of an update.

3.3.2 Data History Requirement GP.3.2



T2S shall store all data, requiring a history, with a valid from date and, if necessary, a valid to date.

Only information with a definite end date shall require a valid to date. For example, a change of legal

address will not require an end date. When the legal address changes, the user enters the new address

with a valid from date. Any application programme can identify immediately the active legal address

for a given date merely by comparing the date with the valid from date. There is no requirement for a

valid to date in this scenario, since T2S will always require a current legal address for an active T2S

party.




Adding an end date only would increase the complexity of maintenance process without adding value

in terms of business information and data consistency. In the case of the example, tracking a valid to

date for change of address would require both a new record to be written and the valid to date of the

previous record to be updated with the new valid from minus one calendar day. The use of a valid to

date in these circumstances does not simplify the reading or querying of data. It merely avoids the

use of a maximum value function in an SQL statement.

However, there are cases where a valid to date for a set of information is mandatory. In these cases, it

sets the end marker for the information chronology. The status of a relationship between a CSD and a

financial instrument in T2S would be such an example. A data entity in T2S will define the securities

for which a CSD acts as either an investor CSD or an issuer CSD. For example, CSD ABC acts as

investor CSD for financial instrument XYZ as of a given date in the past. Today, CSD ABC could

decide that it no longer wishes to be investor CSD for financial instrument XYZ as of a given date in

the future. In this case, the valid to date allows the CSD to specify today the future date from which

the CSD will no longer accept the security for settlement.

3.3.3 Archiving Requirement GP.3.3



Data history and data revisions shall be subject to regulatory and legal data retention requirements. In

order to ensure the integrity of static and transactional data, data revisions and data history shall

remain in the current database until archiving procedures copy the transactional data that reference it

into either a history and/or archiving database.

3.4 Static Data Management Requirement GP.4



Static data management refers to the functionality that T2S shall provide for maintaining static data in

T2S regardless of the type of conceptual entity. T2S will apply the same functional principles for the

deletion of a security, as it will for the deletion of an account.




3.4.1 Static Data Change Management Requirement GP.4.1



Static data change approval specifies the business requirements for processing and approving updates

to static data.

3.4.1.1 Change Approval Configuration




The objective is for T2S to provide a flexible configurable change management component for static

data so that CSDs can parameterise their change approval processes for the various static data entities

according to their legal, regulatory and operational requirements. Change approval configuration

defines the functions, required in T2S, to parameterise the entities and types of updates made by a

user or process that require approval from a second independent user or process.

3.4.1.1.1 Manual or Automated Update

Requirement GP.4.1.1.1



It must be possible to differentiate in the configuration of the second user approval between an

automated update through an interface and an interactive manual update by an individual for a static

data entity on CSD level. For example, it should be possible to specify that an update of security

static data by an automated interface should not require second user approval, but a manual update by

a person is subject to such an approval.




3.4.1.1.2 Change Type




It shall be possible for the user to specify whether second user approval is required for adding,

changing or deleting an occurrence in a specific static data entity for a specific CSD. For example,

the changing of account data may not require authorization by a second user, but its deletion does.

3.4.1.1.3 Combination of Change and Update Type




T2S shall support the configuration of change approval, based on the combination of change type and

update type (manual or automated).

3.4.1.2 Change Processing Algorithms




Any application, used to maintain static data, shall verify if the change to an occurrence of static data

it is processing is subject to approval by a second user. The static data maintenance application shall

read the change approval configuration for its entity / entities and shall process the update according

to the configured parameters.




3.4.1.2.1 Processing a New Occurrence




When a new occurrence in a static data entity is subject to approval by a second user, the static data

maintenance application shall create it immediately in the relevant current static data entity with a

status "awaiting approval". If a second user approves the change, then static data change

management shall reset the status from "awaiting approval" to "approved" in the current data. If the

second user does not approve the new occurrence, then static data change management shall delete

the update from the current entity and write it to the revision entity with the status "rejected". If a

new occurrence is not subject to approval by a second user, then static data change management shall

create it in the applicable current static data entity with a status "approved".

3.4.1.2.2 Processing an Update of an Occurrence




When a user updates an occurrence of static data, which is subject to approval by a second user, static

data change management shall create the changed version of data as a new occurrence in the relevant

revision entity with a status "awaiting approval". The current version shall remain unchanged and all

applications shall use it until a second user approves the update. If a second user accepts the change,

then static data change management shall write the changed occurrence to the current entity with the

status "approved" and delete it in the revision entity. Static data change management also deletes the

previously valid version of the data from the current entity and creates it as part of the audit trail in

the revision entity. If the second user does not approve the update, then static data change

management updates the status of the change to "rejected" and it remains as an unapproved change in

the revision entity.




3.4.1.3 Change Approval User Interface




The change approval user interface defines the requirements for

− identifying all static data changes awaiting approvals;

− searching for specific static changes;

− searching and displaying historic change information, both approved and rejected changes;

− and approving and rejecting static data changes.

3.4.1.3.1 Changes Awaiting Approval




The user shall be able to query static data changes awaiting approval. Access to this facility shall be

restricted to those users who have the necessary access rights to approve static data changes. A

search parameter window shall exist in the online user interface, where a user can enter criteria to

search for updates awaiting approval. Firstly, the user shall be able to specify type of data (e.g.

security static data, account static data, etc.) in the search. The user shall further be able to restrict the

search to a period for the update, the user account of the person who performed an update, or to a

specific mnemonic (e.g. ISIN, account number).

3.4.1.3.2 Search Results List




The results list shall display all changes awaiting approval for those data for which the user has

sufficient access rights - a user of one CSD shall not see the static data changes awaiting approval of

another CSD. The results list shall display the time stamp of the change, the user who made the

change, the static data entity that has been updated (e.g. user, party and security) and the mnemonic of

the occurrence in the static data entity for each result fulfilling the search criteria. The user shall have

the capability to select a change for approval from the search results list.




3.4.1.3.3 Approve or Reject Change Detail




When the user selects a static data change for approval or rejection, a change detail window shall

display the changes to a related the set of data. The change detail window shall show the mnemonic,

identifying the static data occurrence, and the old and new values for each changed field. The user

shall be able to accept or reject the update from this window. It should be noted that for a new

occurrence the column for old values will be empty. A change type shall indicate this.

3.4.2 Deleting a Static Data Occurrence Requirement GP.4.2



The deletion of an occurrence of static data shall only occur logically. The physical deletion of static

data shall not be possible in T2S in order to ensure the referential integrity of information.

3.4.2.1 Validation and Logical Deletion




A logical deletion of an occurrence of static data shall be possible only when there are no active

transactions or holdings in T2S for that occurrence. When a user or application initiates the deletion

of an occurrence in static data, the deletion function must ensure that there are no open settlement

instructions and only zero positions pertaining to that data. If this is the case, then the deletion status

of the occurrence shall be set from 'active' to 'deleted'. Existing open settlement instructions or active

positions for the data, subject to deletion, shall result in the rejection of the deletion.




3.4.2.2 Reactivation of a Logical Deletion




In some instances, it will be necessary to reactivate a logically deleted occurrence of static data. A

generic function shall exist that allows the user to specify the static data entity and the identifier of an

occurrence in that static data entity, and to reset the deletion status of a record in that entity from

“deleted” to back to “active”.

3.4.2.3 Physical Deletion




Only archiving processes shall delete static data from the active T2S database To ensure the

referential integrity of data, the physical deletion of static data occurrences from the active database

shall be performed only after archiving processes have removed and archived the related transactional

and position data as of a cut-off date that is determined by a retention period. The physical deletion

of a static data occurrence shall only be possible for logically deleted occurrences. Data history and

data revisions, that are before the archive date, shall be included in any physical deletion process even

if the current record is still active - since the transactional data for which they are relevant would be

removed by the archiving.




4 Configuration Requirements This section documents the configuration requirements for processing in T2S.

4.1 Business Date Requirement C.1



T2S shall have an internal business date, which will determine the date of processing. This date shall

be independent of the system date in the operating system. T2S will initiate processing for a new

business day before midnight. When this occurs, a process must use the T2S business date instead of

the operating system date to identify transactions for settlement and for updating balances. A

business date, independent from the operating system date, will also facilitate testing in that it allows

processing for a specific business day to be regression tested. The business date must have a valid

date format and must be a working day.

4.1.1 Manual Update of Business Date Requirement C.1.1



An authorised user shall be able to change the business date manually in T2S through an online user

interface.

4.1.2 Automated Update of Business Date Requirement C.1.2



A process shall exist to calculate the next business day from the current business day and to update

the business date to the next business day. It shall be possible to schedule or trigger this update in the

daily processing cycle of T2S.




4.1.3 Resetting Processes after Business Date Update Requirement C.1.3



Mechanisms shall stop all continuously running processes, using the business date, before the

business day change so that all applications register the switchover to the new business day.

4.2 Daily Processing Schedule Requirement C.2


Traceability Proposals 17, 20, 21, 22, 23, 24, 25, 26, 56

The T2S operator shall maintain the T2S processing schedule as well as scheduling dependencies

between processes, regardless of the actual scheduling. For example, the start of process B is must

wait for the successful completion of process A even if process A runs longer than the scheduled start

time for process B.

It is not a requirement to store the processing schedule and processing dependencies as part of the

T2S application. Standard software products exist that fulfil the requirements for time- and event-

driven process automation for T2S.

4.3 System Entity Configuration Requirements Requirement C.3

Traceability Principles 4, 6


Multi-entity configuration requirements in T2S encompass all functionality, needed to support the

segregation of processing capabilities and data by a participating CSD. The CSD is legally

responsible for its participants and its services it provides to its participants - the service offerings of

the CSDs may differ to various extents. Therefore, the CSD must be able to configure its service

offering by granting or denying access to specific functions and facilities of T2S to its participants.




The second dimension of multi-entity configuration is the segregation of data. System entity

configuration is fundamental for the segregation of the static and transactional data of CSDs in T2S.

A CSD must not be able to access the participants, positions and transactions of the other CSDs. The

configuration of CSDs as entities in a multi-entity architecture shall allow for the partitioning of data

on the database level as well as on the functional level in T2S.

4.3.1 Defining System Entities Requirement C.3.1



The implementation of a two level hierarchy shall support the multi-entity configuration of T2S. The

top level in the hierarchy shall define the T2S system operator. The second level of the hierarchy

shall define the CSDs, participating in T2S, as well as the Target2 operator. This means that the

operator(s) of T2S will be responsible for configuring the CSDs and the T2 operator as system

entities in the platform. The CSDs shall be able to create, maintain and access data for their

participants and to their data. The T2 operator is to be able to create, maintain and access data for

connected national central banks (NCB) and the payment banks connected to the NCBs.

Any CSD and the T2 operator shall be unique occurrences as T2S parties in the party static data, but

their configuration as system entities in T2S will be prerequisite for the user to enter the occurrences

in the static data. The T2S operator must configure a system entity before a business user can enter

the entity’s party and other static data as well as other configuration information.

4.3.2 Entity Attribute Requirements for System Entity Definition Requirement C.3.2



Entity attribute requirements specify the information, needed for the configurations of system entities

in T2S.




Table 2 – System Entity Definition


System Entity Identifier

The system entity identifier shall be the unique technical identifier assigned to a CSD and the T2S operator with the exception that the T2S operator shall manually assign this unique sequence.

Mnemonic The mnemonic shall be unique short code used to identify the entity to the business user in addition to the system entity identifier. The mnemonic must be unique.

Entity Name This attribute shall specify the full name of a system entity.

Operating Entity This Boolean attribute shall indicate whether the defined entity is the T2S operator. The system entity configuration shall allow only one occurrence of an operating entity in the system entity definition.

4.3.3 Functional Requirements

4.3.3.1 Segregation of Data

Requirement C.3.3.1



Static and transactional data shall be segregated by system entity, where applicable using the system

entity identifier. This means that the system entity identifier must be an attribute of specific static

data and transactional entities in T2S as the prerequisite for data segregation.

One implementation option for the segregation of data by CSD (or system entity identifier) is storing

only the system entity identifier in the necessary static data and transactional entities without the use

of database partitioning. However, data management operations, such as backup, recovery and data

loads, will occur on the entire table level. A T2S system operator will not be able to undertake these

operations independently on CSD level, when necessary.




The recommended implementation for a multi-entity system configuration is the partitioning of data

by CSD through the utilisation of the system entity identifier in the database. Partitioning of database

tables, using the system entity identifier, shall allow T2S system operators to undertake backup,

recovery and other data operations for one CSD. For example, if a CSD requires a full export of its

data, then the T2S system administrator can perform the data export operation for the data in the

CSD’s partition. A backup by CSD is also possible. Without data partitioning, a data export would

result in an unloading of data for all CSDs. SQL procedures would be required to unload CSD-

specific data in the case where partitioning does not exist. A backup operation would cover all CSDs

making the recovery of data for one CSD very complex.

The T2S database administrators shall undertake the necessary partitioning of data on the system

entity identifier in the relevant database tables. Partitioning requires changes on the database level

when a CSD joins T2S as a new participant.

4.3.3.2 Querying and Selecting System Entities

Requirement C.3.3.2



It shall be possible for a user to query system entities and to select an occurrence for update, display.

It shall also be possible to enter new system entities.

4.3.3.2.1 Parameter Window for Update and Display

Requirement C.3.3.2.1



A parameter window shall exist in the online user interface, where a user is able to enter the

mnemonic or the technical identifier of a system entity for update or display. If the user does not

know either code, then the user shall be able to execute a search, which displays the list of valid

system entities.




4.3.3.2.2 List of System Entities for Input


Traceability Principles

Traceability Proposals

Functions on the T2S operator level shall require the input of the system entity when querying,

entering, changing and maintaining data. T2S shall display a list of valid system entities for any field

in which the system entity can be input as either technical identifier or mnemonic. The list row shall

display the technical identifier, mnemonic and name of a system entity. When the user selects a

system entity from the list, then application shall automatically enter the value into the input field for

the system entity.

4.3.3.3 Maintaining System Entities

Requirement C.3.3.3



System entity maintenance refers to the process of adding, changing and deleting system entities in

T2S. Access to this functionality shall be restricted to the T2S System Administrator of the T2S

operator.

4.3.3.3.1 Adding a System Entity




It shall be possible for a user to add a new system entity from the search parameter window by

executing an add function. An input window shall appear where the user can enter the mnemonic,

technical identifier and name for the system entity. The reader should note that the database

administrator must create the database partition for the new CSD before a business user can enter data

for that CSD.




4.3.3.3.2 Updating a System Entity




It shall be possible for a user to update an existing privilege by selecting it for update from the results

list.

4.3.3.3.3 Deleting a System Entity




It shall not be possible for a user to delete an existing system entity by simply executing a delete

function in the update mode. Deleting a system entity must not be possible from the user interface.

4.4 Closing Day Calendar Requirement C.4



T2S shall have a calendar, which will specify those dates on which T2S is not open for settlement.

Since the system shall support currencies other than Euro, the calendar model in T2S shall support the

differentiation of closing days by currency. The user shall not specify Saturdays and Sundays

explicitly as non-operating days in the calendar. The application shall identify these days through the

system calendar of the operating system.

4.4.1 Entity Attribute Requirements for Calendar Requirement C.4.1



Entity attribute requirements specify the information, required for determining the non-opening days

of T2S by currency.




Table 3 – Non-Operating Day Calendar Definition


Settlement Currency Code

This attribute shall specify the currency code.

Date This attribute shall specify the date on which T2S is not open for the given settlement currency.

4.4.2 Update of Calendar Requirement C.4.2



An authorised user shall be able to modify the closing day calendar in T2S through an online user

interface. The user shall be able to query the closing day calendar by currency. T2S shall provide a

parameter window in which the user can enter the currency code and the year. The user shall be able

to execute a search after entering valid values in both fields. The search function returns a results

window of all closing day for the specified year and currency. T2S shall provide the user with the

functionality to add or delete closing days in this results window.

The application shall not accept the definition of a Saturday or Sunday as a closing day. T2S will

automatically determine these two days of the week through the system calendar.

4.5 Authentication and Authorization

4.5.1 Business Role Classification Requirement AA.1.1



Access to data and applications in T2S will be dependent on the business role of a T2S party. It is

premature at this stage in the project to define the specific applications and functions that a role shall

include. However, the broad categories of functions and data to which a T2S party must have access

to, or have its access restricted by, are definable based on its business roles and responsibilities of the

party in the marketplace and in T2S.




T2S shall place no restriction on the possible roles that a T2S system administrator can configure.

The legal, regulatory and contractual requirements of and between the parties in T2S will define any

constraints in the access to functionality within T2S. For example, a CSD may configure different

roles for its participants in order to provide a differentiated service offering based on their own

customer classifications. Some CSDs may want to offer direct connectivity to T2S while others will

not. It would also be feasible for CSD to allow users with direct connectivity online access to

positions and transactions in T2S as they do in some markets today.

The business requirements for roles establish the principles that will govern access to sets of functions

and data in the system. They do not predicate that a specific role(s) that will be technically

configured for T2S.

Figure 2 - Hierarchy of Roles

CSD A

T2SOperator

CSD nCSD B. . .

CSD B Bank A Broker A

Account 1 Account 2 Account n. . .

Level 1

Level 2

Level 3

Level 4

Level 5

T2Operator

NCB

PaymentBank

Dedicated T2SCash Account 1

AccountLink 1

Dedicated T2SCash Account n. . .

StockExchange

CentralCounterpart

CSD A

T2SOperator

CSD nCSD B. . .

CSD B Bank A Broker A

Account 1 Account 2 Account n. . .

Level 1

Level 2

Level 3

Level 4

Level 5

T2Operator

NCB

PaymentBank

Dedicated T2SCash Account 1

AccountLink 1

Dedicated T2SCash Account n. . .

StockExchange

CentralCounterpart

T2S shall support a hierarchical model of roles and access rights to ensure both the segregation of

functions and data.




4.5.1.1 Role T2S Operator

Requirement AA.1.1.1



The T2S operator shall be the top level of the hierarchical role and access model. The role

classification T2S operator describes all T2S system users of the entity, which will be responsible for

the day-to-day operation and management of Target2-Securities. Its customers will be the CSDs

participating in T2S. At the top level, the T2S operator has access to all data and functionality in the

subordinate level.

4.5.1.1.1 Role of T2S System Administrator

Requirement AA.1.1.1.1



The T2S system administrator role shall be responsible for

− the user administration for all T2S system users of the T2S operator;

− the user administration for the CSD system administrators;

− the day-to-day monitoring of system applications, processes, and communication channels;

− the configuration of privileges and privilege classes in T2S;

− the configuration of roles for the T2S system users of the CSDs, National Central Banks and the 3CB+ Target operator;

− the configuration of roles for T2S business support users;

− the contingency operations, i.e. starting and stopping processes outside of the normal operating schedule, in T2S;

− and the configuration of CSDs as system entities.




4.5.1.1.2 Role of T2S Business Support




The T2S business support role will be responsible for

− the maintenance of the T2S party static data, excluding accounts, for CSDs participating in T2S;

− the maintenance of T2S party static data for National Central Banks and the 3CB+ Target operator;

− providing the 1st level business support to CSD users;

− the maintenance of T2S code tables for global and CSD-specific codes;

− and query and maintenance privileges for all positions, settlement confirmations, settlement instructions and static data of all CSDs and their participants for provision of business support.

Maintenance and query privileges for business data, such as securities and cash positions and

transactions, of CSDs, the CSDs’ participants, and national central banks shall be limited to

emergency response situations only. The T2S system administrator shall restrict access to

maintenance functionality to a subset of T2S business support users, based on the support

requirements of CSDs, the T2 operator and national central banks. For example, maintenance

privileges could only be limited to the business support user for a specific CSD.




4.5.1.2 Business Role CSD




The role classification CSD describes all T2S system users of a CSD participating in T2S. It does not

include the T2S users of the participants of the CSD.

4.5.1.2.1 Role of CSD System Administrator




The CSD System Administrator role will be responsible for

− the user administration for all T2S system users of the CSD and its participants, including the assignment of roles;

− the configuration of roles for the T2S system users of the CSD’s participants;

− and the day-to-day monitoring of system applications, processes, and communication channels at the CSD;

CSDs shall be responsible for defining for its customers the functionality to which its participants can

connect. Therefore, it shall be possible for CSDs to configure roles and access rights to functionality

based on their business service model.

4.5.1.2.2 Role of CSD Business User




The CSD business user role will be responsible for

− the maintenance of the accounts of the CSD in T2S;

− the maintenance of account structures of the CSD;

− the maintenance of T2S party static data, including accounts, for its participants;

− the maintenance of CSD-specific instrument static data and, where applicable, the instrument static data across all CSDs;




− maintenance of any settlement restrictions;

− the definition of roles for the T2S system users of the CSD’s participants;

− and query and maintenance privileges for all positions, settlement confirmations, settlement instructions and static data of specific to the CSD and its participants for provision of business support.

4.5.1.3 Business Role CSD Participant




The role classification CSD participant describes all T2S system users that a CSD maintains for its

participants. The scope of functions and processes that a CSD participant can access shall be

dependent on the business model of the CSD. However, the data access of a CSD participant shall be

limited to its accounts, positions and transactions.

4.5.1.4 Business Role National Central Bank




The role classification National Central Bank describes all T2S system users of central banks that

require access to the cash account balances and postings of the T2S dedicated cash accounts for

central bank money. The role shall enable the T2S system user of the national central bank to:

− query all Target2 dedicated cash accounts for which the NCB is responsible;

− determine the owner of every Target2 dedicated cash account;

− determine the CSDs through which the owner of the account generates postings;

− and query the balances and postings on cash accounts for which the NCB is responsible.

However, it will not be possible for the NCB to view the settlement transactions that have resulted in

a posting.




4.5.1.5 Business Role Target2 Operator




The role classification Target2 operator describes all T2S system users that require access to the cash

account information of all T2S dedicated cash accounts. The role grants access to all functions

provided by the role NCB, but across all Target2 dedicated cash accounts held at all national central

banks. Additional, the role shall include

− the maintenance of the national central banks as T2S parties,

− and the configuration of roles for users of the national central bank.

4.6 Authentication Parameters Requirement AA.2



Authentication parameters define settings, required for login security. The application software,

providing the authentication facilities for T2S (e.g. LDAP, RACF, etc.), shall support the specified

parameters to ensure strong authentication.

Table 4– Authentication Parameters


Password Expiry This attribute defines the maximum number of calendar days that a password is valid.

Minimum Account Name Length

This attribute specifies the minimum number of characters allowed in the account name.

Password Complexity

This attribute allows the specification of the complexity of the password by the user. For example, it must be possible to specify that a password should contain at least on uppercase character, at least one symbol and at least one number.

Minimum Password Length

This attribute defines the minimum number of characters allowed for a password.

Password Reuse This attribute specifies the number of password changes before a user may reuse a password. This includes the specification of rules defining password reuse - i.e. what constitutes reuse.





Maximum Login Attempts

This attribute specifies the maximum number of login failed attempts before the authentication application locks the user account.

4.7 Roles and Privileges for Authorisation Requirement AA.3



The business requirements for T2S shall define the functional capabilities for configuring roles and

privileges for the authorisation of users to execute specific functions or view specific data. The

requirements do predicate a specific technical solution or software product (e.g. LDAP, RACF, etc.).

They define the functional scope any proposed solution or application must provide to ensure the

configurability of access rights to T2S.

4.7.1 Privileges Requirement AA.3.1



A privilege shall define a specific T2S functional capability within a process or application. For

example, within securities static data possible privileges may be add new security, delete security,

change security and display security. The definition of privileges is the prerequisite for granting and

restricting access to functionality and data for specific T2S parties and T2S system users. Any T2S

process, application and, where necessary, function shall have an associated privilege.

− A privilege shall be uniquely identifiable both internally in the application as well as to the user.

− A privilege shall have a setting (allow / deny) that specifies the type of authorisation granted.




4.7.1.1 Querying and Selecting a Privilege




It shall be possible for a user to query privileges existing in the authentication and authorization

component and to select a privilege for update or display. A search parameter window shall exist in

the online user interface, where a user can search for a privilege by inputting criteria defining the

privilege, such as privilege name. If the user does not enter any value for the given search criterion,

then the application shall display a list of all available privileges. The results list shall display all

information that a system administrator requires to identify a privilege.

4.7.1.2 Displaying and Maintaining Privileges




Privilege maintenance refers to the process of adding, changing and deleting privileges, used for

authorization in T2S.

− It shall be possible for a user to add a new privilege, using an online application. The user shall enter the details of the privilege in an input window.

− It shall be possible for a user to update an existing privilege by selecting it for update from a list of available privileges.

− It shall be possible for a user to delete an existing privilege logically by executing a delete function. The user shall not be able to delete a privilege, assigned to an active privilege class or role.

− It shall be possible to display a privilege in read-only mode.




4.7.1.3 Grouping Privileges




Any authorization and authentication solution, deployed for T2S, shall support the grouping of

privileges to facilitate the administration of roles and access rights. In the context of T2S, this

specification will refer to the grouping of a set of T2S functional capabilities within a process or

application as a privilege class. For example, the privilege class for adding a new security, changing

a security, deleting a security and displaying a security would be "Securities Static Data

Management". A one-to-many relationship is to exist between privilege class and privileges.

− A privilege class shall be uniquely identifiable both internally in the application as well as to the user.

− A privilege class shall link related privileges for the assignment to roles.

4.7.1.3.1 Querying and Selecting a Privilege Class




It shall be possible for a user to query privilege classes existing in the authentication and

authorization component and to select a privilege class for update or display. A search parameter

window shall exist in the online user interface, where a user can search for a privilege class by

inputting criteria defining the privilege class, such as privilege class name or a privilege assigned to

the privilege class. If the user does not enter any value for the given search criterion, then the

application shall display a list of all available privilege classes. The results list shall display all

information that a system administrator requires to identify a privilege class.




4.7.1.3.2 Maintaining and Displaying Privilege Classes




Privilege class maintenance refers to the process of adding, changing and deleting privilege classes,

used for authorization in T2S.

− It shall be possible for a user to add a new privilege class, using an online application. The user shall enter the details of the privilege in an input window.

− It shall be possible for a user to update an existing privilege class by selecting it for update from a list of available privileges.

− It shall be possible for a user to delete an existing privilege class logically by executing a delete function. The user shall not be able to delete a privilege class, assigned to an active role.

− It shall be possible to display a privilege class in read-only mode.

− The user must be able to add and remove privileges from a privilege class when the user enters a new privilege class or updates an existing privilege class.

4.7.2 Roles Requirement AA.3.2



A role defines the set of functions and services to which the authorization application allows or denies

the user access. A role consists of one or more privilege classes. When a system administrator

assigns a privilege class to a role, the system administrator shall specify if the privilege within the

class allows or denies access to the functionality defined by the privilege.




4.7.2.1 Entity-Specific Roles




A CSD will retain the legal relationship with its customers and remain responsible for the services

that they provide to their customers. Furthermore, CSDs, participating in T2S, must continue to

comply with legal and regulatory requirements. Therefore, the authentication and authorization

application shall allow for the configuration of entity-specific roles. It must be possible for the CSDs

to differentiate access to T2S services and functions based on their business service model and

requirements. A CSD must be able to configure the valid roles for its participants.

4.7.2.2 CSD Participant-Specific Roles




The CSD shall not maintain the end user administration for its participants. CSDs shall create and

authorise a system administrator for its participant, who shall be responsible for maintaining users and

roles for the participant of the CSD. The system administrator of the participant shall have access

only to those roles for which the CSD grants access to its participant. The authorisation and

authentication component shall allow the CSD to grant access to a different set of roles, depending on

the services provided by the CSD to its participant.

4.7.2.3 Querying and Selecting a Role




It shall be possible for a user to search for roles in the system and to select a role for update or

display. A search parameter window shall exist in the online user interface, where a user can search

for a role by specifying an attribute of a role, such as the role name or a string within the role name or

a privilege class assigned to a role. If the user does not enter any value for the given search criterion,

then the application shall display a list of all available roles. The results list shall display all

information that a system administrator requires to identify a role.




4.7.2.3.1 Maintaining and Displaying Roles




Role maintenance refers to the process of adding, changing and deleting roles, used for authorization

in T2S.

− It shall be possible for a user to add a new role, using an online application

− It shall be possible for a user to update an existing role by selecting it for update from a list of available roles.

− It shall be possible for a user to delete an existing role logically by executing a delete function. The user shall not be able to delete a role, assigned to an active user.

− It shall be possible to display a role with its assigned privilege classes and privileges by selecting it for display in read-only mode.

− The user must be able to add and remove privileges classes from a role when the user enters a new privilege class or updates an existing privilege class.

− The user shall specify whether access role allows or denies access to a function, specified by the privilege within a privilege class assigned to the role.

4.7.3 Users Requirement AA.3.3



A user in T2S shall define an individual or application that can log onto Target2-Securities with a

login name and password. For example, a user may be an individual, who has an interactive access to

T2S online functions; or an application programme, which requests services from T2S. The

authentication and authorization component shall support attributes defining named users. The user

information shall require encryption.




Table 5– User Definition


Account Name Authentication shall require a unique account name for a user. The account name shall define the code used to identify a user for authentication at login.

Name Authentication shall require named users. The name shall store the surname and first name of the user.

Contact E-Mail The contact e-mail of the user shall be an attribute of the user information.

Contact Telephone Number

The contact telephone number of the user shall be an attribute of the user information.

Password This attribute shall specify the password that the user enters at login to authenticate herself / himself.

Authentication This attribute shall define the type of authentication that the authentication component is to apply for a user at login. Simple authentication shall require the user to enter a password only. Smartcard authentication shall require the user to identify herself / himself to the system using a Smartcard in addition to entering the password.

Lockout Status The lockout status shall define whether the authentication component blocks the user from logging into T2S.

Lockout Timestamp From

A timestamp shall define the date and the time from which the authentication component shall lockout a user from the system. The timestamp shall allow the system lock a user out of the system at a future date. It allows the leavers from an organisation to be restricted from the system as per their expected leaving date while allow access until that date.

Password Change on Next Login

This attribute shall define if the user must change the password for the account on the next login. A password change on next login is usually mandatory when a new user account is created or when the password for an existing user changes.




4.7.3.1 User Assignment to T2S Party and System Entity




The user information shall specify the T2S party of a user for the purposes of data segregation. This

assignment information shall be used by the authorisation component to restrict access of the user to

the static and transactional data pertaining to the user’s T2S party and related sub-entities only. For

example, a user, assigned to system entity for the T2S operator, is eligible to access all data of the

T2S operator, CSDs and their participants and account. However, the roles can restrict the access of

this user to business data of the CSDs by denying access to business functions, which display the

business data. If the T2S party is a participant of a T2S-connected CSD, then the assignment shall

restrict access of the user to the static and transactional data of the user's financial institution. CSD-

specific roles and privileges shall restrict access to specific types of data for this user, where

necessary. The assignment of the user to a T2S party also shall establish the relationship between

user and system entity.

4.7.3.2 Querying and Selecting a User




The authorisation and authentication component shall provide the system administrator with the

functionality to search for users stored in the component. A search parameter window shall exist in

the online user interface, where a user can search for a user account by the user name, the account

name or additional criteria as active users, deleted user, users of a specific system entity /

organisational unit, etc. The results list should display the account name, the name of the user and

additional identifying attributes such as the T2S party assignment.

4.7.3.3 Displaying and Maintaining Users




User maintenance refers to the process of adding, changing and deleting users in T2S. Access to this

functionality shall be restricted to T2S system administrators and CSD system administrators.




4.7.3.3.1 Validation




The authentication component shall validate any change to user information.

• The account name must be unique and conform to minimum length requirements.

• The first and last name of the user is mandatory.

• A valid authentication type is mandatory.

• The assignment of a user to a T2S party is mandatory.

• A CSD system administrator shall have read and maintenance privileges only the user to

his/her CSD or to those of its participants.

• The password is mandatory.

• The user must have at least one role.

4.7.3.3.2 Adding of a User




It shall be possible for a system administrator to add a new user. The authentication component shall

provide an input window, where the system administrator can enter the attributes of the user.

4.7.3.3.3 Updating a User




It shall be possible for the system administrator to update an existing user by selecting it for update

from the results lists of the user search function or directly through input of the account name.




4.7.3.3.4 Deleting a User




It shall be possible for the system administrator to delete a user by executing a delete function.

4.7.3.3.5 Locking a User




It shall be possible for the system administrator to lock a user out of the system without deleting the

user. This shall be possible by setting the attribute "lockout status" to "yes". When this status is set,

the current system date is to appear in the field for the lockout timestamp. The system administrator

can opt to use the default timestamp or may set it to any date and time in the future. This feature

supports leavers' processes in that a user's access to the system can be restricted as per his/her planned

leaving date.

4.7.3.4 Displaying Users




It shall be possible to display a user with its assigned roles in read-only mode by selecting it for

display from the results list or through direct input of the account name.

4.7.3.5 Password Reset




A password reset occurs when the system administrator either inputs a password for a new user or

changes the password of an existing user. A password reset shall require the user to renew his/her

password at next login. The attribute "password change on next login" shall be set to "yes" to

indicate this.




4.7.3.6 Role Assignment




It shall be possible for the system administrator to assign roles to or to deactivate roles for a user

when adding a new user or an updating an existing user. The application shall automatically assign

the privileges associated with the role to the user.




5 Currency Data

Requirement CD.1



A currency is not a financial instrument or a security according to Directive 2004/39/EC. In the T2S

context, the notion of currency shall apply to

− the currency in which a cash leg of a DVP transaction is settled;

− the currency in which a security is denominated;

− and the currency in which a security is traded at a particular trading venue.

The static data shall store the currencies eligible for processing or for the purpose of information.

The identification of the currencies in T2S shall adhere to the 3-character ISO 4217 currency code.

Table 6 – Attribute Requirements for the Entity Currencies

Attribute Description

Currency Code This attribute shall define the unique code of the currency sequential identifier of a security in T2S.

Currency Name This attribute shall specify the currency name.

Number of Decimals

This attribute shall specify the number of decimals a currency has.

T2S Settlement Currency

This attribute shall specify if the currency is a T2S settlement currency. The attribute shall differentiate between the currencies in which T2S settles and other currency codes that are required for validation and reporting purposes.




6 Securities Reference Data Model

Requirement SR



This section defines the business requirements for securities reference data. Securities reference data

in T2S shall be restricted to, but will include all, the data required for settlement and auto-

collateralisation in central bank money. The securities reference data model defines conceptual

structures that are required in T2S for storing the attributes of securities. The description represents a

logical model and not a physical implementation. Technical fields for the audit trail and static data

change management are not included to avoid redundancy.

Figure 3 - Conceptual Securities Data Model

SecuritiesCSDLink

SecuritiesName

SecuritiesSettlementRestrictions

SecuritiesCode

Securities

SecuritiesValuation

CSD-SpecificSecuritiesAttributes




6.1 Securities Requirement SR.1



The entity “Securities” shall hold all attributes that exist only once for a financial instrument, i.e.

where a 1:n relationship between the security and a set of information pertaining to the security is not

needed.

Table 7 - Attribute Requirements for the Entity Securities

Attribute Description Instrument Identifier

This attribute shall define the unique sequential identifier of a security in T2S.

CFI This attribute shall classify the instrument according to ISO 10962. It shall be the objective of T2S to use a harmonised securities classification, but this shall not preclude the use of CSD- or market-specific classifications for processing.

Current Instrument Market Status

This attribute shall define the status of a financial instrument in its lifecycle (e.g. “when issued”, issued or matured). It shall not define a blocking status for an instrument – this shall be stored as a security restriction.

Maturity or Expiry Type

This attribute shall specify if the date, stored by the attribute Final Maturity or Expiry Date, is a maturity date (e.g. bond) or an expiry date (e.g. warrant).

Final Maturity or Expiry Date

This attribute shall store the final maturity or expiry date of an instrument, where applicable. It shall remain possible to process instructions and settlements for a security that has matured if it has not been explicitly restricted from settlement through a settlement restriction.

Settlement Type This attribute shall specify whether the financial instrument settles in units or as a nominal.

Minimum Settlement Unit or Nominal

This attribute shall define the minimum unit or nominal of the financial instrument for settlement.

Settlement Volume Multiple

This attribute shall define that the settlement quantity or nominal must be a multiple of the value in this data item. The value must be greater or equal to zero.

Issue Currency This attribute uniquely identifies the issue currency of a security in the system using the standard ISO 4217.

Auto-Collateralisation

This attribute shall specify whether the security is eligible for auto-collateralisation for central bank money.




6.2 Securities Name Requirement SR.2



This entity shall specify the valid long and short descriptions of an instrument. The name of a

security can change over time owing to mergers or acquisitions. Therefore, several names may exist

for a security although one name only can exist for a security at any given point in time. It is

necessary to store the name information of a financial instrument on a timeline basis. This storing

mechanism shall ensure that application programmes have the correct name for backdated queries and

reporting. A harmonised convention shall apply to the naming of financial instruments in T2S

according to ISO standards.

6.2.1.1 Naming Conventions and Standards

Requirement SR.2.1



The instrument short name shall fulfil the requirements of ISO 18774. ISO 18773 Part 1 and Part 2

shall be the naming convention in T2S for the instrument long name.

6.2.1.2 Attribute Requirements

Requirement SR.2.2



The following table specifies the attributes that T2S shall require for tracking the names of financial

instruments.




Table 8 - Attribute Requirements for the Entity Securities Name


Instrument Identifier

This attribute shall define the unique sequential identifier of a security in T2S. It shall link the security name to the security.

Reason for Name Change

This attribute shall specify the reason for the financial instrument name change.

Valid From This attribute shall define the date from which the instrument name is valid. Since the instrument name may change over time, it is necessary to define period in which a name was valid.

Instrument Short Name

This attribute specifies financial instrument short description (FIDS) according to ISO 18774 to identify an instrument. Example: International Business Machines, 4.75% Preferred Non-voting Extendible Redeemable Fixed Rate Interest: IBM Pfd Nvtg Extbl Red FRI 4.75%. T2S shall display this name in addition to the ISIN.

Instrument Long Name

This attribute specifies long description of the financial instrument.

6.3 Securities Code Requirement SR.3



This entity shall store the external security codes, which uniquely identify a financial instrument to

market participants. The ISO 6166 standard shall provide the convention for the unique identification

of a financial instrument: the ISIN. The entity shall link the T2S technical securities identifier to the

external code.

Table 9 - Attribute Requirements for the Entity Securities Code


Instrument Identifier

This attribute shall define unique sequential identifier of a security in T2S. It shall link the security code to the technical identifier of the instrument.

Valid From This attribute shall the date from which the instrument code is valid. This date can be before the actual issue date of an instrument for “when-issued” securities, but may not be a date in the future for a new security entered into the system. On an initial migration of instrument data into T2S, this date could be set to the date of the initial load.




Code Type This attribute shall define the code type, assigned to the unique internal instrument identifier. Although the model can support local market codes, T2S shall support only the ISIN as valid code type.

Security Mnemonic

This attribute shall specify the unique market code of a security, defined by the code type. T2S shall use this attribute to store the ISIN.

6.3.1 Interim or Internal ISIN Requirement SR.3.1



The model shall support the assignment of interim or “internal” ISINs to securities. For example,

CSDs assign an interim ISIN for a “when-issued” security in markets where the national numbering

agency only provides official ISINs for issued securities. Financial institutions commonly undertake

over-the-counter trading in securities their official placement in the market. As it is not certain if the

securities will actually issue, some National Numbering Agencies (NNA) do not assign an official

ISIN for the instrument pre-issue. However, CSDs must be able to accept settlement instructions in

such cases. Therefore, the securities code model shall support the assignment of an interim ISIN by a

CSD with the facility to replace the interim ISIN with the official ISIN as assigned by the NNA.

6.3.2 Change of Interim of Internal ISIN Requirement SR.3.2



The subsequent example provides a clarification of how ISINs shall be stored in the securities code

entity. In this scenario, a CSD has created a security in T2S and has assigned the security an interim

ISIN according to the conventions of ISO 6166, valid from 1 January 2007, since the NNA has not

yet issued the official ISIN. On 23 January, the NNA issues the official ISIN. The CSD has two

options available to change an ISIN. These options do not apply to changes of ISIN due to corporate

events, such as conversions. In such cases, transactions and positions of the old security must be

retained, and open settlement instructions and positions converted




6.3.2.1 Change of ISIN with New Valid Date

Requirement SR.3.2.1



In the example below, the CSD creates the official ISIN as of the date that the NNA issued the

identifier. This means that on searches that the interim ISIN will be valid for queries, reporting up to,

and including 22 January 2007. After this date, the official ISIN would be valid.

Identifier Valid From Code Type Code

1234 01.01.2007 ISIN XXABCDEFGHIJ1

1234 23.01.2007 ISIN DE0007100000 1XXABCDEFGHIJ represents as any internal ISIN according to ISO 6166

This model shall allow the CSD to change the ISIN without the requirement to open a new

instrument, realign transactions and transfer positions from the interim instrument to the new

instrument and closing the interim instrument. Transactions and positions would remain unchanged

with their original references.

6.3.2.2 Replacement of ISIN

Requirement SR.3.2.2



The second option available to the CSD is to change the interim ISIN to the official ISIN. No second

record would be created with a new valid from date. However, in this scenario, the interim ISIN

would no longer be available to the user for queries, etc.

Before change:


1234 01.01.2007 ISIN XXABCDEFGHIJ1 1XXABCDEFGHIJ represents as any internal ISIN according to ISO 6166

After Change:


1234 01.01.2007 ISIN DE0007100000




This replacement of the ISIN shall allow the CSD to change the ISIN without the requirement to open

a new instrument, realign transactions and transfer positions from the interim instrument to the new

instrument and closing the interim instrument. Transactions and positions would remain unchanged

with their original references.

static data business requirements - european central bank

Documents