Converging Paths to a Modern Approach to Financial Accounting, Reporting, Auditing, and Analysis

Someone made me aware of the paper, REA, Triple-Entry Accounting and Blockchain: Converging Paths to Shared Ledger Systems (by Juan Ignacio Ibañez, Chris N. Bayer, Paolo Tasca and Jiahua Xu).  The authors of the paper say the are striving to correct common misconceptions, acknowledge the influence of key individuals, and map out the overlapping paths of REA, TEA, and blockchain.

As a bit of a side note, I was also made aware of the Triple Entry Accounting Inaugural Conference where people thinking about this stuff will soon meet.

While pulling those three pieces together (REA, TEA, and blockchain) is very useful; personally I would go farther and suggest that the overlapping paths the following pieces should be discussed and figure out how they can be pulled together into a system that works like a well oiled digital machine for financial accounting, reporting, auditing, and analysis:

  • Resources, Events, Agents (REA); Algorithmic Contract Types Unified Standard (ACTUS); and other ways to represent business events or “classic transactions” (see The Joy of Accounting).
  • Single entry bookkeeping, double entry bookkeeping, triple entry bookkeeping, and other ways to record transactions that represent business events of an economic entity.
  • Blockchain, Hashgraphs, and other ways to represent immutable digital distributed ledgers. Including smart contracts, IPFS, NFTs, and all the "stuff" related to blockchain.
  • Smart contracts and logical contracts.
  • Ontologies, taxonomies, knowledge graphs, and other ways to represent knowledge in machine readable (and human readable) form.
  • XBRL, RDF+OWL+SHACL (W3C Semantic Web Stack), ISO PROLOG, ISO GSQL, and other global standard technical syntaxes/formats for physically representing knowledge assemblies in the form of knowledge graph systems.
  • Zero Copy Integration: The traditional approach to data sharing is a complex and risky process where information is copied between data silos generally via ETL or API-based data integration. The Zero-Copy Integration framework, the elimination of silos and copies enables access controls to be set once in a shared data architecture at at the metadata-layer and then universally-enforced across all digital solutions, greatly simplifying lineage, compliance, and auditability.
  • Lean Six Sigma and other principles, techniques, and processes for maintaining high quality.
  • Deductive reasoning (GOFAI), inductive reasoning, abductive reasoning, neuro-symbolic AI, explainable artificial intelligence (XAI), and other reasoning approaches (Logical Systems for Business Professionals)
  • Sequential, forward chaining, backward chaining and other techniques for processing logical information contained in a knowledge assembly.
  • Electronic spreadsheets, semantic spreadsheets, logical spreadsheets, and other approaches to exchanging sets of information.

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