From XBRLWiki

CEN Workshop Agreement

Status: Approval Final Draft - Formal Vote

CEN WS CWA3 Convenor: Aitor Azcoaga (EIOPA)

CEN WS XBRL Experts: Pieter Maillard (Aguilonius), Pablo Navarro (Atos)

Editing rules

Editorial comments should be highlighted as follows: A comment

Text or rules in discussion (white): Some text

Text or rules already aligned (green): Some text

Text or rules to be deleted (red): Some text

Text to be delivered (blue): Some text

Foreword

This document has been prepared by CEN/WS XBRL, the secretariat of which is held by NEN.

CWA XBRL 003 consists of the following parts, under the general title Improving transparency in financial and business reporting — Standard regulatory roll-out package for better adoption
— Part 1: XBRL Supervisory Roll-out Guide
— Part 2: XBRL Handbook for Declarers

This CWA is one of a series of related deliverables. The other deliverables are:

CWA XBRL 001 which consists of the following parts, under the general title Improving transparency in financial and business reporting — Harmonisation topics:
— Part 1: European data point methodology for supervisory reporting.
— Part 2: Guidelines for data point modelling
— Part 3: European XBRL Taxonomy Architecture
— Part 4: European Filing Rules
— Part 5: Mapping between DPM and MDM

CWA XBRL 002 Improving transparency in financial and business reporting — Metadata container

Introduction

This document is intended to provide guidelines to European regulators in the implementation and roll out of the reporting standard using XBRL across Europe.

The set of recommendations included in this document aim to facilitate the implementation of European National Supervisors to adopt XBRL in any of the reporting frameworks. The following sections will provide guidance on the use, understanding, preparation, and extension of their filings in eXtensible Business Reporting Language (XBRL).

This guidance is in the form of notes in association with the pertaining requirements clause and uses the terms “should” (recommendation), “may” (allowance) and “can” (possibility). Organizations wishing to implement this CWA would be expected to consider all recommendations where the term "should" is used.

COREP, FINREP (and Solvency II or other future) XBRL taxonomies are offered to European regulators for national implementation. The first releases (2006) of the COREP and FINREP XBRL frameworks have proven that a standardized technical roll-out package is needed to increase the adoption rate and avoid implementation variances, which have a detrimental effect on the overall cross-border effectiveness of using one reporting standard. As well this roll-out guide tries to promote the economies of scale for a better adoption.

Contents 1 Scope 2 How to start with XBRL. Supervisory Perspective 2.1 Determine the level of XBRL adoption 2.2 Plan and prepare the new reporting models 2.3 Review existing reception infrastructure 2.4 Review internal information systems 2.5 Prepare the communication plan for Reporting Entities 2.6 Summary 3 How to implement and extend XBRL taxonomies 3.1 European Framework background information 3.2 XBRL Standard extension Mechanism 3.3 Guideline for creating extension taxonomies 4 Architecture, Methodology and Best Practices 4.1 Introduction 4.2 Context for a Reference Architecture 4.3 Steps for implementation 4.4 XBRL Reference Architecture 4.4.1 Functional Architecture 4.4.2 Technical Architecture 5 Management and maintainability

Scope

This CWA is a general guide to XBRL oriented towards national regulators on how to implement, extend and manage XBRL taxonomies. The guidance and recommendations included in this CWA have been created for regulatory filings in the context of European supervisory reporting.

In this document, “regulatory filings” encompasses authoritative financial reporting standards and generally accepted accounting principles/practices (or GAAP), regulatory reports whose subject matter is primarily financial position and performance and related explanatory disclosures, and data sets used in the collection of financial statistics; it excludes transaction- or journal-level reporting, primarily narrative reports (for example, internal controls assessments) and non-financial quantitative reports (for example, air pollution measurements).

How to start with XBRL. Supervisory Perspective

This section describes how the XBRL standard can be implemented from the regulator's perspective.

First, we present different levels of XBRL adoption, to help define the supervisor's strategy.

