2.1 Dates of the Context

Issued: 1/27/12

Impact: All US GAAP

Instance Document

2.1.3 Forecasted Information

Issue There are a large number of facts that have a context date that is greater than the period end.  Some of these represent subsequent events, but a large number of reported facts have date contexts that are more than 90 days after the year end and, effectively, represent forecast values.  We observed that these […more]


2.4 Decimals

Issued: 12/2/11

Impact: All US GAAP

Instance Document

2.4.1 Decimal Disagreement with the Reported Fact

Issue In a number of filings, the value of the decimal attribute disagrees with the value of the fact reported.  For example, in a number of cases, values are reported with a higher level of accuracy than the decimal would indicate, such as 123,867,000 with a decimal value of -6.  This means that the number […more]


2.1 Dates of the Context

Issued: 12/2/11

Impact: All US GAAP

Instance Document

2.1.2 Subsequent Events and Durational Concepts

Issue A number of companies have reported subsequent events for concepts that are durations. However, in a number of cases, the durations are for periods that have an end date that is later than the date the report is actually issued.  For example, companies report a subsequent event with a duration that spans the period […more]


2.1 Dates of the Context

Issued: 1/28/11

Impact: All US GAAP

Instance Document

2.1.1 Use of Dates in Contexts for Future Payments or Receipts

Issue In files submitted as part of the SEC XBRL filing program, we observed a number of future dates recorded in the context of the XBRL instance. Undoubtedly, some of these are simple data errors, but others are a misrepresentation of the context date. The maximum filed end date observed was “2030-07-01”. The maximum date […more]


2.2 Use of Data Types

Issued: 1/28/11

Impact: All US GAAP

Instance Document

2.2.2 Percentage Item Types

There are a number of issues observed in regards to the use of percentages in filings. Issue 1: Incorrect Scale Issue A number of companies have represented the percentage with an incorrect scale.  In a number of instance documents, percentages were represented on a scale of 0 to 100 as opposed to 0 to 1. […more]


2.2 Use of Data Types

Issued: 1/28/11

Impact: All US GAAP

Instance Document

2.2.1 Defining Date Values

Issue In a number of cases, filers are defining number values (e.g., data types derived from integer or decimal) that represent days months or years as an integer data type. For example, a company created an extension element called NoticePeriodForIncreaseInFacilityAmount with an integer data type.  The value in the instance was 20.  The issuer should […more]


2.3 Units archived

Issued: 10/18/10

Impact: All US GAAP

Instance Document

2.3.1 Use of Units

This guidance is archived. See Using the Units Registry for updated Best Practice Guidance. Issue In the filings to date, issuers have begun to define different kinds of units besides currency. To manage this, issuers have either defined the unit in the label of the extension element, in the element name, as an extended unit or by […more]