Distinguish CRD, CRR and national requirements before choosing a project scope

CRD Directive: Scope the current framework and implementation work

The Capital Requirements Directive establishes a framework for access to banking activities, governance and prudential supervision.

  • 01An institution-specific applicability and obligation map
  • 02Named owners, required evidence and documented implementation decisions
  • 03A clear distinction between current rules, historical amendments and supervisory approval
11+Years of experience
120+Employees
540+Projects
ISO 27001certified

What CRD regulates and how it differs from CRR

The CRD framework is based on Directive 2013/36/EU and its amendments, including the instruments commonly called CRD V and CRD VI. It covers areas such as authorisation, governance, management-body suitability and supervisory powers. A directive requires national implementation, so the applicable country and the institution’s legal and operating structure matter.

CRR is the related regulation with directly applicable prudential requirements, including quantitative rules. A CRD project should therefore identify the governing instrument for each obligation instead of treating every capital, liquidity or reporting requirement as a CRD provision. The current consolidated EU text is a useful reading aid; the relevant amending instruments, national measures, application dates and transitional provisions still need to be checked for the specific question.

An agreed engagement can include applicability analysis, a gap assessment, implementation planning and evidence preparation for selected obligations. Your institution supplies the relevant entity and business-model information, current policies, supervisory correspondence and accountable decision-makers. Management retains its responsibilities; competent authorities retain their assessment and approval powers. Legal opinions, authorisation outcomes and the operation of a compliance platform are not implied by a general consulting scope.

A package name does not establish an institution’s deadline: Identify the specific provision, instrument version, jurisdiction, affected activity and transitional rule before setting an implementation date. A date from a historical CRD V project or one CRD VI provision should not be applied to every current obligation.

6 service modules

Applicability assessment, obligation mapping and implementation evidence

01

Authorisation scope and application preparation

For a defined licensing or change scenario, the work identifies applicable requirements, required information and dependencies. The output is an application-workstream plan and an evidence checklist; it does not predict or guarantee the authority’s decision.

  • Describe the entity, activities, jurisdiction and proposed change
  • Map required information to a source and accountable owner
  • Record missing evidence and supervisory questions
  • Agree milestones around actual dependencies and the applicable procedure
02

Governance responsibilities and oversight

The assessment connects governance requirements to the institution’s organisation, decision rights and control functions. The output records identified gaps, proposed actions and the evidence needed to demonstrate implementation.

  • Review responsibilities, decision paths and oversight arrangements
  • Map policies and their implementation evidence
  • Identify conflicts, dependencies and open management decisions
  • Record review and approval steps without implying automated supervisory communication
03

Suitability and ownership workstreams

Selected suitability or ownership questions are organised around the applicable process and required evidence. Supporting analysis and document preparation remain distinct from an authority’s assessment and from the institution’s own governance decisions.

  • Identify the relevant assessment or notification scenario
  • Capture required facts, source documents and responsibility
  • Track completeness, inconsistencies and unresolved questions
  • Document the review route and the boundaries of any technical workflow
04

Risk-management integration

A scoped review examines how relevant obligations connect to risk responsibilities, policies and reporting. The output is a practical gap-and-action map that identifies dependencies on related CRR or other requirements.

  • Connect obligations to risk owners and existing processes
  • Distinguish policy design from evidence of actual operation
  • Identify affected reporting and control dependencies
  • Record actions and acceptance evidence for the agreed changes
05

Obligation tracking and evidence management

A structured register links each selected obligation to an owner, status and supporting evidence. Workflow automation can support tracking where a specific solution is agreed; it does not establish complete or continuous legal compliance.

  • Record instrument, version, jurisdiction and applicability reasoning
  • Separate confirmed evidence, missing facts and interpretative questions
  • Set review triggers and accountable decisions
  • Use agreed workflows with human review and traceable changes
06

Regulatory change and implementation handover

The change plan connects new or revised obligations with affected policies, processes, systems and training. The handover identifies completed work, remaining decisions and the responsibilities for maintaining the result.

  • Compare relevant versions and national measures
  • Identify process, data and system impacts before assigning tasks
  • Define review, testing and management approval checkpoints
  • Hand over evidence, unresolved issues and the agreed maintenance scope

Worked example: Connect an obligation to an owner and evidence

This original illustration demonstrates a working method. It is not an applicability finding for a particular institution, a complete legal checklist or evidence of a client engagement.

Illustrative obligation-to-owner map; legal applicability and national requirements require institution-specific review. On small screens, scroll the table horizontally.
Question to assessEU source starting pointEvidence to examineAccountable role to identifyCompletion decision
Are governance responsibilities and oversight documented and implemented?CRD Articles 74 and 88, plus applicable national measuresOrganisation, delegated authorities, relevant policies and actual oversight recordsRelevant management body and control-function ownersRecord supported findings, required changes and the authorised decision on remaining gaps
Does a proposed activity require an authorisation workstream?CRD Article 8 and related provisions; national implementation and relevant procedureEntity and activity description, current permissions and proposed changeAuthorisation workstream owner with appropriate legal and regulatory supportDocument the assessment, unresolved facts and the next authority-facing step where required
Can the implementation status of a selected obligation be substantiated?The exact provision, version, jurisdiction and applicable date entered in the registerApproved change, evidence of operation, review result and unresolved exceptionsRelevant process owner and accountable review functionAccept only the agreed scope supported by evidence; keep unresolved legal or supervisory questions visible

