ACER REMIT FAQ for Standard & Non-Standard Contracts
Key terms and practical questions about reporting of standard and non-standard contracts under ACER REMIT.
Regulatory update (effective 29 April 2026)
The EU has adopted a recast REMIT data reporting framework (Commission Implementing Regulation (EU) 2026/256). From 29 April 2026, ACER clarified updated definitions and reporting timelines for standard vs non-standard contracts.
Most provisions apply with a transition period, but reporting parties should already align their processes with the new timelines.
Key timeline changes:
Standard (on OMP): T+2 business days
Non-standard (OTC): T+10 business days
This applies also to lifecycle events.
ACER Open letter on Regulation (EU) 2026/256 (09 April 2026)
Reference open letter on the implications of the recast Implementing Regulation.
Definition of Standard & Non-Standard Contract
Under the recast REMIT Implementing Regulation:
Standard contract
A contract concerning a wholesale energy product admitted to trading at an organised marketplace (OMP).
Non-standard contract
A contract concerning a wholesale energy product not admitted to trading at an organised marketplace (OMP).
ACER practical interpretation (for reporting)
- Transactions concluded on an OMP → treated as standard
- Transactions concluded outside an OMP (OTC) → treated as non-standard
ACER TRUM Version 7.0 (17 December 2024)
Main reporting manual with background and legacy examples for standard/non-standard classification.
How to decide what to report
1
Where was the transaction concluded?
Concluded on an OMP
→ Report as standard (T+2)
Concluded outside an OMP (OTC)
→ Report as non-standard (T+10)
2
Are price and quantity defined at the time of reporting?
OTC deals with defined (agreed) price and quantity
- Report using Table 1 (REMITTable1) within T+10 business days
-
Use
BILCONTRACTin Contract Name (Data Field 22) where applicable
Framework contracts (price/quantity not yet known)
- Report the framework contract using Table 2 (REMITTable2) within T+10 business days
- When price and quantity become known, report the related EXECUTION using Table 1, linked to the Table 2 Contract ID
Uncertainty about 'look-alike' contracts agreed OTC
In practice, reporting parties may not always have full visibility of specifications of products traded on organised marketplaces. If you conclude a contract OTC and you are uncertain whether it is identical to an OMP-traded product, treat it as an OTC/non-standard case for reporting timelines and select Table 1 or Table 2 depending on whether price and quantity are known.
List of Standard Contracts (ACER portal)
Reference list of standard contract characteristics for comparison.
Executions, outright volume and price, and deadlines
Executions under non-standard/framework contracts are reported once the delivered quantity and final price are confirmed by the parties (often after delivery and commercial reconciliation).
When an execution specifies at least an outright volume and price:
-
Report it with Table 1 (REMITTable1) as
EXECUTION - Report it within the non-standard/OTC timeline (T+10 business days) from the execution/confirmation event
Transaction timestamp (Field 30)
Field 30 (Transaction timestamp) should indicate when each market participant confirms the price and quantity of the execution.
If the exact matching execution time is not known to both parties: report the date and, as the schema uses datetime, you may use the default time 00:01:00 UTC.
ACER Knowledge Base – Data fields related to transaction details
Additional guidance on transaction data fields.
Lifecycle events
Lifecycle events are changes after initial reporting and must also be reported within the applicable deadlines:
OMP / standard: T+2
OTC / non-standard: T+10
Action types in electronic formats:
new
First submission
modify
Change to reported record
error
Invalidation of wrong record
cancel
Early termination / withdrawal
TRUM v7.0 (17 December 2024)
For examples and details on lifecycle events, see TRUM v7.0 and its Annexes.