Good Practices XBRL-based Report Repository

I have put together a good practices based repository of XBRL-based reports to show how to build such repositories and understand how to effectively extract information from XBRL-based report repositories.

Here is my repository:

There are currently four reports in the XBRL-based report repository but I want to get the set of reports up to maybe 10 or 20.  The primary purpose of creating this is to (a) show people how to build such repositories, (b) explain to people how to effectively extract information from such repositories, and (c) test software applications that are built to extract information from such XBRL-based machine readable report information repositories.

One important thing to note is that each of the four reports uses a different combination of balance sheet and income statement styles.  There is a net assets, classified, and liquidity based balance sheets.  There are income statements by function and by nature.  This helps one understand the notion of reporting styles and how that impacts extracting information from the financial reports.

Attached to that repository page is another important page which is the base financial reporting scheme that is used for preparing reports that would go into the repository.

Here is the base financial reporting scheme:

A very important thing to understand is that there is a correlation between the quality of the base financial reporting scheme representation and the ability to extract information from the reports created using that financial reporting scheme.  A big part of the reason it can be hard to extract information from XBRL-based reports is because the supporting base financial reporting scheme and report models are substandard.

A I explain in the Essence of Accounting, financial reports are not forms. Nor will financial reports ever be standard forms.  Financial reports are knowledge graphs. Those knowledge graphs are customizable by reporting entities that create reports, but any such customizations must stay within permitted boundaries of the financial reporting rules, mathematics, and logic.

Because of these customizations it is more work extracting information from the XBRL-based reports.  Further, those creating the base financial reporting schemes can do things that make extracting information easier.

When a base financial reporting scheme clearly specifies the disclosures that are required, when reporting economic entities create reports per that clear specification, and when all that information is put into machine readable form and used to verify that reports, in fact, follow that clear specification; then a very useful system results which causes a virtuous cycle.
However, when flaws such as ambiguity, math errors, and other such imperfections make there way into this system then problems occur.

More information that explains the example referenced that I am holding out as a good practices example of quality XBRL-based financial reports and repositories of machine readable report information.

Additional resources:

Comments

Post a Comment

Popular posts from this blog

Relational Knowledge Graph System (RKGS)

Image
Relational Knowledge Graph System (RKGS) is an interesting idea that combines the relational paradigm and the knowledge graph paradigm.  This documentation, Why RKGS , explains the idea. This gets even more interesting with the notion of "relational AI".  RelationalAI is described as follows by the company of the same name, Relational.ai : “RelationalAI is a cloud-based relational knowledge graph management system, with state of the art probabilistic processing and declarative reasoning at scale to make developing Data Applications a superpower for your business.” This notion of knowledge graphs represented in relational databases fits into my belief that knowledge graphs have two aspects: the expression SYNTAX and the logic of what is expressed or SEMANTICS. While the LOGIC of a knowledge graph is always the same regardless of technical syntax used to express that logic; there are many, many different technical syntaxes that can be used to represent a knowledge graph. There
Read more

Graph Hairball

Image
Knowledge graph system logic, the "things" and "relations between things" that  graph theory calls "vertices" (a.k.a. nodes, points, entities, things) and "edges" (a.k.a.  links, lines, relations, associations), looks like a big graph hairball as some people call it an example of which you can see here: Why?  This common view of a graph is because there has to be some "general view" of the information provided by the graph.  This is just like a general view of the information within a relational database is a table ; a set of ROWS and COLUMNS for exactly one table at a time. So what is interesting is that with a graph database the default view is everything in the graph of knowledge.  Whereas the default view of everything in a relational database is one table at a time. Further, it does not really matter whether the information that populates your knowledge graph comes from, say, CSV files, Excel, JSON, XBRL, RDF, PROLOG or whateve
Read more

PLATINUM Business Use Cases, Test Cases, Conformance Suite

Image
A brick wall is made of exactly two things: bricks, mortar. But a brick wall created by a master craftsman, or mason, and a brick wall created by a “weekend warrior” with no knowledge of masonry will be very different. Master craftsmen are created and that process takes time and effort. This blog post is a first prototype that brings several things together into one useful resource for business professionals.  It pulls together the human readable information of the Showcase of Reports   and the machine readable information of the Conformance Suite of XBRL-based Financial Reports Prepared using the Seattle Method .  Then, I want to incorporate the information found in these PLATINUM XBRL-based Financial Report Examples . The three resources can be useful and used independently; but they are even more useful when used together.  Business professionals really could not care a less about the technical details of getting some result that they want.  But technical professionals need to under
Read more