cdq-certified

XBRL US Members and software providers seeking certification for an application must provide two pieces of information and complete the Application Certification Inquiry form at right.

  1. Results from running the Data Quality Committee Conformance Suite
  2. Results from rules run against Actual Filings for the previous 12 months

1. Results from Data Quality Committee Conformance Suite

The Conformance Suite contains sample fail and pass cases published by the Data Quality Committee (DQC) in the ‘tests’ directory of each release, along with files and scripts used to process SEC filings with Arelle and compare results in the ‘out’ subfolder with messages generated when the actual SEC filings listed in the travis.yml file are run.  Download the conformance suite for the latest release from the right-side of this page.

Software providers should provide evidence that their tool produces identical messaging to each of the files in the ‘out’ folder of the Conformance Suite, either by using Travis CI (modify the requirements.txt file of the Conformance Suite to instantiate your environment) or another documented method. See Travis CI results.

2. Results from Actual Filings for the Last Twelve Months

The second requirement is to run the DQC’s Approved Rules with your software against all filings filed with the SEC within the preceding twelve months.

Within that tranche, new rules or updates in subsequent releases will not be evaluated. We summarize changes for releases on https://github.com/DataQualityCommittee/dqc_us_rules/releases and there’s a ‘compare’ button on that URL that diffs releases.

The results of running the rules should be captured in an XML file and shared with XBRL US.

We compare these results against our expected results (see XBRL API query below), identify any differences and let you know where changes may be required. This process ensures that all certified software creates identical results.

These fields must be reported as part of the XML file:

  •   sec_accession_number
  •   company_name
  •   document_type
  •   filing_date
  •   rule_num
  •   rule
  •   message

Download the schema for this file.

The xml file should look like the following:

<rule_results>
  <result>
    <sec_accession_number>0001019687-15-000021</sec_accession_number>
    <company_name>HDIMAX MEDIA, INC.</company_name>
    <document_type>S1</document_type >
    <filing_date>2016-01-02</filing_date >
    <rule_num>DQC.US.0006.14</rule_num >
    <rule_name>DQC.US.0006</rule >
    <message>The number of days, 130 in the date range reported for 1. Description of Business, 2015-05-24 to 2015-09-30 is not consistent with the Document Fiscal Period Focus with a value of Q3.
    The properties of this us-gaap:BusinessDescriptionAndBasisOfPresentationTextBlock fact are:
    Period: 2015-05-24 to 2015-09-30
    Dimensions: none
    Unit: none
    Rule version: 1.0</message >
 <result>
</rule_results>

View a simple example of the result.

XBRL US Members can use the XBRL API to query the results: https://api.xbrl.us/api/v1/assertion/search?assertion.source=DQC&fields=report.accession,entity.*,report.document-type,report.filing-date.sort(DESC),assertion.code,assertion.type,
assertion.detail,assertion.offset(0)

Continue to increment the assertion.offset by 2000 in a process to pull the data back for the preceding 12 months. Within that tranche, subsequently approved rules or updates to the version being evaluated for certification will not be considered. Use the ‘Compare’ option for the release on the DQC Releases page to review a ‘diff’ of the releases.

Updates / Timing

The DQC approves rules 3-4 times per year – software must be certified each time new rules are approved by the Committee.

Comment