This is followed by a description of the minimum steps required to facilitate initial understanding of the XBRL standard, and guidelines describing the review and the likely impact on existing infrastructure and internal information systems.

Finally, we suggest additional considerations which should be taken into consideration during preparation and planning, to help regulators establish which services they need to implement to enable reporting entities to adhere to the XBRL standard. Figure 1 presents an overview of the activities described in the section.

Figure 1 —The Business Overview to Rollout XBRL reporting

[SOURCE: 24th XBRL International Conference: Academic Track 6]

Determine the level of XBRL adoption

Widespread adoption of XBRL as a business information exchange format has revealed a number of implementation alternatives.

Selection of a specific adoption strategy by the regulator establishes the roadmap for implementation from the regulator's current reporting framework to a framework which supports the new legislation. This step is probably the most important step in XBRL adoption.

Attending to the level of penetration (or permeability) of XBRL between the Regulator and the Filing entities the adoption can be classified in the following:

• Use of XBRL solely for the electronic exchange of data between the national regulator and European Authority to comply with legislation.
• Adaptation of existing reporting channels to receive XBRL reports from reporting entities as well as using XBRL for the electronic exchange of data between the national regulator and the European Authority. In this scenario, regulators could make use of automated business rules to validate data received from reporting entities.
• Full exploitation of XBRL for internal reporting models (multidimensional data analysis) in addition to the use of XBRL for receiving data from reporting entities and electronic exchange between the national regulator and the European Authority as described above.

Depending on the strategy selected, the regulator must also determine which XBRL enabled software applications should be made available to their internal departments and also to reporting entities under their jurisdiction.

To name a few examples for consideration: XBRL validation, report visualization, conversion from existing data formats, filing forms, monitoring, security enforcement and versioning that will facilitate the analysis and supervision of reported information.

Plan and prepare the new reporting models

From the regulator's perspective there are two main key drivers in favour of XBRL adoption: compliance with new regulation directives and ensuring the accuracy of data reported by reporting entities.

Compliance with new regulation directives implies the adequacy of the reporting business models and rules to the XBRL language and semantics to be implemented.

The most important requirement for financial supervision reporting is data accuracy. Reported data, for legal reasons, is expected to be:

• accurate for arithmetic purposes;
• calculated accurately based on the required definition;
• preserved during the data transfer process.

It is also a good idea to plan and prepare the adaptation of all data requirements. For this, the regulator needs to learn and understand the following topics:

• XBRL basics – terminology, syntax and structure;
• how the data models correspond to the business model and semantic rules into XBRL syntactic schemas and filers forms that define reporting data. Consider information requirements which could have causes additional issues to be solved in the modelling architecture.

Many are approaching as compliance requirements driven by a new reporting directive. An alternative approach is considering XBRL adoption as a technology evolution of current reporting systems to take advantage of this standard and reap the benefits of a standardised electronic exchange format.

In general, successful XBRL implementations usually do not change the business models, just the report format resulting in a transparent use of XBRL to the end users.

It is specially recommended to apply a structured methodology for data modelling. On this topic the Eurofiling architecture approach is proposing a methodology on normalization called Data Point Modelling. This will be introduced later in Section 5, but mainly consists of defining a method to model dictionary data, their aspects and relationships in terms of domains and hierarchies, business validation rules and the corresponding classifications of the data in different tables and forms for filing and visualization (figure 2).

Figure 2: DPM process and XBRL relationship

[SOURCE: Abstract description of the model represented in taxonomies following the DPM approach]
How this data inherited from the European frameworks fits into the national reporting model. Study if the current information models for reporting entities have more disclosures or information. In case more detailed information is required, knowledge on the extension of European taxonomies is needed. This will be detailed in Section 4.
In order to select the most appropriate XBRL strategy, the regulator should consider the relevant answers to the questions below that will help to address reporting decisions:

