Overview
Imagine it. Freedom from drudgery. Freedom from the toil of tedious, repetitive, mundane, monotonous tasks. Far less time needs to be spent fulfilling the role of "data janitor". Time spent "transaction chasing" is significantly reduced.
This overview is an attempt to take the work that I have done to understand XBRL-based reports and back into a framework for explaining those reports to accountants and software engineers building software for accountants. I am now referring to this as model-driven reporting.
The sources of the information provided below are my "lab notebook" from December 2007 to October 2022; my Digital Financial Reporting blog from October 2022 until January 2025; Mastering XBRL-based Digital Financial Reporting; and finally my Seattle Method documentation.
What I have tried to do is take the seemingly hundreds of incomplete, far too technical, typically nonstandard explanations that I have come across; take the good/best ideas from each, make improvements to those explanations, and resynthesize the information into a form that is useful to me and perhaps useful to other business professionals which have a liberal arts education (i.e. not a technical oriented computer science education). How my conclusions were reached are generally provided via reference to the resources provided above.
Modern accountancy is both inevitable and imminent. However, it is not predetermined. Instead, it will be shaped by the decisions made in the coming years. By making informed choices, we can avoid and prevent undesirable outcomes concerning the needs of business professionals.
This information contributes to making those informed choices.
Narrative
XBRL-based digital financial reporting can improve general purpose financial reporting and other aspects of accountancy. This improvement comes from the fact that such reports can increase mutual understanding of report information thus increasing transparency, make report information truly understandable by computers and computer based processes, and work can be effectively transformed by enabling computer based processes to take over many tedious, repetitive, mundane, monotonous tasks from accountants which frees up accountants to concentrate on more value added tasks.
Humans can team up with computers, offloading much of the drudgery involved in accounting and dramatically amplifying work capabilities.
Accounting and reporting is an area of knowledge. The knowledge within that area of knowledge can be represented in machine understandable form using a number of different possible knowledge representation approaches. Those different knowledge representation approaches are interchangeable to the extent of the logic which is able to be represented using each specific representation approach.
Tools provide leverage. Having knowledge in a form which is reliably machine interpretable enables new types of tools to be built.
Financial statements and financial reporting as practiced when using financial reporting schemes such as United States Generally Accepted Accounting Principles (US GAAP), International Financial Reporting Standards (IFRS), Government Accounting Standards in the United States (GAS), International Public Sector Accounting Standards (IPSAS), and other such financial reporting schemes are not "standardized forms". Rather, such financial reporting schemes are intended to be, and should be, "customized reports".
Both standardized form based reporting and customized report based financial reporting provide specific capabilities. If a customized report based approach is used, "freeform" or uncontrolled report customizations simply will not work. Rather a "controlled report model" approach must be used in order to keep reports created within the boundaries of a specified report model in order to facilitate both the flexibility necessary for reporting economic entities required by these sorts of financial reporting schemes and the control necessary to enable effective reporting systems to eliminate "wild behavior" by reporting economic entities; keeping them within the necessary boundaries to facilitate the level of quality necessary to make use of reported information contained in customized report models and reports.
This reality is independent of any physical technical format used to represent the report models and report information.
There tends to be three approaches to creating such a problem solving system: (1) the Semantic Web Stack, (2) Labeled Property Graphs (LPG), (3) Logic Programming. There tends to be three global open standard technical formats for representing a business report that fit into those technical format. To represent business reports you need a logical conceptualization of a business report. Two global open standard logical conceptualizations of a business report exist: (1) XBRL Internationals Open Information Model (OIM) and (2) OMG's Standard Business Report Model (SBRM).
The Seattle Method is based on XBRL and its Open Information Model and the Seattle Method is the basis for the Standard Business Report Model. As such the OIM and SBRM are logically aligned. The logic of a business report per the OIM or SBRM can be expressed using other physical technical formats. Regardless of the technical format, the logic of the information remains the same. That means the logic of the logical conceptualization of a business report can be bi directionally transferred between the different formats. Further, that logic can be converted from the physical technical format to human readable format using that logical model of a business report and the machine readable physical technical format into a human readable format (this is not bi directional). And finally, a "pixel perfect" human readable representation can also be created by mapping report facts into a human readable format such as Inline XBRL which is a combination of XHTML and XBRL.







Comments
Post a Comment