...
| Issue | Version | Severity | Workaround |
|---|---|---|---|
| Taxonomy extension linkbase changes are not fully detected by the XBRL Instance Comparer. | 1.1.* | Medium | Compare the linkbases manually with the XBRL Report Data View or the Excel report. |
Auditor settings are set to default after version update. | 1.1.4 | Low | After the update, please adjust the setting again according to your needs. |
| Naming convention warning shown in some cases even when file name is correct. (Guidance 2.6.3, ESEF Filing Rule validation 2021 only) | 1.1.4 | Medium | Please ignore messages and check the file name manually. Format should be: Name-Year-Month-Day-Language Code.zip Sample: amana-2020-12-31-de.zip |
The Check 16 returns warnings on tags, even if those tags are valid to be used. | 1.1.4 | Medium | Just ignore messages from check 16, if the tagging is appropriate. Please find more information on the Effective/Expiry attributes in the XBRL taxonomy in the IFRS Preparers Guide (page 32ff): |
The Check 2 returns Auto Check "Failed" after the " with Auto-Check Details "Inline XBRL 1.1 valid!"" button is clicked, even if it was valid before, after loading the document. This happens only if there are XBRL Specification 2.1 errors in the document.
| 1.1.5 | Medium | Please ignore message Auto Check status when Check Details are validfor check 2 if its changing after the document has been opened. The XBRL Validation messages are correct and will correctly show Inline XBRL 1.1 errors if existing. |
