Gas Derivatives Reporting After the GMTF: EMIR and REMIT for Energy Firms

Last updated: June 2026

An energy trading desk can hedge a winter gas position perfectly and still fail two reporting regimes at once. The same forward sold on a regulated venue lands in an EMIR trade repository feed, an ACER data collection under REMIT, and, for many firms, a MiFID II position report. Miss a field in one and gas derivatives reporting quietly breaks across regimes. When the records stop reconciling, supervisors notice, because the whole point of the new oversight push is to line those datasets up side by side.

That push now has a name and a report behind it. On 2 June 2026 the Gas Market Task Force published its findings on the functioning of EU gas and gas derivatives markets, and the parts that matter most to a reporting officer are not the headline conclusions about market health. They are buried in the sections on REMIT implementation, position reporting, single-reporting mechanisms, and data sharing between energy and financial supervisors. Gas derivatives reporting is about to get more scrutiny, not less, even as the Commission talks about cutting administrative burden.

This article walks through what an energy firm and its bank counterparties actually report on a gas derivative today, under which regime, to whom, and by when. It then maps where the GMTF work is likely to change that, so you can tell the difference between a real obligation and a consultation idea.

Related reading: EMIR Reporting Explained

Why the GMTF report matters for your reporting stack

The Gas Market Task Force was set up in February 2025 as part of the Commission’s Affordable Energy Action Plan under the Clean Industrial Deal. It brings together officials from the European Commission and the two EU agencies that supervise these markets: the Agency for the Cooperation of Energy Regulators (ACER) on the energy side and the European Securities and Markets Authority (ESMA) on the financial side. Its mandate was to scrutinise the functioning of EU gas and gas derivatives markets, identify possible shortcomings, and propose actions to address them.

The headline finding is reassuring and easy to skim past: both markets are functioning well. The operational substance sits in the list of areas the Task Force says need further work. That list includes monitoring trends in algorithmic trading, building new market monitoring tools, REMIT implementation, certain commodity derivatives rules including position management controls and position reporting, and data sharing and cooperation between energy and financial supervisory authorities.

Read that list again as a reporting officer rather than a policy analyst. Every item depends on the quality of the data your firm submits. A supervisor cannot monitor algorithmic trading in gas futures if the trade reports are late or carry the wrong execution timestamp. A joint ACER and ESMA team cannot cross-check a position across the spot and derivative legs if the REMIT record and the EMIR record do not share consistent identifiers. The Task Force is, in effect, telling firms that the next phase of oversight runs on reporting hygiene.

In 2025 the Commission launched a broad stakeholder consultation on commodity derivatives markets. It is testing whether further legislative change is needed to give regulators a complete oversight picture, to align the energy and financial rulebooks more closely, and to cut the duplication that energy firms complain about. That is the part to watch, and the part most likely to land on a reporting team’s desk in 2027 and beyond.

Two regimes, two destinations: EMIR and REMIT

The first thing to fix in anyone’s head is that a gas derivatives book answers to more than one regime, and the regimes divide the work rather than each demanding the same transaction. EMIR, REMIT and the MiFID position framework ask different questions for different supervisors, and the trick is knowing which regime takes which record.

EMIR is Regulation (EU) No 648/2012, the European Market Infrastructure Regulation. It governs derivatives reporting from the financial-stability and market-integrity angle. Under EMIR, the details of a derivative contract go to a registered trade repository, and ESMA, the EBA, EIOPA and the ESRB can see the full transaction dataset to oversee systemic risk. The reporting framework was reshaped by EMIR REFIT (Regulation (EU) 2019/834) and again by EMIR 3 (Regulation (EU) 2024/2987), and it now runs on the technical standards that became applicable on 29 April 2024.

REMIT is Regulation (EU) No 1227/2011 on wholesale energy market integrity and transparency, recently strengthened by REMIT II (Regulation (EU) 2024/1106), which entered into force on 7 May 2024. REMIT governs the same trades from the energy-market-abuse angle. Under REMIT, market participants report transactions and orders in wholesale energy products to ACER, and ACER uses that data to detect manipulation and insider dealing in electricity and gas.

