SAP Disclosure Management 10.0, Starter Kit for U.S. GAAP

Transcription

1 SAP Disclosure Management 10.0, Starter Kit for U.S. GAAP Configuration Overview

2 Copyright Legal Disclaimer 2012 SAP BusinessObjects. All rights reserved. SAP BusinessObjects and its logos, BusinessObjects, Crystal Reports, SAP BusinessObjects Rapid Mart, SAP BusinessObjects Data Insight, SAP BusinessObjects Desktop Intelligence, SAP BusinessObjects Rapid Marts, SAP BusinessObjects Watchlist Security, SAP BusinessObjects Web Intelligence, and Xcelsius are trademarks or registered trademarks of Business Objects, an SAP company and/or affiliated companies in the United States and/or other countries. SAP is a registered trademark of SAP AG in Germany and/or other countries. All other names mentioned herein may be trademarks of their respective owners No part of this starter kit may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. The information in this starter kit is proprietary to SAP. No part of this starter kit s content may be reproduced, copied, or transmitted in any form or for any purpose without the express prior permission of SAP AG. This starter kit is not subject to your license agreement or any other agreement with SAP. This starter kit contains only intended content, and precustomized elements of the SAP product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this starter kit is subject to change and may be changed by SAP at any time without notice. SAP assumes no responsibility for errors or omissions in this starter kit. SAP does not warrant the accuracy or completeness of the information, text, pre-configured elements, or other items contained within this starter kit. SAP DOES NOT PROVIDE LEGAL, FINANCIAL OR ACCOUNTING ADVISE OR SERVICES. SAP WILL NOT BE RESPONSIBLE FOR ANY NONCOMPLIANCE OR ADVERSE RESULTS AS A RESULT OF YOUR USE OR RELIANCE ON THE STARTER KIT. THIS STARTER KIT IS PROVIDED WITHOUT A WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON- INFRINGEMENT. SAP SHALL HAVE NO LIABILITY FOR DAMAGES OF ANY KIND INCLUDING WITHOUT LIMITATION DIRECT, SPECIAL, INDIRECT, OR CONSEQUENTIAL DAMAGES THAT MAY RESULT FROM THE USE OF THIS STARTER KIT. THIS LIMITATION SHALL NOT APPLY IN CASES OF INTENT OR GROSS NEGLIGENCE. The statutory liability for personal injury and defective products (under German law) is not affected. SAP has no control over the use of pre-customized elements contained in this starter kit and does not endorse your use of the starter kit nor provide any warranty whatsoever relating to third-party use of the starter kit. 2

3 CONTENTS FOREWORD... 4 FUNCTIONAL ARCHITECTURE... 5 Introducing the data repository... 5 Distinct Configuration principles... 5 Configuration of the data repository... 8 Content Refresh... 9 REPORTS Financial Report Q Form US GAAP-BASED TAXONOMY Organizing the Taxonomy Files Locating and operating the taxonomy files Presentation Groups Organizing Concepts: Presentation, Calculation, Definition EDGAR Filer Manual Validation CONCLUSION APPENDIX Edgar Filer Manual Rules Disclosure Management Documentation

4 FOREWORD The SAP Disclosure Management, starter kit for U.S. GAAP (U.S. Generally Accepted Accounting Principles) delivers business logic for the last mile of finance on top of a collaborative, flexible disclosure solution using both product and business best practices. This pre-configuration assists you in setting up your application in order to publish financial / non-financial regulatory statements and notes as well as to file the corresponding data in XBRL (extensible Business Reporting Language) format. The starter kit is based on the U.S. GAAP taxonomy as published January 31, 2012 by the FASB (Financial Accounting Standards Board), adopted and supported by U.S. SEC (United States Securities and Exchange Commission) effective March 26, It includes predefined financial statements designed according regulation S-X in order to address U.S. SEC requirements for Domestic Private Issuers through a pre-built 10-Q form template compliant with the EFM (EDGAR Filer Manual) rules and the US GAAP Taxonomy 2012 Guide. SAP Disclosure Management, starter kit for U.S. GAAP has been designed to maximize your time-to-value when used in combination with transactional and consolidation systems, in particular SAP Planning and Consolidation and SAP Financial Consolidation applications. The Configuration Overview document firstly explains the principles of SAP Disclosure Management, starter kit for U.S. GAAP data repository. Secondly, the quarterly financial report sample and the content related to the SEC 10-Q form are described. Lastly, this document presents the structure of the starter kit U.S. GAAP-based taxonomy. 4

