UK Transaction Reporting Reform: 65 Fields Cut to 52 by 2028

On 3 August 2026 the Financial Conduct Authority published PS26/15, the policy statement that finalises its overhaul of UK transaction reporting. From 3 April 2028, firms reporting under UK MiFIR will populate 52 fields instead of 65, will no longer report foreign exchange derivatives, and will drop roughly 7 million instruments that trade only on European Union venues from scope. The FCA puts the saving to industry at more than £100m a year.

That headline number is the reason the topic moved up firms’ agendas, but the operative point sits underneath it. Every entity that reports transactions to the FCA, together with the Approved Reporting Mechanisms and vendors that file on their behalf, now has a fixed date to re-scope its reporting logic, rebuild field mappings and re-run reconciliation before the regime changes. The FCA has paired the 2028 go-live with a flexible supervisory approach that runs from publication, so some of the work can start earlier for firms that are ready.

One boundary matters before anyone reads the detail. PS26/15 changes the MiFIR transaction reporting regime only. UK EMIR and UK SFTR reporting obligations are unchanged by this policy statement; for those regimes the relevant development is a separate, longer-term harmonisation programme run jointly with the Bank of England.

Related reading: MiFIR Transaction Reporting.

The dates that anchor the change

PS26/15 is a deadline-driven policy statement, so the calendar is the first thing to lift out of it. The operative dates are:

• 3 August 2026: the FCA publishes PS26/15 and its flexible supervisory approach begins.
• October 2026: the FCA has said it will consult on the technical reporting schema and validation rules that sit under the new field set.
• 3 April 2028: the new rules take effect and the reduced field set becomes the reporting standard.

The July 2026 inaugural meeting of the Transaction and Post-trade Reporting Harmonisation Taskforce sits alongside these dates, but it belongs to the separate cross-regime harmonisation programme covering UK MiFIR, UK EMIR and UK SFTR. For a MiFIR reporting team, the technical implementation window is approximately eighteen months between publication of the October 2026 draft materials and the 3 April 2028 go-live.

Four core changes to UK transaction reporting in PS26/15

The four press-release measures are not the complete implementation scope. PS26/15 also exempts most corporate-event activity other than IPOs, secondary public offerings, placings and debt issuance; creates a conditional single-sided reporting framework; reduces specified trading-venue reporting fields; adds rules and guidance on branch execution; and changes definitions, identifiers, field values, systems-and-controls guidance and instrument-reference-data requirements. Firms should build their impact inventory from PS26/15 Chapters 3 to 6 and the FCA’s made instrument contained in PS26/15 Appendix 2, not from the four headline measures alone.

The first reduces the number of reportable fields from 65 to 52. The second removes foreign exchange derivatives from the scope of the regime, which the FCA says benefits more than 400 firms. The third removes reporting obligations for around 7 million financial instruments, including equities, bonds and certain derivatives, that are tradeable only on EU trading venues. The fourth shortens the default back reporting period for historical error corrections from five years to three, which the FCA expects to cut the volume of transaction reports firms have to resubmit by a third.

Put against the current cost base, the FCA estimates that MiFID transaction reporting costs industry £493m a year today and that these changes take that to about £385m, a net annual saving of £108m. The design principle running through all four is to keep the data the FCA relies on for market oversight while removing reporting that is duplicative or low value.

Who the regime reaches and how the reports get to the FCA

The changes reach an entire reporting chain that runs well beyond a single team, so it helps to be clear on who is in scope. UK MiFIR requires investment firms that execute transactions in reportable financial instruments to report complete and accurate details to the FCA no later than the close of the following working day; reports may be submitted by the investment firm itself, by an Approved Reporting Mechanism acting on its behalf, or by the trading venue through whose system the transaction was completed. The FCA describes these transaction reports as the backbone of its market oversight work, using them to detect and investigate market abuse, monitor market functioning and supervise firms. That supervisory purpose is why the FCA has kept the data it relies on while stripping out the reporting it does not.

