Mezzanine Level of Digital Business Reporting

So there appears to be a need for what I am referring to as a "Mezzanine Level" in XBRL-based digital financial reporting.  Financial reports people tend to get; the general purpose financial report.  They also get the level of tractions which XBRL Global Ledger is supposed to handle; it is purpose built for transactional reporting.

When you look at the full "record to report" process; in between the transaction level and the financial report level you have accounting working papers and audit schedules that support the financial statement; those working papers and schedules tend to have some characteristics of financial reporting and some characteristics of transactions.  Also, remember that not all information in a financial report comes from an accounting system.  That information tends to originate within electronic spreadsheets and documents.  I call this intermediate middle level the "Mezzanine Level" of the record to report process:

Over the years I have created many, many examples of XBRL-based digital financial reports.  The best set of those examples and test cases is my PLATINUM Business Use Cases, Test Cases and Conformance Suite.

I have created far fewer, but some, transaction level examples.  The best examples relate to the prototypes of the record to report process, the best being Effective Automation of Record to Report Process (Iteration #4). I have also done some work related to Engine B's Common Data Model (CDM) V1.1.


This graphic below shows examples of the tasks and process that tend to make up the record to report process. The accounting working papers and audit schedules support these tasks and processes:
The mezzanine level of digital business and financial reporting "hooks" the transaction level and the financial report level together.

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

Getting Started with Auditchain Luca

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 trying creat
Read more

Evaluating the Quality of XBRL-based Financial Reports

Image
From the time public companies started submitting XBRL-based financial reports to the U.S. Securities and Exchange Commission, I have been looking at those reports, trying to understand the XBRL-based reports, and trying to figure out how to get them right.  That information was used to figure out how to create software applications that help professional accountants get these reports right. Here is information that summarizes my testing and results which I stopped doing March 31, 2019: Analysis of the high level accounting relationships in the 10-Ks of about 5,716 financial reports  (5,063 public companies, about 89.1% got all these high level accounting relationships consistent with expectation, 623 were inconsistent and manual confirmation revealed the inconsistency was an error) Documentation that helps you understand 26 different types of errors in XBRL-based reports High quality documentation of hundreds of errors in XBRL-based reports submitted by public companies to the SEC Doc
Read more