5 FUNCTIONAL ARCHITECTURE Introducing the data repository The SAP Disclosure Management, starter kit for U.S. GAAP includes a Microsoft Excel-based data repository, also referred to as data cache, which is the cornerstone of your disclosure management application. It is organized in a way that allows you to clearly define and identify the source data in the reporting application. It also highlights how this data is prepared and linked to the financial report on the one hand, and tagged against the U.S. GAAP-based taxonomy. This data repository can be easily adapted to meet your specific filing requirements for instance inserting new rows and columns, copying existing cells, copying formulas to extract, control the data or applying one of the starter kit pre-defined cell format. Distinct Configuration principles Disclosure Management repository can be configured according to different principles. You therefore start your SAP Disclosure Management reporting from the configuration principle that corresponds to your requirements the most. Explaining the configuration principles Integrated vs. Bolt-on According to the Integrated principle, the data repository is populated by directly extracting the reporting data from the source reporting system. To do so, the Microsoft Excel-based data retrieval methods for the underlying reporting application are leveraged: cell-based formulas or report definition. For example, SAP Financial Consolidation data is extracted directly into the data repository by using the CtGetData() cell-based formula of SAP Financial Consolidation add-in for Excel. In the Bolt-on approach, the data from the data repository is fetched from existing Excel-based reports extracted from or built for the underlying reporting application. It is recommended that the users put in a single report bundle all their financial statements and notes for one period. For example, financial reports designed for SAP Planning and Consolidation application via the SAP EPM add-in for Excel can be manually or automatically refreshed and stored in a Microsoft Windows file directory. They can then be used as data source for populating the SAP Disclosure Management data repository. Unified vs. Separate The Unified approach consists of putting together all financial worksheets inside one workbook of the data repository designed for populating both the reports and the XBRL tagging. Conversely in the Separate approach, worksheets used to prepare data for reports are kept distinct from one another. 5

6 Link with SAP Planning and Consolidation and SAP Financial Consolidation As per the Integrated configuration principle, the data repository workbook leverages the appropriate functionality to fetch the data from your reporting system. However should you have other reporting software, these templates can be easily adapted to the corresponding data extraction function for Microsoft Excel, if any. Configuration Principles applied for sample reporting Q The SAP Disclosure Management starter kit is delivered with a sample reporting period which illustrates how data is distributed from SAP Planning and Configuration or any back-end system supporting Excel output format. Configuration Sample reporting period Integrated / Bolt-on Unified / Separate For SAP Planning and Consolidation / For SAP Financial Consolidation Q Bolt-on Unified YES During your Disclosure Management implementation project, you can make the most of either sample reporting period as a starting point for your configuration depending on how the reporting team and workflow is organized: for example, availability and publication of financial reports, access authorizations by report section, workflow for updating the data repository and performing XBRL-related tasks. As part of this implementation, you may even want to create a new combination that matches your requirements at best from the pre-delivered templates, for example Integrated and Separate. Data Workflow The workbook delivered as part of the SAP Disclosure Management starter kit data repository for the Third Quarter 2012 sample period is configured for extracting the reporting data from Microsoft Excel-based reports located in a shared directory. This corresponds for instance to the use case when SAP Planning and Consolidation reports are being automatically refreshed and published to a network folder by using the SAP Disclosure Management Distribution feature. For Q3 2012, 3 financial reports are managed based on the same data in the repository: 1) Quarterly Report in Word format 2) Form 10-Q in Word format 3) Form 10-Q in XBRL format This organization of reports especially is relevant for granting different access rights to users depending on whether they should work on report data or XBRL tagging. Moreover, it supports 0 to several XBRL reports for the same period. 6

7 The data workflow is summarized in the chart below: SAP Disclosure Management WORKFLOW Data Sources Data Repository Document Management Output Formats Key Figures Quarterly Report Financial Data Form 10-Q CONSO-US-DISTRIB SEP.XLSX on shared drive Scaling Rounding Signing Tagging for XBRL Taxonomy U.S. GAAP 2012 Datalink Schema Reference Preview 7