• How many different reporting templates do we need to receive from reporting entities?
• What is the frequency of this reporting information? Quarterly, semi-annually, annually?
• What is the minimum reporting unit of information expected to receive (one template, one module, one table, one fact, other)?
• What is the profile of reports (minimum and maximum size expected) to be received keeping a margin of security for processing?
• What response time is needed to process received reporting information?
• Will it be allowed partial submissions? Or will all data need to be reported in full?
• What is the minimum precision accepted for data?
• Will it be allowed for reports to be re-submitted if the reporting entity wishes to submit an amendment? Will It be placed any deadlines for receipt of any amendments?

Review existing reception infrastructure

From an IT perspective, regulators will have the opportunity to review their current receipt and transmission infrastructure with their reporting entities to incorporate the new reporting standard to their channels:

If regulator has well established data collection mechanisms in place, it will be necessary to adapt these mechanisms to accept XBRL instance documents, including additional workflows (submit and feedback loops) for the validation of header information and XBRL validation (following recommendations documented in “CEN WS XBRL CWA2 as valuable initiatives to take into consideration).

Specific items likely to require IT review:

• Select a new system or adapt if necessary an existing system for receiving reports from reporting entities and sending acknowledge messages and validation report results from regulator (transmission channel): web secure portal upload, email secure SMTP, web service secure integration submission, cloud portal, etc.,
• Select, reuse or adapt the security methods to maintain confidentiality, integrity, authenticity, non-repudiation (following recommendations documented in CEN WS CWA2 related to digital signature and use of certificates)
• Select which additional services could be provided as part of the submission protocol from reporting entities to national regulator, for example tracking or monitoring submitted reports, visualization of XBRL instances, pre-validation including formulae[4] which defining regulatory requirements, display the specific data set (templates) that each reporting entity is expected to fulfil, etc.

Review internal information systems

Regulators who elect to adopt XBRL for internal information systems will need to consider how to adapt existing systems for XBRL integration and data analysis.

All national regulators across Europe are responsible for defining their local regulation and communicating with their reporting entities. Existing, internal systems vary significantly between national regulators and some will need to adapt more than others to meet the new European directives. The purpose of this section is to establish a common set of high level guidelines based on current best practices that could apply for the internal use of XBRL in regulatory reporting to help realise the benefits of using a standard method of data exchange across Europe.

The European framework and the XBRL International abstract model version 2.0 provide a clear method to enable consistent definition of business information. Aligning the adaptation of internal systems with align those methodologies is foreseen as the key to driving better regulatory practice across Europe.

Making use of automated business-rule validation on reported data will help to assure high quality data and reduces the processing time associated with manual checks allowing more time to analyse and dedicate to analysis real supervisory activity. The creation of data-warehouses based on XBRL taxonomy frameworks and models will facilitate access to reporting information through the different perspectives of regulatory reporting (compliance, risk, prudency, transparency).

In conclusion, adapting internal systems to work with XBRL reporting carries several advantages:

• full utilisation of the multi-dimensional data models and XBRL frameworks provided by European authorities, allowing use of OLAP-enabled databases and exploit this information for integration and analysis and regulatory activity using business intelligence tools;
• reuse and take advantage of native XBRL formula validation across multiple reporting documents to ensure the quality and consistency of the data submitted by the reporting entities saving time and effort in the process using multi-instance sub-module of the specification.

Prepare the communication plan for Reporting Entities

Once the regulator has defined all reporting requirements and project plan to adapt information systems to support the exchange of reporting information using XBRL, it will be required to establish a clear plan for communicating the new regulatory process to reporting Entities.

This communication need to cover several steps to be actions taken by the national regulator to involve their main reporting entities as early as possible to ensure a smooth transition to new processes and new technology in the process normative.

We recommend that national regulators hold periodic plenary sessions with the reporting entities under their jurisdiction to facilitate successful communication about XBRL adoption and implementation roadmap. Example content could include:

• communicating the perimeter of the new recommendations;
• presenting a technical overview of XBRL taxonomy frameworks and the DPM methodology used;
• presenting how to reduce the impact on current data exchange processes with reporting entities;
• communication of expected timelines for compliance.

