Common use of Completeness of delivery Clause in Contracts

Completeness of delivery. All deliveries are a full snapshot of the source, deltas are not requested. The following should be noted with respect to monthly and quarterly deliveries, as noted in the AnaCredit regulation. • Reporting agents must submit the quarterly data for the most recent quarter together with each monthly delivery, i.e. not only with end-of-quarter deliveries. Quarter-specific data must be centralised in the "accounting_data" entity, while other data (reference data, default and risk data and "financial_data") must be updated on a monthly basis. As noted in paragraph 1.4, only qualifying instruments are to be reported for the quarterly data. Example of the 2019 submission schedule for monthly reporting agents: Reporting reference date Reference data, financial data, counterparty, default data10 Accounting data & risk data11 31/12/2018 Balance as at 31/12/2018 Balance as at 31/12/2018 (Q4 2018) 31/01/2019 Balance as at 31/01/2019 Balance as at 31/12/2018 (Q4 2018) 28/02/2019 Balance as at 28/02/2019 Balance as at 31/12/2018 (Q4 2018) 31/03/2019 Balance as at 31/03/2019 Balance as at 31/03/2019 (Q1 2019) 30/04/2019 Balance as at 30/04/2019 Balance as at 31/03/2019 (Q1 2019) … … .. Comparing accounting data attributes to other data attributes, where the accounting data attribute values are from the most recent quarter end and the other data attributes are from a non-quarter end reporting reference date, can lead to inconsistencies. These inconsistencies in themselves will not lead to a blocking validation and hence not to a non-acceptance of the data delivery. Example: The accounting data is from Q4, and the other data is from January. There can exist an inconsistency between the data for one single instrument. This could happen when, for instance, the instrument is securitised in January. In this case, the balance sheet status in the accounting data can become inconsistent with the instrument data and financial data from January, where the instrument is securitised. Ergo, cross checks between those data sets will have to be looked at very diligently. Another type of inconsistency can occur when the instrument is available in the accounting data at the end of Q4 and the instrument itself is not qualifying for reporting in February Q1. This would lead to an accounting data record being present, without a corresponding instrument record, which is a referential integrity invalidation. This will lead to a blocking validation and hence will lead to a non-acceptance of the data delivery. To counter this, only those instruments are requested in the accounting data that are qualifying instruments. This ensures that they are present both in the instrument entity type and in the accounting entity type. The reporting of accounting data for qualifying instruments only, will also tackle the situation where an instrument is created and ended within the same reporting period. The corresponding 10 Debtor default data, protection provider default data 11 Debtor risk data and protection provider risk data accounting data will be reported at reporting period end, together with the instrument data. In following months, the instrument will not be reported in the accounting data, nor in the instrument.