8 Configuration of the data repository Settings In the first worksheet, settings related to the source reporting data are exposed to you on the one hand, and notably the following: The scale factor to be applied to the source amounts (see Error! Reference source not found. Error! Reference source not found.); The period end date, the currency and the currency rate to configure the headers of all financial statements Note regarding data retrieval formula and settings: The settings and formula of SAP Disclosure Management starter kit for U.S. GAAP are defined so it is possible to extract data from the source Excel workbook (SAP Financial Consolidation or SAP Planning and Consolidation). Should this template be used with another source system, the settings can be adapted easily while keeping them based on the same principle for extracting data from a reporting database or other workbooks. Controls The first worksheet also provides you with a table of contents of the financial statements and notes. Formulas are used to retrieve the number of errors in the statements and hyperlinks have been inserted to directly switch to the report you have selected. The control column gives you a snapshot of the number of rollup inconsistencies raised by visual controls defined in the reports, notably those due to rounding issues. 8

9 Adjustments Data Retrieval Formula The data retrieval formulas include mechanism for fetching the source reporting data (Excel links or Excel add-in formula) and: rounding source amounts to the configured scale By default, the amounts filed in the reports are in thousands of U.S. Dollars. reversing the sign of the source amount Some amounts may have a negated sign in the source system compared to the expected sign in the final reports (e.g. expenses, treasury shares). For this reason a specific column exposes the multiplying factor to be applied to the source amount to reverse the sign in this case (column header = N equals to 1 or -1). multiplying source amounts in the case they are originally expressed in thousands or in million for example. Formatting According to the EDGAR Filer Manual (see EFM ), you should not define or use units that imply a scale factor on a currency. If amounts are expressed in thousands or in million in the source reporting application, they should be multiplied accordingly to turn them into amounts in simple unit without factor in the instance file. Thus the retrieval formula finally takes into account the scale factor defined in the Settings section. Microsoft Excel cell styles have not been leveraged in order to streamline the layout applied to cells of different content: statement title, base-level account description, total account description, control formula for example. As a result, you can update the cells layout consistently throughout the workbook by range of cells. Conditional formatting of cells has been implemented in order to highlight all rounded amounts in the report. Content Refresh The SAP Disclosure Management, starter kit for U.S. GAAP showcases best practices for configuring data sources, especially you should be able to refresh all cache data in one click. You can either open the Financial Statements main workbook and click the Refresh button from the Disclosure Management add-in, or click the Content Refresh tab of the report from the Web interface and click the Start refresh button. In addition to the main financial workbook, other Microsoft Excel chapters can be provided to populate additional or industrial specific data in the reports (e.g. Key Figures to illustrate charts in the sample annual report ) These files can be stored out of the SAP Disclosure Management application, for instance on a shared directory, and uploaded in the data repository. 9

10 REPORTS Financial Report SAP Disclosure Management, starter kit for U.S. GAAP, includes a quarterly financial sample report. This report can be used as an illustrative reference for implementing and configuring your own financial reports given the way it leverages a large number of SAP Disclosure Management features while remaining simple and generic. Building your own application by creating a period and reports from your existing documents and applying customization materials and enhancements from the starter kit is much quicker and easier than designing all the necessary configuration building blocks from scratch. Report content Report structure The quarterly report includes a basic financial report structure in order to illustrate Disclosure Management features and best practices. You can reuse chapters, default cover page and templates for your future reports, automatically update the content and layout of the pre-defined table of contents via the usual Microsoft Word capabilities in terms of automation and styles. At the end of your reporting, you can make the most of the SAP Disclosure Management import features and load all the structure of your financial report in one go via a text file, or you can copy existing reports to new 10

11 reports or preferably use the Roll Forward button in the Settings / Period interface. So the default starter kit period is an interesting source of inspiration for implementing Disclosure Management projects. Content of tables: Briefing Books and Data providers Data providers are used to fetch data from the data repository. They correspond to worksheets or a selection of cells from workbooks, also called the Briefing Books. SAP Disclosure Management starter kit for U.S. GAAP is delivered with a set of predefined data providers which allow you to fetch and format relevant data organized in tables for the reports. All Data providers configured in the starter kit for U.S. GAAP are ER tables based on Excel range names. It is recommended to use ER tables in order to reference data independently from the layout of the Briefing Books, so the fetched data keep consistent when adding or removing rows or columns. In addition, an important best practice consists of numerating the Dataproviders in order to insure that the BD data worksheets in the destination Excel report are correctly ordered so the Excel links inside the destination workbook keep consistent. The naming convention for ER tables is: ER_KEYS_(order number)(name of the table) ER_LABELS_(order number)(name of the table) On the other hand, the name of values columns should be as short as possible and not include any order to support insertion or removal of columns: ER_VALUES_(order number)(name of the table)_(column code) Each predefined data provider is associated with a formatting table template defined in the BIP_WordTableDef.doc file (see The naming convention of the templates is: (Report Code)(Formatting Version)_(Table Layout) Report Layout below ). The naming convention for the templates is: (Report Code)(Formatting Version)_(Table Layout) 11

