The European Securities and Markets Authority will activate its revised weekly commodity derivatives position reporting framework on 3 September 2026. The date arrives five months after a planned 1 April launch was stopped during final testing, leaving trading venues one week to complete their move to XML schema v2.0.
The change is narrower than a general reporting deadline for every commodity firm. It applies directly to market operators and investment firms operating trading venues on which commodity derivatives or derivatives of emission allowances are traded. Members and participants still have to supply accurate position and client classifications to those venues, but an OTC commodity CFD broker does not become a weekly v2.0 filer solely because it offers commodity CFDs.
What Goes Live on 3 September and Who Has to File
Under Article 58 of MiFID II, the venue publishes aggregate long and short positions by participant category and sends the report to ESMA for central publication. Venues offering options must produce two reports, including one that excludes options. Venues without options produce one.
The figures cover positions at the previous Friday’s close and divide holders into categories including investment firms, funds, other financial institutions and commercial undertakings. Options are included on a delta-equivalent basis in the inclusive report. The obligation applies only after the relevant thresholds are met, rather than to every thinly traded contract.
Schema v2.0 Changes What ESMA Will Accept
From 3 September, submissions must follow the updated requirements, technical specifications and validation rules in schema v2.0. The framework incorporates changes introduced during the MiFID II review, including two reports where options trade, the exclusion of spot emission allowances and harmonised reporting units for energy derivatives.
The operational risk is rejection, not a cosmetic formatting warning. ESMA’s 38-page reporting instructions say a file can fail if it uses the wrong schema name or version, does not fit the XML schema, carries an invalid venue MIC, or contains inconsistent totals. Long and short fields must be numeric, while risk-reducing and other positions must add up to the reported total. A malformed ZIP file can also be treated as corrupted.
That makes the change a production test of data mapping, file construction and feedback handling. The same concerns sit behind the wider cost of fragmented European reporting, which prompted ESMA’s proposal for a “Report Once” system and recent integrations that embed EMIR and MiFIR reporting into trading platforms.
Why the April Launch Was Postponed
ESMA halted the original rollout on 27 March, only five days before it was due to begin. Its postponement notice said final testing had identified issues requiring corrective work to protect system stability and data quality. Reporting entities were told to remain on the existing version until a replacement date was announced.
The regulator has not disclosed the affected component, the number of failed tests or an industry readiness percentage. Its 14 August confirmation says the extra period was used for technical and operational preparation and that the fixes have been implemented and validated. Claims about a specific vendor failure or broad market unreadiness would therefore go beyond the public record.
Rejected Files Still Have to Be Corrected
ESMA has not announced another transition period. Its system returns feedback showing whether a file was accepted, rejected or corrupted. Submitting venues are responsible for reading every feedback file, correcting rejected records and resending them as soon as possible. Missing submissions generate a reminder to the submitting entity and an ESMA business officer.
The launch notice does not set a new fine schedule. Any supervisory response remains with the relevant national authority under MiFID II, but a rejected file is not a completed report. That distinction matters when reporting classifications can change what the market appears to show, including through the forthcoming EU consolidated tape for OTC derivatives.
What Commodity CFD and Futures Brokers Need to Check
Futures brokers that are venue members or participants should confirm that their position and client-category data reaches each venue in the required form, even where the venue makes the weekly submission. A firm that operates an MTF or OTF carrying the relevant contracts has the direct filing exposure and should test schema versioning, MIC fields, aggregation logic, ZIP packaging and feedback retrieval before 3 September.
Retail OTC CFD providers sit outside this weekly venue-reporting channel unless another part of their structure brings them into scope. Their existing transaction and derivatives reporting duties remain separate, just as ESMA’s treatment of perpetual products depends on legal structure rather than branding. The practical task is to map each legal entity and execution route, rather than applying the deadline to every commodity product on a broker’s screen.