This web site provides information on how to use XBRL to help business users exchange business information. Business information incluldes both financial and nonfinancial information. Everything on this site made available to all under a Creative Commons License. Everything may be reused however one sees fit. All we ask is that you give credit where credit is due. If you have any questions, comments, concerns, suggestions, ideas or other feedback, please contact charles.hoffman@me.com.

The author of this web site assumes all responsibility for this web site and it's content. The views expressed on this web site are the views of the author and may not represent the views of his employer.

Below are links to PDF files that have high-quality documentation of approximately 380 errors that exist in XBRL-based financial reports of public companies which and been submitted to the SEC as of March 1, 2017. I detected these errors as part of my measurement of the fundamental accounting concept relations and the continuity errors discovered as part of those cross-checks.

Examining and understanding these errors can help professional accountants improve their skills in working with XBRL-based digital financial reports and software developers create software useful to business professionals that help them not make these sorts of mistakes.

I created this information so that I could provide it to professional accountants who were not detecting these errors when they created their XBRL-based financial reports. Over the past several years I have made this information available to filing agents and software vendors which they used to understand and fix these sorts of errors. These 380 errors are about one quarter of the remaining high-level errors in the set of about 7,000 public company financial reports.

These errors tend to be very uncontroversial. Proof of that is that software vendors and filing agents, once they are made aware of these errors; fix these errors. For example between 2015 and 2017; Merrill went from 55% consistent to 97% consistent; RR Donnelley went from 73% to 98% consistent; DataTracks went from 62% to 98% consistent. (See the comparison of periods here.)

Using concepts incorrectly relative to other concepts. For example, WHOLE/PART relations that are wrong such as using "us-gaap:CostOfRevenues" (DIRECT operating expenses) as a PART OF "us-gaap:OperatingExpenses" (INDIRECT operating expenses) when they should have used the concept "us-gaap:CostsAndExpenses" (TOTAL DIRECT + INDIRECT operating expenses)

Simply using the wrong concept. For example, a common error that you will see is using a concept that relates to "Other comprehensive Income" to represent a line item related to "Comprehensive income" because an incorrect concept was mistakenly selected.

Creating completely XBRL valid relations, but the relations either is inconsistent with the US GAAP XBRL taxonomy or literally CHANGES THE MEANING of US GAAP.

Each of these errors are logical errors, mechanical errors, or mathematical errors which have NOTHING to do with XBRL technical syntax. Each error was represented using PERFECT XBRL technical syntax; but the information conveyed was just wrong.

Principles help you think about something thoroughly and consistently. As a result of my measurement of the fundamental accounting concept relations, I created the XBRL-based digital financial reporting principles. They help you think about XBRL-based reports.

This information should be very helpful to professional accountants creating XBRL-based reports and software developers building tools those professional accountants use. There are those reports grouped by audit firm. I am not saying that any of these audit firms have responsibility for any of these inconsistencies, I am simply making this information available in this form because I also sent this information to each audit form to help them understand these sorts of errors. (April 2017)