Digital Financial Reporting

I stumbled upon something which I find rather important.  It may sound subtle, but I believe the distinction is important.

Someone provided feedback related to the definition of a fact.  They felt that I did not have the definition quite right.  So, I looked into this.  I knew that the XBRL Abstract Model 2.0 had to define a fact, so I thought I would have a look at their definition to see if there was any thing there which I could leverage (...er...ah...steal).

The XBRL Abstract Model 2.0 uses the term "DataPoint" rather than "fact".  It also uses other different terms such as "aspect".  See here for a reconciliation of this terminology.  This is their definition of DataPoint:

The DataPoint metaclass defines a reportable item of business information contextualized by a set of aspects that identify or describe the item (this is an XBRL primary item fact), and a corresponding data point value (the reported item of business information).

The key word here is contextualized.  This dictionary defines contextualized as:

to place (a word, event, etc.) into a particular or appropriate context for the purpose of interpretation or analysis

"For the purpose of interpretation of analysis."  THAT is exactly how one should look at defining information, so that the information can be property interpreted!

And so, this is my revised definition for a fact as used in my digital financial reporting model:

A fact defines a single, observable, reportable piece of information contained within a financial report, or fact value, contextualized for clear interpretation or analysis by one or more characteristics.  Numeric fact values must also provide the additional traits "units" and "rounding" to enable appropriate interpretation of the numeric fact value.  Facts may have zero or many parenthetical explanations which provide additional descriptive information related to the fact.

(If you don't understand the term characteristics, please see here for specific examples and the Financial Report Semantics and Dynamics Theory for more information.)

Why is this important?  That is exactly what creators of financial reports should be thinking when they create those reports: how the information within the report will be interpreted.  This is why any important characteristics must be articulated along with values and also why it is better to explicitly state what you are saying rather than leave it up to users of the information to imply meaning because they may imply the wrong meaning.

Another term for this is disambiguate which is defined here as:

to establish a single semantic or grammatical interpretation for

Ambiguity, the enemy of automated reuse, is

"doubtfulness or uncertainty as regards interpretation" or "vagueness or uncertainty of meaning".

Unambiguous is:

admitting of no doubt or misunderstanding; having only one meaning or interpretation and leading to only one conclusion

Please don't make the mistake of confusing the need for and the freedom to exercise professional judgment in the creation of a financial report.  That is not the point or the issue here.  Accountants alone determine what should be communicated within a financial report.  What information to report is not the issue here.

What is at issue here is if accountants do say something, what they said should be interpreted the same by all computer software applications or their users.  What I am talking about here is the objective facts, the information level.  The information should have the same meaning to all users of the information.

How reported facts are used, whether reported facts are used at all, the implications or ramifications of that meaning the facts hold, and such is up to the user of those facts, the users of the reported information.  That is a different level of interpretation, more on the level of knowledge.

The point here is that all users of any financial report information set should fundamentally interpret the fundamental facts, the core building blocks, base meaning of the reported information, in the same way:  Assets as of December 31, 2012, for the consolidated entity is $100,000.  Facts such as this are objective, not open to interpretation, the fact itself has one meaning.  Is having $100,000 in such assets good or bad?  That is a different question, certainly open to interpretation.

This distinction is important to understand.

In a message posted to XBRL-Public, the IFRS Foundation announced the release of business rules for the IFRS taxonomy. The business rules are made available using XBRL Formula.  This is the text of their post should you not be a member of the XBRL-Public list:

The IFRS Formula Linkbase 2012 is now available to download. The current version of the formula linkbase is an updated version of the formula prototype which was released in October 2011. The 2012 formulae are designed to work with the IFRS Taxonomy 2012. The majority of the improvements between the current version and the prototype are related to the content.

The formula linkbase can be used with software packages supporting the XBRL formula specification 1.0 and allows for additional validations of the reported facts. The IFRS Formula Linkbase 2012 is developed in a generic manner, which means it can be used directly on the filings created, on the basis of the IFRS Taxonomy (instance documents) or the company specific extensions to the IFRS Taxonomy (filer extension taxonomy and instance document). The guidance documentation for formula linkbase is available to download with the current release.

Technical changes between the current version and the prototype include:

· Positive and negative formula validation has been placed in separate files.
· Redundant members in the filter for the Dimension aggregation formulae are now removed.
· Precondition expressions in the validation have been simplified (Earnings per share formulae).

For futher information and to download tthe files, please visit
http://www.ifrs.org/tools/IFRS+Taxonomy+Formula+Linkbase+2012.htm