XBRL-based Digital Financial Reporting

I ran across a term that I really like.  It is a very practical term and the term is necessary these days. That term is business knowledge blueprint . The notion of the business knowledge blueprint came from the same guy that was behind the Business Rules Manifesto which I really like. The Business Rules Community  seems to be the ones that came up with the notion of the business knowledge blueprint . They explain a business knowledge blueprint thus: "A business knowledge blueprint is without peer as a pragmatic basis for developing a high-quality business vocabulary, as well as a multi-purpose blueprint to your company's business knowledge. This blueprint focuses on business concepts organized in the form of a concept model." "We define a business knowledge blueprint as follows: business knowledge blueprint: a concept model along with everything that communicates its meaning, including vocabulary, definitions, definitional rules, diagrams, and related information ...

The first time I heard the term "bucket brigade" to describe accounting and reporting processes was from the book The Future of Accounting . That description accurately articulated how accounting information systems were connected into a flow which included lots of humans, lots of software applications, and  lots of electronic spreadsheets to connect everything together. But then I ran across the lean bucket brigade . Lean positions the bucket brigade as a "feature" rather than a "bug". (Image by Christoph Roser at AllAboutLean.com under the free CC-BY-SA 4.0 license.) A bucket brigade is not inherently good or inherently bad; it is just a tool. But the metaphor of the bucket brigade is a good metaphor that explains work , the algorithm , the notion of the process , and the input-process-output model ( IPO Model ). And I would propose viewing these ideas from the perspective of Lean Six Sigma  and an industrial engineer with a digital first mindset . As ...

Electronic spreadsheets have been referred to as "the backbone of the enterprise" and "the quiet engines of a modern economy". Gartner points out  (page 2) that the typical Fortune 1000 company uses 800 spreadsheets to prepare its regulatory compliance report. Those 800 spreadsheets are connected together with what amounts to duct tape, bailing wire, and band aids. Spreadsheets are systems, not documents. Spreadsheets just look like documents . As pointed out by Matt Wood of PWC in his article, The Inversion , (paraphrasing) a spreadsheet is a "network of dependencies" and that "meaning lives in the relationships between cells not in any sequence of words" and  "thousands of logical gates that connect input to output". But to a software application that does not understand the information clothed in that document, the information remains "dark matter" that is "present, consequential, but invisible" to software agents...

Financial statements are designed to be analyzed . Analyzing financial statements should not be a guessing game; rather, clarity is better . The threat of inaccuracy should be minimized. A document is a " costume " which a financial statement wears. But don't be fooled by the appearance; just beneath the surface is a rigorously designed logical substrate. I pose a hypothesis and I have reached a conclusion that my hypothesis was correct and I now have my Theory of Financial Analysis . Here is some of the empirical evidence that has led me to believe that there are patterns within financial analysis and those patterns can be explained by a theory . Financial modeling is an approach to financial analysis . Financial modeling is a tool to understand financial information for one or more economic entities and to perform analysis and to guide decision-making. There are patterns of financial modeling and financial analysis.  Here are some of the common financial analysis pat...

This article is inspired by an article by Georg Philip Krog,  Why AI Can’t Read Your Contracts — And What To Do About It , where he explained why artificial intelligence cannot read legal contracts.  I am applying similar thinking to why artificial intelligence cannot read financial statements. The metaphor of a "costume" is excellent. Popular AI systems built on large language models (LLMs) face a fundamental limitation when confronted with something like a financial statement . LLMs can often extract and correctly summarize much of the information, say perhaps 87%.  The key point is, it is never 100%.  However, "much" or even "most" is not sufficient in a domain where precision is non negotiable. You never know which 13% is wrong, and that uncertainty makes the entire output unreliable. LLMs excel at the capability of predicting the next plausible word. That is their core competency. But interpreting a financial statement requires logical reasoning, not...

What does it mean to trust? ONTrust: A Reference Ontology of Trust is a paper which provides an ontology of trust and a rigorous discussion about trust. The paper is described as , "This paper is the culmination of a long-term research program of providing a solid ontological foundation on trust, by creating reference conceptual models to support information modeling, automated reasoning, information integration and semantic interoperability tasks." Additional Information: Procedural Knowledge Ontology (PKO) ValueFlows