Business Cases

Intra-CSD Settlement Scenario

4 GUI Workshop

Frankfurt March 2nd, 2011

an Intra-CSD settlement. Intra-CSD Settlement is defined as the settlement between participants that belong to the same CSD.

Business case: configuration by a CSD of all the necessary Static Data for

the Issuer CSD CSDAITMMXXX and instructing Parties are already present the Issuer CSD creates a new Security (ISIN ABCDEFGHIJKL) the Issuer CSD creates new Security CSD Links for the Security

Description of the main assumptions of the Business Case

Business case References:

URD T2S.16.380, T2S.16.390, T2S.16.400, T2S.16.410, T2S.16.420, T2S.16.460, T2S.16.480

UDFS 1.2, 1.2.2, 1.2.2.1, 1.2.2.1, 1.2.2.2, 1.2.2.3, 1.6.1.10.3

References of the Business Case (URD and UDFS references)

1.

Static data Sitemap

2.

Data Overview

3.

Creation of a new Security

4.

Configuration of Security CSD Links for the Security

1.

Static data Sitemap

2.

Data overview

3.

Creation of a new Security

4.

Configuration of Security CSD Links for the Security

Sitemap Static Data

- Securities -

Securities sitemap and focus on screens visited for the business case We have already seen securities account and party sitemaps in previous GUI WS

1.

Static data Sitemap

2.

Data Overview

3.

Creation of a new Security

4.

Configuration of Security CSD Links for the Security

Data Overview

Transaction
Participant J delivers security ABCDEFGHIJKL to Participant I within CSD I

Parties
CSD I Issuer CSD Participant I Delivering Party Participant J Receiving Party

Securities Accounts
SAC01 CSD participant account of Part. I open in CSD I SAC02 CSD participant account of Part. J open in CSD I

DATA OVERVIEW. The CSD I has created the participants and the Securities Account whose owners are Part. I and Part. J.

Data Overview

Security CSD Links:

CSD I as Issuer CSD CSD I as Investor CSD

Data Overview

1.

Static data Sitemap

2.

Data Overview

3.

Creation of a new Security

4.

Configuration of Security CSD Links for the Security

Creation of Security

Business Case:
CSD I creates security ABCDEFGHIJKL Two Business Rules:
1. 2.

Invalid ISIN Existing ISIN

Business Case: Creation of Security. Two related errors/business cases are shown: An invalid ISIN (in this case, a null value) in inserted An already existing ISIN is inserted In both cases the system shows an error.

Creation of a new Security

Every participant knows how to perform a search, we jump directly to the creation of a security (new button). Note that every not usable button is greyed out.

Creation of a new Security

The system shows the security new screen. Note that it is not possible to insert a starting date for isin and name (system will insert the current date)

Creation of a new Security

Security Code Valid From Security ISIN Security CFI Security Issue Date Security Final Maturity or Expiry Date Security Currency Code Security Country Code Security Name Valid From Security Name Short Name Security Name Long Name Security Settlement Type Security Minimum Settlement Unit Security Settlement unit multiple

Date 12x 6x Date Date 3x 2x Date 35x 350x UNIT/NOMI 8,5x 8,5x
SECURITY DATA

Deviating Securities Settlement Unit --> Deviating Settlement Unit --| Securities Restriction --> Security Restriction Restriction Type Security Restriction Valid From Security Restriction Valid to --|

1--10 8,5x

1--10 35x Datetime Datetime

Market-Specific Securities Attribute Value --> 1--10 Market Specific Security Attribute Name 35x Market Specific Security Attribute Value 35x --|

Creation of a new Security

There are two kinds of error: errors related to the screen fields (front-end errors) and errors related to business data, to be checked in the back-end. Example of front-end error: the user does not insert the mandatory field isin: the system shows the related error.

Creation of a new Security

In case of error, the system shows the related message on the top of the screen...

Creation of a new Security

...And highlights the field that caused the error. Note that if more than one error occurs, the system shows a list of errors and more than one field is highlighted.

Creation of a new Security

Another example of error (back-end error): Errors are shown in the same way

Creation of a new Security

The user inserts data and then pushes the Submit button

Creation of a new Security

Data input and confirmation. During the confirmation user cannot change data or push buttons

Creation of a new Security

After a search now the new security is in the list. It is the first because the default order is by name, but users can sort data by clicking on table header cells

1.

Static data Sitemap

2.

Data Overview

3.

Creation of a new Security

4.

Configuration of Security CSD Links for the Security

Configuration of Security CSD Links for the Security

To insert a CSD Link, search for the relevant Security, Select item in the list and go into details (Details button)

Configuration of Security CSD Links for the Security

In the details, please note valid from date for Security Name is inserted automatically by the system during creation. Click CSD Links button

Configuration of Security CSD Links for the Security

The list of CSD links related to the new security is shown. New CSD links must be inserted

Configuration of Security CSD Links for the Security

The user inserts two csd links, an issuer (itself) that is also responsible of mainteinance. Then the csd defines itself as investor

Intra CSD Settlement

Original Instructions received by T2S from the relevant Parties

No Realignment Instructions

Original Instructions (already matched). The Settlement does not require any realignment instructions since the settlement occurred within a single CSD

THANK YOU