How can I go back to an old version of the XBRL Auditor after installing an update?
When updating the XBRL Auditor, the old version will always be preserved. For instance, if updating from version 1.0.9 to 1.0.10, the version 1.0.9 is still installed. It can be started manually, by running the AMANA.XBRL.Auditor.exe in the users local AppData folder, which can usually be found here:
The taxonomy is available only in English, or the Formula validation results are displayed as cryptical messages?
It seems that the XBRL taxonomy cache is incomplete. To solve this issue, please execute the following steps:
- Open the Auditor and go to Settings -> XBRL Processor Settings.
- Make sure, that Force XBRL Offline cache is checked (if not, please check & save).
- Open the XBRL Cache Folder.
- Extract the following ZIP file in this folder, replace existing files if asked.
- Delete the #bin folder.
- Restart the Auditor.
How can I validate an XHTML report without tagging?
Non-XBRL reports can be validated with the integrated XML Schema validator against the XHTML 1.1 schema. Please open the validator from the Tools menu and select the XHTML files to validate, then click on the large button at bottom of the window. No errors means its a valid file.
When validating non-XBRL XHTML files, I get warnings about invalid XML nodes in the namespace of http://xbrl.org/2013/InlineXBRL
Zhis happens because the XHTML documents contain iXBRL elements (e.g. taggings), which are unknown to the XHTML 1.1 scheme.
When opening the XBRL report, I get an error message about too many errors, what can I do?
The following message box will be shown and no report will be loaded:
This error will be displayed, if there are more then 1000 validation messages raised by the XBRL validation. To solve this issue, just increase the number of errors allowed by changing the XBRL processor settings file.
- Open the XBRL Processor settings from the Settings menu, and click on the Save button. Then close the dialogue and the Auditor.
- Open the settings file from C:\Users\user.name\AppData\Roaming\AmanaConsulting\SmartXBRLSettings.xml with the notepad.
- Look for the line with MaxValidationExceptionLimit and change it to e.g. 1000000.
- Save the file and restart the Auditor.
Where is "Jump-To-Fact" in the context menu?
You can now jump to facts by left clicking on the value you want to jump to.
Why are some calculation inconsistencies WARNINGS and some are ERRORS?
XBRL reports (like ESEF) usually come with an entity specific Calculation Linkbase, that defines how totals in tables are calculated. If calculation inconsistencies are signalled, it means that the calculated value of a total differs from the actual reported value. However, some calculation inconsistencies are often unavoidable: Due to reporting of rounded values (e.g. to millions), small rounding differences are “common practice”. In order to distinguish rounding inconsistencies from real calculation issues (that usually indicate tagging issues), the AMANA XBRL Engine allows to enable a Calculation Linkbase Validation Severity Error Threshold, which must be configured in the XBRL (user based) settings. If the threshold is activated and set to e.g. 1%, it means that the all calculation inconsistencies where the delta is smaller than 1% of the rounded reported value are deemed to be WARNINGS, while all inconsistencies with differences bigger then the threshold are deemed to be ERRORS. If the threshold is not set, all calculation inconsistencies are signalled with a WARNING severity.
To activate this threshold you have to click on Settings>XBRL Processor Settings.
In the window you can mark the first option.
What is the meaning of the warning "The maximum XBRL reporting period columns have been reached, some periods are hidden"?
This warning will be shown if the number of periods in a report exceeds the maximum allowed number.
The periods are then no longer displayed in full in in the Tree View.
A complete display of all periods is then only possible in the Table View or in the Excel export.