Common use of Monthly Terminal Return declarations Clause in Contracts

Monthly Terminal Return declarations. 6.3.1 The Redistributor is liable for all Devices capable of accessing the Data, even in a datafeed environment. It is therefore recommended that permissioning software is implemented by datafeed clients to allow a Redistributor to manage their liability. 6.3.2 Redistributors must collect monthly honesty statements, sometimes referred to as honesty declarations, from all clients to which they supply London Stock Exchange or Borsa Italiana Data via a datafeed. The Redistributor must adhere to the following when using honesty declarations: In the instance that an End Customer is taking one separate Level 2 access and one separate Level 1 access, these are billed as two accesses. These are not counted as one unified access. It is a requirement of the declaration that the Redistributor understands that they interpret the information given by their End Customers in this way. All datafeed activations must be pre approved by the Exchange and all Devices receiving Data from the datafeeds must be clearly reported as such. 6.3.3 A declaration for an installation which is authorised by the Redistributor for Data, but where the End Customer has left the declaration blank does not mean that the End Customer is liable for only one Data Charge. A blank honesty declaration does not provide the required documentation to justify paying fewer Data Charges, and in this situation Data Charges will be expected for all devices capable of accessing Data. 6.3.4 Honesty declarations must be obtained from all secondary sites to which a primary site disseminates Data.

Monthly Terminal Return declarations. 6.3.1 The Redistributor is liable for all Devices capable of accessing the Data, even in a datafeed environment. It is therefore recommended that permissioning software is implemented by datafeed clients to allow a Redistributor to manage their liability. 6.3.2 Redistributors must collect monthly honesty statements, sometimes referred to as honesty declarationsDatafeed access declarations (DADs), from all clients to which they supply London Stock Exchange or Borsa Italiana Data via a datafeed. The Redistributor must adhere to the following when using honesty declarationsDADs: In the instance that an End Customer is taking one separate Level 2 access and one separate Level 1 access, these are billed as two accesses. These are not counted as one unified access. It is a requirement of the declaration that the Redistributor understands that they interpret the information given by their End Customers in this way. All datafeed activations must be pre approved by the Exchange and all Devices receiving Data from the datafeeds must be clearly reported as such. 6.3.3 A declaration for an installation which is authorised by the Redistributor for Data, but where the End Customer has left the declaration blank does not mean that the End Customer is liable for only one Data Charge. A blank honesty declaration DAD does not provide the required documentation to justify paying fewer Data Charges, and in this situation Data Charges will be expected for all devices capable of accessing Data. 6.3.4 Honesty declarations DADs must be obtained from all secondary sites to which a primary site disseminates Data.

Monthly Terminal Return declarations. 6.3.1 The Redistributor is liable for all Devices capable of accessing the Data, even in a datafeed environment. It is therefore recommended that permissioning software is implemented by datafeed clients to allow a Redistributor to manage their liability. 6.3.2 Redistributors must collect monthly honesty statements, sometimes referred to as honesty declarations, from all clients to which they supply London Stock Exchange or Borsa Italiana Data via a datafeed. The Redistributor must adhere to the following when using honesty declarations: In the instance that an End Customer is taking one separate Level 2 access and one separate Level 1 access, these are billed as two accesses. These are not counted as one unified access. It is a requirement of the declaration that the Redistributor understands that they interpret the information given by their End Customers in this way. All datafeed activations must be pre approved by the Exchange and all Devices receiving Data from the datafeeds must be clearly reported as such. 6.3.3 A declaration for an installation which is authorised by the Redistributor for Data, but where the End Customer has left the declaration blank does not mean that the End Customer is liable for only one Data Charge. A blank honesty declaration does not provide the required documentation to justify paying fewer Data Charges, and in this situation Data Charges will be expected for all devices capable of accessing Data. 6.3.4 Honesty declarations must be obtained from all secondary sites to which a primary site disseminates Data.

Monthly Terminal Return declarations. 6.3.1 The Redistributor is liable for all Devices capable of accessing the Data, even in a datafeed environment. It is therefore recommended that permissioning software is implemented by datafeed clients to allow a Redistributor to manage their liability. 6.3.2 Redistributors must collect monthly honesty statements, sometimes referred to as honesty declarations, from all clients to which they supply London Stock Exchange or Borsa Italiana Data via a datafeed. The Redistributor must adhere to the following when using honesty declarations: In the instance that an End Customer is taking one separate Level 2 access and one separate Level 1 access, these are billed as two accesses. These are not counted as one unified access. It is a requirement of the declaration that the Redistributor understands that they interpret the information given by their End Customers in this way. All datafeed activations must be pre approved by the Exchange BIT and all Devices receiving Data from the datafeeds must be clearly reported as such. 6.3.3 A declaration for an installation which is authorised by the Redistributor for Data, but where the End Customer has left the declaration blank does not mean that the End Customer is liable for only one Data Charge. A blank honesty declaration does not provide the required documentation to justify paying fewer Data Charges, and in this situation Data Charges will be expected for all devices capable of accessing Data. 6.3.4 Honesty declarations must be obtained from all secondary sites to which a primary site disseminates Data.