Basic functionality

ABACUS/Regulator supports regulators to fulfill their requirements in the areas of regulatory data collection, data validation, data storage, data visualization as well as data remittance, e.g. to pan-European authorities.

The following are examples of reporting frameworks currently available in ABACUS/Regulator as modules (they need to be separately licensed):

EBA-ITS:

EIOPA:

The reporting frameworks defined by EBA and EIOPA are ever evolving. New reporting requirements are added, existing reporting requirements are modified. Such changes will be implemented as defined and to the extent included in the maintenance services. ABACUS/Regulator is currently available in English and German.
 Other languages are available on demand. This applies to the GUI menus as well as application dialogues and messages.

ABACUS/Regulator is designed as a multi-user system. This means that multiple users can work with the application simultaneously. Data integrity is accounted for via database mechanisms in order to avoid inconsistencies or data losses. Master data is usually set up during the initial installation of the application and remains mainly static (e.g. reporting entity keys, reporting entity details, user management etc.).


Data model and interfaces

The data model builds the foundation of the application and its logic. In addition to the data model, interfaces refer to the means of delivering required data to the application (input data) or to external applications and stakeholders (output data).

Input Interface

Based on the data model, ABACUS/Regulator provides an XML-based and XBRL-based input interface to load data. ABACUS/Regulator allows automatic and bulk upload of multiple datasets. The files can be imported manually (via the ABACUS GUI) or automatic via batch processes and the use of external scheduling tools (e.g. UC4).
 In order to simplify regulatory data collection an Excel input interface module (X2A – Excel to ABACUS) can be separately licensed.

Output Interface

On the output end, reports can be generated in XBRL format according to definitions given by the EBA/EIOPA.
 In addition to the XBRL files, ABACUS/Regulator is also able to generate output files for Excel as well as output files in PDF format. In contrast to the XBRL files, these formats display the data in the actual report layout/format to provide better usability. A detailed documentation of the interfaces is provided through the ABACUS/Regulator Wiki.

Data collection and data validation

The ABACUS/Regulator data model and interfaces are specifically designed to efficiently handle the reporting process necessary for all covered reporting requirements.

Collection of regulatory reports

Automated upload and manual data collection are possible. The generation of reporting templates is handled by mapping the input data to the fields of the output reports. These mappings are defined as allocation rules and form the main logic of ABACUS/Regulator. The underlying allocation rules are accessible on a cell basis for each cell via the conditions menu within ABACUS/Regulator.

Validation of regulatory reports

To support in the verification of the reporting data, ABACUS/Regulator provides a validation rules engine that is executed as a separate process step.
 Each validation checks for a correct dependency between different cells, e.g. “cell A = cell B + cell C”. Validation checks support in verifying that delivered data is reasonable and meaningful. In case of validation errors, the results are captured within the database in an readable error table. 
The validation engine covers all rules specified by EBA/EIOPA and implemented in the underlying XBRL taxonomies.

Back
Share:

Choose your language

×