Turning Accounting On It's Ear (Brainstorming)

I very well could be wrong, but I believe that I am going to turn accounting on its ear as is said.  I have been trying to figure this out since about 2002 and a meeting I had in Singapore.

You may or may not have seen the following graphic in SFAC 6 which was published by the FASB: (see here on page 21)


What the diagram shows are the categories of "all transactions and other events and circumstances that affect a business enterprise during a period".  The graphic then breaks down those transactions, events, and circumstances into categories. The categories relate to the 10 elements of a financial report that SFAC 6 defines: Assets, Liabilities, Equity, Comprehensive Income, Investments by Owners, Distributions to Owners, Revenues, Gains, Expenses, Losses.

And this graphic below is from the table of contents of the book The Joy of Accounting which is described by it's authors Peter Frampton and Mark Robilliard as "game-changing".
So, I don't know whether I should use the term "Classic Business Events" or "Classic Transactions" or some combination of those terms yet.  And so, I am using both and I created TWO PROTOTYPES, one for each:
What have I done?  Well, what I have done is created a prototype of six "classic transactions" of "classic business events".  For each of those I:
  1. Gave each event/transaction a specific name, for example "Acquire Inventory On Account" is one.
  2. I represented information about each specific event/transaction in machine readable form using global standard XBRL.
Why would I do that?  Well, as Benjamin Franklin said, "An ounce of prevention is worth a pound of cure."  Another way to say the same thing is the 1-10-100 rule. Put simply, the 1-10-100 rule states that it costs exponentially more to identify and correct data entry errors than to fix a system to avoid making the error in the first place.  Also, if an error goes undetected it can cost exponentially more to deal with ramifications of the error.


And so why is that important?  Well, because now I understand how to build an accounting system that leverages expert systems functionally to augment the skill of accountants.

For a little more background information, see this blog post Classic Transactions and Canonical Representations of Business Events.

Stay tuned! I will lay out all the pieces for you and explain.

Resources:
Uniform System of Accounts

Comments

Post a Comment

Popular posts from this blog

Getting Started with Auditchain Luca (now called Luca Suite)

Image
(Note that a newer, production version as opposed to only the development version , of Luca Suite is available) The Innovator's Dilemma points out that disruptive innovations often look like toys that are doing everything wrong. Auditchain Luca , which is part of the Auditchain Suite , is a unique approach to creating a knowledge graph .  To experience using Auditchain Luca, have a look at the Getting Started with Auditchain Luca instructions. Be sure to grab the Excel and JSON import files used for this getting started exercise.   This getting started exercise uses one of several different approaches to getting information into a tool for constructing and viewing professional quality knowledge graphs .  Additional getting started guides will be made available over time. Auditchain Luca might not make sense to you if you don't understand the paradigm shift that is occurring and if you have not shifted your mental map. For the next step in your journey, consider t...
Read more

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

Professional System for Creating Financial Reports Leveraging Knowledge Graphs

Image
The document Professional System for Creating Financial Reports Leveraging Knowledge Graphs explains a new approach, a new paradigm, for creating financial reports.  The document provides a practical, nontechnical description of a professional system for creating provably high-quality financial reports where the report creator is using financial reporting schemes (such as US GAAP and IFRS) where report creator is permitted to modify the report model which leverages global standard knowledge graphs represented using XBRL. This new approach is useful, it is highly novel, and the details were highly complicated to pull together.  This is certainly not an incremental innovation.  It is definitely a disruptive innovation and it could very well be a foundational innovation. You can decide which for yourself. Foundational technologies have two dimensions that need to be considered: novelty and complexity. The more novel the technology is, the more effort needed to ensure users ...
Read more