A LEVEL 0 financial report is not physically readable by a computer. Therefore, it has to be read by humans in order to use information from the report. Report examples include:

A LEVEL 1 financial report is readable by computer, but the information in the report is structured only for presentation of information and not standard. This make is POSSIBLE to read information from EACH individual report; but each individual report must be individually configured to use reported information. Report examples include:

A LEVEL 2 financial report is readable by computer and the report information is structured for meaning but the structure syntax is nonstandard. No "dictionary" (a.k.a. taxonomy, schema, ontology, conceptual model) that explains the report pieces is available. No rules to verify reported information or the report model is available. Again, it is POSSIBLE to read information with machine, but very challenging across many reports and information quality is low. Report examples might include:

A LEVEL 3 financial report is readable by computer and the syntax is standard, structured for meaning, a "dictionary" (a.k.a. taxonomy, schema, ontology, conceptual model) is provided; but an INCOMPLETE set of rules are provided to verify the report model or reported facts to make sure there are no inconsistencies or contridictions in the reported information. The high-level report model is INCOMPLETE. Because of the lack of control which rules would provide, quality issues are likely. Because of a lack of high level report model, information extraction is challenging, but possible. Report examples include:

A LEVEL 4 financial report is READABLE by computer but not understandable by computer and the information is structured for meaning and a "dictionary" (a.k.a. taxonomy, schema, ontology) is provided; rules are provided so information quality is improved; a nonstandard high-level report model is provided. But because structures can be modified but there are no structure control mechanisms, errors can creep in to report due report configurations that are not permissable or perhaps even logical. Report examples include:

A LEVEL 5 financial report information is UNDERSTANDABLE by computer, global standard syntax, structured for meaning, a complete "dictionary" (a.k.a. taxonomy, schema, ontology) is provided, COMPLETE set of rules provided, COMPLETE standard high-level report model is provided. EVERY disclosure is explicitly identifiable using rules, type-subtype rules (a.k.a. wider-narrower) are provided, consistency crosschecks are provided, disclosure rules are provided, reoprting rules are provided. All the rules enable report to be proven to be a properly functioning logical system (consistent, complete, precise). Information can easily and reliably be extracted from report. A verifiable, proven, tested FRAMEWORK and METHOD are employed to prove report is a properly functioning logical system (control report quality). Additional verification information and report examples include:

A LEVEL 6 financial report is everything included within Level 5 PLUS blockchain-anchored XBRL-based taxonomies, rules, and reports to increase trust and transparency and make sure underlying metadata has never been changed or otherwise manipulated or tampered with. Examples blockchain (prototype):

A LEVEL 7 financial report is everything included within Level 6 PLUS blockchain-anchored transaction details enabling information provenance so you can understand the origin and full audit trail of every report detail. Think triple entry accounting. All this enables: