Sample Data Issues

Negative Value Reported for a Concept that is expected to have a Positive Value

Detected by XBRL Consistency Suite 156,303 times.

What causes this data issue?

The fact for a specific concept (tag) is reported with a negative value. The concept selected should be reported as a positive amount. The amount should only be negative in exceptional circumstances.

Below are XBRL Consistency Check details for this data issue as it was included in a company filing to SEC summarizing the period between '2010-07-01', '2010-09-30'.

The concept "GrossProfit" has a negative value reported for a concept that is expected to have a positive value in the period duration('2010-07-01', '2010-09-30'). Element: GrossProfit
In general terms, GrossProfit is expected to have a zero or positive value. GrossProfit has been input with a -67,632. Ensure that the input is as intended and consistent with the entity having a gross loss for the period noted. The context is [ entity=entity('http://www.sec.gov/CIK', '0001427714'), period=duration('2010-07-01', '2010-09-30'), unit=USD ] (id:3874) {GrossProfit [ entity=entity('http://www.sec.gov/CIK', '0001427714'), period=duration('2010-07-01', '2010-09-30'), unit=USD ]} r17885

Invalid Axis Member Combination

Detected by XBRL Consistency Suite 126,788 times.

What causes this data issue?

The member used for this value cannot exist on the axis defined in the company extension. The filer needs to select a valid member for the axis or consider using a different hypercube to report the fact.

Below are XBRL Consistency Check details for this data issue as it was included in a company filing to SEC summarizing the period between '2011-04-01', '2011-06-30'.


The StockIssuedDuringPeriodValueNewIssues with a value of 26,400 is dimensionally qualified with the StatementScenarioAxis (Statement, Scenario [Axis]). Members on the Statement, Scenario [Axis] should represent various types of reporting scenarios (e.g., actual, budget, previously reported). In the case noted, it appears that the preparer has included a non-reporting scenario element as a member element on the Statement, Scenario [Axis]. Consider the use of this member element on the Statement, Scenario [Axis] and replace it with a member that represents a financial reporting scenario. (id:9609) {StockIssuedDuringPeriodValueNewIssues[ entity=entity('http://www.sec.gov/CIK', '0001160479'), period=duration('2011-04-01', '2011-06-30'), unit=USD, StatementScenarioAxis=EmploymentContractsMember ]} r17885

Incorrect Calculation Weight Used

Detected by XBRL Consistency Suite 51,872 times.

What causes this data issue?

Below are XBRL Consistency Check details for this data issue as it was included in a company filing to SEC summarizing the period between '2011-01-01', '2011-12-31'.

The concept "NetCashProvidedByUsedInOperatingActivities" has a incorrect calculation weight used in the period duration('2011-01-01', '2011-12-31'). Element: NetCashProvidedByUsedInOperatingActivities
The concept IncreaseDecreaseInAccountsReceivable is included in the calculation of NetCashProvidedByUsedInOperatingActivities. IncreaseDecreaseInAccountsReceivable is a credit balance type representing an increase in the value of the asset as the natural positive input value. As an increase in the value of the asset over the period the item should have an overall negative one (-1) calculation weight impact on NetCashProvidedByUsedInOperatingActivities. This represents a subtraction from NetCashProvidedByUsedInOperatingActivities. The item has incorrectly been provided a positive one (+1) calculation weight in the extension taxonomy. Correct the calculation weight to negative one (-1) and input the value as a positive amount if this is an increase in the value of the asset and a negative amount if a decrease in the value of the asset. (id:10007) {NetCashProvidedByUsedInOperatingActivities with [ entity=entity('http://www.sec.gov/CIK', '0000352998'), period=duration('2011-01-01', '2011-12-31'), unit=USD ]} r17885

Value Reported for a Concept that should be Zero or Empty

Detected by XBRL Consistency Suite 21,021 times.

What causes this data issue?

In some cases the value reported for a concept should be zero or empty. This can occur in tables where facts can be reported in multiple intersection points of the tables defined in the US GAAP Taxonomies. These checks indicate when these intersection points could be invalid. For example in the Statement of Shareholders Equity the value of new stock issued should not be comprised of a treasury stock component.

Below are XBRL Consistency Check details for this data issue as it was included in a company filing to SEC summarizing the period between '2011-01-01', '2011-06-30'.

