Digital financial reports contain thousands and sometimes many thousands of individual pieces or structures. These structures, commonly formatted in machine-readable form using XBRL, are used to represent the information contained in the digital financial report. There are two different aspects of these details that are important to recognize:
These objective mechanical aspects are distinct from the subjective aspects which require professional judgment. The mechanical aspects relate to the things and relations between the things in a digital financial report. These mechanical aspects are governed by logic, common sense, and the rules of math. These mechanical aspects are what makes up a financial report.
The subjective aspects tend to have more to do with which things should be put into the financial report, some aspects of the values of those things, how the values are measured, and so forth. Here are some examples to help you understand the difference:
But now consider the physical report itself. These are the very basic mechanical things and relations between those things which make up a digital financial report:
It may not be natural for accounting professionals to think about financial reports in this manner, basically given names to the structures of a financial report. Professional accountants creating these reports don't consciously think of a financial report in this manner, nor do financial analysts using these reports.
However, information technology professionals creating software for business professionals need to be aware of these mechanical things and relations between things which make up a financial report in order to create software useful to business professionals. This is how the information technology professionals get computers which are machines to perform work.
Empowered by software which properly manages the mechanical aspects of a financial report; professional accountants no longer need to deal with these mindless mechanical aspects of creating such reports. Professional accountants are freed to employ their professional skills which are impossible to automate, areas which require the professional judgment of a skilled human.
Other side benefits are increased quality by removing humans from mechanical processes which humans are really not that good at but computers can perform well.
So exactly what can be automated?
Mike Willis, a PWC partner, wrote an article Disclosure management: Streamlining the Last Mile explains how software applications can enable a streamlining of current “last mile” manual financial report assembly and review processes. He points out that companies can increase net benefits by gaining a clear understanding of common areas where opportunities exist for financial reporting process enhancement. This is a summary of what a disclosure management system needs to do, per Mike Willis:
An effective Disclosure Management implementation should enable many of the capabilities and process enhancements such as:
- Automated Spreadsheet Assembly;
- Automated Report Assembly;
- Automated Report Validation;
- Automated Narrative Text Generation;
- Contextual Review Process;
- Automated XBRL Reports;
- Automated Benchmarking;
- Explicit References;
- Collaborative Review Processes;
- Virtual Service Center.
What Mike Willis is pointing out is only the tip of a much bigger iceberg in my view. In another blog post I pointed out specific categories of benefits:
A while back I wrote a blog post describing how accounting work practices would be changed because of structured formats such as XBRL. I showed parallels between digital financial reports and CAD/CAM (computer aided design, computer aided manufacturing). This is one thing that I pointed out:
Architectural objects have a relationship to one another and interact with each other intelligently. For example, a window has a relationship to the wall that contains it. If you move or delete the wall, the window reacts accordingly.
In addition, intelligent architectural objects maintain dynamic links with construction documents and specifications, resulting in more accurate project deliverables. When someone deletes or modifies a door, for example, the door schedule can be automatically updated. Spaces and areas update automatically when certain elements are changed, calculations such as square footage are always up to date.
While the first paragraph which points out that there is a relation between a window and a wall is interesting; it is the second paragraph which is the most important to understand. CAD/CAM changed the ways architects, designers, and engineers worked in very fundamental ways.
Financial reporting is poised for a similar change enabled by structured formats such as XBRL. But for this change to occur, information technology professionals need to build the right software for accounting professionals. A first step in that process for information technology professionals is to understand the basic mechanics of a financial report.
Things like the Financial Report Semantics and Dynamics Theory and the Financial Report Ontology help information technology professionals both understand and leverage basic and more advanced mechanical aspects of a financial report.