Article 317
Loss data set
For the purpose of paragraph 1, institutions shall:
include in the loss data set each operational risk event recorded during one or multiple financial years;
use the date of accounting for including losses related to operational risk events in the loss data set;
allocate losses and recoveries related to a common operational risk event or related operational risk events over time and posted to the accounts over several years, to the corresponding financial years of the loss data set, in line with their accounting treatment.
Institutions shall also collect:
information about the reference dates of operational risk events, including:
the date when the operational risk event happened or first began (“date of occurrence”), where available;
the date on which the institution became aware of the operational risk event (“date of discovery”);
the date or dates on which an operational risk event results in a loss, or the reserve or provision against a loss, recognised in the institution’s profit and loss accounts (“date of accounting”);
The level of detail of any descriptive information shall be commensurate with the size of the gross loss amount.
For the purposes of this Article, institutions shall ensure the soundness, robustness and performance of their IT systems and infrastructure necessary to maintain and update the loss data set, in particular by ensuring all of the following:
their IT systems and infrastructure are sound and resilient and that that soundness and resilience can be maintained on a continuous basis;
their IT systems and infrastructure are subject to configuration management, change management and release management processes;
where an institution outsources parts of the maintenance of its IT systems and infrastructure, the soundness, robustness and performance of the IT systems and infrastructure is ensured by confirming at least the following:
its IT systems and infrastructure are sound and resilient and that soundness and resilience can be maintained on a continuous basis;
the process for planning, creating, testing and deploying the IT systems and infrastructure is sound and proper with reference to project management, risk management, governance, engineering, quality assurance and test planning, systems’ modelling and development, quality assurance in all activities, including code reviews and, where appropriate, code verification, and testing, including user acceptance;
its IT systems and infrastructure are subject to configuration management, change management and release management processes;
the process for planning, creating, testing and deploying the IT systems and infrastructure and contingency plans is approved by the management body or senior management and the management body and senior management are periodically informed about the IT systems and infrastructure performance.
EBA shall submit those draft regulatory technical standards to the Commission by 10 January 2026.
Power is delegated to the Commission to supplement this Regulation by adopting the regulatory technical standards referred to in the first subparagraph of this paragraph in accordance with Articles 10 to 14 of Regulation (EU) No 1093/2010.