Core concepts
Regulatory scope
A scope groups reportings together, for example an entity or a consolidation level. It is defined by:
- a mandatory, unique name;
- a description;
- a preferred threshold: the threshold offered by default when a control plan is run on this scope.
Reporting file
A reporting file is a regulatory reporting loaded into a scope. It is characterised by:
- its type:
- DPM: EBA reportings (COREP, FINREP, etc.), in XBRL or XBRL-CSV format, or as a ZIP archive;
- RUBA: ACPR / Banque de France national taxonomy;
- ANACREDIT: if the module is enabled;
- its reporting date;
- its templates;
- its processing status;
- the “Official” flag: it distinguishes the official version of a reporting from working versions. Control plan and dashboard runs offer only official reportings by default;
- tags: some are added automatically from the file’s templates.
A given file can be loaded only once into a given scope. It can be loaded into another scope.
Control
A control is a formula that compares data from a reporting. It is defined by its reference, which is unique: two controls cannot have the same reference. It is best to adopt a reference pattern, for example REF_0001.
In addition to the reference, the control is defined by:
- a mandatory name: a fuller and more explicit text than the reference. Two controls can have the same name.
- a list of tags: each tag is a text, created by pressing the Enter key. Tags are used to group and filter controls according to your own criteria.
- a description: free, formatted text.
- a mandatory formula: the core of the control.
- It is made of two members, left and right, separated by an operator.
- It can also combine several comparisons.
- See the control grammar.
- a mandatory base: Left or Right. It designates the member used as the reference for computing the relative difference. For the formula A == B:
- with Left, the relative difference is (A-B)/A;
- with Right, it is (B-A)/B.
- a mandatory match type:
- Threshold: the difference is compared to the values of the threshold chosen at run time;
- Exact: the formula checks strict equality or inequality, with a rounding tolerance (see Thresholds).
- an optional precondition: a formula that must be true for the control to be applied. The same rules as for the formula apply. The precondition has its own base and its own match type (Left and Exact by default);
- an optional release window: the DPM 2 releases (Min release and Max release, bounds included) the control applies to. On a reporting of a release outside the window, the control is not evaluated and its result is Not applicable. Without a window, it applies to every release.
The control does not store a reporting date. The date chosen in the list (Check validity for) or in the form (Dictionary at) is used only to check the formula against the DPM dictionary in force at that date. The actual evaluation date is set when the control plan is run.
Validity status
Each control and each indicator receives a status, computed per quarter. The status indicates whether the formula can be evaluated with the taxonomy in force at the end of the chosen quarter.
| Status | Meaning |
|---|---|
| Valid | The formula is correct and every coordinate matches a cell of the taxonomy. |
| Not valid | The formula does not follow the grammar. |
| Issue – Ambiguous | A coordinate matches several possible cells. |
| Issue – Incomplete | The template code is not exact, but only one candidate cell exists. |
| Issue – Valid in a previous taxonomy | A cell does not exist at this date, but exists in another taxonomy. |
| Computing | The status is being computed. It appears on its own. |
Statuses are computed in the background, without blocking the lists. They are also recomputed every night and after each formula change. A control with a release window has no status for the quarters whose release is outside its window.
When a control plan is run, custom controls with the Valid and Valid in a previous taxonomy statuses are evaluated.
Control libraries
In addition to your custom controls, the platform provides published control libraries. They can be viewed but not modified:
| Library | Content |
|---|---|
| EGDQ-XL | The ECB data quality checks (ECB Guidance on Data Quality), published in native DPM-XL format. Each rule is executed as published, without conversion (see Reading a DPM-XL rule). |
| VR-XL | The EBA validation rules (Validation Rules), published in DPM-XL format and executed the same way. |
| EGDQ | The EGDQ checks in their legacy layout. Each published check is automatically converted into one or more sub-controls written in the platform’s grammar. This library is deprecated: EGDQ-XL is replacing it. |
| Validation Rules | The EBA validation rules in their legacy layout, converted in the same way. This library is deprecated: VR-XL is replacing it. |
| Analytical Controls | Breakdown definitions (total and detail rows and columns) per template. They are used for the analytical review of reportings. Unlike the other libraries, these definitions belong to your organisation: only the administrator can create, edit or delete them, or integrate the catalogue designed by MLA. |
| Anacredit | The AnaCredit reporting controls (if the module is enabled). |
A published control is identified by its reference and its version. For EGDQ-XL and VR-XL, the version is the module concerned, for example COREP_OF_4.2. You can add your own tags to them.
Control plan
A control plan groups the controls to be run together on reportings. It is defined by its reference, which is mandatory and unique: two control plans cannot have the same reference.
In addition to the reference, the control plan is defined by:
- a mandatory name, which can be shared by several plans;
- a list of tags: control plan tags are separate from control tags;
- a description;
- five lists of controls, each of which can be empty:
- custom controls;
- EGDQ-XL controls;
- VR-XL controls;
- EGDQ controls and validation rules in the legacy layout.
A control can appear in several plans. The plan only holds a link to the control: a change to the control applies to every plan that uses it.
Each run produces a control plan result. This result keeps the date, the files, the threshold, and the status of each control and sub-control. If the Teams module is enabled, the result belongs to the team that started the run (see Teams and permissions).
Thresholds
A threshold sets the tolerance granted to controls with the Threshold match type. It is defined by its name, which is mandatory and unique. It is best to adopt a naming pattern, for example T_Relative_5_10.
In addition to the name, the threshold is defined by:
- a mandatory type:
- Relative: the difference is measured as a percentage of the base member;
- Absolute: the difference is measured as a value;
- Relative & absolute: both deviations are checked, and a combination says how their results combine. Both must hold (AND): the stricter result wins, the control passes only if both deviations pass. Either is enough (OR): the more lenient result wins, the control passes as soon as one of the two deviations passes. Lists show the type as “Relative and absolute” or “Relative or absolute” depending on the combination.
- a mandatory success value: the maximum difference, bounds included, for the control to pass.
- a mandatory warning value: the maximum difference, bounds included, for the control to pass with reservations.
- The warning value must be greater than or equal to the success value.
- For the Relative & Absolute type, two success values and two warning values are required.
How the threshold applies:
==formula (equality):- the control passes if the difference does not exceed the success value;
- it passes with reservations if the difference does not exceed the warning value;
- it fails beyond that.
!=formula (difference): the logic is reversed. The control passes if the difference exceeds the warning value, and fails if it does not exceed the success value.<,>,<=,>=formulas, and Exact controls: the threshold does not apply. Two values are considered equal if their relative difference does not exceed 0.01% and their absolute difference does not exceed 1. These controls never result in “passed with reservations”.- EGDQ-XL and VR-XL controls: they do not use the threshold.
Each control plan result keeps a copy of the values of the threshold used. Changing a threshold therefore does not change past results.
Indicators
An indicator is a value computed from reportings, for example a solvency ratio. It is defined by its reference, which is unique: two indicators cannot have the same reference. It is best to adopt a reference pattern, for example REF_0001.
In addition to the reference, the indicator is defined by:
- a mandatory name, which can be shared by several indicators;
- a list of tags;
- a mandatory type:
- Ratio: the indicator is a percentage. It is displayed multiplied by 100 with the % sign.
- Amount: the indicator is a number.
- a description;
- a mandatory formula: unlike a control formula, it contains only one member and no comparison operator (see the control grammar);
- the Cumulative checkbox: descriptive information about the nature of the indicator. It is displayed and exported, but does not change the calculation.
As with controls, the indicator does not store a reporting date. Its validity status is computed per quarter.
The EBA indicators page presents the EBA risk indicator catalogue, with their formulas, in read-only mode. The Import into my indicators button of this page, or Import the EBA indicators on the Custom indicators page, copies this catalogue into your indicators, which you can then edit.
Dashboard
A dashboard groups indicators to be tracked together over time. It is defined by its name, which is mandatory and unique. It is best to adopt a naming pattern, for example Dashboard_0001.
In addition to the name, the dashboard is defined by:
- a list of tags: dashboard tags are separate from indicator tags;
- a description;
- a list of indicators.
- An indicator can appear in several dashboards.
- The dashboard only holds a link to the indicator: a change to the indicator applies to every dashboard that uses it.
Each run produces a dashboard result: the value of each indicator for each date of the chosen files. If the Teams module is enabled, the result belongs to the team that started the run.
A result is a snapshot:
- It keeps the formula and tags of the indicators as they were at run time.
- The review status, priority, comments and tags you enter on a result do not change the indicator in the library.
Dashboard template
A dashboard template is an Excel workbook in which some cells hold indicator formulas, written between %% (for example %%…%%). It is presented by the Analysis › Dashboard templates page.
- Generating a template on reportings (perimeter, reference date, processed files) produces a result: the workbook filled with the computed values, to download.
- Templates are shared by the whole organisation. Only the organisation’s administrator can add, edit or delete them.
- A template can also be built from chosen indicators, with one row per indicator.
- If the Teams module is enabled, each result belongs to the team that generated it.