Open Source RDF Accounting Engine

 LodgeiT Labs has created what they are calling an open source RDF accounting engine. This YouTube video provides a glimpse.  Information that I have received says that you can get the code for this RDF accounting engine here. This YouTube playlist provides more information. (When I asked Microsoft's Copilot to generate an image of an RDF accounting engine, this is what I got below.)

This open source RDF accounting engine, apparently called "Robust" is described as follows:

"Robust is our LodgeiT experimental, open-source accounts-processing engine able to generate investment reports with realised & unrealised gain/(loss) as well as currency gain/(loss). Read more about it here - https://github.com/lodgeit-labs/accounts-assessor" 

What I would be very interested to see is my "record to report" working prototype to be run through that accounting engine. My working prototype took the transactions from the Microsoft Dynamics "The World Online" (TWO) set of demo data, output the transactions, ran them through a bunch of steps and ultimately generated a financial report.  This report is the end result.  This is the financial reporting scheme that I used.

This MINI2023 is an updated set of files. I made a few modifications to the "roll forward grouping codes".  For discussion purposes, use this report and this validation result. This report was generated from a set of general ledger transactions which I have.

The key to making all this work effectively is what I call the "roll forward grouping codes" and what LodgeiT refers to as "transaction verbs" and Workday refers to as "work tags" (for information on work tags see this and this and this and this. This information is key to getting accounting systems to do what accountants need them to do.  They enable aggregation and disaggregation of information when used properly.  Workday seems to have formalized their work tags idea in their Foundation Data Model (FDM).

Although, people seem to be missing something.  Someone said this about work tags, "The more details we can use to describe transactions, the more information we will have for reporting and decision-making."  It is not about "more".  It is about the RIGHT DETAILS, not just more junk.  It is about precision, not volume.

To set up an accounting system effectively, at the very minimum you need to establish the following:

  • Accounts (i.e. chart of accounts), these tend to be nouns
  • Account types or categories
  • Traction types or categories (what I call the roll forward grouping codes, LodgeiT calls the transaction verbs, and Workday calls work tags
  • Report line items and groupings (usually in a report writer)

To understand more, read my Effective Automation of Record to Report Process Narrative for Iteration #4 documentation.  I think I am going to create an improved version of that working prototype.

Accountants seem to be gratified by pain of the month end close.  In most cases, that pain is self-imposed or imposed by those that built the accounting information systems used.  There are better ways.

Additional Information:

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