Other successful XBRL programs around the globe have found it beneficial to create an "Early Adopters" program between the national regulatory Authority and a reduced number of major reporting entities. The “Early Adopters” program can be used to set up an initial proof of concept for XBRL reporting exchange and facilitate the success of a full rollout.

The main benefits of an “Early Adopters” program are:

• to refine the process in the receipt and acknowledgement of XBRL reports;
• to enable the reporting entities to study the new requirements, to analyse any potential impact in their business models, to realise the estimation effort required and develop or adapt their IT systems to support XBRL;
• to test the performance of services deployed by the national regulator in terms of processing, security enforcement, integrating, analysing and validating XBRL reports.

Summary

During this section the regulatory supervisor has been able to introduce all the topics required to establish a roadmap to adapt their systems and plan the new reporting information system to rollout.

How to implement and extend XBRL taxonomies

One of the key challenges faced by regulators when adopting the XBRL standard is to fit the reporting requirements set by European frameworks and directives into existing national supervisory and compliance processes.

In most of the cases, the flexibility of the XBRL standard will allow the national supervisor to fulfil both requirements. Mechanisms to implement and extend taxonomies are likely to vary from one to another.

The objective of this section is to provide a set of guidelines to facilitate a harmonized approach to XBRL implementation collected from previous national XBRL adoptions across Europe.

The main objectives in regulatory reporting are: maintain data accuracy, data transparency, regulatory compliance and process interoperability.

European Framework background information

The scope of this section focuses on the European framework for regulatory reporting. Under this context, there are currently two major European Authorities that will drive the application of a harmonized reporting using XBRL. And therefore will address the corresponding recommendations in terms of implementation and extension of taxonomies for regulatory supervisors:

• Taxonomy frameworks of the European Banking Authority (EBA): COREP and FINREP;
• Taxonomy framework of the European Insurance and Occupational Pensions Authority (EIOPA) for Solvency II.

Figure 3 — European Taxonomy Frameworks Diagram

These two authorities have been developing XBRL implementations which form the basis of the European frameworks pillars for supervisory reporting (Basel II, Solvency II and Financial Statements).

Eurofiling initiative is an open collaboration between groups of experts, including regulatory reporting experts from EBA, EIOPA, XBRL Europe and other volunteers working on a common project to collect the regulatory reporting practice across Europe. The cross-sector definitions common to Solvency II, COREP and FINREP is most likely to be defined in the [1] namespace and location.

National regulators will use the taxonomies defined by these authorities to implement their regulatory reporting process in accordance with national law and EU directives.

In terms of XBRL implementation those National adoption will represent the third namespace owner for reporting (covering the national GAAP)1 as shown in figure 4 below.

Figure 4 — National Supervisor Regulatory Extension Diagram

Table 1 shows an example on the owners and namespaces and owner prefixes for the used to establish the institution that defines the different concepts to be reported in the corresponding models.

Table 1 — Owner namespaces and prefixes example

Owner Internet domain European Banking Authority Eurofiling Namespace Prefix http://www.eba.europe.eu http://www.eba.europe.eu/xbrl eba http://www.eurofiling.info http://www.eurofiling.info/xbrl eu http://www.bde.es http://www.bde.es/xbrl es 1 Banco de España Footnotes 1 For concepts shared with other European supervisors.

[SOURCE: EBA Representation in XBRL of the Data Point Model]

Another example on use is the EIOPA Solvency II XBRL Preparatory Taxonomy where we can find a similar use of cross-sector definitions on EuroFiling owner namespace differentiated from EIOPA institution as owner of solvency II concept definitions:

Table 2 — Example of owner Namespaces, prefixes and official locations

Owner Namespace Prefix Official location Eurofiling (cross-sector) http://www.eurofiling.info/xbrl eu http://www.eurofiling.info/eu/fr/xbrl EIOPA Solvency II HD and MD common http://eiopa.europa.eu/xbrl/s2c s2c http://eiopa.europa.eu/xbrl/s2c EIOPA HD version http://eiopa.europa.eu/xbrl/s2hd s2hd http://eiopa.europa.eu/xbrl/s2hd EIOPA MD version http://eiopa.europa.eu/xbrl/s2md s2md http://eiopa.europa.eu/xbrl/s2md

