Code development platform for open source projects from the European Union institutions 🔵 EU Login authentication by SMS has been phased out. To see alternatives please check here

Skip to content

[RRMV documentation] - Introduction

We kindly ask to revise the text in the introduction section of the documentation:

  1. Introduction

1.1 Context

As EU policies evolve, the demand for data in the form of reporting requirements from Member States and other stakeholders continues to grow. This may potentially lead to an increase in the regulatory reporting burden, as stakeholders need to increasingly monitor regulations to be fully compliant with them.

To address this issue, the European Commission, in its 16 March 2023 Communication on the Long-term competitiveness of the EU, committed to "make a fresh push to rationalize and simplify reporting requirements for companies and administrations with first proposals for each of the green, digital and economic thematic areas before the autumn. The aim should be to reduce such burdens by 25%, without undermining the related policy objectives.”

In line with this effort, streamlining regulatory reporting burdens has been identified as a critical policy need for the European Commission's proposals. The European Commission aims to eliminate redundancies and harmonise reporting requirements to assist policy officers in understanding existing frameworks in detail. By avoiding duplicate requests and considering factors such as dates and reporting frequencies, the Commission seeks to optimise new requirements effectively.

1.2 Use cases

The RRMV proposes a model that allows to execute the following Use Cases:

UC 1: Extract structured information about reporting requirements from existing legislation including what, by whom, to whom, etc. The goal of this Use Case is to systematically extract key elements of reporting requirements within legal texts and annotate them accordingly allowing further detailed analysis about potential overlaps, redundancies, or inconsistencies in mandated data flows. UC 2: Identify reporting due dates and essential planning information, including conditional start dates, milestones, and derogations. This Use Case focuses on annotating conditional start dates, key milestones, and any applicable derogations of reporting requirements. The objective is to provide clear and actionable timelines and conditions of the obligations set in reporting requirement clauses allowing further detailed analysis about potential overlaps, redundancies, or inconsistencies in temporal aspects. UC 3: Identify changes in reporting requirements of new versions of legislations affecting reporting requirements. This Use Case involves continuously monitoring the versioning of legislations to ensure the metadata extracted (UC1) remains up to date. The goal is to identify the Modifications set in a specific article located in the legal text affecting reporting requirements, providing a snapshot of the change in terms of data flow or temporal aspects. UC 4: Extract exceptions and legal relationships pertaining to applicable reporting requirements. The Use Case focuses on detecting clauses that affect the applicability of reporting requirements at a given moment in time (meaning inferring on exception, suspension, or abrogation decisions related to existing reporting requirements).

1.3 History

The context let to the Study on Regulatory Reporting Standards (SORTIS), a combined effort of the University of Bologna, the University of Liège, and the European Commission. The project aimed to define a vocabulary to standardise and organise regulatory reporting metadata of EU legislations and to develop standard formulations to be able to identify the appropriate data of reporting requirements.

The results of this study included a definition of a model known as Reporting Requirements Metadata Vocabulary (RRMV). This model aimed at defining the set of concepts and categories contained in reporting requirements within existing EU legislations and define their properties and the relations between them. It could serve as a base for interoperable reporting requirements monitoring solutions that could extract information and automatically feed regulatory reporting databases across different policy domains to be accessed by stakeholders.

SORTIS provided an initial data model which is visually depicted below.

[IMAGE OF PREVIOUS MODEL]

The initial data model has been further elaborated by a SEMIC action conducted by PwC EU Services, resulting in this specification.

Edited by Alessio NARDIN