Digital Financial Reporting Proficiency

Proficiency is the capability, skill, and knowledge that you might have for doing something.  Proficiency is a progression.  There are general levels of proficiency: literacy, fluency, mastery.

Given that the IFRS Foundation is now talking about “digital financial reporting”; one could conclude that the era of XBRL-based digital financial reporting is here.  The FASB talks about digital business reporting and XBRL.

In the document, Digital Financial Reporting: Facilitating digital comparability and analysis of financial reports; in the section "What is needed to realise the benefits of digital financial reporting?" the IFRS Foundation provides four points for users of financial reports to realize the full benefits of XBRL-based reporting:

  • be a complete and accurate representation of reported information;
  • be structured in a digitally comparable format; 
  • be publicly available at the same time as reported information; and
  • be centrally accessible in an easy-to-use format.

In that same section the IFRS Foundation has a call to action:

Over the past 10 or 15 years, some accountants have built up a proficiency in constructing rather poor XBRL taxonomies and XBRL-based reports that have far, far too many quality issues (i.e. errors).  That really needs to be fixed, and it will be fixed over time.  Perhaps this might take 5, 10, maybe 25 years; but it will be fixed.

What accountants new to XBRL-based reporting do not want to do is repeat the same mistakes as the early adopters of XBRL-based reporting.  Rather; learn from those mistakes and avoid making those same mistakes.

Early on, I make the same mistakes that others made.  But what I did differently was to figure out that I was making a mistake and I struggled to fix my processes and avoid those mistakes.  This struggle led me to the creation of what I call the Seattle Method which offers guidance on how to create high-quality XBRL-based digital financial reports.

Over the past 20 years, I have kept what amounts to a "lab notebook" of my work. The information is not particularly well organized; but I will fix that.  A first attempt is to try and put the information into helpful buckets.  Here is a first pass at those buckets and specific resources that might be helpful to other accountants trying to wrap their head around digital financial reporting and digital business reporting:

Fundamental Awareness (basic knowledge, literacy)

Novice (limited experience, literacy)

Intermediate (practical application, fluency)

Advanced (applied theory, mastery)

Expert (recognized authority, mastery)

Eventually, I will organize this into somewhat of a "skills framework".

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