Considerations for XBRL Software Development Karl Busch Ernst & Young LLP November 5, 2003 XBRL Software Requirements for the Development of XBRL Taxonomy Editor and Instance Document Creator Software

AICPA XBRL Implementation Task Force Project Objective To exercise the process of creating XBRL instance documents from full financial statements. Project Result Series of development considerations for Taxonomy and Instance Document Creation Software vendors.

Project Details  AICPA, E&Y, KPMG, & PWC  30 Public Companies –US GAAP C&I and BASI Taxonomies  Report Sections  Entity Information  Management’s Discussion and Analysis  Auditor’s Report  Report of Management  Balance Sheet  Income Statement  Statement of Cash Flows  Statement of Shareholders’ Equity  Notes to the Financial Statements  Detailed Notes  Consumer and Industrial (C&I)  Long Term Debt, EPS, Pensions, PP&E, Inventory, Income Taxes  Banking and Savings Institutions (BASI)  Long Term Debt, Income Taxes, Securities, Loans

US GAAP Taxonomy and Framework

XBRL Mapping Process

XBRL Instance Document and Taxonomy Extension Process

Resulting Software Requirements  Taxonomy Requirements  Minimum  Suggested  Optional  Instance Document Requirements  Minimum  Suggested  Optional

Minimum Requirements Definition: The “Minimum” are a suggested list of requirements necessary for the creation of successful XBRL taxonomy editor and instance document creator software.

Suggested Requirements Definition: “Suggested” are recommended to be a part of a user friendly or superior taxonomy and instance document editor. These are not necessary for the software to be functional; however, these requirements are highly recommended for successful XBRL software.

Optional Requirements Definition: Items in the “Optional” list are intended to be extra features or requirements that should prove useful for certain cases but might not be necessary for all taxonomy and instance document software.

Taxonomy Editor Requirements The XBRL Implementation Task Force project required the creation of extension taxonomies to fully represent the financial statements of the selected companies. This is not meant to be an exhaustive list, but a helpful collection of the requirements the project identified as being essential for anXBRL taxonomy editor. (These requirements also apply to the creation of the base taxonomies).

Taxonomy Editor: Minimum Requirements  Full XBRL Specification Support  Search Features  Versioning Plan  Reporting  Schema and Linkbase Validation

Taxonomy Editor: Suggested Requirements  Import Ability  Copy/Cut and paste  Undo Feature  Multi-Select  Move Elements Between Schemas  Sorting / Filtering  View Relationships

Taxonomy Editor: Optional Requirements  Application Globalization  Customizable Reports  Instance Document Template  Work Flow

Instance Document Creator Requirements Instance Document Creators 1. “Stand Alone” instance document creators 2. “ERP-type” instance document creators 3. “Adapter-type” instance document creators

“Stand Alone” Instance Document Creators Software specifically geared towards manually entering or importing data into a format that creates an XBRL instance document.

“ERP-Type” Instance Document Creators This is generally a reporting feature of an ERP product that allows fields to be mapped to the elements in a taxonomy.

“Adapter-Type” Instance Document Creators This type is typically used to map a database to a schema and create instance documents.

Instance Document Creator: Minimum Requirements  Handling Tuples  Search Capabilities  Basic Printing of instance document contents  View by Linkbases  Display Balance and Weight Info  Validation

Instance Document Creator: Suggested Requirements  Scale Data  Import data into instance document creator  Rendering/presenting instance documents  Validate data against calculation linkbase  Drag Drop sections between documents and clipboard.

Instance Document Creator: Optional Requirements  Wizards  Roll Back Data  Audit Tools – check for discrepancies  Feedback Tools – Calculation checks, Missing Data, etc.  Collaborative Group Process Tools

Additional Findings  Process Improvement Tools  User Consensus  Combined Instance Document Creator/Taxonomy Editor  Automatic Instance Document Creator/Editor

Combined Instance Document Creator/ Taxonomy Editor  One tool for process consistency.  Save time and effort  Complete Instance Document Creator  Full or Light Taxonomy Editor – can be Add-In  Useful & Comprehensive Reporting

Automatic Instance Document Creator/Editor  Built upon requirements for Instance Document Creators  Load PDF, Word,etc document into tool  Auto Tag Intelligence (closest match)  Synonym database  Auto Context Creation  Simple Review Functions  Choose from close matches  Context review  Scaling of data

Questions ?? Karl Busch Ernst & Young LLP