4 phases

From an applicability question to accountable implementation work

The initial scope identifies what must be established, which sources are authoritative and who can make the necessary decisions. Implementation depth depends on that assessment.

  1. Establish the facts

    identify the entity, activities, jurisdictions, current permissions and assessment objective.

    an agreed scope with explicitly missing information.

  2. Map sources and obligations

    check current EU instruments, national implementation and relevant supervisory material for the selected questions.

    a versioned applicability and obligation register.

  3. Assess evidence and plan changes

    compare the selected requirements with policies and operating evidence.

    findings, accountable owners, dependencies and proposed acceptance checks.

  4. Review and hand over

    document implementation evidence, management decisions and issues requiring specialist or supervisory clarification.

    a reviewable handover with maintenance responsibilities.

Your contact

Melanie Düring

Head of Risk Management

The intelligent implementation of CRD Directive requirements is the key to supervisory excellence and strategic flexibility in EU banking. Our solutions enable institutions not only to achieve regulatory compliance but also to develop operational superiority in governance and supervisory interaction. By combining in-depth banking supervision expertise with advanced technologies, we create sustainable competitive advantages while protecting sensitive corporate data.
ADVISORI expert opinion

9 QUESTIONS, BRIEFLY ANSWERED

Frequently asked questions about CRD Directive

What is the Capital Requirements Directive?

The framework based on Directive 2013/36/EU addresses access to banking activities, governance and prudential supervision, with requirements developed through subsequent amendments. Applying it involves national implementation and the institution’s facts. Identify the current instrument, jurisdiction, activity and assessment question before treating an obligation as applicable. A package label such as CRD V or CRD VI is not a complete institution-specific analysis.

How do CRD and CRR differ?

CRD is a directive requiring national implementation. CRR is the related regulation setting directly applicable prudential requirements, including quantitative rules. They interact but have different provisions and legal routes. In an implementation register, link each obligation to its correct instrument, version and relevant national or supervisory material. A capital, liquidity or reporting question should not automatically be assigned to CRD.

How do CRD IV, CRD V and CRD VI relate to the current framework?

The labels refer to successive banking-package developments; they are not three interchangeable standalone project specifications. Directive 2013/36/EU has been amended, including by the instruments commonly called CRD V and CRD VI. Use the current consolidated text as a reading aid and check the relevant amending, application and national provisions. The historical CRD V page is linked separately for that context.

Why must national implementation be checked?

A directive requires Member States to introduce the necessary national measures. The applicable law, competent authority, procedure and institution-specific scope therefore require a jurisdiction-specific check. An EU transposition deadline does not by itself prove that a particular national measure is in force or that every provision has the same application date. Document the source and current status of each material conclusion.

Which governance topics can a CRD assessment examine?

The selected scope can examine responsibilities, management oversight, risk processes, internal controls and relevant policy arrangements. The current CRD text addresses governance in Articles 74 and 88, among other provisions. An assessment should connect the applicable requirements to the institution’s organisation and actual operating evidence. Management remains accountable for its responsibilities; a policy document or workflow tool is not sufficient evidence of implementation by itself.

What is the relationship between CRD and bank authorisation?

CRD Article 8 establishes a requirement for authorisation before credit institutions commence their activities, with related provisions and national rules defining the relevant framework. The actual route depends on entity, activity and jurisdiction. A consulting workstream can organise facts, evidence and application tasks. It cannot decide the authority’s assessment or justify a guaranteed approval probability from a generic checklist.

How can ADVISORI support a scoped CRD implementation project?

The engagement can be structured around applicability questions, selected obligations, evidence gaps and accountable implementation tasks. The offer must specify which advisory, documentation, process or system work is included and what the institution supplies. A practical handover identifies completed work, remaining decisions and maintenance responsibility. Particular automation, legal-opinion or managed-service capabilities require an explicitly agreed and substantiated scope.

Which implementation date applies to a CRD obligation?

Start with the exact provision and amending instrument, then check national implementation, application and any transitional rule. Different provisions can have different dates. Record why the date applies to the institution and the relevant activity. The consolidated reading text and a country tracker are useful starting points; neither replaces the authoritative national and EU sources for a specific conclusion.

What information is needed before scoping an engagement?

Provide the entity and group structure, relevant jurisdictions and activities, current permissions, the business change or supervisory question and the selected obligations. Identify existing policies, evidence and accountable owners. This establishes the workstreams, dependencies and specialist review needed. A general description of the banking package cannot establish the scope, cost or completion date of an institution-specific project.