Completeness of delivery. All deliveries are a full snapshot of the source, deltas are not requested. The following should be noted with respect to monthly and quarterly deliveries, as noted in the AnaCredit regulation. •  Reporting agents with a quarterly reporting obligation must always submit the quarterly and monthly data of the relevant quarter. For these reporting agents, there is no difference between monthly data and quarterly data  Reporting agents with a monthly reporting obligation must submit the quarterly data for the most recent quarter together with each monthly delivery, i.e. not only with end-of-of- quarter deliveries. Quarter-specific data must be centralised in the "accounting_data" entity, while other data (reference data, default and risk data and "financial_data") must be updated submitted on a monthly basis. As noted in paragraph 1.4, only qualifying instruments are to be reported for the quarterly data. Example of the 2019 submission schedule for monthly reporting agents: Reporting reference date Reference data, financial data, counterparty, ,default data10 Accounting data & risk data11 31/12/2018 Balance as at 31/12/2018 Balance as at 31/12/2018 (Q4 2018) 31/01/2019 Balance as at 31/01/2019 Balance as at 31/12/2018 (Q4 2018) 28/02/2019 Balance as at 28/02/2019 Balance as at 31/12/2018 (Q4 2018) 31/03/2019 Balance as at 31/03/2019 Balance as at 31/03/2019 (Q1 2019) 30/04/2019 Balance as at 30/04/2019 Balance as at 31/03/2019 (Q1 2019) … … .. Comparing accounting data attributes to other data attributes, where the accounting data attribute values are from the most recent quarter end and the other data attributes are from a non-quarter end reporting reference date, can lead to inconsistencies. These inconsistencies in themselves will not lead to a blocking validation and hence not to a non-acceptance of the data delivery. Example: The accounting data is from Q4, and the other data is from January. There can exist an inconsistency between the data for one single instrument. This could happen when, for instance, the instrument is securitised in January. In this case, the balance sheet status in the accounting data can become inconsistent with the instrument data and financial data from January, where the instrument is securitised. Ergo, cross checks between those data sets will have to be looked at very diligentlydilligently. Another type of inconsistency can occur when the instrument is available in the accounting data at the end of Q4 and the instrument itself is not qualifying for reporting in February Q1. This would lead to an accounting data record being present, without a corresponding instrument record, which is a referential integrity invalidation. This will lead to a blocking validation and hence will lead to a non-acceptance of the data delivery. To counter this, only those instruments are 10 Debtor default data, protection provider default data 11 Debtor risk data and protection provider risk data requested in the accounting data data, that are qualifying instruments. This ensures that they are present both in the instrument entity type and in the accounting entity type. The reporting of accounting data for qualifying instruments only, will also tackle the situation where an instrument is created and ended within the same reporting period. The corresponding 10 Debtor default data, protection provider default data 11 Debtor risk data and protection provider risk data accounting data will be reported at reporting period end, together with the instrument data. In following months, the instrument will not be reported in the accounting data, nor in the instrument.

Completeness of delivery. All deliveries are a full snapshot of the source, deltas are not requested. The following should be noted with respect to monthly and quarterly deliveries, as noted in the AnaCredit regulation. •  Reporting agents with a quarterly reporting obligation must always submit the quarterly and monthly data of the relevant quarter. For these reporting agents, there is no difference between monthly data and quarterly data  Reporting agents with a monthly reporting obligation must submit the quarterly data for the most recent quarter together with each monthly delivery, i.e. not only with end-of-of- quarter deliveries. Quarter-specific data must be centralised in the "accounting_data" entity, while other data (reference data, default and risk data and "financial_data") must be updated submitted on a monthly basis. As noted in paragraph 1.4, only qualifying instruments are to be reported for the quarterly data. Example of the 2019 submission schedule for monthly reporting agents: Reporting reference date Reference data, financial data, counterparty, default data10 Accounting data & risk date counterparty,default data10 data11 31/12/2018 Balance as at 31/12/2018 Balance as at 31/12/2018 (Q4 2018) 31/01/2019 Balance as at 31/01/2019 Balance as at 31/12/2018 (Q4 2018) 28/02/2019 Balance as at 28/02/2019 Balance as at 31/12/2018 (Q4 2018) 31/03/2019 Balance as at 31/03/2019 Balance as at 31/03/2019 (Q1 2019) 30/04/2019 Balance as at 30/04/2019 Balance as at 31/03/2019 (Q1 2019) … … .. Comparing accounting data attributes to other data attributes, where the accounting data attribute values are from the most recent quarter end and the other data attributes are from a non-quarter end reporting reference date, can lead to inconsistencies. These inconsistencies in themselves will not lead to a blocking validation and hence not to a non-acceptance of the data delivery. Example: The accounting data is from Q4, and the other data is from January. There can exist an inconsistency between the data for one single instrument. This could happen when, for instance, the instrument is securitised in January. In this case, the balance sheet status in the accounting data can become inconsistent with the instrument data and financial data from January, where the instrument is securitised. Ergo, cross checks between those data sets will have to be looked at very diligentlydilligently. Another type of inconsistency can occur when the instrument is available in the accounting data at the end of Q4 and the instrument itself is not qualifying for reporting in February Q1. This would lead to an accounting data record being present, without a corresponding instrument record, which is a referential integrity invalidation. This will lead to a blocking validation and hence will lead to a non-acceptance of the data delivery. To counter this, only those instruments are 10 Debtor default data, protection provider default data 11 Debtor risk data and protection provider risk data requested in the accounting data data, that are qualifying instruments. This ensures that they are present both in the instrument entity type and in the accounting entity type. The reporting of accounting data for qualifying instruments only, will also tackle the situation where an instrument is created and ended within the same reporting period. The corresponding 10 Debtor default data, protection provider default data 11 Debtor risk data and protection provider risk data accounting data will be reported at reporting period end, together with the instrument data. In following months, the instrument will not be reported in the accounting data, nor in the instrument.

