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

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