The two regimes overlap on exactly the instruments an energy desk cares about most: gas and power derivatives traded on organised venues. A gas future executed on a regulated market is a derivative for EMIR and a wholesale energy product for REMIT. That overlap is not a drafting accident. It exists because the financial supervisor and the energy supervisor each need the data for a different statutory job, and neither mandate is wide enough to cover the other’s. ESMA’s own data quality work makes the boundary explicit: ACER’s access to derivatives data is strictly limited to contracts where the underlying is energy or emission allowances, while the financial authorities hold the broader cross-market view.

Where gas derivatives reporting actually starts: EMIR Article 9

The legal anchor for the financial side is Article 9 of EMIR. It requires counterparties and central counterparties to report the details of any derivative contract they conclude, and of any modification or termination, to a trade repository. The deadline is tight: no later than the working day following the conclusion, modification or termination of the contract. Practitioners call it T+1, and it applies to both over-the-counter derivatives and exchange-traded derivatives, so a gas future cleared on a venue is in scope just as much as a bilateral swap.

The content of the report is set by the technical standards rather than the Level 1 text. The implementing technical standards in Commission Implementing Regulation (EU) 2022/1860 fix the fields, formats and frequency, and the regulatory technical standards in Commission Delegated Regulation (EU) 2022/1855 set the minimum detail to be reported. Both became applicable on 29 April 2024, which is the version your gas derivative reports follow today. That EMIR REFIT field set runs to well over a hundred data elements, including the Unique Trade Identifier, the Unique Product Identifier, valuation and margin fields, and the action and event type codes that tell the repository what happened to the trade.

One operational detail trips up energy desks specifically. Both sides of a derivative must report, and both reports must reconcile inside the trade repository on the shared fields, the UTI chief among them. A gas forward booked against a bank counterparty fails reconciliation the moment the two sides disagree on the UTI or the notional. I have watched a clean economic hedge sit in a repository’s pairing-and-matching exception report for days, not because the trade was wrong, but because the two firms generated the UTI under different conventions. Agreeing UTI generation logic with each counterparty before the first trade is reporting work, not legal housekeeping, and it is where commodity-trading firms with thin operations teams lose the most time.

Energy firms as non-financial counterparties, and the EMIR 3 threshold question

Most energy trading firms are non-financial counterparties under EMIR. That status is not a free pass. It drives whether your derivatives are subject to clearing and margin, and under EMIR 3 it is being recalibrated in a way that reaches commodity derivatives directly.

The mechanism is the clearing threshold. A non-financial counterparty measures its positions in OTC derivatives against asset-class thresholds, and exceeding the threshold in any class can pull the firm into clearing and exchange-of-margin obligations for that class. EMIR 3 reworked this regime, and ESMA published its final report on the draft technical standards for the new clearing thresholds on 25 February 2026. EMIR 3 invited ESMA to consider more granular thresholds for the commodity derivatives class specifically, which is the asset class where gas and power desks build their exposure.

The practical point for a reporting team is that clearing-threshold status is a reporting-driven number. You calculate it from the positions you are already capturing, and crossing it changes both your EMIR obligations and the way your trades clear. A common misread is to treat the threshold calculation as a one-off legal classification done at onboarding. It is not. It is a rolling measurement, and a desk that grows its gas derivative book through a volatile winter can move from below to above the commodity threshold without anyone in compliance noticing until the clearing obligation has already bitten. In its 25 February 2026 final report ESMA retained five clearing-threshold categories and did not introduce a more granular commodity sub-threshold, so the commodity asset-class threshold remains the figure that decides whether your gas book stays uncleared.

This is also where the EMIR margin world meets gas trading. Firms that cross the threshold and trade uncleared OTC commodity derivatives face the exchange of collateral, which is its own reporting and operational stream. Our guide to EMIR initial margin reporting covers how those margin obligations and their reporting fields work once a firm is in scope.

REMIT data collection: what ACER expects, and what it does not cover

