Re: Strange Validation error in COREP reporting.

128 views
Skip to first unread message
Message has been deleted

Victor Berg

unread,
Apr 7, 2015, 8:04:48 AM4/7/15
to arelle...@googlegroups.com
Sorry my bad this is Corep 2.0.3 report. NOT AE. 

Den tisdag 7 april 2015 kl. 13:32:50 UTC+2 skrev Victor Berg:
Hi.

I have created a xbrl file using the ArelleGUI as attached.

I am using Arelle 1.0.0 64-bit 2015-02-01 15:53 UTC release.

The attached file gets the following validation error. Please note


loaded in 48.27 secs
Formula xpath2 grammar initialized in 1.53 secs
[info:profileActivity] ... custom function checks and compilation 1.31 secs
no relationships for Calculation
views 61.06 secs
[info:profileActivity] ... assertion and formula checks and compilation 18.37 secs
[message:eba_v0172_m] v0172_m: [C 01.00 (c010)] {r020} = {r030} + {r130} + {r180} + {r200} + {r210} + {r220} + {r230} + {r240} + {r250} + {r300} + {r340} + {r370} + {r380} + {r390} + {r430} + {r440} + {r450} + {r460} + {r470} + {r471} + {r472} + {r480} + {r490} + {r500} + {r510} + {r520} + {r524} + {r529} - http://www.eba.europa.eu/eu/fr/xbrl/crr/fws/corep/its-2013-02/2014-07-31/val/vr-v0172_m.xml 9
[message:eba_v0172_m] v0172_m: [C 01.00 (c010)] {r020} = {r030} + {r130} + {r180} + {r200} + {r210} + {r220} + {r230} + {r240} + {r250} + {r300} + {r340} + {r370} + {r380} + {r390} + {r430} + {r440} + {r450} + {r460} + {r470} + {r471} + {r472} + {r480} + {r490} + {r500} + {r510} + {r520} + {r524} + {r529} - http://www.eba.europa.eu/eu/fr/xbrl/crr/fws/corep/its-2013-02/2014-07-31/val/vr-v0172_m.xml 9
validated in 29.84 secs

I am not using any validation options at all and running the Validation from the GUI. This is EBA 2.2 AE AssetEncumbarance validation.

Do you have any tips why this is occurring? Is there any resource limitations that can be upped?

Br
Victor

Gregorio Mongelli

unread,
Apr 9, 2015, 4:12:30 AM4/9/15
to arelle...@googlegroups.com
Dear Victor,

No resource limit has been reached.

What you have got is a quite usual validation error. It is generated based on rules from the COREP taxonomy.

The error message uses the EBA conventions. Explained in plain English, it would sound like follows:

There is a validation error in the table C 01.00 (the second one when displayed in Arelle). For column c010, the cell at row r020 should be equal to the sum of the cells r030, r130, r180, r200, r210, r220, r230, r240, r250, r300, r340, r370, r380, r390, r430, r440, r450, r460, r470, r471, r472, r480, r490, r500, r510, r520, r524 and r529. Arelle has found that this is not the case with the XBRL instance that you have opened.

Open again your XBRL instance in Arelle and go to table C 01.00. You will easily find the cells at the origin of the message. The rows and columns are labelled with numbers that correspond to the numbers given in the error message.

The complete reference for the notation can be found at the EBA Web site:

Data Point Model and Taxonomies for Implementing Technical Standard (ITS) on Supervisory Reporting

Best regards,

Gregorio Mongelli

Victor Berg

unread,
Apr 10, 2015, 7:12:09 AM4/10/15
to arelle...@googlegroups.com
Thank you Gregorio!

But it is not the solution to my problem.
I forgot to mention that the values in the suggested validation error add up ok in ArelleGUI! I made the calculation manually to check.
So that is not it.

And also this validation error does not appear in previous version of Arelle.

Kind regards
Victor

Gregorio Mongelli

unread,
Apr 10, 2015, 10:07:23 AM4/10/15
to arelle...@googlegroups.com
Hello Victor,

That case is different.

Have you checked your 'New Fact Item Options'? What values do you currently use for 'Monetary decimals' and 'Non-Monetary decimals'? The used interval arithmetic gives sometimes counter-intuitive results...

Other possible causes for problems is a mismatch in the decimal separator. For the COREP taxonomy to work reliably, you must set the language to English-UK. The decimal separator is in that case the dot ('.'). It is a quite basic suggestion, but sometimes it is overseen.

Best regards,

Gregorio Mongelli
Reply all
Reply to author
Forward
0 new messages