[SOURCE: EIOPA Solvency II XBRL Preparatory Taxonomy]
The use of different levels of reporting definitions identified by the use of owner, namespace, prefix and location, provides a proper method to harmonize the use of definitions and concept frameworks across Europe. For technical details on taxonomy architecture nomenclature refer to CEN Agreement document CWA1.

XBRL Standard extension Mechanism

XBRL is extensible. This means that the set of concepts defined in a taxonomy framework can be reused in local taxonomies using the import tag mechanism inherited from XML Schema definition of taxonomies as the next figure 5 illustrates:

Figure 5: Import tag mechanism

In the example of the figure 5 is shown the local national taxonomy schema es-be-rp22.xsd is using the concepts defined in the European taxonomy framework COREP extending the XSD schema defined in www.c-ebs.org for the t-c1-2006-07-01.xsd schema

It is important to notice that when a taxonomy extends another schema using the xsd:import mechanism all the inherited concepts to be used in the local taxonomy schema are referred with the corresponding namespace (in this example the c-ebs namespace indicated that could be assigned to a concrete namespace prefix to shorten and be used along the relationships and local definitions (table rendering, formula assertions, dimension relationships, etc.)

One of the recommendations when extending taxonomies is to fully qualify the schema location URL for the taxonomy resource we are extending, instead of using a local copy or a relative location.

Guideline for creating extension taxonomies

A national regulator extending one of the European Framework taxonomies should take into account the following set of basic principles to facilitate efficient regulatory oversight, consistency of supervision and reduction of redundant data collection:

1. Simplicity of the reporting process: the resulting regulatory taxonomy architecture must focus on simplification of instance document creation.
2. Stability: the application of the regulatory taxonomy architecture must minimize the impact of changes resulting from amendments to consuming systems.
3. Consistency: the framework under the regulatory taxonomy architecture must be consistent in design and the taxonomies must be coherent and explicit.
4. Compliance with specifications, best practices and related taxonomies: the regulatory taxonomy architecture must conform as much as possible to the approaches inherited from related projects (Level 1 and Level 2).
5. Maintainability: the regulatory taxonomy architecture framework must be easy for supervisors to maintain.
6. Performance: the application of the regulatory taxonomy architecture should result in other technical advantages including reduced size of instance documents, better performance in processing (e.g. DTS loading, validation),
7. Review and avoid duplicate redefinition of concepts. When extending existing taxonomy frameworks one of the common practices is to redefine a concept that does not match the local definition exactly. This practice should be avoided as far as possible to reduce complexity in the final framework aggregation. The current modularization of taxonomy frameworks and well documented metrics and aspects of the model allows a better adaptation to local redefinitions instead of building a new set of duplicated concepts for local purposes.
8. Avoid redefinition of extended templates. One of the lessons learned from early versions of European frameworks is that the extension mechanism to prohibit relationships or dimension definitions (grey cells not allowed for extended reporting templates) at the end is not a good practice in terms of taxonomy complexity and maintainability. In cases where the reporting template in a local extension is different the recommended approach is to define a new reporting template reusing as many of the existing concepts, metrics, relationships and aspects of the base taxonomy and then compound the concrete local aggregations, table, rendering and views.

As a summary the extensions should take into consideration the following high level guidelines:

• reduction of redundant or duplicate definitions;
• standardization, simplification;
• reduced information friction to facilitate (more) continuous monitoring and audit of controls;
• consistency of regulatory supervision;
• facilitate efficient regulatory oversight;
• maintain the coherence and consistency of the base taxonomy model.

Architecture, Methodology and Best Practices

Introduction

Some reference documents that regulators should consider reading are:

1. "An Architecture for European XBRL Taxonomies" (EXTA [1]) where a description in the followingtopics is described:

• supporting concepts (Owner, Model supporting schema, Namespaces);
• public elements;
• dictionary of concepts (Metrics, Dimensions, Families, Perspectives, Domains, Explicit domain[2] members and hierarchies );
• reporting requirements layer (Frameworks, Taxonomies, Tables, Modules, Validation rules);
• architecture.

1. "Data Point Modelling Methodology" (DPM Methodology [2])"
2. "Abstract description of the model represented in taxonomies following the DPM approach" (Abstract Model 2.0 [3])
3. "Comparison of Conceptual, Logical and Physical models vs. the Data Point Modelling" (Comparison DPM [4])

This section will introduce regulators to the current design techniques and implementation approach used to represent financial models defined by European Regulators. It is important to become familiar with the terminology used in the European XBRL Architecture and Data Point Modelling Methodology, as these will be the base of best practice recommendations in terms of creating financial models based on European regulatory frameworks.

XBRL Abstract Model version 2.0: defines the reference to understand and better design in a separate and consistent form the financial and business models and rules that conforms the aspects, concepts, relationships and formulae of the information to be modelled. Introduce an important decoupling vision for business reporting chain that enables design, architecture and implementation of XBRL.

Data Point Model, also known as DPM Methodology: A set of guidelines, based on a long track record in regulatory reporting modelling, describing methods for the definition and identification of the data exchanged in reporting frameworks. It establishes a systematic method to represent and describe the data to be reported. Using a data centric approach where properties are assigned to defined ‘data points’, including all their semantic aspects and relationships to give precision to their meaning.

XBRL Architecture: based on the dictionary of concepts modelled previously, this defines the set of technical definitions and rules that will enable the implementation of the model using the XBRL standard language in the reporting systems. This architecture should be used as a reference to ensure common practice across implementations to enable interoperable, consistent and harmonized reporting. To achieve this goal the architecture is intended to provide a set of definitions with a concrete structure to implement the model. It is intended to be flexible and open enough, based on previous XBRL implementation for European financial reporting framework versions, giving conventions in the way to implement the concrete frameworks.

Context for a Reference Architecture

XBRL standard has been adopted in Financial Supervisory Reporting

• Public and Private Financial Statements for National Regulators extending COREP and FINREP taxonomy frameworks are in place in several countries across Europe.
• National financial statements using GAAP taxonomy definitions based on IFRS reporting.
• All these initiatives have required several changes in their current IT systems to integrate XBRL.
• Lack of Native XBRL treatment XBRL considered as a format ignoring the semantic information provided by the XBRL taxonomies.

Architectures on Distributed Systems have been established during last 10 years

• Service Oriented Architectures enable modular implementation in the Architecture Stack.
• There are several Layers in the reference Reporting Architecture to decouple the external reporting reception with the internal processing and analytic systems:
• security Layer;
• front End and reception layer;
• middle Processing and XBRL treatment Layer;
• Integration and Analytic Layer.

Steps for implementation

Launch an internal Proof of Concept project. Benefits:

• Appropriate to evaluate XBRL requirements, functional services and technical processing capabilities to implement and adapt the information systems.
• It will enable a proper feedback on results for designing the different processes to build.

Extend the reporting XBRL PoC to the architecture layers:

• Design the Functional Architecture and their modules.
• Review current product market status in XBRL processing, validation and reporting tools.
• Identify Information systems where to extract, collect, validate, receive or analyze the reporting information.
• Review the performance requirement on current implementation vs. XBRL PoC results.
• Identify the interfaces and transformations to be completed to current data information (messaging, data models, validations to run, storage and exploit systems, etc.).

XBRL Technical Architecture definition. Adapt and deploy the different technical architecture to support XBRL reporting process:

• Define how to process XBRL information (natively using processors, products or tools, direct programming transformations building custom components, other, etc.).
• Adapt Development Environment: Integration tools for development teams to provide taxonomy editors/viewers, XBRL Processor for validation and formula editing, APIs to extract and compose data reported to the current integration components to exploit the information).
• Define or adapt Methodology for XBRL development and deployment.
• Define or adapt XBRL Process and Services catalogue to orchestrate the XBRL component execution in current integrated systems (different operational flows for XBRL reception, validation, storage and integration on Data Warehouse).
• Deploy XBRL components packaged with other infrastructure and security services (certificate, signature, reporting management policies, etc.) including performance designs.

