XBRL-based Digital Financial Reporting

Most accountants have created what amounts to what I refer to as a "closing book". For a smaller financial statement, that closing book might be only one or maybe a handful of electronic spreadsheets. For a larger closing book, such as that of a Fortune 1000 company, as Gartner consultancy points out , it might be more than 800 electronic spreadsheets. And those spreadsheets have mistakes.  Consider the fact that 94% of business operational spreadsheets are known to have critical errors . This includes the spreadsheets in that closing book. Now, PWC says that they have been able to get artificial intelligence to accurately read  electronic spreadsheets about 74% of the time with hopes that they can get accuracy up to about maybe 87%. And because an accuracy rate of 87% is not sufficient for a compliance report; humans are going to close the gap between the perhaps 87% accuracy rate and the theoretical goal of 100% accuracy. While this is maybe a viable approach; is this the o...

The following is a set of digital financial statements.  Each of these financial statements was loaded from the XBRL-based financial statements submitted by each of these public companies to the United States Securities and Exchange Commission (SEC): Microsoft 10-K Apple 10-K Amazon 10-K Facebook 10-K Salesforce 10-K Alphabet 10-K Nvidia 10-K Each of these reports was loaded from the XBRL-based report that was submitted by the public company to the SEC.  The report can be broken down into structures: Network, Component, Hypercube, Block, and if provided the Disclosure . Viewing the report by disclosure is not functional in this basic viewer. This representation of prototype disclosure mechanics rules helps you understand what disclosure mechanics rules look like which enable disclosures to be detected and verified. I am not going to go into this, to dig into this yourself see the Theory of Disclosures and Disclosure Mechanics . Below are comparisons for two rather common disc...

I am trying to understand the relationship between the Universal Business Language (UBL, an ISO/IEC standard ) which defines the structure, content, and semantics of business documents which end up as business events ; the ISO/IEC standard Accounting and Economic Ontology  which includes REA for representing business events , Algorithmic Contract Types Unified Standards ( ACTUS , on path to become ISO/IEC standard) which is a global initiative to bring clarity, consistency, and precision to the way financial contracts (e.g. the business events of financial institutions but one side of those events related to enterprises served by those financial institutions ) are represented and analyzed; the FASB US GAAP Taxonomy and IFRS Accounting Taxonomy that enables aggregated information about business events to be reported to regulators, the Semantics of Business Vocabulary and Business Rules (SBVR, an OMG standard) which is an initiative and general tool or mechanism for representin...

The Universal Business Language (UBL) is an XML-based standard created and maintained by OASIS (Organization for the Advancement of Structured Information Standards) for electronic business documents. Think of it as a universal vocabulary for invoices, credit notes, purchase orders, and other commercial documents. In addition, ISO/IEC 19845:2015  (which is free to download) specifies the OASIS Universal Business Language (UBL version 2.1), which "defines a generic XML interchange format for business documents that can be restricted or extended to meet the requirements of particular industries".  Specifically, UBL provides the following three things: A suite of structured business objects and their associated semantics expressed as reusable data components and common business documents A library of XML schemas for reusable data components such as "Address", "Item", and "Payment", the common data elements of everyday business documents A set of X...

The condition of today's accounting information systems is that of a chance product driven over the last fifty years by a continuous sequence of requirements to meet the immediate needs of an enterprise. The result is describe as a " software wasteland ". An " integration hairball ". A kludge that gets the job done, sort of.  There are gaps .  There is fragmentation . Bucket brigades are needed to connect things together. And this has been normalized. Effectively, current accounting information systems are based on the knee-jerk reaction of IT folks implementing software to satisfy the immediate need of an enterprise; and so what you have is an accumulation of “stuff”, a chance product, which an accumulation of incremental adjustments. What if a different approach were used?  What if, rather than a chance product, a conscious and deliberate designed effort was used to create industrial processes which were scalable? What if the fundamental characteristics of...

At it's essence, a work system is the real-world system where people and technology combine to get something done. Steven Alter explains the work system in his work system theory (WST) in his paper,  Work System Theory: Overview of Core Concepts, Extensions, and Challenges for the Future .  Per that theory, a work system has six basic ingredients (components) : Participants : who performs the work Activities and processes : actual work performed Information : what participants use to perform the work Technologies : tools that assist in the performance of the work Products and services : output from the work activities and processes Customers : those who receive value from the work Those six ingredients above interact within three contextual elements which are: Environment : external factors which the work system cannot control but rather must adapt to Strategies : guiding intent or direction choices made which shapes how the work system operates Infrastructure : shared techni...