Market participants are required to backload their trades. For the backloading, is it enough to report a contract once or should we do monthly executions on this specific contract for the duration of the contract in the past also?
As an example: we report a bilateral contract, which runs from 01.01.2010 until 31.12.2020. For the Backloading, would it be sufficient to report the contract once with the non standard contract Template and do the monthly execution from April 2016 on? Or should we report the monthly executions with the std contract Template for the time in the past (01.01.2010-01.04.2016), which in this example would mean 75 execution reports.
Please refer to FAQ. 3.6.2:
Any outstanding contract has to be reported as back loaded. Execution under the framework of non-standard contracts concluded before the 7 April 2016 do not fall under the scope of back-loading.
Executions under the framework of non-standard contracts should be reported with Table 1 and linked to non-standard contracts that have already been reported to the Agency with Table 2. See examples in Annex II to the TRUM.
Since there is a three-month period time for the back loading of outstanding non-standard contracts, the reporting of transaction executed under the framework of non-standard contracts are reportable if they take place after the reporting of the back loaded report.
Last update: 26/04/2017
Related documents: II.3.6 of the Frequently Asked Questions
Question relates to the reporting of executions under back loaded nonstandard contracts.
According to II.3.2 of FAQs, an execution completed before 7 April 2016 does not need to be reported. Executions with delivery period extending beyond 7 April 2016 need to be reported. However, as the deadline for backloading of nonstandard contracts is 7 July 2016, the questions are:
- Does an execution with a delivery period ending before the nonstandard contract is back loaded need to be reported?
- If yes, what is the deadline for reporting such an execution? Should it be reported within 30 days of the end of the delivery period, even if this is a date earlier than 7 July 2016 (in which case the nonstandard contract should be back loaded not later than the date of reporting of the execution)? Or should such an execution be reported only when the nonstandard contract is back loaded, even if this falls later than 30 days from the end of the delivery period of the execution.
Answer to the second question of II.3.6 of FAQs (which probably should be properly marked as question 3.6.2, instead of 3.6.1) suggests that only executions with delivery periods ending after a nonstandard contract is actually back loaded are reportable. This would mean that executions with delivery period ending after 7 April 2016 but before the nonstandard contract is actually back loaded (which can happen by 7 July 2016) would not be reportable at all. We are not clear if this was the actual intention of the Agency.
As a follow up question: when new executions of a back loaded contract are reported after the backloading is done, do the data reported by each of the counterparties regarding such executions need to match? Many Xxxx market participants are reporting to me that they have significant difficulties in agreeing with some counterparties how the historical contracts are to be reported and it is quite likely that several back loaded contracts will be reported by each of the respective counterparties differently (with non-reconciled data). I would greatly appreciate your input on this. My understanding is that in case of back loaded contracts both data reported by the two counterparties under table 2 and data reported under table 1 for executions of back loaded contracts are not required to match.
Executions under the framework of non-standard contracts with a delivery period ending before the nonstandard contract is back loaded do not need to be reported.
Criteria for back loading are more relaxed. Please refer to TRUM Annex II, e.g. Example 4.05 to see the differences in the back loaded contract reported by two counterparties.
Last update: 10/07/2017