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 2015 SEC reporting year from 2015-01-01 to 2015-12-31

1. Results from Data Quality Committee Conformance Suite

The conformance suite contains fail and pass cases for each rule published by the Data Quality Committee (DQC).  Download the conformance suite zip file.

The conformance suite produces results outlined below in a .csv file:

  • Test case rule id – This should follow the format DQC_0001.51.2538 where the last sequence of numbers is the tescase number. This number for each testcase is included in the conformance suite files.
  • Name of the testcase – This is the name given to the testcase in the conformance suite files.  For example:”Flag a fail case when no line item item element is used but the member EstimateOfFairValueFairValueDisclosureMember appears on the FairValueByFairValueHierarchyLevelAxis Axis
  • File  – This is the file location of the testcase. This could either be a file included in the conformance suite or a file filed with the SEC or at a URL.
  • Status – This is the status of the test. It can be either pass or fail. This is the results generated by your XBRL software for the specific testcase.
  • Expected – This field has the name of the expected rule number that is returned from running the rule. This is included in the variation file of the conformance suite. For example for testcase  DQC_0001.51.2533 the filed will be populated by  DQC.US.0001.51
  • Number – This should report the expected number of errors. If a rule runs 3 times for the testcase it will give a result of 3. The number of errors is included in the variation.xml file.
  • Actual – This field has the name of the actual rule number that is returned from running the rule. Each time the rule firs it is added as a space separated list in this field. For example  DQC.US.0009.15 DQC.US.0009.15

Download a sample of the results report.

2. Results from Actual Filings for 2015

The second requirement is to run the DQC’s Approved Rules with your software against all filings filed with the SEC in a given base year. The current base year is 2015. 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, 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>2015-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, 2014-05-24 to 2014-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: 2014-05-24 to 2014-09-30
    Dimensions: none
    Unit: none
    Rule version: 1.0</message >
 <result>
</rule_results>

View a simple example of the result.

Updates / Timing

The DQC approves rules semiannually – software must be certified each time new rules are approved by the Committee.

Comment