This Q&A is intended as general guidance prepared by the XBRL US DQC (Data Quality Committee), and should not be relied upon as authoritative. Filers are encouraged to consult with their own legal and/or with the SEC directly.
The SEC test filing system currently returns warnings for several conditions which should be evaluated to ensure that there are no false positives. The following Q&As should help registrants evaluate these warnings.
- What should we do if we receive a warning that elements used in the filing are deprecated in a future taxonomy? The FASB has deprecated elements in the 2019 taxonomy which are still valid modeling selections for filers who are still reporting using the 2018 taxonomy. The system will generate a warning when a deprecated element is used regardless of which taxonomy is used. While filers are encouraged to convert to the most recent taxonomy, there is no requirement to convert until the SEC removes the 2018 taxonomy; therefore, filers should not create extension elements to replace future deprecated elements. They may proceed filing with this element until they convert to the newest taxonomy.
- What should we do if we get warnings on “negative values” that pass the DQC rules (DQC_0015 and DQC_0080)? The SEC “Negative Values” validation contained in the test filing system does not consider all the exclusions that should be allowed. Values tagged to certain axis/member combinations may allow the tagged value to be negative. Therefore, it is possible that the occurrence of this warning in the test filing result may be a false-positive.Two DQC Validation Rules check numeric reporting items that are tagged incorrectly as negative. DQC_0015 checks the US GAAP filings; and DQC_0080 checks the IFRS filings. These rules incorporate a comprehensive listing of exclusions.Filers are encouraged to run the DQC rule validation. If the DQC validation shows no error on “negative values”, you should proceed with filing and not make any changes to avoid the SEC warning message.
- How should we tag the element securityExchangeNameTradingSymbolDependency if we file on a foreign exchange? The element dei_SecurityExchangeName has a data type edgarExchangeCodeItemType. It currently only allows the following enumerated values: ‘GEMX’, ‘CboeBYX’, ‘CHX’, ‘NYSEAMER’, ‘NASDAQ’, ‘ISE’, ‘MRX’, ‘MIAX’, ‘NYSEArca’, ‘BOX’, ‘NYSE’, ‘CboeBZX’, ‘PEARL’, ‘NYSENAT’, ‘IEX’, ‘CboeEDGX’, ‘CBOE’, ‘C2’, ‘CboeEDGA’, ‘Phlx’, ‘BX’, ‘NONE’.When a filer has securities trading on an exchange other than those that are listed (for example, Toronto Stock Exchange), it will not be able to use the element dei_SecurityExchangeName. Using this element with a value entered that is different from the enumerated values (above) will cause the filing to be suspended. We have received guidance from the Structured Data group at the SEC that these values should not be tagged. If the filing is on a foreign exchange, the field should be left blank.
- What should we do if we receive warnings related to hidden facts? The SEC test system generates a warning for hidden facts. Hidden facts should be referenced by the sec-ix-hidden style property. However, extensible list elements are always hidden without a reference. Registrants should not adjust the modeling to avoid warnings for hidden extensible list elements.
- What should a foreign filer do if it has no tax identifier? The SEC test system does generate a warning when the filer does not tag a value for tax identifier. Therefore, if a company has no Tax identifier, tag a value of “00-0000000”. This option will not generate an SEC warning (revised January, 2020).