Useful Generative AI Coming to Accounting and Reporting

People are starting to figure out how to apply generative artificial intelligence to accounting and reporting processes.  Here are three examples:

  • Engine B's Copilots:  As explained in this press release, Engine B is bringing "copilots" that leverage generative AI to audit, tax, and accounting markets.
  • Workiva's Generative AI: Watch the video about half way down the page.  It shows how generative AI can be used effectively in the process of creating reports.
  • PWC's Consulting Chatbot: This is a collaboration between OpenAI and PWC to offer consulting on complex issues such as tax, legal, and human resources.
  • Jinsei.ai is a startup that is unifying generative AI, machine-learning, and rules-based AI.
There are very likely others creating similar solutions that leverage GPT4 transformers working on specific large language models (LLMs).  Those solutions will very likely prove to provide benefits.  But this will only be the beginning.

Imagine combining technologies, creating a hybrid of GPT4 transformers, specific large language models, and rules based deductive reasoning that leverage properly created XBRL taxonomies that describe financial reporting schemes. A unified LLM and knowledge graph that offers the best of both worlds.

Today, financial reporting schemes are books or maybe content management systems containing information organized for humans to read.  So, that information is semi-structured; but the structure is for the presentation of information in paragraphs, tables, and such for an accountant to read.  So, consider something like the documentation of a typical financial reporting scheme exemplified here in this PDF that documents, describes, and specifies AASB 1060 which is effectively financial reporting for small and medium sized enterprises in Australia.

Just parsing that PDF (with a tool like this) will not get you where you want to be. Why? The reason is that the document is in no way connected so something like an XBRL taxonomy for AASB 1060 which provides explicit rule-based information.

But what if you did connect the PDF and the XBRL taxonomy?  I created a prototype of what I am talking about, see page 13 of this document, which shows this mapping of the financial reporting scheme disclosure rules with the XBRL taxonomy terms using hashtags:

So, imagine having a well constructed ontology-like thing (a.k.a. knowledge graph) that is connected to a specific large language model which included the accounting and reporting rules specified by a standards setter or regulator for a specific financial reporting scheme connected to a knowledge graph that explained that information precisely and accurately in a manner that is readable, and therefore understandable, by machine-based processes.  All this is hooked to the logical model of a financial report represented in the form that is usable  by software.  Tie all this together into one framework, create a method for processing all this and what do you get?  A paradigm shift.

But don't make the mistake of imagining one instance of what I am describing.  Even better, imagine a framework for creating hybrid artificial intelligence solutions for any financial reporting scheme.


Now, imagine connecting all that to a software application for creating financial reports.  What do you get?  Well, if the software is built correctly you get an expert system for creating financial reports.

Now, tie all of the above together with some other technologies that seem to be converging such as blockchain, triple-entry accounting, REA, semantic spreadsheets, Lean Six Sigma and you get a whole bunch of possibilities that open up.  You get a great transmutation.

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