Because Approved Reporting Mechanisms and reporting vendors file on behalf of many firms at once, the field, scope and schema changes propagate through shared infrastructure that serves the whole market. Under current UK MiFIR, a firm remains responsible for the completeness, accuracy and timely submission of its reports except for failures attributable to an Approved Reporting Mechanism or reporting trading venue, provided the firm has taken reasonable steps to verify reports submitted on its behalf. It should therefore confirm its ARM’s and vendors’ implementation timelines against the April 2028 date, because there is no guarantee the wider market moves in step. The remapping work has to be reconciled end to end, from a firm’s own booking systems through to what actually reaches the FCA.

Why this is a Handbook rewrite, not a technical-standard tweak

It would be easy to read the field reduction as an amendment to the existing technical standards. The change is structurally larger than that. The MiFIR transaction-reporting regime applied in 2018 under EU law and later became retained EU law, now assimilated law, after EU exit. HM Treasury plans to repeal the UK MiFIR transaction-reporting provisions and their implementing technical standards before 3 April 2028. The FCA’s made instrument (contained in PS26/15 Appendix 2, made under FSMA 2000 rule-making powers) will replace them with new transaction-reporting Handbook chapters.

The practical consequence is that firms should map their obligations to the FCA’s own rules and the new reporting schema, and stop treating today’s onshored Regulation and its technical standards as the fixed reference point. The underlying obligation is familiar: UK MiFIR requires firms to report complete and accurate details of reportable transactions to the FCA no later than the close of the following working day. What is moving is the instrument that carries the field definitions and validation logic, which is why the FCA is consulting separately on the schema in October 2026. Teams that treat this as a Handbook change, with the version control and testing that implies, will be closer to ready than teams that wait for a marked-up technical standard.

Fewer fields, but a larger remapping job

The headline reduction from 65 to 52 fields understates the implementation work required in the year before go-live. A reporting engine does not simply stop populating thirteen columns; the fields that remain have to be re-mapped against the new schema, the internal data lineage feeding each one has to be re-validated, and every reconciliation and exception rule that references a removed field has to be found and retired. Firms that built their MiFIR reporting on hard-coded field positions instead of a mapped data dictionary will feel this most.

The FCA has also framed the change as improving consistency in how key fields are populated, which signals that some retained fields carry tighter or clarified expectations, so treating them as a pure carry-over would be a mistake. The detail lands with the October 2026 schema and validation consultation. Until that publishes, the safe working assumption is that the final 52-field set must be mapped and tested as a re-specification, not treated as a simple subset of the current 65 fields. Whether a firm’s current logic survives that re-specification is exactly the question the schema consultation is designed to answer.

Foreign exchange derivatives leave UK MiFIR; UK EMIR must be assessed separately

Removing foreign exchange derivatives from MiFIR transaction reporting is the change most likely to be misread. Scope-out of MiFIR transaction reporting means the obligation to submit a transaction report to the FCA falls away for these contracts; any continuing UK EMIR obligation is a separate question requiring assessment by entity and transaction.

UK EMIR coverage must be assessed by entity and transaction rather than assumed. During the implementation period, the FCA will refrain from supervisory action for omitted UK MiFIR FX reports only where the firm is subject to UK EMIR reporting requirements. Firms outside UK EMIR, including UK branches of third-country firms, must continue applicable UK MiFIR reporting until 3 April 2028. From 3 April 2028, the UK MiFIR exclusion covers currency options, futures, swaps, forward rate agreements and other currency derivatives settled physically or in cash, as defined in PS26/15.

The seven million instruments that fall out of scope

The EU-only instrument measure is expected to save about £32m a year by removing reporting obligations for roughly 7 million financial instruments that are tradeable only on EU trading venues. The larger quantified annual saving comes from removing FX derivatives; CP25/32 Annex 2 sets out the specific figure. The scope boundary is precise and worth stating exactly: it is instruments traded solely on EU venues, spanning equities, bonds and certain derivatives, that leave scope. An instrument that is also admitted to trading or traded on a UK venue, or that meets the other MiFIR reportability tests, is a different case, and firms should not read the carve-out as covering everything with an EU nexus.

During the implementation period, EU-only instruments can be identified using FCA FIRDS instrument reference data per the implementation guidance in PS26/15. Instruments tradeable on a UK venue remain within the new geographic scope. Firms should therefore base implementation-period scope controls on the FCA FIRDS test and any October 2026 update rather than on a generic ‘EU nexus’ classification.

A shorter window to correct historical errors