On the energy side, the reporting obligation flows from Article 8 of REMIT. Market participants report the details of their wholesale energy market transactions, including price, volume, date and time, to ACER. The reports do not go straight to ACER from a spreadsheet; they pass through Registered Reporting Mechanisms, the REMIT equivalent of a regulated reporting channel, and inside information is published through Inside Information Platforms.

REMIT II broadened this. The 2024 amendment aligned more of the REMIT rulebook with financial market legislation, widened the set of products and participants in scope, and strengthened ACER’s and the national regulators’ supervisory and investigatory powers. It also expanded fundamental and position-style data collection. Larger market participants face new reporting of trading positions and forecast data to ACER on a forward-looking basis, which is a different exercise from the transaction reporting that REMIT has always required. Treat the exact thresholds and timetables for that new collection as still bedding in, and confirm the current ACER implementing acts before you build to a specific number.

What REMIT does not do is replace EMIR, and the two directions are not symmetrical. Reporting a gas trade to ACER under REMIT does not discharge the EMIR obligation: the EMIR report to a trade repository always stands on its own. The reverse is governed by an anti-double-reporting rule. A derivative that is a financial instrument and has already been reported under EMIR Article 9 or MiFIR Article 26 is not reported again by the market participant to ACER. As ACER’s Transaction Reporting User Manual sets out, the trade repositories and approved reporting mechanisms pass that transaction data to ACER instead. So the gas future executed on a venue is reported once as a transaction, through the financial channel, not twice. What REMIT still requires firms to send to ACER directly are orders to trade, which EMIR does not capture, and wholesale energy contracts that are not reported under EMIR or MiFIR. ACER cannot see your interest rate or equity derivatives at all, because its mandate stops at energy and emission allowance underlyings. ESMA has noted that firms often report the same contract under all three frameworks even where they are not obliged to, an inefficiency the single-reporting work aims to remove rather than a legal requirement.

Position management controls and position reporting under MiFID II

The third regime in the stack is the markets framework. Commodity derivatives traded on EU venues sit inside MiFID II (Directive 2014/65/EU) and MiFIR (Regulation (EU) No 600/2014), and two MiFID II tools are squarely in the GMTF’s sights: position management controls and position reporting.

Position limits and position management controls live in Article 57 of MiFID II. Trading venues that admit commodity derivatives apply position management controls, and national competent authorities set position limits on certain contracts to support orderly pricing and settlement. Position reporting lives in Article 58. Venues publish a weekly report on the aggregate positions held by the different categories of position holder in the commodity derivatives they trade, and members report their positions to the venue, while investment firms trading off-venue report to the relevant competent authority. The categorisation of holders, including the distinction that flags commercial hedging by non-financial firms, is what lets a regulator tell a genuine gas hedge from speculative length.

For a reporting team, MiFIR transaction reporting is the cousin obligation that often gets conflated with EMIR. They are not the same filing, and our MiFIR transaction reporting guide sets out where the two diverge on scope, fields and destination. The GMTF flags position reporting because the categories and thresholds were designed for a market that has since changed, and the Commission’s consultation asks whether the MiFID and REMIT rules on commodity positions should be brought into closer alignment. If that happens, the position-reporting category logic your firm applies today is a candidate for revision.

Data sharing between ACER and ESMA, and why data quality is the real bottleneck

The Task Force puts heavy weight on data sharing and cooperation between energy and financial supervisors, and this is the area where reporting quality stops being an internal housekeeping issue and becomes a supervisory one.

ACER and ESMA already cooperate through a joint task force and through the Energy Trading Enforcement Forum, where energy regulators, financial regulators, ESMA and ACER compare supervisory and enforcement experience. The GMTF work is meant to broaden that cooperation into routine data and knowledge exchange. The obstacle is structural. Each authority holds part of the picture under a mandate that is deliberately narrow, so a complete view of a cross-market gas strategy only appears when the REMIT dataset and the EMIR dataset are joined. They only join cleanly if the underlying reports are accurate, complete and identifiable on common keys.

