Version 14 includes five new automated checks described below and guidance on tagging axis and members for filers using the IFRS Taxonomy, as well as updates to DQC_0001 and DQC_0081. At its January 20, 2021 meeting, the Data Quality Committee approved the new rules and guidance and set effective dates for: fixes to existing rules for filings after February 28, and; new rules and guidance for filings after April 30, 2020.
New rules and guidance:
DQC_0101 - Movement of Concepts between Calculation Trees (IFRS) - The rule identifies inappropriate calculation descendants of investing, financing or operating items in the company’s extension filing for the statement of cash flows. This rule identifies the calculation children of investing, financing or operating elements in the calculation linkbase of the IFRS taxonomy and compares the set of elements to the calculation children used in the company’s extension calculation linkbase. The rule creates a set of elements from the IFRS taxonomy (under each category) and compares the set to the children of the element in the extension taxonomy and flags an error if the two sets intersect.
DQC_0102 - Element Values Are Equal (IFRS) - This rule tests that the values reported between element relationships that are identified as an accounting constant are consistent within the filing. For example Assets equals Liabilities plus Equity. The rule checks that the components of the calculation are present before checking the calculation. In some cases the components may not be present but their children are. In these cases the value can be derived by adding values across a dimension.
DQC_0103 - Invalid Value for Percentage Items (IFRS) - This rule identifies where filers have used a percentage item type (as defined in the IFRS taxonomy) with a value that is greater than the value of 10.
DQC_0104 - Axis with Inappropriate Members (IFRS) - Certain axes in the IFRS taxonomy should only have certain members as shown in the IFRS taxonomy. This rule tests whether these axes have inappropriate members. Certain axes can have custom or extended (i.e., company specific) members. This rule also tests whether only these axes have custom members and, therefore, limits the use of custom or extended members to those situations where they are appropriate because the member is unique to the filer.
DQC_0105 - FS with No Associated Calculation - The rule checks if a calculation is defined in any role of the company extension, not just the calculations associated with the roles used to define the presentation linkbase for the Income Statement, the Balance Sheet, the Statement of Cash Flows and the Statement of Comprehensive Income.
Removed DQC_0106 - Assets and Liabilities Classified as Held-For-Sale using Duration Element
Guidance on Tagging Axis and Members Using the IFRS Taxonomy (updated January 11, 2021) - Certain axes in the IFRS taxonomy should only have certain members, otherwise consumption of the data is adversely impacted because the resulting axis and member combinations are nonsensical. This guidance provides limitations on the use of certain axis and member combinations that should be adhered to when tagging financial information using the IFRS Taxonomy.
- #500 -
- Updated rule 81 for detailed messages
- Updated test cases for new rules and changes to existing rules (DQC_0001 and DQC_0081)
- Updated Arelle source code install URL
- #504 -
- Update dqc_0095 to only check facts within 90 days of each other
- Update dqc_0104 for new extension item
- Update 2018 ruleset to include dqc_0091 and dqc_0095
- #506 - Fix IFRS 2020 taxonomy references
- #512 -
- DQC_0015 - non-negative removals
- 1039 -
- 1040 -
- 7084 -
- DQC_0046, DQC_0089, DQC_0099 messages
- Updated taxonomy references to https
- #513 - Bump lxml from 3.4.4 to 4.6.2
- #518 - Add rules for 2021 UGT
v14.0.1: #526 plus commit to update DQC_0099 documentation
v14.1.1: #534, #536, #538, #540 (no release deployed at #536)
Change logs, build details & unit test results:
- since last approved release v13.0.6...v14.1.5
- within the current release v14.0.0...v14.1.5
- DQC build 3.0.22782 || xule build 3.0.23221
- Travis CI status -
- the test archive is attached to the release and also embedded in the release in the tests directory. The readme.md outlines the testing process.
Users should update DQC Rules plugin installations to at least 14.1.1 to ensure you're running the latest xule processor for the DQC rules. Remember to update to the latest rulesetMap - see the last step for new installations below.
If you're adding the plugin to your Arelle installation for the first time, install according to the instructions below.
To use DQC Rules with Arelle's graphic interface (GUI):
Download and extract the source code .zip or tar.gz archive from the Assets for this release listed below to your local computer.
Remove all prior DQC Rules plugin installations from Arelle. Any prior version of DQC rules / xule should be removed. To do this, start Arelle, Go to Help->Manage Plugins menu. Select the existing xule (DQC) plugin and click on remove, close the Plugins menu and click "Yes" to allow the Arelle application to restart, then close Arelle.
xulefolder from Arelle's
pluginfolder and replace with files from this release. The plugin folder in the DQC release follows the plugin folder structure in Arelle. The
DQC.pyfile from the
plugin\validatesubfolder of the release should be dropped in the corresponding folder in the Arelle install. Likewise, the
xulefolder and files should be located at the
plugin\xulefolder in the Arelle install.
Initialize the DQC plugin. After the files are copied from the release archive into the Arelle folder structure on the local computer, start Arelle and go to the Help->Manage Plugins menu. Click on the "Select" button, choose "DQC.py" from the list and then click "OK" and "Yes" to restart Arelle. NOTE: It is not necessary to to select the "xule" plugin - the DQC.py plugin imports the xule files automatically.
Set the plugin to validate filings. After Arelle (re)starts, check that there is a check mark next to the DQC option under the Tools->Validation menu. If the DQC is not selected, click on the option to select it and it is now ready to run DQC checks when a filing is opened in Arelle. The current build references are listed in the Change log section of this release page (in Arelle, this detail is found under the Tools->DQC->Version... menu)
Use the Tools->DQC menu to update the Ruleset Map to the current version or manage changes to a customized Ruleset Map in the existing environment. See the README and Usage pages for more details and options.
To use DQC Rules from the command line:
--plugin validate/DQCon the command line. See Using DQC Rules with Arelle - from a command prompt for complete details.
Ruleset Map Options
- The current v14 rulesetMap.json file for public exposure (and previously approved) rules is located at: https://raw.githubusercontent.com/DataQualityCommittee/dqc_us_rules/v14.1.5/plugin/xule/rulesetMap.json
About the DQC Rules Plugin
The DQC rules are run using an Arelle plugin written in an XBRL rule syntax called Xule. Xule is processed in a plugin for the SEC's EDGAR Renderer/Previewer - Arelle on a local computer or server. The DQC plugin reads a specified ruleset and the assertions defined in the ruleset are evaluated against an XBRL instance, a taxonomy or an extension taxonomy, creating validation messages.