From 3 August 2026, the FCA’s default supervisory expectation is three years of back reports, unless it instructs otherwise. The FCA may exceptionally require up to five years of back reports. Existing five-year transaction and order record-retention obligations remain unchanged.

The requirement to correct inaccurate or omitted reports also remains. Remediation programmes should therefore use three years as the default only after checking for any FCA direction and should preserve the records needed to satisfy an exceptional five-year request.

The timeline and what the flexible supervisory approach allows

The new rules take effect on 3 April 2028. That is the date the reduced field set, the FX carve-out and the narrowed instrument scope become the standard. The FCA has deliberately given firms a long runway because the changes touch reporting systems, vendor releases and testing cycles that cannot be turned around quickly.

PS26/15 limits the implementation-period supervisory approach to the areas identified in Chapter 6. Immediate relief includes the three-year back-reporting default, non-reporting of EU-only instruments and specified corporate-event activity; early cessation of FX reporting is conditional on the firm being subject to UK EMIR. The FCA also identifies specified transaction-report fields, guidance and trading-venue or reference-data items for supervisory flexibility, with some validation-rule changes planned for October 2026. This is not blanket permission to adopt the 52-field schema or all final rules before 3 April 2028.

What UK EMIR and UK SFTR reporters actually get

Because PS26/15 sits within a broader cross-regime programme, its specific scope is worth stating plainly. PS26/15 finalises changes to MiFIR transaction reporting. It does not change UK EMIR or UK SFTR reporting obligations. Reporters under those regimes get no new rule from this policy statement.

What they get instead is a direction of travel. The FCA and the Bank of England have set a shared goal of a streamlined and harmonised framework for transaction reporting across the UK MiFIR, UK EMIR and UK SFTR regimes, a goal first set out in the November 2025 consultation CP25/32. To inform it, the two authorities established the cross-industry Transaction and Post-trade Reporting Harmonisation Taskforce, which held its inaugural meeting in July 2026 and runs through three working groups covering policy, strategy and architecture. The Taskforce is explicitly not a decision-making or formal advisory body, its outputs are not binding on the authorities, and it does not replace consultation. In other words, it shapes future proposals; it does not itself change what an EMIR or SFTR reporter files.

For those teams the practical stance is watchful: monitor the Taskforce and keep current reporting steady. Firms with material derivatives or securities financing books can follow its work and respond when consultations follow, while running their current EMIR and SFTR reporting exactly as it is today. The EU is running its own parallel simplification of EMIR, MiFIR and SFTR reporting, which we cover in our note on the ESMA transaction reporting simplification, and UK and EU firms should not assume the two programmes will land in the same place. The UK’s MiFIR changes are the concrete deliverable today; the cross-regime harmonisation remains a programme to watch.

Frequently Asked Questions

Does PS26/15 change what we report under UK EMIR or UK SFTR?

No. PS26/15 finalises changes to UK MiFIR transaction reporting only. UK EMIR and UK SFTR obligations are unchanged by this policy statement. The cross-regime work sits with the Transaction and Post-trade Reporting Harmonisation Taskforce, which informs future proposals and does not change current reporting.

If foreign exchange derivatives leave MiFIR transaction reporting, do we stop reporting them entirely?

Not as a blanket rule. During the implementation period, the FCA will refrain from supervisory action for omitted UK MiFIR FX reports only where the firm is subject to UK EMIR reporting requirements. Firms outside UK EMIR must continue applicable UK MiFIR reporting until 3 April 2028. From that date, the UK MiFIR exclusion applies to currency derivatives as defined in PS26/15. Assess UK EMIR separately by entity and transaction before switching off any feed.

Our instruments are dual-traded on a UK venue and an EU venue. Do they fall within the seven million that leave scope?

The carve-out targets instruments tradeable only on EU trading venues. An instrument also traded or admitted to trading on a UK venue is a different case and may remain reportable. The determinant is how the instrument is classified in instrument reference data on the relevant date, so the reference data logic has to make that distinction reliably.

What does the flexible supervisory approach let us do before April 2028?

The approach is limited to the areas specified in PS26/15 Chapter 6; it does not permit blanket early adoption of the 52-field schema. Before changing a report, map the proposed change to the relevant Chapter 6 provision, check any UK EMIR condition and confirm whether the necessary validation-rule change has taken effect.

