Financial Statement Designed to be Analyzed

A general purpose financial statement has a formal structure that varies only slightly from industry to industry, country to country, and therefore from reporting economic entity to reporting economic entity. This regularity is by design. The trend is toward even more standardization.  Examples of that standardization include International Financial Reporting Standards (IFRS), United States Generally Accepted Accounting Principles (US GAAP), and the Extensible Business Reporting Language (XBRL).

In fact, general purpose financial statements are so formal and predictable as to be literally mechanical.

Over the past 50 years, these general purpose financial statements have grown in size and complexity. And yet, the general mechanism to construct and analyzed has not changed that much for these important artifacts of the global capital markets.

The general purpose financial statement is a designed system; it has been created by humans for a purpose. The global capital markets use the general purpose financial statement as one of many inputs to value an economic entity. Arguably, general purpose financial statements help the global capital markets function better.

Arguably, a better functioning general purpose financial statement would help the global capital markets function even better.

General purpose financial statements were designed for systematic computational analysis. General purpose financial statements were designed to be analyzed. Financial statements are knowledge graphs.

General purpose financial statements are comprised of a set of disclosures. Each disclosure is likewise designed for systematic computational analysis. This systematic computational analysis is achieved by leveraging the disclosure design patterns of a disclosure.

The mechanics of this formal, predictable, mechanical nature of a general purpose financial statement can be described using various mechanisms.  In the past, that description tended to be paragraphs and sentences of a document.  But technologies available today, such as UML models, ontologies, and machine-readable theories expressed using PROLOG are far better suited for describing the mechanics of this very mechanical designed system.  Other tools such as logic programming can be used to effectively perform that systematic computational analysis.

Quantitative analysis is an obvious first step toward systematic computational analysis.  Qualitative analysis is another step.  Strategic analysis is another step.  Competitive analysis is another step.  Landscape analysis is another step.  What I am doing with the Seattle Method is only the beginning.

Models, frameworks, and standards are tools.  One needs to be sure they are using the right tools for a job.  The tools of "realspace" (think industrial economy) and the tools of "cyperspace" (think information economy) are different. It takes skills and experience to be able to pick the right tools for a job.

Accounting, the universal technology of accountability, is arguably one of the most important technologies invented in the history of human civilization and has been around about 7,000 years.  Accounting was invented before writing and before the invention of numbers.  The global multinational organization simply could not exist without double entry bookkeeping and accounting.

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