12 When associating a table template to a Data provider, you can configure the rendering of each line items with a formatting code (for example, Default leaf-level or total-level formatting styles provided with the starter kit). 12

13 The naming convention of the templates is: (Report Code)(Formatting Version)_(Table Layout) Report Layout Table Formatting Templates Applying normalized formats to tables requires designing and implementing a specific Microsoft Word-type file. Such a file is delivered by the starter kit and configured to be shared by all the document writers. This file includes various formatting templates depending on the table type: financial statement over two periods, financial statement over two periods including the reference to notes, statement of changes in equity and others. The text formats of the different table components are streamlined by leveraging the Microsoft Word styles (headers, labels, amounts.). With this it is much easier for you to update these formats according to your company s brand image and to apply the changes throughout your financial report. All Word styles used to format table templates are prefixed by DM. It is forbidden to include Normal style in the design of table templates. Text Styles, Headers and Footers SAP Disclosure Management, starter kit for U.S. GAAP also includes a template for text styles, headers and footers, which by default is applied to all chapters when creating the final financial report. This template showcases many interesting examples and best practices in terms of page layout, such as streamlining the text formats via Microsoft Word styles, differentiating even and odd pages, including the title of the current chapter or section in the page header or page numbers. As with table formatting template, the template for text styles, headers and footers will be easily updated in accordance with your company s brand image, notably by replacing the SAP logo, replacing the default report title and adapting the text styles. 13

14 Validation Dashboard The starter kit for U.S. GAAP includes a Validation Dashboard configured as a specific chapter of the financial report. It will be kept out of the final rendering of the final report while providing you with an at-aglance understanding of the data consistency. Firstly the dashboard shows the number of possible errors raised in the table of contents of the data repository. Secondly it highlights the specific controls you may configure in the report based on the amounts included in the tables. 14

15 10-Q Form 10-Q Structure The starter kit includes a report whose chapters structure corresponds to the 10-Q form as defined by the U.S. Securities and Exchange Commission. When designing your 10-Q filing in SAP Disclosure Management, you can start from this report and import your Microsoft Word files into this structure. 10-Q Heading and Items In addition to the 10-Q form structure, a generic 10-Q heading template and sample items are available including placeholders dedicated to the information related to your company. 15

16 XBRL Tagging Concepts, Contexts and Units Each cell of the tagging file for period Q have been tagged with the following elements: One Concept from the starter kit s taxonomy (see U.S. GAAP-based Taxonomy on page 20), One of the base Contexts, or one of the related dimensional Contexts defined for the Statement of Changes in Equity and the notes, o No unused context was defined as per EFM (see Appendix), One of the following Units when appropriate: USD (Dollar), pershare (USD per Share), shares. o Unit templates defined in the starter kit are being used to tag amounts with decimal attribute (no precision attribute as per EFM ). In terms of contexts, six base contexts have been created in order to tag position data (period type = instant) and periodic data (period type = duration) for both the current fiscal year and the prior fiscal year, and position data for the year before the prior fiscal year: Base Context ID Description Period Type FYp0YTD Current Year Year To Date Duration FYm1YTD Prior Year Year To Date Duration FYp0Qp0e Current Year, Current Quarter End Instant FYm1Qp0e Prior Year, Same Quarter End Instant FYm1Q4e Prior Year, Fourth Quarter End Instant FYm2Q4e Year minus 2, Fourth Quarter End Instant Additional dimensional contexts are derived from the base contexts above. They were created to dimensionally tag the data in the Statement of Changes in Equity with members of the Component of Equity axis, and the data in the notes with members corresponding to components of tangible and intangible assets. Example of dimensional context: Current Year to Date, Retained Earnings Member 16