The concept "StockIssuedDuringPeriodValueStockDividend" has a value reported for a concept that should be zero or empty in the period duration('2011-01-01', '2011-06-30'). Element: StockIssuedDuringPeriodValueStockDividend

Member(s) Impacted if any: RetainedEarningsMember

StockIssuedDuringPeriodValueStockDividend with value -2,359,755 must be zero or absent. The context is [ entity=entity('http://www.sec.gov/CIK', '0001426506'), period=duration('2011-01-01', '2011-06-30'), unit=USD, StatementEquityComponentsAxis=RetainedEarningsMember ] (id:0575) {StockIssuedDuringPeriodValueStockDividend[ entity=entity('http://www.sec.gov/CIK', '0001426506'), period=duration('2011-01-01', '2011-06-30'), unit=USD, StatementEquityComponentsAxis=RetainedEarningsMember ]} r17885

Deprecated Element is Reported

Detected by XBRL Consistency Suite 15,643 times.

What causes this data issue?

Below are XBRL Consistency Check details for this data issue as it was included in a company filing to SEC for the period ending '2010-12-31'.

The deprecated concept "RelatedPartyDebtNoncurrent" is incorrectly reported in the period instant('2010-12-31'). Element: RelatedPartyDebtNoncurrent
RelatedPartyDebtNoncurrent is a deprecated item, but has been reported in the Instance with a value of 3,055. Deprecated items should not be used. Guidance on the replacement item to use for this item is provided in the Deprecated Label of the RelatedPartyDebtNoncurrent concept. (id:9612) {RelatedPartyDebtNoncurrent[ entity=entity('http://www.sec.gov/CIK', '0001381341'), period=instant('2010-12-31'), unit=USD ] r17885

Context Date is Subsequent to the Period Reported

Detected by XBRL Consistency Suite 11,075 times.

What causes this data issue?

Below are XBRL Consistency Check details for this data issue as it was included in a company filing to SEC summarizing the period between '2010-01-03', '2011-01-01'.


It is expected that OtherPostretirementBenefitsPayments with a value of 15,000,000 and an end date of instant('2011-01-01') is a forecasted value based on the fact that end date of the Document Period End Date is instant('2010-07-03'). As such the forecasted value should be dimensionally qualified with the Scenario axis and the forecast member. For values that are forecasts of future values use the scenario axis with the Forecast Member element to indicate that these are not actual values but estimates of the value for this line item in the future period. If the value is not a forecasted value consider revising the context date of OtherPostretirementBenefitsPayments to be the same as the context end date of the document or changing the context of the Document Period End Date. (id:11425) {OtherPostretirementBenefitsPayments [ entity=entity('http://www.sec.gov/CIK', '0000055067'), period=duration('2010-01-03', '2011-01-01'), unit=USD, DefinedBenefitPlansDisclosuresDefinedBenefitPlansAxis=OtherNonPensionPostretirementMember ]} r17885

Required Value that is Not Reported

Detected by XBRL Consistency Suite 9,885 times.

What causes this data issue?

Certain facts under a given set of circumstances are required to be reported in a filing. For example a company should report assets or earnings per share/unit. Very few concepts meet this condition but the ones that do should be reported. It should be rare for an extension to be made for these concepts as their meaning is either very generic or explicitly defined in US GAAP.

Below are XBRL Consistency Check details for this data issue as it was included in a company filing to SEC summarizing the period between .

The concept "IncomeLossFromContinuingOperationsPerDilutedShare" is a required value that is not reported in the period . Element: IncomeLossFromContinuingOperationsPerDilutedShare
Disregard this rule, if the entity is not required to report earnings per share. IncomeLossFromContinuingOperationsPerDilutedShare was not reported. As Registrant has reported EntityPublicFloat of 1,030,000,000, indicates within the Instance the existence of income or loss from continuing operations, discontinued operations or income or loss from extraordinary items, and the existence of dilutive securities, it is expected that IncomeLossFromContinuingOperationsPerDilutedShare will be reported. If the Registrant does not have discontinued operations, but has extraordinary items and has used the element IncomeLossBeforeExtraordinaryItemsAndCumulativeEffectOfChangeInAccountingPrinciplePerDilutedShare then consider replacing the element with IncomeLossFromContinuingOperationsPerDilutedShare as it is more specific to the concept. (id:5885) {IncomeLossFromContinuingOperationsPerDilutedShare[]} r17885

Invalid unit of measure

Detected by XBRL Consistency Suite 9,874 times.

What causes this data issue?

Below are XBRL Consistency Check details for this data issue as it was included in a company filing to SEC for the period ending '2009-12-31'.


It is expected that the element ConcentrationRiskPercentage with a value of 0.02 is reported with a unit that is equal to pure. If the unit is equal to pure check that the reference is described correctly. The measure should be described as xbrli:pure NOT pure. In those cases where an extension type is used then consider changing the datatype from pureItemType to a datatype that matches the unit used. (id:8835) {ConcentrationRiskPercentage [ entity=entity('http://www.sec.gov/CIK', '0001489137'), period=instant('2009-12-31'), unit=pure, ConcentrationRiskByBenchmarkAxis=SalesRevenueGoodsNetMember, ProductOrServiceAxis=OtherCeriumProductsMember, EconomicEntityAxis=MolycorpMountainPassFacilityMember ]} r17885

Calculation Error

Detected by XBRL Consistency Suite 8,358 times.

What causes this data issue?

Below are XBRL Consistency Check details for this data issue as it was included in a company filing to SEC summarizing the period between '2010-01-01', '2010-12-31'.

The concept "IncomeLossFromContinuingOperationsPerBasicShare" has a calculation error in the period duration('2010-01-01', '2010-12-31'). Element: IncomeLossFromContinuingOperationsPerBasicShare
IncomeLossFromContinuingOperationsPerBasicShare with a reported value of 1.57 IncomeLossFromContinuingOperationsPerBasicShare does not equal the quotient derived by dividing income (loss) from continuing operations available to common shareholders by the weighted average number of basic shares outstanding for the period or a per share value of 1.345 (3 d.p.) (id:5709) {IncomeLossFromContinuingOperationsPerBasicShare[ entity=entity('http://www.sec.gov/CIK', '0000812074'), period=duration('2010-01-01', '2010-12-31'), unit=USD/shares ]} r17885

Incorrect Decimals Defined

Detected by XBRL Consistency Suite 6,984 times.

What causes this data issue?

Below are XBRL Consistency Check details for this data issue as it was included in a company filing to SEC summarizing the period between '2010-01-01', '2010-12-31'.


The value 0.89 of the fact PercentageOfPartnersCapitalLongFutureContract is inconsistent with the "decimals" value of 0. The fact value indicates a higher level of accuracy than the decimal value implies. Consider either amending the fact to a lower level of accuarcy or changing the decimal value to match the accuracy of the fact. The context is [ entity=entity('http://www.sec.gov/CIK', '0000794775'), period=duration('2010-01-01', '2010-12-31'), unit=USD, InvestmentTypeAxis=CurrencySwapMember ] (id:10134) {PercentageOfPartnersCapitalLongFutureContract [ entity=entity('http://www.sec.gov/CIK', '0000794775'), period=duration('2010-01-01', '2010-12-31'), unit=USD, InvestmentTypeAxis=CurrencySwapMember ]} r17885

Required Value that Should be Reported if Another Value is Reported

Detected by XBRL Consistency Suite 6,474 times.

What causes this data issue?

In certain circumstances if a fact is reported for a concept then a fact for another concept should also be reported. These checks help to determine if the company has selected the correct element by cross referencing the concept selection against other concepts. These checks are most applicable when dimensions have been used.

Below are XBRL Consistency Check details for this data issue as it was included in a company filing to SEC summarizing the period between '2010-01-01', '2010-12-31'.

The concept "ComprehensiveIncomeNetOfTaxAttributableToNoncontrollingInterest" is a required value that should be reported if another value is reported in the period duration('2010-01-01', '2010-12-31'). Element: ComprehensiveIncomeNetOfTaxAttributableToNoncontrollingInterest
The element ComprehensiveIncomeNetOfTaxAttributableToNoncontrollingInterest with a value of 1,429,000 has been included in the Instance, indicating that the entity has a non-wholly owned subsidiary for which exists a noncontrolling interest ('NCI') that is represented in the consolidated financial statements. However, the Instance does not include ProfitLoss (Standard label: Net Income (Loss), Including Portion Attributable to Noncontrolling Interest) nor IncomeLossFromContinuingOperationsIncludingPortionAttributableToNoncontrollingInterest (Standard label: Income (Loss) from Continuing Operations, Including Portion Attributable to Noncontrolling Interest) as is expected when an NCI exists. Preparer should consider reviewing the Instance to ensure that the NCI item is properly included and that the reporting entity item is intentionally excluded. (id:9604) {ComprehensiveIncomeNetOfTaxAttributableToNoncontrollingInterest[ entity=entity('http://www.sec.gov/CIK', '0000018926'), period=duration('2010-01-01', '2010-12-31'), unit=USD ]} r17885

Negative Value Reported for an Extension Concept

Detected by XBRL Consistency Suite 5,225 times.

What causes this data issue?

The fact for a specific concept (tag) is reported with a negative value. The concept selected should be reported as a positive amount.

Below are XBRL Consistency Check details for this data issue as it was included in a company filing to SEC for the period ending '2011-03-31'.


The extension item LimitedLiabilityCompanyMemberEquity with a value of -1,612,000,000 is a component of liabilities and stockholders equity but has a negative value. Please review to determine that this is correct. (id:8837) {LimitedLiabilityCompanyMemberEquity[ entity=entity('http://www.sec.gov/CIK', '0001307954'), period=instant('2011-03-31'), unit=USD, StatementEquityComponentsAxis=RetainedEarningsMember, LegalEntityAxis=LimitedLiabilityCompanyMember ]} r17885

Value Reported for a Concept Appears Unreasonably Large or Small

Detected by XBRL Consistency Suite 5,118 times.

What causes this data issue?

Below are XBRL Consistency Check details for this data issue as it was included in a company filing to SEC for the period ending '2011-08-10'.

The concept "EntityPublicFloat" has a value reported for a concept appears unreasonably large or small in the period instant('2011-08-10'). Element: EntityPublicFloat
An EntityPublicFloat with a value of 0 or possibly 'Nil' has been reported with respect to the submitted quarterly report. Reporting a value of zero or nil is incorrect, if the registrant does not report its public float (market cap) in its quarterly submission; this element should not be included in the instance. (id:8081) {EntityPublicFloat[ entity=entity('http://www.sec.gov/CIK', '0001112551'), period=instant('2011-08-10'), unit=USD ]} r17885

Value that Should be Zero or Empty if Another Value is Not Reported

Detected by XBRL Consistency Suite 4,871 times.

What causes this data issue?

In certain circumstances the value of a concept should be zero or absent if another concept is not reported. This is the inverse of the rule that indicates a value is required when another value is reported.

Below are XBRL Consistency Check details for this data issue as it was included in a company filing to SEC for the period ending '2010-12-31'.

The concept "CommonStockNoParValue" has a value that should be zero or empty if another value is not reported in the period instant('2010-12-31'). Element: CommonStockNoParValue
CommonStockNoParValue with a value of 0 has been reported in the Instance. CommonStockNoParValue is defined in the taxonomy as the issuance value per share of no par value common stock. If the preparer discloses the issuance value per share of its CommonStockNoParValue, the tag should be populated with such amount. If, however, the preparer does not disclose the issuance value per share of its CommonStockNoParValue, the tag should either not be provided a value or context in the Instance, or, if the preparer chooses to include CommonStockNoParValue in the Instance, assign a NIL value to the tag. NIL is used to report a fact for which a value is not being disclosed (see Edgar Filer Manual – Volume II 6.6.15). (id:9611) {CommonStockNoParValue[ entity=entity('http://www.sec.gov/CIK', '0001211583'), period=instant('2010-12-31'), unit=USD/shares ]} r17885

Extension Element Should be Considered

Detected by XBRL Consistency Suite 4,097 times.

What causes this data issue?

Below are XBRL Consistency Check details for this data issue as it was included in a company filing to SEC summarizing the period between '2009-01-01', '2009-07-04'.

The concept "StockIssued" has a extension element should be considered in the period duration('2009-01-01', '2009-07-04'). Element: StockIssued
StockIssued, which has a 32,537,000 value in the Instance, is incorrectly modeled in the base taxonomy as a debit balance type. The concept should be a credit balance type; this element was identified and corrected in the 2011 Taxonomy. Consider creating an extension element for this item, using the element that exists in the 2011 Taxonomy. For example, based on the base taxonomy replacement element, the extension element would be StockIssued1 (standard label: Stock Issued, documentation label: The fair value of stock issued in noncash financing activities., balance type: credit, base item type: monetaryItemType, period type: duration). (id:8606) {StockIssued [ entity=entity('http://www.sec.gov/CIK', '0000098677'), period=duration('2009-01-01', '2009-07-04'), unit=USD ]} r17885

Duplicate Value that does Not Match

Detected by XBRL Consistency Suite 3,829 times.

What causes this data issue?

Below are XBRL Consistency Check details for this data issue as it was included in a company filing to SEC summarizing the period between '2011-01-01', '2011-12-31'.

The concept "ShareBasedCompensation" has a duplicate value that does not match in the period duration('2011-01-01', '2011-12-31'). Element: ShareBasedCompensation
Value 18,692,000 for ShareBasedCompensation must be equal to value 18,948,000 for AllocatedShareBasedCompensationExpense. The context is [ entity=entity('http://www.sec.gov/CIK', '0000078814'), period=duration('2011-01-01', '2011-12-31'), unit=USD ]. (id:11966) {ShareBasedCompensation[ entity=entity('http://www.sec.gov/CIK', '0000078814'), period=duration('2011-01-01', '2011-12-31'), unit=USD ]} r17885

Duplicate Extension Concept

Detected by XBRL Consistency Suite 3,490 times.

What causes this data issue?

Below are XBRL Consistency Check details for this data issue as it was included in a company filing to SEC summarizing the period between .

The concept "" has a duplicate extension concept in the period . Element: Not Applicable
'UnitedStatesMember' is an extension element that was reported in the Instance, but duplicates a concept that exists in the US GAAP Financial Reporting or the SEC Non-GAAP taxonomy. Consider replacing 'UnitedStatesMember' with the existing taxonomy concept 'US from the Non-GAAP Country taxonomy'. (id:9021) {'UnitedStatesMember'} r17885

Value Reported for a Concept is Different than the Dimensional Equivalent

Detected by XBRL Consistency Suite 3,328 times.

What causes this data issue?

Below are XBRL Consistency Check details for this data issue as it was included in a company filing to SEC summarizing the period between '2010-01-01', '2010-06-30'.

The concept "NetIncomeLossAttributableToNoncontrollingInterest" has a value reported for a concept is different than the dimensional equivalent in the period duration('2010-01-01', '2010-06-30'). Element: NetIncomeLossAttributableToNoncontrollingInterest
It is expected that NetIncomeLossAttributableToNoncontrollingInterest with a value of 64,301,000 reported on the face of the Income Statement is equivalent to the dimensionally qualified concept, defined by ProfitLoss with [StatementEquityComponentsAxis=NoncontrollingInterestMember] with a reported value of 2,082,000 included in the Statement of Shareholders' Equity and Other Comprehensive Income. This error occurs when the dimensionally qualified fact is not equal to the value (monetary, numerical, or text) input for the standalone item. (id:5763) {NetIncomeLossAttributableToNoncontrollingInterest [ entity=entity('http://www.sec.gov/CIK', '0000895930'), period=duration('2010-01-01', '2010-06-30'), unit=USD ]} r17885

Invalid Line Item Used with an Axis

Detected by XBRL Consistency Suite 3,319 times.

What causes this data issue?

Below are XBRL Consistency Check details for this data issue as it was included in a company filing to SEC summarizing the period between '2008-01-01', '2008-12-31'.


The ScheduleOfEmployeeServiceShareBasedCompensationAllocationOfRecognizedPeriodCostsByReportLineAxis is intended only to be used with AllocatedShareBasedCompensationExpense, ShareBasedCompensation, ShareBasedCompensationArrangementByShareBasedPaymentAwardCompensationCost, EmployeeServiceShareBasedCompensationAllocationOfRecognizedPeriodCostsCapitalizedAmount, StockOptionPlanExpense or RestrictedStockExpense. The Instance has used CostOfGoodsAndServicesSold with a value of 2,535,000, which is not an expected or intended Line Item to be used with this Axis. Reconsider the purpose of the Table and the use of CostOfGoodsAndServicesSold. (id:10497) {CostOfGoodsAndServicesSold[ entity=entity('http://www.sec.gov/CIK', '0000816284'), period=duration('2008-01-01', '2008-12-31'), unit=USD, ScheduleOfEmployeeServiceShareBasedCompensationAllocationOfRecognizedPeriodCostsByReportLineAxis=ShareBasedCompensationExpenseMember ]} r17885