Separate the 2019 reform from current implementation work

CRD V: Identify the requirements that still matter to your institution

CRD V remains a useful search term, but a current compliance project needs more than a historical checklist.

  • 01A versioned applicability register for the agreed entities
  • 02Governance and remuneration gaps linked to evidence
  • 03Clear responsibility for interpretation, implementation and approval
  • 04A handover that distinguishes completed work from open decisions
11+Years of experience
120+Employees
540+Projects
ISO 27001certified

CRD V is an amendment to a framework, not a complete current rulebook

CRD V is Directive (EU) 2019/878, which amended the Capital Requirements Directive, Directive 2013/36/EU. Its subjects include prudential governance, remuneration, certain holding-company arrangements and supervision. It formed part of the 2019 banking package alongside separate instruments such as CRR II and BRRD II. Obligations should be traced to the relevant instrument rather than attributed indiscriminately to CRD V.

For a current project, the starting point is the applicable version of the framework and its national implementation. CRD VI, Directive (EU) 2024/1619, and CRR III, Regulation (EU) 2024/1623, must be considered where relevant. Their provisions, implementation and application arrangements are not interchangeable. For example, the newer harmonised third-country branch regime should not be described as a change introduced by CRD V. Article 2 of CRD VI contains staged application arrangements, so one package-wide date cannot determine every project deadline.

The initial scope needs the relevant legal entities, jurisdictions, group structure, activities, existing policies and supervisory findings. Your legal and compliance owners confirm applicability and interpretation; process owners provide the agreed evidence and decide on implementation. Where a question needs legal advice or supervisory clarification, it is recorded and assigned rather than treated as resolved.

Depending on the agreed assignment, outputs include an applicability register, a gap-and-evidence map, revised control or policy proposals and an owned implementation plan. Technical workflow or reporting automation is a separate scope decision. Preparing documentation does not obtain regulatory approval or establish complete compliance. The handover identifies the legal version used, reviewed evidence, remaining gaps and who must decide each open issue.

Jurisdiction and legal review: This overview is not a legal opinion or an exhaustive implementation timetable. Applicability, national transposition and relevant application arrangements require current review for the institution. Regulatory or supervisory decisions remain with the competent authority.

6 service modules

Applicability, governance and implementation evidence for the agreed scope

01

Legal and operational applicability mapping

A versioned register connects relevant entities and topics with the legal source, national implementation and accountable reviewer.

  • Separate CRD V changes from later amendments and other instruments
  • Record entity, jurisdiction, source version and unresolved interpretation
  • Assign legal confirmation before treating an obligation as applicable
02

Governance and control gap assessment

A gap map compares the agreed governance requirements with documented responsibility and selected evidence from actual operation.

  • Map decision rights, escalation and oversight to responsible roles
  • Distinguish a policy statement from evidence that the process operates
  • Describe each gap with impact, owner and a completion check
03

Suitability and remuneration process review

Process proposals address the in-scope suitability and remuneration questions without turning historical changes into universal new requirements.

  • Identify the applicable suitability and remuneration framework
  • Trace identification, decisions and records to responsible owners
  • Keep exemptions and proportionality subject to specific legal assessment
04

Risk and capital governance evidence

An evidence map connects the agreed governance processes with information, decisions and controls required for the institution's scope.

  • Clarify boundaries between CRD governance and separate CRR calculations
  • Review document ownership and consistency of selected evidence
  • Record unresolved dependencies on risk, finance and legal teams
05

Reporting and evidence workflow design

An agreed workflow makes source data, review, approval and retention traceable. Automation is proposed only where inputs and rules are sufficiently defined.

  • Identify the actual submission or internal reporting obligation
  • Document source, review, approver and correction handling
  • Test a selected case before expanding technical automation
06

Implementation planning and change handover

An implementation plan turns reviewed findings into assigned actions and a process for handling later legal or organisational changes.

  • Prioritise actions by applicability, risk and dependencies
  • Agree acceptance evidence and escalation for unresolved questions
  • Hand over the register with version and change responsibilities

Example: What a useful obligation register records

The fictional example shows the information needed before a historical CRD V topic becomes an institution-specific action. It deliberately contains unresolved statuses rather than invented legal conclusions or submission dates.

Illustrative review structure; not a complete regulatory mapping or legal assessment.
Review itemInput requiredCurrent statusCompletion check
Applicable legal basisEntity, jurisdiction, source version and national implementationApplicability not yet confirmedDesignated legal owner records the reviewed basis and exclusions
Governance processApproved responsibility map and selected operating recordsPolicy available; operating evidence not reviewedReviewer traces a decision and escalation through the actual process
Remuneration treatmentStaff population, policy and relevant proportionality conditionsSpecific treatment requires assessmentAccountable reviewer documents the applicable rule and its rationale
Submission or internal reportConfirmed obligation, data source, approver and correction routeWorkflow not yet testedA selected case is reconciled from source to reviewed output

