Intra Csd Settlement Bc Final

8/3/2019 Intra Csd Settlement Bc Final

http://slidepdf.com/reader/full/intra-csd-settlement-bc-final 1/30

Business Cases

Intra-CSD Settlement Scenario

4°GUI Workshop Frankfurt – March 2nd, 2011



Business case:Business case: configuration by a CSD of all the necessary Static Data forconfiguration by a CSD of all the necessary Static Data foran Intraan Intra--CSD settlement.CSD settlement. IntraIntra--CSD Settlement is defined as the settlementCSD Settlement is defined as the settlement

between participants that belong to the same CSD.between participants that belong to the same CSD.

••the Issuer CSDthe Issuer CSD CSDAITMMXXXCSDAITMMXXX and instructing Parties are already presentand instructing Parties are already present

••the Issuer CSD creates a new Security (ISINthe Issuer CSD creates a new Security (ISIN ABCDEFGHIJKL)ABCDEFGHIJKL)

••the Issuer CSD creates new Security CSD Links for the Securitythe Issuer CSD creates new Security CSD Links for the Security

Description of the main assumptions of the Business Case



Business case ReferencesBusiness case References::

••URD T2S.16.380, T2S.16.390, T2S.16.400, T2S.16.410, T2S.16.420,URD T2S.16.380, T2S.16.390, T2S.16.400, T2S.16.410, T2S.16.420, T2S.16.460, T2S.16.480T2S.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.3UDFS 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.1. Static data SitemapStatic data Sitemap

2.2. DataData OverviewOverview

3.3. CreationCreation ofof a newa new SecuritySecurity

4.4. ConfigurationConfiguration ofof SecuritySecurity CSD Links forCSD Links for thethe SecuritySecurity




2.2. DataData overviewoverview





Sitemap – Static Data- Securities -

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









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.1.

Static data SitemapStatic data Sitemap






Creation of Security

• Business Case:

– CSD I creates security ABCDEFGHIJKL

– Two Business Rules:

1. Invalid ISIN

2. 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 insertedIn both cases the system shows an error.



CreationCreation ofof a newa new SecuritySecurity

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».




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)




Security Code Valid From Date

Security ISIN 12x

Security CFI 6x

Security Issue Date Date

Security Final Maturity or Expiry Date Date

Security Currency Code 3x

Security Country Code 2x

Security Name Valid From Date

Security Name Short Name 35x

Security Name Long Name 350x

Security Settlement Type UNIT/NOMI

Security Minimum Settlement Unit 8,5x

Security Settlement unit multiple 8,5x

Deviating Securities Settlement Unit --> 1--10

Deviating Settlement Unit 8,5x

--|

Securities Restriction --> 1--10

Security Restriction – Restriction Type 35x

Security Restriction – Valid From DatetimeSecurity Restriction – Valid to Datetime

--|

Market-Specific Securities Attribute Value -->1--10

Market Specific Security Attribute Name 35x

Market Specific Security Attribute Value 35x

--|

“SECURITY” DATA




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.




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




...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.




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




The user inserts data and then pushes the “Submit” button




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




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











Configuration ofConfiguration of

Security CSD Links for the SecuritySecurity 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





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





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

Documents

Intra Csd Settlement Bc Final