FCA and PRA publish final rules on operational incident reporting: firms have to ready by 18 March 2027

TLT picks out the key points you shouldn't miss...

What’s this about?

The FCA and PRA have created a unified framework for reporting serious operational incidents across regulated firms, including payment services firms, through the publication of policy statements and finalised guidance (PRA’s PS7/26 and SS1/26 / FCA’s PS26/2 and FG26/3). The policy statements also have rules on material third party reporting.  For more details on the new Third Party reporting regime, read our update here.

The reporting requirements are driven by an increasing frequency and sophistication of attacks on the financial sector, including attacks affecting the third parties on which firms rely, combined with the rapid pace of technological change including AI and the growing interconnectedness of the industry. The resulting data will help the regulators triage incidents at pace, identify wider market disruption, and over the medium to long term, develop thematic insights to improve industry practices and inform future interventions.

The operational incident reporting requirements come into force on 18 March 2027, so firms have less than 12 months to assess which reporting requirements apply to them, and what systems and controls need to be put in place to ensure you are fully prepared before the new regimes coming into force.

Partner in our Financial Services Regulation team, Andrzej Wieckowski says...  

"These requirements mean that regulators are no longer asking whether firms have incidents, they are asking how quickly firms recognise them, understand their impact and act. Operational resilience is now proved in real time. Firms that cannot identify, assess and escalate serious incidents quickly will be engaging with regulators at the worst possible moment.”

The points not to miss...

Who is impacted?

The new rules apply to all regulated solo regulated, dual regulated and payment services providers (PSPs).

Key points to note:

  • Dual regulated firms and solo regulated enhanced SMCR firms and PSPs will be enhanced reporting firms
  • PSPs have additional reporting requirements
  • Other solo regulated firms will be standard reporting firms
What is an operational incident?

The FCA and PRA have aligned their definition of ‘operational incident’ to include either a single event or a series of linked events that disrupts the firm’s operations such that one or more of the following occurs:

  • the delivery of a service to an end user external to the firm is disrupted; or
  • the availability, authenticity, integrity, or confidentiality of information or data relating or belonging to such an end user is impacted.

Firms are not expected to report on potential or uncrystallised events.

Key points:

  • The definition covers single events or a series of linked events, including cascading failures and third-party incidents.
  • An incident does not need to affect an Important Business Service to be reportable.
  • Near misses are not reportable under this regime but may still need notifying under Principle 11 or general notification rules.
  • Firms must use judgement, based on information available at the time; thresholds are not prescriptive or quantitative
  • End user can be retail or business customers, other legal entities, trustees, market participants, supervisory regulators, and members of the firm’s group.
When an operational incident must be reported

Firms must report when they reasonably believe an incident poses a risk to one or more statutory objectives:

  • Consumer harm (FCA): risk of intolerable harm from which consumers cannot easily recover.
  • Safety and soundness (FCA and/or PRA).
  • Market stability, integrity or confidence in the UK financial system (FCA).
  • Policyholder protection (PRA, for insurers).
  • the stability of the UK financial system (PRA). This only applies to CRR firms that are Other Systemically Important Institutions
  • PSPs - Under the Payment Services Regulations, PSPs must report a "major operational or security incident." Under the new regime, these concepts are mapped directly to the FCA's framework i.e. an operational or ‘security incident' would be an operational incident that must be reported

Key points:

  • Even though the reporting thresholds are broadly aligned between the FCA and PRA, they are not identical. As such, dual-regulated firms will need to assess the FCA and PRA threshold independently
  • The PRA and FCA provide guidance on factors that firms could consider when assessing what their threshold would be. The factors are not exhaustive or prescriptive but rather examples, which may help firms calibrate the threshold for reporting.
  • PSPs, when considering the threshold for reporting an operational incident, are also expected to consider:
    • the proportion of transactions affected;
    • the proportion and nature of payment service users affected;
    • the service downtime; and
    • the impact on their distribution channels.

