Disclosures

A disclosure is something that is disclosed within a financial report.  To understand the disclosure, it is best to first understand the notion of the block. If you understand atomic design methodology you will understand what blocks and disclosures are useful.  Effectively, blocks and disclosures are logical assemblies of facts within a report or some set of reports.

But if you try and search the US GAAP or IFRS XBRL taxonomies for disclosures you will be unsatisfied by the result.  Why? Because neither the US GAAP nor IFRS XBRL taxonomies has the notion of "disclosure" and provides no identifiers which enables software to identify, find, and work with disclosures.  Further, neither the Accounting Standards Codification (ASC) for US GAAP or IFRS Accounting Standards Navigator for IFRS provide identifiers for disclosure or name disclosures.

However that is exactly what is necessary to get a machine such as a software application to be able to identify and work with specific disclosures.

But what if there were such a list of named disclosures for US GAAP and IFRS?  Well, if you check out the links there; you see that I have created such lists (working prototypes).  But you still have to somehow connect the list of explicitly named disclosures and the US GAAP or IFRS XBRL-based representations of disclosures.  Did that also with my disclosure mechanics rules.  Those disclosure mechanics rules effectively define the essence of a disclosure and can be used to identify specific disclosures with financial reports.

Software such as XBRL Cloud, Pesseract, Auditchain Pacioli, Auditchain Luca and other such software leverages that metadata to find and work with financial disclosures.

Very detailed testing was performed on the Microsoft 10-K for 2017. (Another version of that experimentation and testing.)  Two different software applications get very similar results.

Here are artifacts for one specific disclosure, the disclosure:BalanceSheet.

The ultimate objective is to be able to do an as reported or a normalized comparison of any block of information that represents any disclosure provided between different reporting periods for the same reporting entity (i.e. period comparison) and/or between reporting entities (i.e. peer comparison).

Additional Information:

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