BLOG: Digital Financial Reporting
This is a blog for information relating to digital financial reporting. This blog is basically my "lab notebook" for experimenting and learning about XBRL-based digital financial reporting. This is my brain storming platform. This is where I think out loud (i.e. publicly) about digital financial reporting. This information is for innovators and early adopters who are ushering in a new era of accounting, reporting, auditing, and analysis in a digital environment.
Much of the information contained in this blog is synthasized, summarized, condensed, better organized and articulated in my book XBRL for Dummies and in the chapters of Intelligent XBRL-based Digital Financial Reporting. If you have any questions, feel free to contact me.
Entries from January 1, 2012 - January 31, 2012
Consistent and Explicit Data Models: More on the Data Points Model
I mentioned the data points model in a previous blog post. Someone posted a video to XBRL-Public which explains the data points model approach in detail. You can find this video here.
While this video is long (1 hour and 26 minutes), is detailed, and discusses data modeling and the data points model from the perspective of the FINREP taxonomy; this video will help one grasp the important general issues related to expressing information in XBRL.
You can distill the message of this video into one concise statement:
Build consistent and explicit data models.
What I have created and documented in my Modeling Business Information Using XBRL document follows those two key principles. So I could not agree more with those who support the data points model.




XBRL House
Eiichi "Ed" Watanabe, an early evangelist for XBRL in Japan and globally, has set up a web site, XBRL House. This is how Watanabe-san describes his web site:
My intent of creating this website was to share what I have with respect to XBRL so that the information included would be of some value for those who join the XBRL world. I thought it would be good for me to do that because I was so involved in XBRL and I am retired almost from XBRL, although I am still an advisor of XBRL Japan.
One thing I would point out on the site is the library. I counted 20 books related to XBRL.
Stop by XBRL House and say hello to Ed!




Microsoft PowerPivot and Azure Show Possibilities
I have mentioned Microsoft PowerPivot before. But, I did not have Excel 2010 at the time; now I do. I did not know about the Windows Azure Marketplace back then.
PowerPivot is basically an Excel pivot table on steroids. It is a free add in to Excel. It is a beautiful looking interface, but it does take some time to figure out.
The Windows Azure Marketplace is, well, a market place where publishers of applications and data can sell there wares to people who want to buy those applications and data. There is an Excel add in, also free, which lets you connect to these data sets.
This video what helpful in getting a connection to some free data which is available in the Azure Marketplace, basically letting you experiment with Azure and PowerPivot.
All this stuff is worth checking out.
My question is: When will working with XBRL information be this easy?




Understanding the Metadata Opportunity (or Threat)
The move to digital financial reporting will cause a number of very significant shifts. One of these shifts relates to how metadata can be employed. This shift is both an opportunity and a threat. Most accountants and CPAs don't have a good enough grasp as to what metadata is or the role it plays. Therefore, nor do they understand the side of the shift equation on which they will end up.
This is what I mean.
Let me use the external financial statement as an example. Most external financial statements today are created using Microsoft Word. I hear the number 85%. I am not talking about the balance sheet, income statement, and maybe cash flow statement which might be generated from an accounting or ERP system. I am talking about a complete financial statement.
So, how much does Microsoft Word know about financial statements? You are probably thinking that this is a rather odd question, of course Word knows nothing about financial statements. The person creating the financial statement is the one which knows about financial statements; they use their knowledge of financial reporting and US GAAP or IFRS to create a financial statement using Word.
That is exactly the problem. In fact, it is two problems. The first problem is that Word cannot help you create that financial statement and get it correct. The second problem is that once the information is put into Word, because Word does not have any knowledge of the financial information within the financial statement; reusing that information involves humans, usually with domain knowledge, rekeying that information in order to make the information actionable.
The graphic below shows this has worked in the past (and likely how most people do this today):
But what if Word did understand financial statements? Well, word my never understand external financial statements, but other applications will. You could get Word to understand financial statements by using its macro language, which is VBA and actually quite powerful, but more likely other applications will be created. And how might a software application understand a financial statement you might ask? Structured information and metadata. (To understand that statement is a journey, start here on that journey. This has the complete story. Once you see this in action, you will get it, get it.)
Basically information which you and other know about a domain such as financial reporting will be expressed in a form which a computer can understand. That is what the XBRL medium does, it expresses information in a structured form so a computer can understand it. Additional information, metadata, will be expressed which is helpful in working with that structured information.
Algorithms, or computer programs, will do stuff with that structured information and metadata. Lots of stuff. The graphic below shows this:
So two things will happen. First, who can create information and how they create that information will change dramatically. Because the computer can help the user, a less skilled person can do the work because the "human knowledge" is now expressed in the metadata. Second, automated reusing the information will become possible.
This will spiral, the possibilities widening and widening as more and more metadata and algorithms are created and employed.
What is the threat? If your skill is memorizing and regurgitating information, this is a threat. If your skill is rekeying information, this is a threat. Basically, think of what numerically controlled (NC) machines did to the manufacturing process. Robots build a lot of stuff today using algorithms and metadata which control the machines which churn out consistent, higher quality output than humans can generally create.
The opportunity? Creating algorithms, creating metadata, doing value-add analysis of all that structured, model-based information.
And these opportunities and threats are not limited to external financial reporting, or even financial reporting. These same ideas can be applied to many, many other domains.
Stay tuned to my blog, it may help you understand and take advantages of the opportunities and not end up as road kill.




Understanding the Term Actionable Information
The best explanation of what actionable information is that I have found came from an article by John Alber, Delivering Actionable Information To Front-Line Lawyers:
If a friend tells you that you have something in your teeth, chances are you’ll visit a mirror and attend to the problem. That’s actionable information. It is information (1) from a trusted source, (2) about something that’s important to you, and (3) that, once known to you, will impel you to take action.
While the article talks about law firms, it has general aplicability in my view.
Ask yourself this question. In your organization, how does the mass of information which you have available become actionable? Is that process as effecient and as effective as it can be? Chances are that the process involves lots of reports, spreadsheets, re-keying, etc.
Think about this. More later on how to improve this process.