17 When filing data are changed in the DEI worksheet, a macro is triggered to update the time-related attributes (Instance, Start Date, and End Date) and the company attributes (Entity URI and Entity Code) of all contexts, thus avoiding tagging information more than once. This macro uses the Report Builder s Application Programming Interface (see Updating Contexts Automatically below). Data Retrieval Formula The data retrieval formulas for XBRL include additional mechanism for validating the reporting data against the U.S. GAAP taxonomy and: reversing the sign of the source amount Data may be of negative sign in the financial reports whereas the values of the business facts in the XBRL instance are absolute to match the balance attribute (debit or credit) of the corresponding taxonomy concepts. adjusting the weight of the amounts by 1 or -1 to check the rollup consistency on rounded amounts. The calculation hierarchy is displayed in column B of the reports in order to ensure consistency controls of total accounts. Rollup Consistency Controls Worksheets include control columns (right columns in red color) in which the difference between amounts stored on parent accounts and the sum of amounts stored on the respective child accounts is computed. These visual controls reflect the rollup calculation controls defined in the taxonomy, and therefore allow you to anticipate on possible rollup errors raised by the validation engine of Report Builder. 17

18 Formatting Microsoft Excel cells have no background color except for the tagged cells. Notes block tagging and table tagging In order to comply with the SEC filing requirement, textual information and entire tables must be blocktagged. As a reminder, the 4 levels of tagging required by the SEC from the second year of mandatory XBRL filing: Level 1: block tagging of notes Level 2: separate block tagging by significant accounting policy Level 3: separate block tagging by table Level 4: detail tagging at amount level for amounts included in tables and footnotes In the data repository report, subsections have been created under the chapter of the XBRL tagging workbook so that the content of the corresponding Microsoft Word chapters can be tagged and notably entire blocks of chapters, paragraphs and tables. Thus SAP Disclosure Management, starter kit for U.S. GAAP illustrates how the different levels of text detail are associated with the appropriate concept in the U.S. GAAP taxonomy. Opening the chapters from this data cache view allows you to tag the required information in the same text files that make up your annual report, and ensure the consistency of the data in the report and in the XBRL filing. By following these examples for the rest of your financial report, all the required textual information of your notes will be included in your XBRL instance. Updating Contexts Automatically A VBA (Visual Basic for Applications) macro is attached to the DEI worksheet so that it is triggered when one of the context-related pieces of information is updated in this sheet: entity URI, entity code, period end date 18

19 or fiscal year end date. This allows you to automatically update all the time and entity related properties of the predefined contexts, including dimensional contexts. This macro is based on the Application Programming Interface (API) of the Report Builder component. It illustrates how you can leverage the openness and smart programming capabilities of this SAP Disclosure Management component. 19

20 U.S. GAAP-BASED TAXONOMY Organizing the Taxonomy Files The starter kit includes a customizable XBRL taxonomy which can be modified to reflect your own filing requirements, notably in terms of specific concepts. In this respect, the namespace prefix comp has been defined and identifies the taxonomy items that are specific to your group: extended primary concepts and members, labels and links between elements (presentation links, calculation links and definition links). The taxonomy files are named and organized in compliance with rule of the EDGAR Filer Manual (see EFM in Appendix). XBRL Document Schema Calculation Linkbase Definition Linkbase Label Linkbase File name* comp xsd comp _cal.xml comp _def.xml comp _lab.xml Presentation Linkbase comp _pre.xml *For a company identified with comp and for 2012 third quarter end According to this EFM rule, for Q year end, the XBRL instance that you will create with your corporate extensions should be named comp xml where comp stands for your SEC registrant ID. The comp default prefix must be changed to the filing prefix of your company both for taxonomy elements and the files names. You can do this in the Taxonomy Information section via Taxonomy Designer. Locating and operating the taxonomy files The xml taxonomy files are stored in the Disclosure Management repository. Therefore they are stored in the server s side as with any Microsoft Office file used in the data repository or the financial report. A specific XBRL taxonomy-type report has been created for this purpose for the Q period: U.S.GAAP2012- based taxonomy. In order to operate the XBRL tagging workbook, the user needs to load the taxonomy from the Report Builder menu. For doing so, the taxonomy files can be accessed via WebDAV 1 as illustrated hereafter: 1 WebDAV is an extension of the HTTP protocol which allows you to browse the content of the database as in a folders hierarchy. WebDAV must be properly setup on the Disclosure Management server; it is strongly recommended to map a network drive in Windows Explorer to the WebDAV directories and to refer to this drive for loading the taxonomy. 20

