Another Look at the World's First Expert System for Creating Financial Reports

It is time for another look at the world's first expert system for creating financial reports. Here are some ways you can take a look should you be interested:

There is a lot there to see; but you really need to understand what you are looking at.


Think about something: Exactly how much does Microsoft Word or Excel understand financial reports or financial accounting?  Zip, zero, nota.  But what if software did, in fact, understand financial reports to a useful degree?  How exactly would you communicate that information to such a software application?  Here is how:

  1. Provide a logical model. Here is my logical model, Logical Conceptualization of Financial Report.
  2. Provide a framework that leverages the model.  Here is my framework, the Seattle Method.
  3. Provide machine-readable metadata that follows the framework.  Here is my metadata. What you should see if you look at this is progressively more complex working prototypes: Accounting Equation, SFAC 6, SFAC 8, Common Elements of Financial Statements, MINI Financial Reporting Scheme, PROOF Financial Reporting Scheme (to test 100% of the logical patterns), AASB 1060 which is a real life financial reporting scheme with about 20% of the reporting scheme completely represented using the framework.
  4. Provide a steel thread working prototype. Here is my steel thread working prototype.
  5. Provide working software.  Pesseract works, but it is a desktop application and a working proof of concept. XBRL Cloud works, but what they created was too inflexible, it was not complete and besides...they appear to have gone out of business. Auditchain Pacioli works, but the GUI/UX leaves a lot to be desired and is therefore not approachable to the average business professional.  Auditchain Luca works, but is is not quite there in terms of the GUI/UX; but give it a little more time.

Most people looking at this information will make the mistake that all this looks like some sort of toy.  Trust me when I say, what you are looking at is not a toy.  Most disruptive innovations look like toys when they emerge.  Besides, don't trust me. Examine the evidence for yourself and reach your own conclusion.

My target is a new way to create accounting schedules, audit working papers, and financial reports. This really has less to do with XBRL-based reports and more about a paradigm shift in financial accounting, reporting, auditing, and analysis.  Big idea?  Why not.

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