XBRL Reference Architecture

According to The Open Group Architecture Framework (TOGAF2)) architecture lifecycle (figure 6), a XBRL reference Architecture is a concrete specialization of The Open Group distributed Architecture in which services have been implemented to cover the functionalities of the reporting chain.

Figure 6 — TOGAF Architecture Lifecycle diagram

[SOURCE: commons.wikimedia.org TOGAF ADM (Architecture Development Method) - The Open Group]

The information presented in this document and the reference documentation indicated at the beginning of the section will provide background information to help regulators to establish the goals of Preliminary phase and steps A and B in the lifecycle illustrated above.

The following section focus on steps C and D to complete the reference architecture for XBRL implementations, based on best practice across Europe.

Functional Architecture

For national regulators the Functional Architecture is the first step in designing the building blocks where the architecture layers will be implemented.

The reporting cycle between parties will drive the different modules to be implemented. A typical set of functions could be:

Interface with Reporting Entities

• Submit and receipt module

• Receipt of XBRL Reporting Data
• Consistency checking of reported information (XBRL valid 2.1) [1]

• Reporting Entities Front Services

• Report follow up and status management
• Auxiliary services (visualization, taxonomy repository reference, form filling application)

Data Reporting Treatment

• Data Validation Module

• XBRL advanced validation (formula, rules, and additional data compliance)
• Error and validation results reporting communication

