T2S GUI Workshop Change Summary of GUI BFD V1.6 & Outstanding Issues

Transcription

1 /2011/ T2S GUI Workshop Change Summary of GUI BFD V1.6 & Outstanding Issues Frankfurt, 24th January 2011 T2S Project Team European Central Bank

2 GUI BFD V1.6 Change Summary Business Object Business Function Change description Four-eye principle management Display Data Change Approval Request Details For an approval request, user will the ability to copy the associated revision of the underlying business object and create a new approval request Securities Account Add Securities Account Delete the condition of addition of at least one T2S dedicated cash account (DCA) to a new securities account at the time of securities account creation T2S DCA Amend T2S DCA Include the feature of specification of the Party BIC authorized to use the T2S DCA 2

3 GUI BFD V1.6 Change Summary Business Object Business Function Change description T2S DCA Delete T2S DCA Modified the valid set of conditions required for deletion of T2S DCA Securities Positions Cash Balances Display Securities Account Positions Display T2S DCA Cash Balances Updated the function to include the display of restriction references in case of blocked and reserved securities positions Updated the function to include the display of restriction references in case of blocked and reserved cash balances 3

4 GUI BFD V1.6 Change Summary User interface framework and business functions included for additional Business Objects Country (section 4.29 of the GUI BFD) Service Items (section 5.4 of the GUI BFD) Billing Data (section 5.5 of the GUI BFD) Network Service (section 7.2 of the GUI BFD) Routing (section 7.3 of the GUI BFD) Inbound File (section 7.4 of the GUI BFD) Revision is only displayed for the business objects they are applicable 4

5 GUI BFD V1.6 Change Summary All business functions that are exclusively for T2S operator have been removed from the GUI BFD Add, Amend and Delete business functions have been deleted for the business objects listed below: Currency System Entity Closing Day Calendar Tolerance Amount Privileges Conditional Securities Delivery SWIFT BIC Directory 5

6 GUI BFD V1.6 Change Summary Amend business function has been deleted for the business object listed below Business Date Partial Settlement Thresholds T2S Schedule of Settlement Day 6

7 Outstanding Issue 1 Query Settlement Transaction URD version 5.0 (see user requirement T2S ) Monitoring facility T2S shall provide CSDs in T2S with a tool to help them monitor their participant securities accounts. This tool should enable each CSD in T2S to access data on its participant securities account; it should be able to view: Holdings; Transactions of pending, failed and settled status; Instructions, in whichever status they may be; Cash Liquidity (under authorisation of their participant or account beneficiary). 7

8 Outstanding Issue 1 Query Settlement Transaction For a pending settlement transaction, some of the details may be different from the underlying settlement instructions Priority Settlement Transaction Link set Settlement Amount Collateral Valuation Partial Settlement Does this query provide any business or operational benefit? In case yes, please confirm the business scenarios? Do the CSD participants also need the facility to query settlement transactions? 8

9 Outstanding Issue 1 Query Settlement Transaction What details of the settlement transaction corresponding to this matching object be displayed to either of the CSDs (Investor CSD A and CSD B) 9

10 Outstanding Issue 1 Query Settlement Transaction What details of a settlement transaction must be made available for view to the CSD business users in case of a cross CSD settlement scenario? Option 1: Only the generic details of the settlement transaction are displayed to either CSD. For other details, the CSD can query and view details of the underlying settlement instruction Option 2: CSD should be able to view either the deliver or the receive leg of the settlement transaction (corresponding to the settlement instruction they own) and the generic details of the settlement transaction Option 3: The settlement transaction in case of a cross CSD scenario is not available for display Option 4: All details of the settlement transaction are displayed to either CSD 10

11 Outstanding Issue I1 LCMM Instruction Additional Information An ISO compliant settlement instruction received via A2A mode can have 700 data fields (approximately). These data fields are not relevant for T2S and are categorised as LCMM instruction additional information. Current Information available to the users is: A GUI business function already exists for querying the settlement instruction with the information needed for settlement. Specific Additional fields reported in Status Advices and Allegement messages are also included to cope with business needs. A GUI business function already exists for querying messages and can be utilised in case all the LCMM instruction additional information is required for display to the users. Question: Is the structure and level of the information enough to satisfy the business needs? 11

12 Outstanding Issue I1 LCMM Instruction Additional Information Question : Should all the LCMM instruction additional information data fields be available to the users for addition of a settlement instruction? In case the answer to the above question is YES, please elaborate the business needs. Also, an impact analysis has to be done from the functional and technical perspectives. In case the answer to the above question is NO and only some data fields are required, then. Question: Could you please specify the data fields required in your market? 12

13 Settling without borders 13 13