Does the shorter back reporting period mean we can stop correcting older errors now?

The FCA’s three-year default supervisory expectation applies from 3 August 2026, unless the FCA instructs otherwise. It may exceptionally require up to five years of back reports for serious reporting failings, and five-year record-retention obligations remain. Do not close an existing remediation exercise without checking for FCA directions and preserving the records needed for a possible five-year request.

Will there be a new reporting schema and validation rules to build against?

Yes. In October 2026, the FCA intends to publish a draft schema, draft validation rules and new guidelines for consultation. Use the draft schema, validation rules and guidelines for provisional design and testing, but treat those technical materials as changeable until finalised; the 52-field legal field set is already contained in the FCA’s made rules in PS26/15 Appendix 2.

Who is affected by the removal of foreign exchange derivatives from scope?

The FCA says the FX derivatives change reduces costs for more than 400 firms. Any firm that currently files FX derivative transactions in its MiFIR reports should scope the change, but the wider point applies to all MiFIR reporters: the field and instrument changes affect the whole reporting population and reach well beyond FX desks.

Related Articles

• MiFIR Transaction Reporting: how the UK MiFIR transaction reporting obligation works, who reports and what the fields capture.
• EMIR Reporting Explained: the separate derivative-reporting regime that may continue to capture an FX derivative where the relevant counterparty is subject to UK EMIR.
• SFTR Reporting Explained: securities financing transaction reporting, one of the three regimes in the harmonisation programme.
• ESMA Transaction Reporting Simplification: the EU’s parallel effort to simplify EMIR, MiFIR and SFTR reporting.
• UK Bond Consolidated Tape: the FCA’s wider programme of UK capital markets and transparency reform.

Key Takeaways

• PS26/15 was published on 3 August 2026 and takes effect on 3 April 2028; the field, FX and instrument changes become the standard on that date.
• MiFIR transaction reports move from 65 to 52 fields; plan for a re-mapping and re-testing programme, not a simple deletion of thirteen columns.
• Foreign exchange derivatives leave the scope of UK MiFIR transaction reporting on 3 April 2028. During the implementation period, the FCA will refrain from supervisory action for omitted UK MiFIR FX reports only where the firm is subject to UK EMIR reporting requirements; firms outside UK EMIR must continue applicable UK MiFIR reporting until commencement.
• Around 7 million instruments tradeable only on EU venues leave scope, saving about £32m a year; dual-traded instruments turn on instrument reference data classification.
• The default back-reporting expectation is three years from 3 August 2026, but the FCA may exceptionally require up to five years; five-year record retention and the accuracy obligation remain unchanged.
• Use the October 2026 draft schema and validation consultation for impact assessment and provisional design; finalise production implementation only against the FCA’s final technical materials.
• UK EMIR and UK SFTR reporting are unchanged by PS26/15; the harmonisation Taskforce shapes future proposals and is not binding.
• Implementation-period supervisory flexibility is limited to the specified Chapter 6 areas; do not adopt the complete 52-field schema or all final rules early.

Sources and References

• FCA press release: FCA finalises rules to cut firms’ transaction reporting costs by over £100m a year (3 August 2026)
• FCA PS26/15: Improving the UK transaction reporting regime
• FCA CP25/32: Improving the UK transaction reporting regime (November 2025)
• FCA and Bank of England: Terms of Reference for the Transaction and Post-trade Reporting Harmonisation Taskforce (2 April 2026)
• UK MiFIR Article 26: the current UK obligation to report transactions
• UK RTS 22: the current UK technical standards for transaction reporting
• FCA PS26/15 Appendix 2: the FCA’s made instrument and new transaction-reporting Handbook rules

What MiFIR reporters should put on the calendar now

The saving is real, but it is earned through work that has to happen before it arrives. Between now and 3 April 2028, MiFIR reporters need a reference data view that can identify the EU-only instruments leaving scope, an EMIR reconciliation for the FX derivatives coming out, and a field-mapping design ready to test against the schema the FCA consults on in October 2026. The October 2026 consultation is the next published milestone for draft technical materials. Use it for detailed impact assessment and provisional design; finalise production mappings only against the FCA’s final schema, validation rules, guidelines and consequential Handbook amendments.

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.