PS26/15 simplifies UK transaction reporting, but readiness demands robust controls. Explore how to prepare your operating model before April 2028.
PS26/15 is the biggest overhaul of UK MiFIR transaction reporting since 2018.
The FCA estimates that annual industry costs could fall from around £493m to £385m once the new regime is fully implemented. Firms will only realise those savings if they use the change to simplify their reporting architecture, controls and operating model.
The larger opportunity may sit with firms that look beyond MiFIR.
What's changing?
Fewer fields. The report drops from 65 fields to 52. Five indicator fields disappear entirely: waiver, short selling, OTC post-trade, commodity derivative and SFT.
Narrower scope. Around 7 million EU-only instruments fall out of scope. FX derivatives are removed, affecting more than 400 UK firms, while most corporate actions become exempt.
A shorter look-back. The default back-reporting period falls from five years to three.
A new home. From 3 April 2028, the rules move into MAR 14 of the FCA Handbook.
On paper, this looks like straightforward simplification. The harder work is underneath.
Where the real impact will land
Reporting responsibilities are changing.
The scope of conditional single-sided reporting is widening. The sending firm will pass on four categories of information rather than ten individual fields. This needs a written agreement that sets, at minimum, a time limit for providing the information. The agreement should be in place before firms trade.
Buy-side firms and their brokers should revisit who reports what, formalise those responsibilities and confirm the operating model works in practice.
Scope is harder to get right.
Reportability is determined against the FCA's reference data. If an instrument has not appeared there within seven working days of the trade, the guidance allows firms to conclude that it is not reportable.
The safe harbour helps, but firms should keep checking.
Firms operating in the UK and EU will also need to run two diverging scope models. Getting scope wrong in either direction is a controls issue. MAR 14 expects firms to identify both over-reporting and under-reporting.
The remaining fields matter more.
Take trading capacity. If a firm deals on own account, its own LEI must appear as buyer or seller. If it acts as agent or matched principal, it must not.
With fewer fields, the remaining ones need to be higher quality and more consistent.
Enforcement and accountability remain.
The FCA can still require up to five years of back reporting for serious failings, while record-keeping remains at five years.
It also expects firms to have a proper incident-management framework covering triage, root-cause analysis, remediation, escalation and notification to the FCA.
Simpler reporting does not reduce accountability.
Beyond MiFIR: stop paying three times for the same data
For firms reporting under several regimes, PS26/15 is only the start.
The FCA and Bank of England are working to harmonise UK MiFIR, EMIR and SFTR. In the EU, ESMA has proposed a single "report once" template spanning all three regimes, potentially from the second half of 2031.
Reporting may get more complicated before it gets simpler.
UK and EU scope will diverge, so firms operating in both will run two rulebooks. Adding UK changes to existing processes will add cost and complexity, not remove them.
The firms that gain most will:
- Fix data once, at source. LEIs, client identifiers, trading capacity and instrument data should serve every reporting regime.
- Make scope rules configurable. The next change should mean adjusting parameters, not rebuilding systems.
- Consolidate controls, vendors and change programmes. MiFIR, EMIR and SFTR should increasingly run on one reporting architecture, not three separate problems.
Key dates
October 2026: The FCA published the draft schema and validation rules alongside CP26/34.
Q1 2027: The FCA is expected to consult on the new user pack, with the final version due by 3 April 2027.
3 April 2028: The new transaction-reporting regime goes live.
What should firms be doing now?
Start with the quick wins. The FCA's flexible supervisory approach already lets firms use several of the relaxations.
Then focus on the underlying model:
- Map your reporting logic against the new schema.
- Review single-sided reporting arrangements with counterparties and put the required written agreements in place.
- Stress-test client indicator and trading-capacity logic, particularly where data is derived upstream.
- Review scope determination across the UK and EU and identify where divergence needs to be managed explicitly.
- Decide whether this is simply a UK regulatory change or the first step towards a common reporting model across MiFIR, EMIR and SFTR.
That decision matters most.
Why work with us?
Software can flag what is wrong with a report. We help you decide what your reporting function should look like in 2028 and who owns it.
We start with governance: senior-manager accountability, management and board MI, and an incident-management framework that will hold up to FCA scrutiny.
We work on root causes. A broken reporting field often starts upstream, in trade booking, static data, client onboarding or another system. That is where remediation should start.
We take cost out of the operating model by looking across MiFIR, EMIR and SFTR together. Many firms maintain duplicate data, controls, technology and processes for essentially the same outcome.
How Delta Capita can help
Our Readiness Assessment covers more than field mapping.
To support this transition, we bring purpose-built accelerator tools that combine regulatory expertise with technology to help firms assess their current reporting framework, identify gaps and understand the operational impact of the new requirements. These solutions help reduce manual effort, prioritise remediation, avoid unnecessary implementation costs and provide clearer visibility of readiness, enabling firms to make informed decisions well ahead of the April 2028 deadline.
We assess governance, accountability and incident management against MAR 14, test where reporting data breaks and why, and, for firms across several regimes, identify where a common data and control model could cut complexity and cost.
Three tools support this work:
Scope Assessment
A structured assessment of what is moving into and out of scope, which relaxations can be adopted early, and what that means for reporting volumes and cost. The output turns regulatory change into figures stakeholders can understand and approve.
Readiness Dashboard
A single view of change across reporting, data, technology and operations. It shows gaps, owners, milestones and overall readiness, so management can track progress without chasing individual workstreams.
AI-Powered Auto Mapper
Maps existing source-system and reporting fields to the new MAR 14 schema. It flags new, changed and redundant fields, suggests transformation logic and highlights data gaps. Weeks of manual spreadsheet work become a focused review.
The aim is to free your people for decisions and delivery.
We won't push technology where it isn't needed.
We will tell you what to fix, keep or consolidate.