ACER REMIT

Understand, validate and oversee REMIT reporting with confidence

REMIT reporting is designed to increase transparency and integrity in EU wholesale energy markets. ACER explains that, under REMIT, the Agency collects the data needed for assessing and monitoring wholesale energy markets, with reporting supported through the Transaction Reporting User Manual (TRUM), reporting guidance and the RRM framework. The current TRUM version became effective on 17 December 2024, with further guidance updates continuing into 2025 and 2026.

For firms in scope, the challenge is not simply sending data to ACER. It is demonstrating that reportable transactions and orders to trade have been identified correctly, that contract and lifecycle data is complete and accurate, and that the control framework around reporting can withstand regulatory scrutiny. The REMIT framework is also evolving following the revised REMIT Regulation.

What is REMIT Reporting?

REMIT reporting refers to the obligation under REMIT to provide ACER with a record of wholesale energy market transactions, including orders to trade, through Registered Reporting Mechanisms. The framework covers standard and non-standard contracts relating to the supply and transportation of electricity and gas, together with certain derivatives and lifecycle information.

ACER supports the regime through the TRUM, annexes, FAQs and reporting guidance, all of which are critical to understanding how the REMIT obligation should be applied in practice.

Who is required to report under REMIT reporting?

REMIT reporting applies to market participants in wholesale energy markets. Reports may be submitted by the market participant directly or by an RRM or other permitted reporting person acting on its behalf, depending on the arrangement used.

That means firms need to understand not only whether a transaction or order is reportable, but also how responsibility is allocated, how the operational reporting model works and how reporting quality is overseen where another party is doing the submission.

Scope and REMIT nexus

REMIT covers wholesale energy market transactions and orders to trade, including standard and non-standard contracts and certain derivatives falling within the regime. Scope often turns on contract type, delivery characteristics, whether the instrument is standardised and how the contract sits within the REMIT perimeter.

For firms active across physical and derivative energy markets, that makes contract classification, delivery-point logic, lifecycle ownership and coordination between trading and reporting functions especially important. In practice, firms need to be confident not just that they understand the perimeter in theory, but that they can apply it consistently across contract types and reporting workflows.

What must be reported?

REMIT reporting requires records of:

• wholesale energy market transactions

• orders to trade

• lifecycle events and amendments

• contract-specific data required under the ACER reporting model

In practice, that means firms need to control not only the core contract data, but also:

• UTI-related logic where relevant

• delivery point or zone data

• lifecycle event handling

• standard vs non-standard treatment

• alignment between REMIT and EMIR treatment for relevant derivatives

Reporting deadlines

REMIT deadlines depend on the contract type. Standard contracts and orders to trade are generally reportable no later than the working day following execution, placement, modification or cancellation, while non-standard contracts are generally reported within 30 days.

For firms in scope, that means reporting timeliness depends on correct contract classification as much as it does on technical submission capability. If firms get the classification wrong, they can easily end up applying the wrong timing rule.

Is REMIT reporting single-sided, dual-sided or delegated?

REMIT is not best described through classic trade repository shorthand such as single-sided or dual-sided. It is a market participant reporting regime to ACER, often operationalised through an RRM or other reporting party. The correct analysis is therefore based on the REMIT legal and reporting framework rather than assumptions borrowed from derivatives trade repository regimes.

Operationally, firms may rely on RRMs and third-party reporting arrangements, but accountability for the completeness and accuracy of the data remains a core compliance issue. Delegation changes the operating model, not the need for oversight.

Are there REMIT reporting exemptions or reliefs?

REMIT includes distinctions between standard and non-standard contracts and other perimeter considerations that materially affect reporting treatment, but the framework is not well served by assuming simple, broad exemptions. The TRUM and REMIT reporting guidance remain the most reliable sources for applying the regime correctly.

The practical point is that firms should not assume a contract is out of scope or lower risk simply because it looks operationally different from a standard exchange-style transaction. REMIT classification needs to be tested carefully.

Consequences of non-compliance

REMIT reporting failures create regulatory, operational and reputational risk, particularly where firms cannot evidence control over contract classification, order reporting, lifecycle updates, delivery-point data and reporting timeliness. ACER’s continuing publication of updated guidance, annexes and FAQs reinforces that this remains an actively interpreted and supervised framework.

For firms in scope, the expectation is clear: REMIT reporting must be accurate, timely and supported by a defensible control framework.

How En:ACT helps with REMIT reporting oversight

En:ACT helps firms strengthen control over their REMIT reporting obligations by ingesting raw transaction data from any source system, performing books and records reconciliation, and assessing 100% of transactions and fields against the applicable REMIT rules.

Using transparent, regulator-linked logic, the platform identifies:

• scope and classification issues

• field-level errors

• cross-field inconsistencies

• delivery point and zone issues

• lifecycle reporting gaps

• reporting anomalies

• REMIT / EMIR overlap issues where relevant

Each identified issue is linked directly to the specific REMIT rule breached, giving firms a clear view of what is wrong, why it matters and where remediation is required.

En:ACT also ensures rules are kept up to date to reflect developments across:

• regulatory text

• regulator guidance

• consultation papers

• relevant industry papers

For REMIT specifically, that means firms benefit from rule coverage maintained in line with the REMIT legal framework, TRUM, annexes and ACER reporting guidance.

Specialist REMIT expertise from the Novatus Intelligence team

Our REMIT capability is supported by specialists within the Novatus Intelligence team, including SMEs with backgrounds across banking, asset management, product and regulation.

For REMIT specifically, that means access to specialists who understand ACER reporting, RRMs, TRUM interpretation and the control issues firms face in maintaining reporting quality across wholesale energy products.

‍

Common REMIT reporting challenges

Some of the most common REMIT reporting issues include:

• misclassification of standard vs non-standard contracts

• weak order-to-trade reporting controls

• poor delivery point or zone logic

• lifecycle event gaps

• REMIT / EMIR overlap confusion

• weak oversight of RRM reporting models

In many cases, the issue is not one bad field. It is a mismatch between the contract as traded, the contract as classified and the final report delivered to ACER.

‍

Why firms choose En:ACT for REMIT oversight

Firms use En:ACT because it gives them more than a validation tool. It provides a control framework around REMIT reporting.

With En:ACT, firms can:

• test reporting quality against transparent rule logic

• reconcile source data to reported data

• identify issues before they become regulatory problems

• evidence oversight of RRM reporting models

• benchmark reporting quality over time

• prepare for regulatory change ahead of go-live

The result is stronger reporting assurance, better governance and a clearer line of sight from raw transaction data to ACER submission quality.

‍