The FCA has disapplied the EBA's Guidelines on Incident Reporting under the Payment Services Directive for PSPs.

Firms should not forget that Principle 11 (FCA) and Fundamental Rule 7 (PRA) still apply i.e. they must disclose to the FCA and/or PRA anything relating to the firm that either regulator would expect notice of. Therefore, incidents below the threshold may be reportable - not via this incident reporting arrangement but rather via the firm’s normal supervisory contact.

Standard vs enhanced incident reporting

Firms must submit reports via FCA Connect, irrespective of whether they are a standard or enhanced reporting firm or dual regulated

Standard reporting:

  • Firms must submit the notification within 24 hours of having determined that the incident meets the thresholds.
  • Firms subject to standard reporting will not have to update their submission. Occasionally, the FCA may engage further with a firm depending on the quality of the information submitted, or the severity of the incident. Firms are not required to update a standard incident report once it has been submitted.

Enhanced reporting requires updates across the lifecycle:

Initial phase

  • Reports made as soon as practicable, generally within 24 hours of threshold determination.
  • PSPs must report within 4 hours of detection.

Intermediate phase

  • Firms must submit updates where there is a significant change (e.g. worsening impact, third party origin identified, BCP activation).

Final phase

  • Firms must submit within 30 working days of resolution (up to 60 in exceptional circumstances); and
  • include root cause, lessons learned and remediation actions.
Governance and accountability

Firms should develop or adapt internal incident assessment frameworks to map against the relevant regulatory thresholds that apply to you.

  • For PRA regulated firms, overall responsibility for the incident reporting framework is expected to sit with SMF24 (Chief Operations) or an equivalent SMF.
  • SMF approval of individual incident reports is not required, but senior management oversight must be demonstrable.
  • Incident reporting does not replace supervisory engagement; firms may still need to contact supervisors directly in serious cases.
What firms should be doing now

In practical terms, firms should:

  • determine or recalibrate incident criteria that must be escalated;
  • map incident management processes to the new threshold tests and timelines;
  • identify whether they are standard or enhanced reporting firms;
  • confirm internal accountability, escalation and sign off structures;
  • prepare systems and data to support Connect reporting;
  • test playbooks for third-party incidents and cascading failures, especially where PSPs or critical suppliers are involved.

How TLT can help

We have prepared more detailed summaries for:

  • Dual regulated CRR firms
  • Solo regulated enhanced reporting firms (non-PSPs)
  • PSPs
  • Solo regulated standard reporting firms

If you would like a copy, then please email Nikesh Shah.

If you would like to discuss what these new regimes mean in practice, including next steps regarding the measures your firm should put in place to ensure it is ready for this new regime, please get in touch.

At a glance...

Publication link PS26/2 – Operational Incident and Third Party Reporting (FCA)

PS7/26 – Operational resilience: Operational Incident and Third Party Reporting (PRA / Bank of England)

FG26/3 – Finalised guidance: Operational incident reporting (FCA)

Supervisory Statement – Operational resilience: incident reporting (PRA)
Published date 18 March 2026
Who has published it? Financial Conduct Authority (FCA); Prudential Regulation Authority (PRA)
Publication type Final rules (Policy Statements) and finalised guidance
Any key dates? Rules come into force 18 March 2027. Two-year post-implementation review to follow.
What's it relevant to? Operational resilience; operational incident reporting; payments; e-money; banks; building societies; FCA‑regulated firms

Author: Hannah Stanley

This publication is intended for general guidance and represents our understanding of the relevant law and practice as at April 2026. Specific advice should be sought for specific cases. For more information see our terms & conditions.

No items found.

No items found.
Date published
24 Apr 2026

Abstract overlapping curved shapes in varying shades of violet and purple on a solid violet background.

Legal insights & events

Keep up to date on the issues that matter.

Abstract yellow background with overlapping translucent olive green curved shapes.

Follow us

Find us on social media

No items found.
No items found.