PLATINUM XBRL-based Financial Report Examples

In 1494 Luca Pacioli documented the Venetian Method of double-entry bookkeeping and that documentation was used to implement that best practices method first in Europe and then around the world.  The Seattle Method and Mastering XBRL-based Digital Financial Reporting is my best effort to enhance the Venetian Method for the Information Age.

Need a simpler more condensed "jump start".  Have a look at my new Platinum Examples.  See below.

Over the years I have created a plethora of examples and samples of XBRL-based digital financial reports.  You can find these on my "lab notebook" (my older blog).  The best set of examples are on this specific blob post, "The End (Start Here)".  The set of "Golden Examples" is what helped me tune the Seattle Method and my contributions to the Standard Business Report Model (SBRM).

The set of examples below, what I call my PLATINUM Examples, were explicitly created to follow the very best practices of the Seattle Method.  This set of examples minimizes duplication, maximizes consistency, and provides the most complete set of examples that can be used for testing software applications and training accountants to understand XBRL-based digital financial reporting.  These examples are deliberately created, rigorously tested, and provide a complete foundation for understanding XBRL-based financial reports.

The examples start with what can be thought of as very small financial reporting schemes and then get progressively larger, trying to introduce a manageable set of new ideas incrementally.  This helps those trying to teach and those trying to learn absorb information. You can see each report example here: AE, SFAC6, SFAC8, Common, MINI, PROOF, XASB, AASB1060. (Download all)

Here are the details for each of the example reports organized by financial reporting scheme prototype:

  • Accounting Equation (ae), an extremely basic example financial reporting scheme. This small example helps you grasp the fundamentals using the minimal number of moving parts.
  • SFAC 6 (sfac6), builds upon the accounting equation, uses the ten elements of a financial report defined by the FASB to introduce the notion of "structures".
  • SFAC 8 (sfac8), builds upon SFAC6, introduces the notion of alternative disclosures and the use of reporting styles to manage flexibility.  Also introduces the idea of a reference report that is used to make certain that a taxonomy is functioning properly.
  • Common Elements of Financial Report (common), builds upon SFAC8, adding a cash flow statement to provide something that begins to look more like a real financial statement. Helps to consolidate the notions of alternative disclosures and reporting styles.
  • MINI Financial Reporting Scheme (mini), builds upon the ideas of prior examples finally showing something that looks much, much more like a real financial report. This example has primary financial statements that look "real" and introduces basic policies and disclosures.  The focus here is showing the logical relations between financial report pieces and consolidating your understanding of "roll ups" and "roll forwards".  To keep this simple, only one reporting style is used.
  • PROOF Financial Reporting Scheme (proof), rounds out the fundamentals by introducing the notion of "dimensions" and adding a complete set of information model patterns that you will run across when working with XBRL-based digital financial reports.
  • AASB 1060 (aasb1060), complete representation of about 20% of a real financial reporting scheme
After you have mastered the ideas from the above progressively more sophisticated examples, then have a look at the larger examples provided in the GOLDEN Examples of General Purpose Financial Reports.  In particular, explore the AASB 1060 financial reporting scheme which is a complete example of about 20% of a real financial reporting scheme XBRL taxonomy represented using the ideas you learned from the PLATINUM EXAMPLES above. (Try this enhanced approach to providing information about a financial reporting scheme.

In addition to the progressively more complex examples above, a Hello World! example is also provided.

These particularly helpful resources below can be helpful in working through this information:
  • ZIP archive which includes all the report renderings
  • Documentation of the Platinum Examples in one PDF
  • Improved version of Essentials of XBRL-based Digital Financial Reporting which is a work in progress that tries to simplify the earlier version of this documentation and replaces the older examples with these PLATINUM examples.
  • Auditchain Suite can be used to create the reports above.  Import files are provided, but it is best to practice by creating the reports manually.  The Auditchain Pacioli Power User Tool can be used to verify reports.
  • Pesseract can be used for viewing the reports.  Contract me if you need a Pesseract license.
  • General Luca is another cloud based software application which can be used.
  • Arelle is an open source API and GUI that is a fully compliant XBRL processor.  Arelle is more focused on the XBRL technical syntax and does not support the higher-level features provided by the Seattle Method related to XBRL-based digital financial reporting.  But Arelle is helpful in verifying your XBRL technical syntax.  Note that both Auditchain Pacioli and Luca make use of Arelle in their software stack.
  • Showcase of Reports helps you understand where all this XBRL-based digital financial reporting can go.  This will show you the real capabilities of XBRL-based reporting.
What is next?  Try Mastering XBRL-based Digital Financial Reporting.  That 700 page trove of information should keep you occupied for awhile.

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