5 phases

Start with the legal version and finish with a traceable decision

The assignment is handed over when every agreed review item has a documented status, its evidence or missing input can be found, and remaining actions have an accountable owner. Findings are not marked resolved solely because a new policy has been drafted.

  1. Define scope

    Agree entities, jurisdictions, topics and the legal reference date.

    Scope record and named applicability reviewers.

  2. Map the framework

    Identify source instruments, national measures and relevant later changes.

    Versioned register with open interpretation questions.

  3. Review evidence

    Compare selected policies and operating records with the agreed requirements.

    Gap map distinguishing missing evidence from confirmed deviation.

  4. Plan implementation

    Agree process changes, dependencies, ownership and acceptance checks.

    Prioritised plan with legal or supervisory decisions clearly separated.

  5. Check the handover

    Trace a selected requirement through its source, evidence and remaining action.

    Reviewed register and assigned change-monitoring responsibilities.

Your contact

Melanie Düring

Head of Risk Management

CRD V is part of an evolving framework, rather than a new standalone implementation deadline. A useful assessment connects the relevant entity and jurisdiction to the currently applicable EU provisions, national implementation and supervisory expectations. Technology choices should follow that applicability analysis and a documented gap assessment.
ADVISORI expert opinion

7 QUESTIONS, BRIEFLY ANSWERED

Frequently asked questions about CRD V Implementation & EU Banking Package

What is CRD V, and is it the right starting point for a current project?

CRD V is Directive (EU) 2019/878, an amendment to Directive 2013/36/EU. It addresses topics including governance, remuneration and certain group and supervisory arrangements. Its Article 2 set a general application date of 29 December 2020 for national measures, with specified exceptions. A current project must identify relevant later amendments and national implementation. A historical checklist alone cannot establish today's obligations. Start by agreeing entities, jurisdictions, topics and the legal reference date.

How should CRD V governance changes be assessed against existing arrangements?

Identify the relevant amended provision and the applicable national framework before comparing it with the institution's responsibilities and controls. Review selected evidence of decisions, oversight and escalation, not only the wording of policies. Record whether a finding is a missing document, an operating deviation or an unresolved interpretation. Do not present all existing governance obligations as if CRD V introduced them for the first time.

Does proportionality exempt smaller institutions from CRD requirements?

Proportionality depends on the particular provision, applicable conditions, national implementation and the institution's circumstances. For example, Article 94(3) concerns specified remuneration requirements; it does not exempt an institution from the whole CRD framework. Related national options also matter. Identify the exact rule, qualifying facts and accountable reviewer. A small balance sheet or simple business model alone does not justify ignoring other obligations. Document any different treatment with its reviewed basis and limits.

What should a CRD V remuneration review cover?

A review needs the applicable policy framework, staff identification approach, decision records and any relevant proportionality assessment. The EBA's CRD V-related guidance includes gender-neutral remuneration policies. Other features, including the bonus-cap framework, predate CRD V and should not be described as entirely new 2019 requirements. Specific treatment of material risk takers and any exemptions require an institution-specific legal assessment.

How do we review suitability and fit-and-proper processes?

First establish which requirements and supervisory guidance apply to the relevant roles and jurisdiction. Then examine responsibility for assessment, required information, decision records and handling of changes or identified concerns. A documented workflow is useful only if the responsible people can demonstrate its operation. Preparing an assessment pack does not determine the competent authority's decision or guarantee that an individual will be accepted.

When is an intermediate EU parent undertaking relevant?

Article 21b concerns two or more institutions in the Union belonging to the same third-country group. Paragraph 4 excludes groups whose total EU assets are below EUR 40 billion; paragraph 5 defines the asset calculation, including relevant EU branches. The complete conditions, entity definitions and any permitted structure still need assessment. It is not a general requirement for every overseas business or branch. Legal and regulatory owners should record the group facts, reviewed basis and supervisory questions before implementation is planned.

How do CRD V, CRR II, CRD VI and CRR III fit together?

They are separate instruments within the evolving EU prudential framework. CRD V and CRR II belong to the 2019 package; CRD VI and CRR III are later reforms. Directives and regulations have different implementation mechanisms, and individual provisions may have distinct application arrangements. Map each project requirement to its actual source and current version. Neither a single package label nor a shared project deadline is a substitute for that review.