Issues with the communication and integrity of audit reports when financial reporting shifts to an information-centric paradigm

A core application of XBRL is to facilitate the flow of tagged financial statements and annual reports, from companies and other entities directly to the databases, web sites, and computers of regulators, stakeholders and other information consumers. Increasingly, XBRL provides the technological foundation for the communication of financial information where there is independent assurance. This XBRL-based assurance may be on the financial statements (i.e., an electronically consumable form of today's standard PDF or HTML audit report) or focus on the quality of the XBRL exhibit (i.e., the instance document). Regardless of the type of XBRL assurance report, maintenance of the security and integrity of the instance document is paramount. This conceptual paper identifies and discusses the communication, security challenges and relevant research issues when there is independent assurance on financial statements formatted in XBRL. Successful electronic communication of assurance to information consumers should clearly distinguish the responsibilities of management (i.e., the financial statements) and the auditor (i.e., the audit report). It is important to have an integrated approach where the assurance report, financial statements and other reports in which facts in the financial statements are incorporated are inextricably tied at the level of automated data consumption. Further, as much as possible, human interaction should be accommodated. The paper sets out a range of alternatives for maintenance of security on the assurance report.