• Data consumption and integration processes

• Post process data information
• Permanent record and storage on back office systems

• Analyst Information Services

• Preparation of data for internal reporting systems
• Integrate in Business Intelligence systems implemented in Data Warehouses (DW) and / or DataMarts (DM)

• Expectation Handling

• Due Dates
• Messages sent to late filers
• Confirm all expected set of data have been received

• Monitoring and Statistics

Technical Architecture

According to the Functional architecture defined, the Technical reference architecture should at least enable decoupling reporting entities services from middleware data treatment components and the backend repositories and systems:

Interface with Reporting Entities

• Multi-channel reception
• Access security services

Middleware Processing Services

• XBRL Services

• Dedicated components and frameworks to process, validate and treat the reported data
• XBRL Repository (taxonomies and reports are stored, cached and retrieved to support )

• Infrastructure

• Platform dependent components to trace, secure, transform, adapt, route and integrate.

Backend Systems Integration

• Messaging and Integration services

• To transform, adapt, convert and store into the different systems:

• Corporate BackOffice
• Data Warehouse systems (DW)
• Relational Data Base Management Systems (RDBMS)
• Department systems

• An Enterprise Service Bus with adaptors and connectors to internal systems

• Analytic Packages and Business Intelligence Tools

• Prepare and Post process data information

As a summary, the figure 7 illustrates an overview diagram with the typical technical components and services that make up an XBRL Technical Architecture of Reference.

Figure 7 — XBRL Technical Architecture of Reference Overview

The specific implementation technology selected for these services is fully dependent on each National Supervisor Authority (NSA), and out of the scope of these guidelines.

Our recommendation is to invest enough time during the preparation phase to select specific technologies for each service, to determine the optimal solution in terms of products, tools or custom development frameworks and their functional coverage. As a good practice to ensure the success of the solution, we recommend creating a Proof of Concept (PoC) during the preparation phase to verify appropriate technology integration, performance and service quality that is required for the operational system, and allow time for refinement of the initial design.

The evolution of this reference architecture is foreseen as distribute computing resources to process data using better computing capacities and storage facilities to optimize by scaling these resources. Several rising technologies like cloud computing and big data analytics are establishing new environments to process and find new correlation on collected information. Those technical architectures oriented towards separation of services implementation are better prepared to be evolved to these new technologies with less effort and investment. According to the TOGAF lifecycle we have introduced the initial steps for XBRL Architecture definition in National Supervisors.

The next steps for the regulator will be to identify the concrete service implementation according to their needs.

Management and maintainability