ESMA’s annual report on the quality and use of EMIR data, published on 29 May 2026, makes the point that data originates at the level of the reporting counterparty and that reporting can be delegated to a third party without transferring legal responsibility. That last clause is the one teams underweight. Outsourcing the mechanics of submission to a vendor or a bank counterparty does not move the legal liability for a wrong or missing report. When a joint ACER and ESMA review finds a gas position that does not reconcile across the two regimes, the firm that delegated its reporting is still the firm on the hook. The lesson from the data quality work is blunt: delegation is an operational convenience, not a transfer of accountability.

What the GMTF consultation could change for reporting teams

The single most consequential idea in the GMTF package, from a reporting standpoint, is the single-reporting mechanism. The Commission’s consultation explicitly explores reducing the administrative burden on companies that trade energy products on financial markets, including through single-reporting, and aligning MiFID and REMIT more closely.

The promise is obvious. A firm that today builds a gas trade into an EMIR report, a REMIT report and, where relevant, a MiFID position report could in principle submit once and let the supervisors share. The reality is more cautious. Single-reporting only works if the two regimes agree on field definitions, identifiers and timing, and they currently do not. EMIR runs on T+1 to a trade repository with the UTI and UPI at its core. REMIT runs on its own schemas through RRMs to ACER. Bridging those is a multi-year standards exercise, not a switch.

So the honest read for 2026 is this. Nothing in the GMTF report removes an existing obligation. A reporting team that hears single-reporting and quietly deprioritises one of its current feeds is making a planning error. The obligations are live until a legislative change says otherwise, and any change will arrive with its own implementation window and its own technical standards. The right move now is to make the existing EMIR and REMIT feeds clean enough that a future merge is a mapping exercise rather than a rebuild.

What teams get wrong about gas derivatives reporting

A handful of mistakes recur across energy desks, and each one is cheap to avoid once it is named.

The first is assuming the regimes are interchangeable. They are not, because EMIR, REMIT and MiFID position reporting answer to different supervisors and follow different rules. But the opposite error is just as common, and ESMA has flagged it: reporting the same contract under all three when REMIT’s anti-double-reporting rule means a derivative already reported under EMIR or MiFIR is not re-reported to ACER. Map which regime takes which record, because the GMTF push to share data makes inconsistencies between the datasets more visible, not less.

The second is treating clearing-threshold status as static. A non-financial counterparty’s commodity position is a moving number, and under EMIR 3 the commodity threshold is being recalibrated, so a desk can drift into a clearing obligation mid-season. Recalculate it on the schedule the rules require, not at onboarding.

The third is leaning on delegation as if it transferred risk. It does not. Whether your bank counterparty or a vendor submits the file, the legal responsibility for a correct and complete EMIR report stays with your firm, as ESMA’s data quality work spells out. For high-volume reporting officers, our SFTR reporting guide shows the same delegation-without-liability pattern in the securities financing world, which is worth reading across because the trap is identical.

Frequently Asked Questions

Does reporting a gas trade to ACER under REMIT satisfy the EMIR obligation?

No. Reporting a gas trade to ACER under REMIT does not discharge the EMIR obligation, which always stands on its own. The reverse works differently: REMIT carries an anti-double-reporting rule, so a derivative already reported under EMIR or MiFIR is not reported again to ACER as a transaction, and ACER receives that data from the trade repositories and approved reporting mechanisms instead. What REMIT still requires directly are orders to trade and wholesale energy contracts not reported under EMIR or MiFIR. A full single-reporting mechanism that would merge the regimes does not yet exist in law.

Who has to report a gas derivative under EMIR?

Under Article 9 of EMIR, both counterparties to a derivative report it, as do central counterparties for cleared trades. This includes financial counterparties and non-financial counterparties, and it captures contracts where at least one counterparty is established in the EU. Reporting can be delegated, but legal responsibility for the report stays with the counterparty.

What is the EMIR reporting deadline for a gas future?

The details must reach a registered trade repository no later than the working day following the conclusion, modification or termination of the contract, which practitioners call T+1. The same deadline applies to both over-the-counter and exchange-traded derivatives, so cleared gas futures are included.

