FCA — PS26/2: Operational incident and third-party reporting
Tag: S-2026-03-fca-ps26-2
Type: report
Author(s): Financial Conduct Authority, jointly with PRA and Bank of England
Date of source: 2026-03 (joint Policy Statement published). Obligations come into force 18 March 2027.
Date ingested: 2026-05-17
Authority weight: high — joint UK regulator Policy Statement.
Raw file: Open Brain corpus snapshot at /_raw_sources/open-brain-2026-05-17-corpus.md.
What it claims
PS26/2 sets out operational incident reporting and third-party reporting obligations for FCA-regulated firms, jointly aligned with PRA and Bank of England policy. Obligations commence 18 March 2027. The accompanying “Operational resilience: insights and observations one year on” review (April / May 2026) follows firms’ self-assessments after the 31 March 2025 transition deadline. The regulatory shift framed in PS26/2 is from one-time compliance exercises to demonstrating continuous adherence to impact tolerances.
Notable quotes
None captured verbatim — fca.org.uk fetches were blocked.
What’s speculative vs. asserted
- Asserted: PS26/2 exists, jointly authored, in-force 18 March 2027.
- Speculative: specific reporting templates and incident-classification thresholds — not captured in the corpus.
Topics this feeds
Open questions raised
- Interaction between PS26/2 reporting obligations and DORA major-incident notification timing for cross-border firms.
- Whether AI-system incidents will be in-scope of PS26/2 operational incident reporting.
Ingestion note
Consolidates Open Brain thoughts dated 5/10, 5/9, 5/5, 4/20, 4/3, 4/2 (the joint Policy Statement).