21 Presentation Groups The following presentation groups, i.e. Extended Link Roles in XBRL terms, have been created in the taxonomy in order to reflect the 4 levels of tagging required by the SEC mandate: Document - Document And Entity Information Statement - Consolidated Statement Of Operations Statement - Consolidated Balance Sheets Statement - Consolidated Statement Of Cash Flows Statement - Consolidated Statement Of Shareholders Equity Disclosure - Significant Accounting Policies Disclosure - Acquisitions Disclosure - Significant Accounting Policies (Policies) Disclosure - Acquisitions (Tables) Disclosure - Acquisitions (Details) Disclosure - Goodwill And Intangible Assets Disclosure - Goodwill and Intangible Assets (Tables) Disclosure - Goodwill and Intangible Assets (Details) Disclosure - Goodwill and Intangible Assets (Details2) Disclosure - Supplemental Balance Sheet Information Disclosure - Supplemental Balance Sheet Information (Tables) Disclosure - Supplemental Balance Sheet Information (Details) Disclosure - Capital Stock Disclosure - Income Taxes Disclosure - Pension Plan Disclosure - Fair Value Measurements Disclosure - Commitments And Contingencies Disclosure - Comprehensive Income Disclosure - Business Segments Disclosure - Geographic Areas The descriptions of these presentation groups abide by the EFM rule ({SortCode} - {Type} - {Title}). 21

22 The first presentation group (00000) includes mandatory information related to the document and the publisher entity (DEI) as per EFM such as the document type, the document fiscal year focus and the entity registrant name. The four presentation groups to correspond to the publishable financial statements. The coding of the disclosures enable to quickly identify the level of tagging required for the concepts: The first position corresponds to the level of tagging (1 for block tagging, 2 for tagging of policies, 3 for tagging of tables, 4 for detailed tagging) The second to the the third position is the ordering number of the document The forth and the fifth position is the ordering number of the detail data for Level IV tagging Organizing Concepts: Presentation, Calculation, Definition The vast majority of concepts used in the taxonomy for the financial statements listed above are U.S. GAAP concepts imported from the U.S. GAAP taxonomy released by the FASB ( ). The hierarchies of concepts defined in the Presentation view, in the Calculation view and in the Definition view are essentially based on those of the standard U.S. GAAP taxonomy. Example 1: Statement of Operations Presentation view Example 2: Statement of Cash Flows, Indirect Method Calculation view 22

23 Example 3: Statement of Changes in Equity Definition view Example 4: Note Supplemental Balance Sheet Information Presentation view 23

24 The names of extension concepts have been defined as per the Label Camel Case Concatenation (LC3) convention (see EFM in Appendix). Besides, all standard labels are different from one another in accordance with section of the Edgar Filer Manual (see EFM in Appendix). EDGAR Filer Manual Validation The EDGAR filing process requires that electronic filings to the SEC be validated prior to submission against the most recent version of the EDGAR Filer Manual Volume II published on the U.S. SEC website. In support of this requirement, Report Builder implements an automated electronic financial review checklist for Interactive Data Exhibit 100 (attachment type EX-100) and Exhibit 101 (attachment type EX-101). The validation process is based on Rules Library catalogs that are defined in formula linkbases. By default, rules associated to U.S. GAAP 2010 and 2011 may exist in the current release Report Builder but not U.S. GAAP In order to support the U.S. GAAP 2012 taxonomy, you may need to create a new library of business rules for Report Validation. To do so, follow these steps: 1) Update the Taxonomy List Edit the resource file TaxonomiesList.xml located in your user directory (in Windows 7 environments: C:\Users\(name)\AppDataLocal\EDGAR Online\UBmatrix Report Builder\RBMEResources\System) and declare the U.S. GAAP 2012 taxonomy by adding new rows in the XML file: <taxonomynamespace> <taxonomynamespace> <taxonomynamespace> <taxonomynamespace> <taxonomynamespace> </taxonomylist> </taxonomy> <taxonomy> <taxonomytype>us_gaap 2012</taxonomyType> <taxonomylist> <taxonomynamespace> <taxonomynamespace> <taxonomynamespace> <taxonomynamespace> <taxonomynamespace> <taxonomynamespace> 24

