Framework for Predicting Changes to Financial Accounting, Reporting, Auditing, and Analysis

Let's face it.  Most people don't yet grasp the transformational changes that are unfolding in financial accounting, reporting, auditing, and analysis.  To do so, you need the right combination of skills and experience. Getting that skill and experience is not an insurmountable endeavor.  You simply have to gain the skill and/or get the experience.

As Malcom Gladwell pointed out, it takes about 10,000 hours to master something.  But, "Practice does not make perfect," as is often said.  Perfect practice makes perfect.  If you practice the wrong things you could become an expert in the wrong area.

I have consolidated what I personally believe to be the important moving pieces of the puzzle into related to The Great Transmutation of financial accounting, reporting, auditing, and analysis into the document Evolution of a System - Framework for Predicting Changes to Financial Accounting, Reporting, Auditing, and Analysis.

The universal technology of accountability is transitioning to digital.  Transitions like this tend to have some winners and some losers.

Pattern recognition is a skill. Advanced pattern recognition skills can be taught, and learned. Have a look at the video below.  You should be able to see the correlation between the amassing technological advancements displayed in that video and what is very likely to happen to financial accounting, reporting, auditing, and analysis over the next 5 or 10 or 25 years.  If you have the skills, can can probably project pretty well what might change in 5, in 10, and in 25 years.  What is even more important to understand is what it takes for those changes to occur.

What is occurring is one of those once every 500 years change. If you don't understand the value of an expert system for creating financial reports or if you don't think something like that can be built, you might want to tune your pattern recognition skills.



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