The practical effect of REMIT II is that firms now own the contract classification decision. Regulators will expect that decision to be consistent, documented, reproducible and auditable years after it was made. Under REMIT, every electricity or gas contract must be classified as either a standard or non standard contract because that classification determines the reporting deadline.
That change stems from Commission Implementing Regulation (EU), which took effect on 29 April 2026. The European Commission redefined a standard contract as any contract admitted to trading on an organized marketplace, for example EEX or Nord Pool. ACER, which had maintained a published list of contracts meeting the previous definition, discontinued that list as of the same date. That list had grown from 15,846 to 22,593 contracts in a single quarter of 2026, which is offered here as context on scale, not as ACER’s own stated reason for discontinuing the list. Instead of validating classifications against ACER’s list, firms must now determine for themselves whether a contract is standard or non standard.
The bigger shift is that the recast Implementing Regulation transfers responsibility for contract classification from the regulator to the firm. This shift comes as REMIT II increases the complexity of energy market reporting. The recast expands the scope of reportable activity, introduces additional reporting requirements and brings further data requirements across areas such as LNG, algorithmic trading and other market activities. Implementation will continue through 2027 and 2028, meaning firms must adapt their reporting processes while requirements continue to evolve.
In practice, contract classification rarely sits within a single function. Trading understands the products, compliance interprets the regulation, operations manages reporting, and technology determines whether the rationale can still be reproduced years later.
REMIT II turns contract classification into a governance decision that spans all four. If nobody has explicitly assigned that decision, it does not sit with all four functions. It sits with none of them, until a regulator asks who made the call.
For many firms, the challenge is not only understanding the new rules. It is ensuring the underlying trade, order and position data exists in a form that can support accurate reporting, explain decisions and withstand regulatory scrutiny.
Exposure reporting under REMIT II
Exposure reporting introduces the same governance challenge from a different direction, though not in the way it is sometimes described. Once a firm’s positions in forwards, futures and options, combined with forecasted generation and consumption, are equal to or above 600 GWh in a year, assessed separately for power and gas, the firm must report its exposure positions to ACER quarterly, via an Registered Reporting Mechanism (RRM), broken down by month, covering the eighteen months following the reference period. The first report is due 31 October 2027. What is not submitted is the threshold assessment itself: the calculation that decides whether a firm is in scope in the first place.
ACER’s own guidance is explicit that no compulsory submission of that calculation is required, but a firm must be able to demonstrate its assessment if a regulator asks for it, on an ad hoc basis. The threshold is assessed once a year, as at 31 December, for the year ahead: for 2027 delivery, the assessment date is 31 December 2026, and ACER has committed to issuing further exposure reporting guidance and formats by 29 October 2026.
Contract classification and exposure reporting may appear unrelated, but they test the same organisational capability. Regulators are placing greater emphasis on whether firms can explain and reproduce their decisions, not simply whether they met a reporting deadline.
Under the revised standard contract rules, firms must justify how they classified contracts. Under exposure reporting, they must justify whether they crossed the reporting threshold.
Most REMIT reporting programs were built to answer the first question, submitting correctly and on time. Few were built to answer the second: demonstrating, on demand, that reporting decisions were complete and correct months or even years later.
The same regulatory principle appears elsewhere in REMIT II, in a provision that actually falls on the firm rather than the marketplace. Article 14 makes market participants responsible for the completeness and accuracy of their reported information, even when an organized marketplace or an RRM submits that information on their behalf. Handing off the submission does not hand off the responsibility.
Waiting costs more than starting early under REMIT II
REMIT II is not one implementation project but several. The scale of change is easiest to see in REMIT’s own reporting tables.
| REMIT reporting table | What it covers | What changes |
|---|---|---|
| Table 1 | Standard contracts for the supply of electricity and gas | Adds 17 fields, removes 2 |
| Table 2 | Non-standard contracts. Power purchase agreements (PPAs) were already reportable here; new are three PPA-specific fields: type of generation asset, underlying mechanism, and PPA type (baseload, pay-as-produced) | 45 to 51 fields (adds 7, removes 1) |
| Table 3 | Electricity transportation contracts, capacity allocations and transmission rights | Adds 7 fields |
| Table 4 | Gas transportation contracts, capacity allocations | Adds 4 fields |
| Table 5 | New: trade-matching systems such as SIDC, the Single Intraday Coupling mechanism | Entirely new, covers OMP-to-OMP trade matching |
Each REMIT II phase introduces new obligations, but together they reinforce the same expectation: firms must be able to support their reporting decisions with reliable data and evidence. That expectation is also why transparency in how classification logic is configured matters as much as the decision itself. Logic buried inside SQL queries or other technical code is hard to explain to a regulator in business terms, since someone has to reverse-engineer the code before the reasoning behind a given contract’s classification is even visible. Logic held as human-readable, transparent configuration does not need that translation step. It is understandable on its own terms, which is what makes it defensible.
Waiting for the final technical guidance is a risky strategy. The earlier exposure reporting section already shows why: the threshold assessment date and ACER’s own guidance deadline are both fixed points on the calendar, not open-ended waiting. The legal obligations are already defined, while some implementation details will continue to emerge over time. Firms that postpone planning until every reporting format is final may leave themselves with too little time to address the underlying data and governance work.
| Stage | What it adds | Applies from | First report due |
|---|---|---|---|
| Already in force | Standard and non standard contracts redefined. Standard contracts reported within two business days (T+2), non standard within ten (T+10). This deadline also applies to lifecycle events such as amendments or cancellations, even where the event itself happens off exchange but relates to an exchange traded contract | 29 April 2026 | Continuous, from that date |
| First wave | Exposure reporting. Continuous transaction reporting under the new T+2/T+10 timeframes. LNG market data moved into the standard electronic reporting format | 29 October 2027 (exposure reporting applies from 1 January 2027) | 31 October 2027 (this date applies to exposure reporting; continuous transaction reporting has no single first-report date, it runs continuously from 29 October 2027) |
| Second wave | Capacity mechanism transactions, balancing services, gas storage derivatives, updated fundamentals reporting including imbalance settlement data | 29 April 2028 | Between June and August 2028, depending on the obligation |
| Third wave | Hydrogen supply, storage and transportation contracts | 1 July 2028 | 31 January 2029 |
Several implementation rules reinforce the need to prepare early. One example is the backloading requirement under Article 16, though it is narrower than it first appears: it applies specifically to transactions falling under the new periodic reporting type introduced by Article 4, not to every new obligation across the recast. ACER has also carved out final consumer contracts above 600 GWh a year that were already reported continuously before the recast. Where it does apply, firms have 90 days to report any outstanding transactions that have not already been reported, a deadline measured from the date the obligation applies, not from the date the transaction took place.
Registration also requires advance planning. Firms must register with their national energy regulator before entering into reportable transactions, not afterwards. For hydrogen trading, registration should be initiated before 1 July 2028, ahead of the reporting obligation itself.
Registration is also required to disclose inside information, meaning some firms may need to register well before their wider REMIT II reporting obligations begin.
When a classification error becomes a systemic problem
The commercial risk is not a single reporting error. It is embedding the same reporting error across hundreds or thousands of trades before anyone notices. Every contract sharing that misclassification is reported against the wrong deadline until someone notices. What a regulator asks afterward is rarely about the individual mistake. It is about how long the error ran, and whether the firm can show exactly when it started.
There is a second, quieter risk in the same mechanism. Any system that sorts contracts into categories creates edges between those categories, and edges create gaps. A contract that does not sit cleanly inside a category can fall between two, and unlike a misclassified contract, a contract that falls into a gap may not be reported at all, rather than reported late or against the wrong deadline. That is exactly why reconciliation has to work as hard as classification itself: reconciliation is what catches a trade that never made it into any category, not just one that landed in the wrong one.
This is not a decision for the reporting team to make alone. Whether classification judgment sits with one person’s knowledge, an inherited spreadsheet, or a system that can reproduce its own reasoning later is a decision about how the trading firm is run. In most firms, nobody has actually made that decision. It happened by default, at the same moment ACER stopped making the call for them.
What REMIT II will ask you to prove by 2028
In two years, your national regulator, using data ACER has collected, will not be asking whether your firm reported correctly in 2026. It will be asking whether your firm can still prove it did, on a date of its choosing, and Article 14 puts that responsibility on the firm regardless of who submitted the report on its behalf. Firms that treat this as a decision about how their data and systems are set up now will answer that easily. Firms that treat it as a series of deadlines will be rebuilding the same evidence every time they are asked again.
If REMIT II is becoming a question of evidence rather than submission, the next question is where that evidence comes from, and who controls it. Today, updating what a firm sends to its RRM is a narrow task: a handful of standard fields, tested against one binary criterion. As reporting moves from that binary test to the more adaptive, field-heavy requirements arriving through 2028, keeping that submission current becomes continuous work, not a one-off mapping exercise.
BroadPeak captures trade data from exchanges including EEX, Nord Pool and EPEX, and internal trading systems such as ION, SAP, Molecule and Orchestrade, into a single reconciled view the firm owns directly. As REMIT II grows more complex, that view adapts once, rather than being rebuilt against each RRM’s changing specification, reproducing the evidence behind both classification and exposure reporting years later.
The question is no longer whether your firm can submit REMIT reports. It is whether someone owns the decisions behind them.
