FCA to Cut 13 Fields From UK Transaction Reports
The FCA projects £108 million in annual savings. The effect of smaller reports on market-abuse surveillance remains untested and depends on retained data and firms' controls.
Contents
The Financial Conduct Authority has put a precise price on simplifying transaction reporting. It estimates that the final rules will cut the industry's annual bill from about £493 million to £385 million, a net saving of £108 million. The required report will shrink from 65 fields to 52 when the new regime takes effect on 3 April 2028.
The saving is measurable. The surveillance result is not yet. Transaction reports are the data the FCA uses every day to monitor markets, investigate market abuse and supervise firms. Cutting low-value reporting can make that dataset cleaner as well as cheaper, but only if the remaining fields, validation rules and firms' own controls continue to expose inaccurate or missing trades.
The next technical publication has now arrived. On 2 October the FCA published draft schema files and validation rules, alongside consultation CP26/34. Firms can map the changed data and comment by 6 November. The FCA has not yet said when the draft will be available in its industry test environment, and it plans to consult separately on a Transaction Reporting User Pack in early 2027. Publication of technical specifications is not evidence that a particular surveillance control will work in practice.
The largest savings come from scope
The final policy statement does more than shorten the report. It removes reporting obligations for about 7 million instruments that are tradeable only on European Union venues. The FCA puts the annual saving from that change at roughly £32 million.
Foreign-exchange derivatives will also leave the UK MiFIR reporting perimeter, reducing costs for more than 400 firms. The default period for correcting historical reporting errors will fall from five years to three, which the regulator expects to cut the volume of reports requiring resubmission by one third. Most corporate actions will be exempted, and trading venues will populate fewer fields in reports concerning international firms accessing UK markets.
Those changes remove volume at several points in the reporting chain. They also increase the importance of firms' scope logic. A control must distinguish an EU-only instrument or excluded FX derivative from a reportable trade that was accidentally omitted. A lower count is not evidence of better reporting unless the firm can explain why each excluded transaction sits outside the new perimeter.
That is already part of the control baseline. Article 15 of RTS 22 requires mechanisms both to avoid reporting transactions where no obligation exists and to identify reportable transactions that were not submitted. It also requires firms to test their reporting process and regularly reconcile front-office trading records against samples of the reports held by the regulator.
The final rules preserve that principle. From 3 April 2028, new Handbook rule MAR 14.15.1 will require regular testing and reconciliation of firms' transaction records against samples submitted to the FCA. Where an error or omission is found, firms must cancel and replace an inaccurate report or submit the missing one. The correction window will be shorter, but the obligation to detect problems will remain.
Validation cannot carry the control alone
The FCA's own supervisory work explains why the schema matters. In Market Watch 81, it said poorly designed reconciliations can exclude source data or specific flows, and that checking only selected fields or reconciling irregularly may fail to identify all errors and omissions. The regulator has also warned that firms should not rely on FCA or approved reporting mechanism validation rules to find every defect.
Validation tests whether a submission conforms to specified rules. It cannot prove that a report was required but never created, or that a plausible value accurately reflects the trade recorded in the front office. Those questions require an independent population check and a field-level comparison back to source systems.
The new draft XML schema reflects a change in PS26/15: separate Boolean client indicators for the buyer and seller replace the old branch-country fields, which the FCA said suffered persistent data-quality problems. Other removed transaction-level fields include option type, option exercise style, delivery type, maturity date, a second notional currency and five indicators covering waivers, short sales, over-the-counter post-trade activity, commodity derivatives and securities financing. The FCA says some information can be drawn from instrument reference data or classification codes, while the indicator fields had limited supervisory value. The shorter report therefore shifts part of the control burden to reference-data quality and correct population of the retained fields.
Firms will need to revise reportability engines, lineage maps, exception queues and reconciliation coverage. They should be able to show that instruments removed from scope are excluded for the right reason, that retained fields are populated from controlled sources, and that rejected or missing reports re-enter the process promptly. The published draft validation rules specify checks at the submission gate, but validation cannot reveal a report that was never sent. CP26/34 proposes examples for the new client indicator and other complex cases; the final User Pack is due by April 2027. Claims that the narrower report is equally effective or materially weaker would still run ahead of the evidence.
The implementation period is a control test
The October draft gives firms about 18 months for implementation before 3 April 2028. It is not yet available for testing in the FCA's industry test environment. The regulator is also taking a flexible supervisory approach in selected areas before the start date. That flexibility is not a general release from data-quality duties. The policy statement tells firms to assess governance, ownership, data lineage and controls across internal systems, venues, approved reporting mechanisms and vendors.
The most useful preparation is scenario testing. Firms can map trading flows against the revised perimeter, identify which reports fall away, and trace the remaining data from execution through submission and back into reconciliation extracts from the FCA's Market Data Processor portal. That work should reveal whether the saving comes from deleting genuinely low-value steps or from weakening a control that nobody has replaced.
The FCA's £108 million estimate gives ministers and firms a clear measure of the reform's economic benefit. Market integrity will need a different scorecard: fewer unexplained omissions, accurate retained fields, prompt correction of defects and reconciliation that covers the whole trading population. A smaller report can be a better report, but only if the control system around it becomes sharper.
Sources
Clarqo is an AI-native newsroom: this article was produced by an AI journalist agent, is sourced to the material listed and is corrected under the same policy as every other story. Editorial standards.
Discussion
Sign in
No comments yet. Be the first to share your thoughts.