While October 2027 may still seem far away to many firms, preparing for the reporting requirements under REMIT II will likely commence much sooner than the actual changes to take place.
The implementation timeline is already beginning to take shape:
- Q4 2026: ACER TRUM and XML Schemas Finalised
- January 2027: ACER Technical Testing Environment Opens
- October 2027: New REMIT II Reporting Requirements Apply
While that may initially sound like ample time, firms familiar with major reporting changes know that regulatory reporting requirements rarely start at the point when the changes take effect. Instead, they start with assessing the impact of these changes on data, reporting logic, controls, and operating model.
That is, for many firms, preparations have started already.
REMIT II Reporting Changes: More Than Additional Reporting Fields
Of all REMIT II changes to come into play, one of the most substantial is the extension of Table 1 standard contract reporting.
As a result, the number of reportable fields will increase from 58 fields currently to 88, adding further reporting requirements for various aspects such as:
- Liquidity provision
- Algorithmic trading
- Third party activity
- Fixing and index data
- Contract optionality
A jump from 58 to 88 reportable fields sounds like a lot of additional reporting requirements. But that number alone is rarely what makes the implementation process particularly challenging.
Experience shows that what seems like an extra dozen reporting fields can often translate to a wide variety of challenges in data sourcing, mapping, business logic, and controls.
What starts as a relatively straightforward change to reporting rules can very quickly turn into a full-scale implementation programme involving various functional units.
The Biggest Challenges Are Not Reporting Fields
When discussing REMIT II changes, conversations typically revolve around new reporting requirements introduced by regulators.
However, for firms implementing any major reporting requirement, reporting requirements are often just a starting point.
What comes after that are questions about data, processes, and controls that will ensure that the new reporting framework is compliant and sustainable in the long term.
This means that each change to reporting creates additional pressures on various data management, control, and governance areas. This is something that often takes longer than merely updating the reporting schema.
For this reason, REMIT II should be approached not as a reporting requirement update, but as an opportunity to re-evaluate the firm’s current reporting framework.
REMIT II Impacts More Than Regulatory Reporting Teams
As a reporting team, you will likely spearhead the implementation of REMIT II changes within your organisation.
But the changes themselves extend well beyond regulatory reporting, requiring the involvement of:
- Compliance teams that need to make sure that the reporting output meets regulatory standards.
- Operations teams owning critical processes and data.
- Technology teams supporting any necessary system changes.
- Data teams addressing possible data quality, lineage, and data ownership issues.
Success will depend on the ability of all these teams to collaborate and deliver the expected outputs.
In short, REMIT II goes beyond reporting, and so should your plans for implementing it.
Five Critical Questions to Ask Your Firm Today
With implementation milestones looming on the horizon, there are a few things your organisation needs to assess.
1. Does your organisation have access to all the necessary data?
With increased reporting requirements, chances are that your firm will find gaps in data availability and quality.
2. Are your current reporting fields compatible with the new ones?
Reporting field requirements may often necessitate changes to current reporting business logic and workflow.
3. Does your firm have adequate control and governance frameworks?
Any increase in reporting requirements calls for strengthened internal controls and governance.
4. How willadditional reporting fields be validated and reconciled?
New reporting fields imply new opportunities for errors in your reporting processes.
5. Are your regulatory reporting controls robust enough?
Your firm will likely need to show proof of controls supporting data accuracy and quality.
Reporting Data Quality Will Be Scrutinised
If you have had experience implementing EMIR Refit, ASIC Rewrite, or another major reporting requirement, you probably recognise a common pattern.
Reporting requirements tend to be quite clear on what data needs to be provided. But once organisations start assessing their reporting data quality, they discover issues that would otherwise go unnoticed under previous rules.
And, as reporting requirements continue to evolve, regulators will increasingly put data accuracy and completeness under scrutiny.
Why You Should Prepare For REMIT II Implementation Now
Organisations that are best prepared for REMIT II changes are unlikely to be those waiting until the implementation phases start.
Instead, they will be the firms that start assessing REMIT II requirements, impacts, and readiness long before ACER testing commences.
Since the opening of ACER Technical Testing Environment is expected in January 2027, the time for preparations is shorter than you may think.
How Reg-X Helps With REMIT II Implementation
At Reg-X, we are already helping firms prepare for REMIT II through RegAssure data assurance capabilities and specialist regulatory reporting advisory services.
From assessing data readiness and reporting logic to strengthening controls, reconciliation frameworks, and reporting quality assurance, we help firms understand where risks exist and how to address them before implementation deadlines arrive.
REMIT II FAQs
1. When do the new REMIT II reporting requirements start?
New REMIT II reporting requirements are scheduled to become applicable from October 2027.
2. What is changing under Table 1 standard contract reporting?
Reporting fields under REMIT Table 1 will increase from 58 to 88, adding new reporting requirements on various topics, including algorithmic trading, liquidity provision, third-party activity, fixing and index data, and contract optionality.
3. What is the ACER Technical Testing Environment?
ACER’s Technical Testing Environment is scheduled to be launched in January 2027.
4. How can my firm prepare for REMIT II implementation?
Start assessing:
- Your data readiness
- Current business logic of reporting fields
- Adequacy of internal controls and governance frameworks
- Potential impacts of changes on your organisation’s operations
5. Why is data quality relevant for REMIT II compliance?
Reporting data quality and internal controls will continue becoming increasingly important for firms’ regulatory reporting practices, making strong data governance frameworks even more crucial.
REMIT II Readiness Starts Before October 2027
The firms best positioned for implementation are already assessing data, controls, reporting logic, and operational impacts today.
If you’re beginning your REMIT II planning journey, our specialists can help you understand where the key challenges and risks may exist within your reporting framework.
Talk to our REMIT II specialists.
