- Introduction
-
FAQs on transaction reporting on supply and derivative contracts
-
II.1. TRUM
-
II.1.1 General questions
- Question 1.1.1
- Question 1.1.2
- Question 1.1.3
- Question 1.1.4
- Question 1.1.5
- Question 1.1.6
- Question 1.1.7 [DELETED]
- Question 1.1.8
- Question 1.1.9
- Question 1.1.10
- Question 1.1.11
- Question 1.1.12
- Question 1.1.13
- Question 1.1.14
- Question 1.1.15
- Question 1.1.16
- Question 1.1.17
- Question 1.1.18
- Question 1.1.19
- Question 1.1.20
- Question 1.1.21
- Question 1.1.22
- Question 1.1.23
- Question 1.1.24
- Question 1.1.25
- Question 1.1.26
- Question 1.1.27 [ARCHIVED]
- Question 1.1.28
- Question 1.1.29
- Question 1.1.30
- Question 1.1.31
- Question 1.1.32
- Question 1.1.33
- Question 1.1.34
- Question 1.1.35
- Question 1.1.36
-
II.1.1 General questions
-
II.2. Questions related to standard contracts
-
II.2.1 TRUM – Data Fields () and XSD schema Table
- Question 2.1.1 Data Field (1) and (8)
- Question 2.1.2 Data Field (2)
- Question 2.1.3 Data Field (3)
- Question 2.1.4 Data Field (3)
- Question 2.1.5 Data Field (4)
- Question 2.1.6 Data Field (4)
- Question 2.1.7 Data Field (8) [DELETED]
- Question 2.1.8 Data Field (8)
- Question 2.1.9 Data Field (8)
- Question 2.1.10 Data Field (9)
- Question 2.1.11 Data Field (11)
- Question 2.1.12 Data Field (15)
- Question 2.1.13 Data Field (15)
- Question 2.1.14 Data Field (21)
- Question 2.1.15 Data Field (21)
- Question 2.1.16 Data Field (21) [ARCHIVED]
- Question 2.1.17 Data Field (21)
- Question 2.1.18 Data field (21) and (22)
- Question 2.1.19 Data Field (23)
- Question 2.1.20 Data Field (25)
- Question 2.1.21 Data Field (25)
- Question 2.1.22 Data Field (27)
- Question 2.1.23 Data Field (27)
- Question 2.1.24 Data Field (28)
- Question 2.1.25 Data Field (28)
- Question 2.1.26 Data Field (30)
- Question 2.1.27 Data Field (30)
- Question 2.1.28 Data Field (30)
- Question 2.1.29 Data Field (30)
- Question 2.1.30 Data Field (31) [ARCHIVED]
- Question 2.1.31 Data Field (31)
- Question 2.1.32 Data Field (31)
- Question 2.1.33 Data Field (35) and (38)
- Question 2.1.34 Data Field (35), (38), (40), (41) and (42)
- Question 2.1.35 Data Field (39)
- Question 2.1.36 Data Field (40)
- Question 2.1.37 Data Field (43)
- Question 2.1.38 Data Fields (48 to 57)
- Question 2.1.39 Data Field (48)
- Question 2.1.40 Data Field (48)
- Question 2.1.41 Data Field (48)
- Question 2.1.42 Data Field (48)
- Question 2.1.43 Data Field (48)
- Question 2.1.44 Data Fields (49) and (50)
- Question 2.1.45 Data Fields (49) and (50)
- Question 2.1.46 Data Field (51) [DELETED]
- Question 2.1.47 Data Field (52)
- Question 2.1.48 Data Field (53)
- Question 2.1.49 Data Field (53)
- Question 2.1.50 Data Field (54)
- Question 2.1.51 Extra field in the schema
- Question 2.1.52 Extra field in the schema
- Question 2.1.53 Extra Field in the schema
- Question 2.1.54 Local flexibility products
- II.2.2 Trading examples – Annex II
- II.2.3 Derivatives
- II.2.4 Lifecycle events
- II.2.5 Back loading of standard contracts [ARCHIVED]
- II.2.6 Questions related to bilateral trades
- II.2.7 Questions related to ACER’s No-action Letter
-
II.2.1 TRUM – Data Fields () and XSD schema Table
-
II.3. Questions related to non-standard contracts
-
II.3.1 General questions: non-standard contracts
- Question 3.1.1
- Question 3.1.2 [DELETED]
- Question 3.1.3
- Question 3.1.4
- Question 3.1.5
- Question 3.1.6
- Question 3.1.7
- Question 3.1.8
- Question 3.1.9
- Question 3.1.10
- Question 3.1.11
- Question 3.1.12
- Question 3.1.13
- Question 3.1.14
- Question 3.1.15
- Question 3.1.16
- Question 3.1.17
- Question 3.1.18
- Question 3.1.19
- Question 3.1.20
- Question 3.1.21 [DELETED]
- Question 3.1.22 [DELETED]
- Question 3.1.23 [DELETED]
- Question 3.1.24 [DELETED]
- Question 3.1.25 [DELETED]
- Question 3.1.26 [DELETED]
- Question 3.1.27
- Question 3.1.28
- Question 3.1.29
- Question 3.1.30
- Question 3.1.31
- Question 3.1.32
- Question 3.1.33
- Question 3.1.34
- Question 3.1.35
- Question 3.1.36
- Question 3.1.37
- Question 3.1.38
- Question 3.1.39
- Question 3.1.40
- Question 3.1.41
- Question 3.1.42
- Question 3.1.43 [DELETED]
- Question 3.1.44
- Question 3.1.45
- Question 3.1.46
- Question 3.1.47
- Question 3.1.48 [DELETED]
- Question 3.1.49 [DELETED]
- Question 3.1.50
- Question 3.1.51
- Question 3.1.52
- Question 3.1.53
-
II.3.2 TRUM – Data Fields () and XSD schema for Table 2
- Question 3.2.1 Data Field (3)
- Question 3.2.2 Data field (11) [ARCHIVED]
- Question 3.2.3 Data field (12)
- Question 3.2.4 Data field (16) and (18)
- Question 3.2.5 Data field (19)
- Question 3.2.6 Data field (21), (22) and (23)
- Question 3.2.7 Data field (21)
- Question 3.2.8 Data field (24)
- Question 3.2.9 Data field (24) to (31)
- Question 3.2.10 Data field (24) to (30)
- Question 3.2.11 [DELETED]
- Question 3.2.12 Data field (28)
- Question 3.2.13 Data field (28) and (29)
- Question 3.2.14 Data field (30)
- Question 3.2.15 Data field (42)
- II.3.3 Trading examples – Annex II
- II.3.4 Executions under non-standard contracts
- II.3.5 Lifecycle events
- II.3.6 Back loading of non-standard contracts [ARCHIVED]
-
II.3.1 General questions: non-standard contracts
-
II.1. TRUM
-
FAQs on transaction reporting of transportation contracts
- III.4.1 Electricity
-
III.4.2 Gas
- Question 4.2.1
- Question 4.2.2
- Question 4.2.3
- Question 4.2.4
- Question 4.2.5
- Question 4.2.6
- Question 4.2.7 Reporting of capacity conversion and capacity upgrade
- Question 4.2.8
- Question 4.2.9
- Question 4.2.10
- Question 4.2.11
- Question 4.2.12
- Question 4.2.13
- Question 4.2.14
- Question 4.2.15
- Question 4.2.16 [DELETED]
- Question 4.2.17
- Question 4.2.18 [DELETED]
- Question 4.2.19
- Question 4.2.20
- Question 4.2.21
- Question 4.2.22
- Question 4.2.23
- Question 4.2.24
- Archive: FAQs on backloading
Question 3.2.2
Question 2.1.26 states that in case of backloading of standard contracts, in assigning a UTI this doesn’t have to match with the one reported by the other market participant.
Under the obligation to report non-standard contracts, there is the same issue with regards to the Contract ID for contracts that are subject to backloading.
Party A and Party B have to report a non-standard contract that is subject to the back loading requirement. As this contract was in existence prior to the entry into force of the obligation to report, a common Contract ID will not have been agreed and allocated to the contract. Does the same logic for the backloading of UTI in standard contracts apply?
Answer
Non-standard contracts that are subject to the back loading requirement under REMIT should be reported with a Contract ID, but there would be no expectation that the Contract ID adopted will match between the two market participants for back loaded contracts.
The Contract ID is required because otherwise the market participant will not be able to link the executions to the contract. The Contract ID can be anything the market participant would like to submit as long as it is unique to the market participant and does not need to match the Contract ID of the other market participant.