Browse our growing collection of case studies, white papers and resources documenting the significance of the business reporting data standard, or check out one of our Infographics to get a clear picture of the hows and whys of the financial data standard.
Contact firstname.lastname@example.org to share details about your use case or tool.
Case Studies & White Papers
|Review case studies, white papers and research from XBRL US and others. Here’s a sample:
This paper provides the XBRL US position on the use of financial data standards and recommends adopting the freely available, open XBRL data standard for all financial data reporting required by U.S. regulators. Only the XBRL standard has 1) the appropriate format to render data computer-readable; 2) the appropriate information component to clearly and consistently portray definition, time period, units and other attributes of financial data and; 3) the appropriate identifier mechanism to persistently define needed identifiers such as reporting entity.
View this infographic for problems in today’s business to government reporting and this infographic for steps government can take to save billions with standards.
The gains for the US economy by adopting this approach will be substantial:
- Significant savings in data collection and processing costs for business, government and the American taxpayer
- Reduced burden (cost) on US businesses
- Consistent, comparable, timely information for investors, businesses and policymakers
|Get the big picture on selected topics with one of our standardized financial data infographics.
Since the first specification was introduced in 2003, the XBRL Specification has evolved to meet changing regulatory requirements and emerging technology opportunities.
Changes in financial data, e.g., debt coverage ratios or loan to value ratios, trigger the execution of loan covenants in the contract. If data standards are used, smart contracts can automatically update the blockchain with payable and receivable information. No human intervention is required.