Which technical standards set the EMIR fields I report?

Commission Implementing Regulation (EU) 2022/1860 sets the standards, formats, frequency and arrangements for reporting, and Commission Delegated Regulation (EU) 2022/1855 sets the minimum detail. Both became applicable on 29 April 2024 and define the current EMIR REFIT field set, including the UTI and UPI.

Why does the EMIR 3 clearing threshold matter to an energy firm?

A non-financial counterparty that exceeds the clearing threshold in the commodity derivatives class can be pulled into clearing and margin obligations for that class. EMIR 3 reworked the thresholds and asked ESMA to consider more granular figures for commodity derivatives. ESMA published its final report on the draft standards on 25 February 2026, so the commodity threshold is the figure energy desks should track.

What did REMIT II change for reporting?

REMIT II (Regulation (EU) 2024/1106) entered into force on 7 May 2024. It aligned more of REMIT with financial market rules, widened the products and participants in scope, strengthened ACER and national regulator powers, and expanded data collection, including new forward-looking position and forecast reporting for larger participants. The transaction reporting obligation to ACER through Registered Reporting Mechanisms remains.

Is MiFID II position reporting the same as EMIR reporting?

No. MiFID II position reporting under Article 58 is about aggregate positions in commodity derivatives by category of holder, published weekly by venues and reported to competent authorities. EMIR reporting is transaction-level detail to a trade repository. A gas derivative can trigger both, plus REMIT, which is exactly the duplication the GMTF consultation is examining.

When will a single-reporting mechanism actually arrive?

There is no date. Single-reporting is an idea in the Commission’s commodity derivatives consultation, not an enacted rule. Any change would require aligning EMIR and REMIT field definitions, identifiers and timing, then new technical standards and an implementation window. Until then, all current EMIR, REMIT and MiFID obligations stand on their own.

Related Articles

• EMIR Reporting Explained – The full EMIR reporting workflow, from counterparty scope and the T+1 deadline to the trade repository field set.
• EMIR Initial Margin Reporting – How margin obligations and their reporting fields apply once a counterparty is in scope for uncleared derivatives.
• MiFIR Transaction Reporting – Where MiFIR transaction reporting diverges from EMIR on scope, fields and destination.
• SFTR Reporting Explained – The securities financing reporting regime, including the same delegation-without-liability rule that applies under EMIR.
• ESMA Active Account Requirement Reporting Templates – The EMIR 3 active account obligation and the templates clearing members report against.

Preparing your reporting stack for a single-reporting future

The GMTF did not hand reporting teams a new deadline. It handed them a direction of travel. Supervisors want to see a gas position whole, across the REMIT and EMIR records, and they are building the cooperation to do it. The firms that will cope best are the ones whose two feeds already reconcile, whose UTIs agree with their counterparties, and whose clearing-threshold maths is run on a calendar rather than on memory. Do that work now and a future single-reporting regime becomes a remapping. Skip it and the same regime becomes a reconstruction, under a supervisor that can finally see both halves of the trade.

Key Takeaways

• The Gas Market Task Force published its findings on 2 June 2026; the reporting-relevant parts cover REMIT implementation, position reporting, data sharing, and a possible single-reporting mechanism.
• A gas derivative that is a financial instrument is reported as a transaction under EMIR, and where relevant MiFIR, not separately to ACER, because REMIT’s anti-double-reporting rule routes that data to ACER from the trade repositories. REMIT still captures orders to trade and contracts that are not reported under EMIR or MiFIR, and MiFID II position reporting is a further, separate layer.
• EMIR Article 9 requires T+1 reporting to a registered trade repository, on the field set fixed by Commission Implementing Regulation (EU) 2022/1860 and Commission Delegated Regulation (EU) 2022/1855, applicable since 29 April 2024.
• Energy firms are usually non-financial counterparties; EMIR 3 (Regulation (EU) 2024/2987) recalibrated clearing thresholds, with ESMA’s 25 February 2026 final report retaining five threshold categories and declining a more granular commodity sub-threshold, so the commodity asset-class threshold is the figure to track.
• REMIT II (Regulation (EU) 2024/1106), in force 7 May 2024, widened REMIT scope and data collection; transaction reporting to ACER still runs through Registered Reporting Mechanisms.
• ACER’s data access is limited to energy and emission allowance derivatives, so the full cross-market view only exists when REMIT and EMIR data are joined, which depends on report quality.
• Delegating reporting does not transfer legal responsibility, a point ESMA’s 29 May 2026 data quality report makes explicit.
• Single-reporting is a consultation idea, not law; no current obligation has been removed, so keep every existing feed clean and reconciled.