Completeness of delivery. All deliveries are a full snapshot of the source, deltas are not requested. The following should be noted with respect to monthly and quarterly deliveries, as noted in the AnaCredit regulation. •  Reporting agents with a quarterly reporting obligation must always submit the quarterly and monthly data of the relevant quarter. For these reporting agents, there is no difference between monthly data and quarterly data  Reporting agents with a monthly reporting obligation must submit the quarterly data for the most recent quarter together with each monthly delivery, i.e. not only with end-of-of- quarter deliveries. Quarter-specific data must be centralised in the "accounting_data" entity, while other data (reference data, default and risk data and "financial_data") must be updated submitted on a monthly basis. As noted in paragraph 1.4, only qualifying instruments are to be reported for the quarterly data. Example of the 2019 submission schedule for monthly reporting agents: Reporting reference date Reference data, financial data, counterparty, default data10 Accounting data & risk data11 31/12/2018 Balance as at 31/12/2018 Balance as at 31/12/2018 (Q4 2018) 31/01/2019 Balance as at 31/01/2019 Balance as at 31/12/2018 (Q4 2018) 28/02/2019 Balance as at 28/02/2019 Balance as at 31/12/2018 (Q4 2018) 31/03/2019 Balance as at 31/03/2019 Balance as at 31/03/2019 (Q1 2019) 30/04/2019 Balance as at 30/04/2019 Balance as at 31/03/2019 (Q1 2019) … … .. Comparing accounting data attributes to other data attributes, where the accounting data attribute values are from the most recent quarter end and the other data attributes are from a non-quarter end reporting reference date, can lead to inconsistencies. These inconsistencies in themselves will not lead to a blocking validation and hence not to a non-acceptance of the data delivery. Example: The accounting data is from Q4, and the other data is from January. There can exist an inconsistency between the data for one single instrument. This could happen when, for instance, the instrument is securitised in January. In this case, the balance sheet status in the accounting data can become inconsistent with the instrument data and financial data from January, where the instrument is securitised. Ergo, cross checks between those data sets will have to be looked at very diligently. Another type of inconsistency can occur when the instrument is available in the accounting data at the end of Q4 and the instrument itself is not qualifying for reporting in February Q1. This would lead to an accounting data record being present, without a corresponding instrument record, which is a referential integrity invalidation. This will lead to a blocking validation and hence will lead to a non-acceptance of the data delivery. To counter this, only those instruments are 10 Debtor default data, protection provider default data 11 Debtor risk data and protection provider risk data requested in the accounting data that are qualifying instruments. This ensures that they are present both in the instrument entity type and in the accounting entity type. The reporting of accounting data for qualifying instruments only, will also tackle the situation where an instrument is created and ended within the same reporting period. The corresponding 10 Debtor default data, protection provider default data 11 Debtor risk data and protection provider risk data accounting data will be reported at reporting period end, together with the instrument data. In following months, the instrument will not be reported in the accounting data, nor in the instrument.