Validation: Unterschied zwischen den Versionen
Keine Bearbeitungszusammenfassung |
Keine Bearbeitungszusammenfassung |
||
Zeile 112: | Zeile 112: | ||
| Error. Finalisation is not successful and the XBRL cannot be created. | | Error. Finalisation is not successful and the XBRL cannot be created. | ||
|- | |- | ||
| style="width: 40%" style="text-align: center;| '''Duplicate Label''' <br> <br> [[Datei:Word_Screenshot_toolsxbrl_duplicate label.png|center|400px]] | |||
| A duplicate label warning or error is displayed on cells with equal tag combinations but with different names (labels). For instance, “ifrs-full:Equity” might be tagged in the balance sheet as “Total Equity”, as well as in the Statement of changes in Equity with the label “Equity at 01.01.2019” and “Equity at 31.12.2019”. In this case, three different labels are provided for the same tag. In order to differentiate the meaning of the different labels, its required to set its so called label role. The most common label roles are (samples in brakets): | |||
*Standard label (Equity) | |||
*Total label (Total Equity) | |||
*Period start / Period end label (Equity at beginning/ending of period). | |||
*Verbose label (Equity, as determined by nature). | |||
It is important to align all labels used across the report for all values, that are tagged to the same element. Only one label per role is allowed. This also usually means to remove date references from the period start and end label, “Equity at the end of period” instead of “Equity at 31.12.2019”, because two period end labels (31.12.2019 and 31.12.2020 ) are not possible. | |||
Change preferred label roles and labels under Table Cell Properties: | |||
[[Datei:Word_Screenshot_toolsxbrl_duplicate label description.png|center|800px]] | |||
| Fehler. Eine erfolgreiche Finalisierung und XBRL-Erstellung ist nicht möglich. | |||
|- | |||
| style="width: 40%" style="text-align: center;| '''Duplicate Extension''' <br> <br> [[Datei:Word_Screenshot_toolsxbrl_duplicate extension.png|center|400px]] | |||
| A duplicate extension error is displayed, when the cells with extensions have different properties: e.g. different anchors in the current an previous year; diffrent sign logic for every cell. | |||
| | |||
|- | |||
| style="width: 40%" style="text-align: center;| '''Perid Type''' <br> <br> [[Datei:Word_Screenshot_toolsxbrl_period type.png|center|400px]] | |||
| Period type of the ifrs-full elements is defined in the taxonomy. Items with different period types cannot be included in one calculation: | |||
[[Datei:Word_Screenshot_toolsxbrl_period type description.png|center|800px]] | |||
If the period type is not correct and the item is an extension, please change the period type under Taxonomy Extension Properties. | |||
| | |||
|- | |||
|} | |} | ||
Version vom 12. Januar 2021, 11:27 Uhr
Validating a document
In toolsxbrl you can validate tagged contents in two different ways.
Quick access via the menu ribbon or the status bar
When working with toolsxbrl, you can access the “Validate Document” function at any time. This checks the XBRL taxonomy contents that you entered in the document manager for their structural validity.
Alternatively, you can use the “Status” function in the status bar to start the validation function.
![]() |
Good to know
|
---|---|
toolsxbrl cannot check the contents to see if the XBRL taxonomy contents were used correctly. |
Validating contents when creating iXBRL files
When you create your XBRL-compliant presentation files in iXBRL format, you can have the validity of the taxonomies that you saved checked at the same time. In the “XBRL” menu, click on “Generate iXBRL”.
Once you have configured your iXBRL file, you can click on “Generate and Validate iXBRL”.
![]() |
Good to know
|
---|---|
The validation is performed provided you have not selected the “Skip Validation” setting. |
You then see a detailed overview of possible validation errors. These are displayed categorised according to their severity as a “Warning” or “Error”.
Validation errors and solution approaches
When using the validation quick access
Error/warning | Description | Severity |
Report Entity Identifier: LEI missing |
A valid ESEF document requires the correct LEI of the payee: www.gleif.org | Warning - Can be ignored for testing purposes only. Finalisation is not possible |
No Table Element mapped |
Each table with mappings must be given a table element. | Error. Finalisation is not successful and the XBRL cannot be created. |
Cell status „in edit“ or „review pending“ |
Workflow only: Not all cells have the final status. | Warning - It is recommended that you eliminate this warning before finalisation |
Cell has no mapping“ |
A cell in the table with a table tag has not been assigned. All cells with internal information must be given a tag. | Warning - Can be ignored for testing purposes only. Finalisation is not possible |
Cell not part of calculation relationship |
All selected cells containing internal information must be part of a calculation | Warning - Can be ignored for testing purposes only. Finalisation is not possible |
Duplicate mapping |
Tags may appear twice in a document only if the context is different or the value is equal | Error. Finalisation is not successful and the XBRL cannot be created. |
Extension element has no anchors |
Each extension requires at least one anchor, unless it concerns the total of a calculation | Error. Finalisation is not successful and the XBRL cannot be created. |
The reported total does not match the calculated total |
The rounded sum of a calculation does not equal the rounded calculated sum. | Warning - It is recommended that you eliminate this warning before finalisation |
The selected format is incompatible with tag |
An incorrect basic format was used such as a date format for a monetary value | Error. Finalisation is not successful and the XBRL cannot be created. |
The value is not valid for the format |
The selected format cannot be applied to the value of the tag. | Error. Finalisation is not successful and the XBRL cannot be created. |
Tagging element not found in taxonomy |
The selected element was not found in the taxonomy. It is recommended that you use a different taxonomy version. | Error. Finalisation is not successful and the XBRL cannot be created. |
Line item missing |
A cell has selected dimension elements but no position. | Error. Finalisation is not successful and the XBRL cannot be created. |
Dimensionally invalid |
Each mapping element in a table must contain the same dimensions | Error. Finalisation is not successful and the XBRL cannot be created. |
Duplicate Label |
A duplicate label warning or error is displayed on cells with equal tag combinations but with different names (labels). For instance, “ifrs-full:Equity” might be tagged in the balance sheet as “Total Equity”, as well as in the Statement of changes in Equity with the label “Equity at 01.01.2019” and “Equity at 31.12.2019”. In this case, three different labels are provided for the same tag. In order to differentiate the meaning of the different labels, its required to set its so called label role. The most common label roles are (samples in brakets):
It is important to align all labels used across the report for all values, that are tagged to the same element. Only one label per role is allowed. This also usually means to remove date references from the period start and end label, “Equity at the end of period” instead of “Equity at 31.12.2019”, because two period end labels (31.12.2019 and 31.12.2020 ) are not possible. Change preferred label roles and labels under Table Cell Properties: |
Fehler. Eine erfolgreiche Finalisierung und XBRL-Erstellung ist nicht möglich. |
Duplicate Extension |
A duplicate extension error is displayed, when the cells with extensions have different properties: e.g. different anchors in the current an previous year; diffrent sign logic for every cell. | |
Perid Type |
Period type of the ifrs-full elements is defined in the taxonomy. Items with different period types cannot be included in one calculation:
If the period type is not correct and the item is an extension, please change the period type under Taxonomy Extension Properties. |
When applying the validation process when creating the XBRL files
Error/warning | Description | Solution |
Empty XBRL taxonomy extension created |
It was determined that the report may need a taxonomy extension. | Configure the correct document setting. |
All other types in Report generation folder |
An error occurred when the XBRL report files were created. | If the validation can run via the quick access without any errors, please contact firesys. |
XBRL Instance Dimension Specification |
An invalid output file was created/found. | If the validation can run via the quick access without any errors, please contact firesys. |
Filing Rules Validation |
It is assumed that the approval regulations set out by the supervisory authorities were not complied with. | Ensure that the corresponding taxonomies and configurations were selected (such as ESMA for ESEF). |
XBRL Instance Specification 2.1 |
The converted XBRL file is invalid. | You can ignore these warnings if they refer to errors in calculation relationships for example. If in doubt, please contact firesys. |
XBRL Taxonomy Specification 2.1 |
The extension taxonomy is invalid. | Please contact firesys. |
XBRL Instance Formula 1.0 |
Presumably, not all rules from the taxonomy were met. | You may be able to ignore these warnings if you can create documents without any problems. However, it is recommended that you correct errors (where possible). If in doubt, please contact firesys. |