Sources and References

• Gas Market Task Force presents its findings on the functioning of EU gas and gas derivatives markets, European Commission, 2 June 2026: https://energy.ec.europa.eu/news/gas-market-task-force-presents-its-findings-functioning-eu-gas-and-gas-derivatives-markets-2026-06-02_en
• GMTF presents its findings on EU gas and gas derivative markets, ESMA news, 2 June 2026: https://www.esma.europa.eu/press-news/esma-news/gmtf-presents-its-findings-eu-gas-and-gas-derivative-markets
• Regulation (EU) No 648/2012 (EMIR), Article 9 reporting obligation, EUR-Lex: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32012R0648
• ESMA Interactive Single Rulebook, EMIR Article 9 Reporting obligation: https://www.esma.europa.eu/publications-and-data/interactive-single-rulebook/emir/article-9-reporting-obligation-0
• ESMA EMIR Reporting overview (technical standards, applicable 29 April 2024): https://www.esma.europa.eu/data-reporting/emir-reporting
• Commission Implementing Regulation (EU) 2022/1860 (EMIR reporting ITS), EUR-Lex: https://eur-lex.europa.eu/eli/reg_impl/2022/1860/oj
• Commission Delegated Regulation (EU) 2022/1855 (EMIR reporting RTS), EUR-Lex: https://eur-lex.europa.eu/eli/reg_del/2022/1855/oj
• Regulation (EU) 2024/2987 (EMIR 3), EUR-Lex: https://eur-lex.europa.eu/eli/reg/2024/2987/oj
• ESMA sets out clearing thresholds under EMIR 3, ESMA news, 25 February 2026: https://www.esma.europa.eu/press-news/esma-news/esma-sets-out-clearing-thresholds-under-emir-3
• Regulation (EU) No 1227/2011 (REMIT), Article 8 data collection, EUR-Lex: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32011R1227
• Commission Implementing Regulation (EU) 2026/256 (recast REMIT data-reporting IR, repealing Commission Implementing Regulation (EU) No 1348/2014, with specified provisions of 1348/2014 continuing to apply transitionally into 2027 and 2028); the routing of records already reported under EMIR Article 9 or MiFIR Article 26 to ACER carries over from Article 6 of 1348/2014, EUR-Lex: https://eur-lex.europa.eu/eli/reg_impl/2026/256/oj
• Regulation (EU) 2024/1106 (REMIT II), in force 7 May 2024, EUR-Lex: https://eur-lex.europa.eu/eli/reg/2024/1106/oj
• Directive 2014/65/EU (MiFID II), Articles 57 and 58 on position limits, position management controls and position reporting, EUR-Lex: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32014L0065
• ESMA Report on Quality and Use of Data 2025 (covering EMIR, SFTR, MiFIR, AIFMD and MMFR), ESMA92-2024897840-14578, 29 May 2026: https://www.esma.europa.eu/sites/default/files/2026-05/ESMA92-2024897840-14578_Report_on_quality_and_use_of_data_2025.pdf
• ACER and ESMA enhance cooperation to strengthen oversight of energy and energy derivative markets, ACER: https://www.acer.europa.eu/news/acer-and-esma-enhance-cooperation-strengthen-oversight-energy-and-energy-derivative-markets

Disclaimer: The information on RegReportingDesk.com is for educational and informational purposes only. It does not constitute legal, regulatory, tax, or compliance advice. Always consult your compliance officer, legal counsel, or the relevant supervisory authority for guidance specific to your institution.