25 <taxonomynamespace> <taxonomynamespace> <taxonomynamespace> <taxonomynamespace> <taxonomynamespace> <taxonomynamespace> <taxonomynamespace> <taxonomynamespace> <taxonomynamespace> <taxonomynamespace> </taxonomylist> </taxonomy> </list> 2) Stop and restart Excel 3) In the UBmatrix tab of the Microsoft Office ribbon, click the Manage Rules icon: 4) Add a new rule set name for the XBRL formulas located in the C:\Program Files (x86)\edgar Online\UBmatrix Report Builder\RBMEResources\XPE\resources\formulaeSEC_v19\EX_101 folder and associated with the U.S. GAAP 2012 taxonomy: 25

26 5) If the library of business rules is correctly configured, Report Builder allows you to enter the Input Parameters for the filing: the Central Index Key (CIK), the entity name and the submission type (10-Q, 10- K ) Finally, you can use the built-in validation capabilities of Report Builder that enable preparers to verify filings prior to submission. Enable EDGAR Filer Manual validation by ticking the Include XBRL Formula Trace ofthe Validation dialog box: This is the validation report for the XBRL filing sample included in the U.S. GAAP starter kit: 26

27 CONCLUSION Corporate reporting is very specific to each company. In terms of content, many lines of your financial statements, your notes and all the textual information are relevant to your company only. As regards the form, the layout of your annual and quarterly reports is similar to no other. SAP Disclosure Management, starter kit for U.S. GAAP provides you with a valuable starting point to secure and accelerate your own disclosure implementation. In order to make sure that you benefit from all SAP best practices, you just have to follow simple steps such as: Adapting the cache Excel files to import your financial statements, Creating reports and periods, Updating the pre-delivered text styles, Extending the default taxonomy, and Inserting your logo. It is always easier and safer to adapt existing tried-and-tested elements than designing them from scratch. Take advantage of SAP Disclosure Management, Starter Kit for U.S. GAAP to streamline your compliance to disclosure requirements and reduce implementation time. 27

28 APPENDIX Edgar Filer Manual Rules This section lists the EFM rules which are explicitly referred to throughout the present document. More detailed explanations about these rules can be found in chapter 6 of the Edgar Filer Manual, Volume II available on the U.S. SEC website at the following URL: EFM EFM EFM EFM EFM EFM EFM EFM EFM EFM XBRL document names must match {base}-{date}[_{suffix}].{extension}. Every xbrli:context element must appear in at least one contextref attribute in the same instance. The xbrli:xbrl element must not have any facts with the precision attribute. An instance must contain one non-empty fact for each required Entity Information element, each with a contextref attribute referring to a Required Context. The value of an EntityPublicFloat fact in an instance will be 0 for an entity that has only public debt. The content of a numeric fact never has a scale factor. Do not define or use units that imply a scale factor on a currency. A link:roletype element must contain a link:definition child element whose content will communicate the title of the financial statement section, the level of facts in the instance that a presentation relationship in the base set of that role would display, and sort alphanumerically into the order that statements and footnotes appear in the official HTML/ASCII document. The link:roletype link:definition text must match the following pattern: {SortCode} - {Type} - {Title} Wherever possible, registrants should assign a standard and other labels for an element defined in a standard taxonomy schema in preference to declaring a new element in a company schema. The name attribute of an xsd:element should consist of capitalized words corresponding to the standard label, a convention called LC3. The DTS of an instance must have no distinct elements having the same English standard label (xml:lang attribute equal to en-us ) Disclosure Management Documentation A set of documents is available on SAP Service Market Place and provides you with useful information on how to install and use SAP BusinessObjects Disclosure Management and about best practices when updating the taxonomy or the tagging workbook. Visit SAP Service Marketplace at the following location: Release & Upgrade Info Installation & Upgrade Guides SAP BusinessObjects SAP BusinessObjects Enterprise Performance Management (EPM) Disclosure Management Example of documentations: SAP Disclosure Management Starter kit for U.S. GAAP Installation guide How-to Guide: How to Migrate XBRL Tagging to a Newer Taxonomy Version 28

29 29