Skip to main content
DORA Auditor

guide

DORA Article 16: Who Qualifies for the Simplified Framework

DORA Article 16 exempts four named entity types from Articles 5-15, but not from incident reporting, testing, or third-party rules. Updated October 2026.

DORA Auditor Editorial Team·Published

DORA Article 16 lets a named list of smaller or exempted financial entities, small and non-interconnected investment firms, certain exempted payment and e-money institutions, specific institutions exempted under Directive 2013/36/EU, and small occupational pension institutions, replace the full Articles 5-15 framework with a lighter, still-documented one. It is not a general small business exemption, and it does not touch incident reporting, testing, or third-party rules.

What Article 16 actually exempts, and what it does not

Article 16(1) is narrow by design: "Articles 5 to 15 of this Regulation shall not apply to" the entities it names. That single sentence is the entire scope of the exemption. It removes the detailed governance and control requirements in DORA's ICT risk management chapter, things like a dedicated ICT risk control function, granular policy documentation across eight domains, and the full audit cadence the baseline framework demands.

It does not touch anything else in the regulation. Chapter III (incident reporting), Chapter IV (resilience testing), Chapter V (third-party risk), and Chapter VI (information sharing) all still apply in full to a simplified-framework entity, subject only to the general proportionality principle in Article 4 that applies to every in-scope firm regardless of size. An entity that qualifies for Article 16 still classifies and reports major incidents, still maintains a register of ICT third-party arrangements, and still runs a proportionate testing programme. The exemption is scoped to one chapter, not the regulation as a whole.

The four entity categories named in Article 16(1)

Only entities that fall into one of these categories can use the simplified framework:

  1. Small and non-interconnected investment firms, as defined under the Investment Firms Regulation thresholds (small balance sheet, limited interconnectedness with the wider financial system, and none of the factors that would otherwise classify the firm as Class 2 or systemic).
  2. Payment institutions exempted under Directive (EU) 2015/2366 (PSD2), where the Member State has granted the small-institution exemption from full authorisation.
  3. Electronic money institutions exempted under Directive 2009/110/EC, on the same small-institution basis.
  4. Institutions exempted under Directive 2013/36/EU (the Capital Requirements Directive), specifically those for which the Member State has not applied the option in Article 2(4) of DORA to bring them back into full scope.
  5. Small institutions for occupational retirement provision (IORPs), as defined in the IORP II Directive.

If an entity does not fall cleanly into one of these categories, it is in the full Articles 5-15 regime regardless of headcount or revenue. A mid-sized investment firm that fails the "small and non-interconnected" test, or a payment institution that holds a full PSD2 authorisation rather than the small-institution exemption, gets no benefit from Article 16. There is no case-by-case waiver process; eligibility turns on the entity's status under its own sectoral directive, not on a separate DORA application.

What the simplified framework still requires

Article 16(2) lists the core obligations that survive even where Articles 5-15 do not apply. A qualifying entity must still maintain:

  • A sound, documented ICT risk management framework, covering the ICT systems, protocols, and tools the entity actually depends on.
  • Continuous monitoring of the security and functioning of ICT systems, with mechanisms to minimise their impact on ICT risk.
  • Business continuity and disaster recovery arrangements adequate to the entity's size, risk profile, and the criticality of the services it provides.
  • Identification of ICT third-party dependencies, so the entity knows which of its ICT systems rely on which providers.
  • A mechanism for incorporating lessons learned from ICT-related incidents and from testing, feeding back into the framework rather than sitting in a closed report.

The framework must be reviewed periodically and after major ICT-related incidents, following supervisory instructions, and the entity must be able to produce a report on that review for the competent authority on request. In practice this is a scoped compliance programme, not a checklist waiver: an entity still needs policies, an assigned owner, and evidence of ongoing review, just not the full eight-domain structure Article 5 requires of larger institutions.

The technical standards behind Article 16

Article 16(3) requires the European Supervisory Authorities, in consultation with ENISA, to develop regulatory technical standards further specifying the content of the simplified framework. That mandate produced Commission Delegated Regulation (EU) 2024/1774, which sets out the detailed elements of both the full and the simplified ICT risk management frameworks. The RTS is explicit that the simplified framework's proportionate character must not be eroded by the technical detail it adds: the obligations in Article 16(2) are specified, not expanded into a parallel version of the full framework.

How to check whether your entity qualifies

  1. Confirm your sectoral status first. Eligibility for Article 16 is a consequence of status under the Investment Firms Regulation, PSD2, Directive 2009/110/EC, Directive 2013/36/EU, or IORP II, not a DORA-level test on its own. If that status changes (the firm grows past the small and non-interconnected thresholds, for example), Article 16 eligibility changes with it.
  2. Check whether your Member State disapplied the Article 2(4) option for CRD-exempted institutions. Some Member States have chosen to bring these institutions back into full DORA scope, which overrides the Article 16 exemption for that category.
  3. Document the review, even while simplified. Supervisors can request the review report at any time; an entity that assumed simplified status meant no paperwork will not have one ready.
  4. Re-test eligibility on a schedule, not once. A firm that qualified as small and non-interconnected at authorisation can lose that status as it grows, and nothing in DORA grants a grace period for re-scoping into the full framework.
  5. Map what Article 16 does not cover. Run the DORA Readiness Score against the full set of DORA requirements rather than assuming simplified ICT risk management means simplified DORA compliance generally.

Common mistakes entities make with Article 16

The most frequent error is treating Article 16 as a general small-business carve-out. It is not: a small fintech that is not a payment institution, e-money institution, or small IORP, and is not a "small and non-interconnected" investment firm under the statutory test, gets no benefit from this article no matter how few people it employs. The second most common mistake is assuming the exemption reaches beyond ICT risk management, entities have been caught out assuming simplified status also meant a lighter incident-reporting timeline or an automatic exemption from third-party contract requirements, neither of which Article 16 provides. The third is documentation drift: because the simplified framework has fewer mandated components, firms sometimes stop maintaining evidence altogether, leaving nothing to show when a competent authority asks for the review report Article 16(2) requires.

Frequently asked questions

What is DORA Article 16's simplified ICT risk management framework?
Which entities can use the DORA simplified framework?
Does Article 16 exempt a firm from DORA incident reporting or third-party rules?
Is Article 16 a general exemption for small businesses?
What must a simplified-framework entity still document?
Can an entity lose its Article 16 eligibility?

Sources

Last updated: 5 October 2026.

#ict-risk-management#article-16#simplified-framework#investment-firms#proportionality

More from the blog