Accounting Equation

One can better understand errors that can exist in XBRL-based reports by using a very basic reporting scheme prototype, the accounting equation.


The document, XBRL: Understanding What can Go Wrong, explains the sorts of things that can be impediments to an XBRL-based report being a properly functioning system.  The document Testing_Impediments.pdf shows how software can detect these errors.

I also created an XBRL International Conformance Suite rig which can be used to run software through all these tests to see if the software reports the correct result.

And finally, here are the individual files for all the tests:
  1. Accounting Equation - State 1 (Properly Functioning System): Human Readable | All Files | Conformance Suite | Full Validation
  2. Accounting Equation - State 2 (Incomplete Coverage by Rules): Human Readable | All Files | Conformance Suite | Full Validation
  3. Accounting Equation - State 3 (Inconsistent and Imprecise): Human Readable | All Files | Conformance Suite | Full Validation
  4. Accounting Equation - State 4 (Unreported Facts): Human Readable | All Files | Conformance Suite | Full Validation
  5. Accounting Equation - State 5 (Incomplete): Human Readable | All Files | Conformance Suite | Full Validation
  6. Accounting Equation - State 6 (Imprecise): Human Readable | All Files | Conformance Suite | Full Validation
  7. Accounting Equation - State 7 (Extension Without Anchoring): Human Readable | All Files | Conformance Suite | Full Validation
  8. Accounting Equation - State 7' (Extension WITH Anchoring): Conformance Suite | Full Validation (after fix)
  9. Accounting Equation - State 9 (Anchoring Extension Structures): Human Readable | All Files | Conformance Suite | Full Validation
  10. Accounting Equation - State 9' (Anchoring Extension Structures): Conformance Suite | Full Validation (after fix)
  11. Accounting Equation - State 10 (Improper Report Model Structure): Human Readable | All Files | Conformance Suite | Full Validation
  12. Accounting Equation - State 11 (Improper XBRL Technical Syntax): Human Readable | All Files | Conformance Suite | Full Validation

When you master the above, try having a look at the PROOF. After than, then these two AASB 1060 reports.

 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