SAP Disclosure Management 10.0, Starter Kit for IFRS. Configuration Overview

Transcription

1 SAP Disclosure Management 10.0, Starter Kit for IFRS 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 DATA REPOSITORY... 5 Introducing the data repository... 5 Distinct Configuration principles... 5 Common Configuration Principles...11 External Excel Workbooks...15 REPORTS...16 Financial Report F Form...20 IFRS-BASED TAXONOMY...22 Organizing the Taxonomy Files...22 Locating and operating the taxonomy files...22 Presentation Groups...23 Organizing Concepts: Presentation, Calculation, Definition...24 CONCLUSION...27 APPENDIX...28 Edgar Filer Manual Rules...28 Disclosure Management Documentation

4 FOREWORD The SAP Disclosure Management, starter kit for IFRS (International Financial Reporting Standards) 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 and 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 IFRS taxonomy as published on March 29th, 2012 by the IASB (International Accounting Standards Board) and includes a predefined financial report designed according to IAS 1 and IAS 7 requirements. In addition, the starter kit addresses U.S. SEC (United States Securities and Exchange Commission) requirements for Foreign Private Issuers through a pre-built 20-F form template compliant with the EFM (EDGAR Filer Manual) rules and the IFRS Taxonomy 2012 Guide. SAP Disclosure Management, starter kit for IFRS has been designed to maximize your time-to-value when used in combination with transactional and consolidation systems, in particular SAP Business Planning and Consolidation and SAP Financial Consolidation applications. The Configuration Overview document firstly explains the two design principles of SAP Disclosure Management, starter kit for IFRS data repository. Secondly, the annual financial report sample and the content related to the SEC 20-F form are described. Lastly, this document presents the structure of the starter kit IFRS-based taxonomy. 4

5 DATA REPOSITORY Introducing the data repository The SAP Disclosure Management, starter kit for IFRS 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 IFRS-based taxonomy on the other hand. This data repository can be easily adapted to meet your specific filing requirements as for example 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 The starter kit data repository is configured according to different principles depending on the sample reporting period. You can therefore start your SAP Disclosure Management application from the configuration principle that corresponds to your requirement 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 GetCtData() cell-based formula of SAP Financial Consolidation add-in for Microsoft Excel. In the Bolt-on approach, the data from the data repository is fetched from external Excel-based reports extracted from or built for the underlying reporting application. For example, financial reports designed for SAP Business Planning and Consolidation application via the SAP EPM add-in for Microsoft 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. XBRL-enabled data repository vs. XBRL specific report On the one hand, SAP Disclosure Management allows you to design one data repository workbook by reporting period that includes both source data for financial reports and data tagged for XBRL instances. On the other hand, it is also possible to create one report dedicated to XBRL tagging and to keep it distinct from the data repository workbook(s) used to populate Microsoft Word chapters. Single workbook vs. Multiple workbooks The Single workbook approach refers to the unification of the financial statements within one single workbook of the data repository designed for populating the report s chapters. Conversely in the Multiple workbooks approach, the data repository is made up of several workbooks, for example one per financial statement. 5

6 Link with SAP Business Planning and Consolidation and SAP Financial Consolidation As per the Integrated configuration principle, the data repository workbook must leverage the appropriate functionality to fetch the data from your reporting system. In this respect, the SAP Disclosure Management starter kit data repository includes a workbook pre-designed to fetch data from a SAP Financial Consolidation application and another workbook pre-designed to fetch data from a SAP Business Planning and Consolidation application (by default the data from the respective consolidation starter kits for IFRS). However should you have other reporting software, these templates can be easily adapted to the corresponding data extraction function for Microsoft Excel, if any. Summary of Configuration Principles by Sample Reporting Period The SAP Disclosure Management starter kit is delivered with two sample reporting periods which illustrate how the configuration principle explained above can be implemented and combined. Reporting period 2011 A 2011 B Source application Integrated / Bolt-on XBRL SAP Business Planning and Consolidation SAP Financial Consolidation SAP Business Planning and Consolidation SAP Financial Consolidation Mix Integrated and Bolt-On Integrated Bolt-on Integrated XBRL-enabled data repository XBRL specific Report Single / Multiple workbook(s) Single Single 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 disclosure team and workflow is organized: for example, availability and publication of reporting 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 multiple integrated data repository workbooks and one XBRL-specific report on top of a SAP Business Planning and Consolidation application. 6

7 Sample Period 2011 A Integrated and Mixed, XBRL-enabled data repository The workbooks delivered as part of the SAP Disclosure Management starter kit for IFRS data repository for the 2011 A sample period provides you with an adaptable template to fetch data directly from SAP Financial Consolidation or SAP Business Planning and Consolidation and to handle data both for chapters and XBRL alongside in the same worksheet. The worksheets that include the financial statements are based on a common structure that allows you to streamline and clarify the data flow between your reporting system and the filing output: Identifying the reporting data define the relevant dimension members and check them via the respective labels, Defining the data tables in chapters define line IDs for dynamic content and layout update, overwrite the source application labels when necessary, adjust figures according to your rounding policy, Control check that the amount of each total items matches the sum of the respective breakdown in rows and column Data for XBRL tagging apply a scale factor to amounts if different from the one used in the financial report, and tag them (see EFM and EFM in appendix). 7

8 The data workflow according to this principle is summarized in the chart below: SAP Disclosure Management Charts.xlsx on shared drive Data Sources Data Repository Document Management Annual Report Output Formats 14 SCI & SCE.xlsm* on shared drive Business Planning and Consolidation Financial Data (BPC) OR Form 20-F Financial Consolidation Financial Data (FC) Scaling Rounding Signing XBRLTagging Taxonomy IFRS 2012 Datalink Schema Reference Output * Statement of Comprehensive Income and Statement of Changes in Equity from SAP Business Planning and Consolidation 10.0 starter kit for IFRS. 8

9 Sample Period 2011 B Bolt-on (BPC) or Integrated (FC), XBRL specific report The major distinctive configuration principle of the 2011 B sample period is that the XBRL tagging is performed in one dedicated workbook outside the data repository, which is a modular configuration in terms of both XBRL management and access management. Firstly keeping XBRL workbooks distinct from the data repository allows you to easily handle one, multiple or no XBRL reporting for the period. Secondly, this file organization is also relevant for granting different access rights to users depending on whether they should work on report data or XBRL tagging. Moreover this sample period is configured for extracting the reporting data from Microsoft Excel-based reports located on a shared directory. This corresponds for example to the use case when SAP Business Planning and Consolidation reports are automatically refreshed and published to a network folder by using the Distribution feature of the SAP EPM Add-In for Microsoft Excel. 9

10 The data workflow according to this principle is summarized in the chart below: SAP Disclosure Management Data Sources Data Repository Document Management Output Formats CONSO-BPC-DISTRIB DEC.XLSX on shared drive Key Figures Annual Report Financial Data (BPC) Form 20-F OR Financial Consolidation Financial Data (FC) Tagging for XBRL Scaling Rounding Signing Taxonomy IFRS 2012 Datalink Schema Reference Output 10

11 Common Configuration Principles Settings In the first worksheet, settings related to the source reporting data are exposed to you, and notably the following: The scale factor to be applied to the source amounts (see Data Retrieval Formula below) on the one hand, and for XBRL data on the other hand; For the 2011 A approach, the dimensional identifiers of the data slice that includes the financial information to disclose. Note regarding data retrieval formula and settings: The settings and formula of SAP Disclosure Management starter kit for IFRS are defined so as to extract data from the SAP consolidation starter kits for IFRS (SAP Financial Consolidation or SAP Business 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. Table of Contents and Control The Table of Contents worksheet (ToC tab) provides you with a summary of the financial statements and notes. Formulas are used to retrieve the statements name. Moreover a 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. This summary can therefore be consulted as a control dashboard prior to updating the chapters and creating the XBRL instance. XBRL Tagging Concepts, Contexts and Units The cells of the tagging section for period 2011 A and the cells of the XBRL report for 2011 B have been tagged with the following elements: One Concept from the starter kit s taxonomy (see IFRS-based Taxonomy on page 22), 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: EUR (Euro), EURperShare (Euro per Share), Share. o Unit templates defined in the starter kit are being used to tag amounts with decimal attribute (no precision attribute as per EFM ). 11

12 In terms of contexts, five 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 FYm2Qp0e Year-2, Same 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 When the filing date information is updated in the DEI worksheet, the time-related properties of these contexts (Instance, Start Date, and End Date) are automatically updated by a specific macro that leverages the Report Builder s Application Programming Interface (see Updating Contexts Automatically below). 12

13 Data Retrieval Formula As explained in the Instructions worksheet, the data retrieval formula includes the formula for fetching the source reporting data (Excel add-in formula or external formula) and takes into account the following: Rounding source amounts to the nearest integer Amounts filed in an XBRL instance must be integers. Reversing the sign of the source amount Some amounts may have a reversed sign in the source system compared to the expected sign in the XBRL instance (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 = S ). Adjusting the amount by 1 or -1 to ensure the rollup consistency on rounded amounts. The sum of rounded amounts for base level accounts in the hierarchy does not necessary equal the rounded amount for the respective parent account. Therefore the retrieval formula takes into account the content of a dedicated column where you can input the adjustment on an account by account basis, generally +1 or -1 (column header = R ). Multiplying source amounts in the case they are originally expressed in thousands or in million for example. 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. Rollup Consistency Controls Worksheets include control columns 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. Formatting Microsoft Excel cell styles have been leveraged to streamline the layout applied to cells depending on their content: statement title, base-level account, total account, control formula for example. As a result, you can update the cells layout consistently throughout the workbook by updating the pre-defined cell styles. 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. 13

14 Thus SAP Disclosure Management, starter kit for IFRS illustrates how the different levels of text detail are associated with the appropriate concept in the IFRS 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 XBRL tagging workbooks 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 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. 14

15 External Excel Workbooks The SAP Disclosure Management, starter kit for IFRS showcases how you can mix data from different Microsoft Excel-based data sources while streamlining both the links between files and the data workflow. In addition to the data repository workbook, other Microsoft Excel files are provided and allow you to populate additional data both in the data repository and directly in chapters. They can be classified into three categories: SAP Business Planning and Consolidation 10.0 reports used as part of the bolt-on approach (CONSO- BPC-DISTRIB-2011.DEC.xlsx), Files dedicated to the calculation of Comprehensive Income accounts, and items of the Changes in Equity statement according to the configuration principle of the SAP Business Planning and Consolidation 10.0, starter kit for IFRS (14 SCI & SCE.xlsm), and One workbook which includes data dedicated to illustrative charts in the sample annual report (DR - Charts Datasource.xlsx). These files can be stored out of the SAP Disclosure Management application, for instance on a shared directory, while keeping them linked to the data repository and chapters. 15

16 REPORTS Financial Report SAP Disclosure Management, starter kit for IFRS includes a sample of annual financial report. This report can be used as the starting point for configuring your own financial report given the way it is configured: it leverages a large number of SAP Disclosure Management features while remaining simple and generic. Building your own application by adapting and enhancing the starter kit is much quicker and easier than designing all the necessary configuration building blocks from scratch. Report content Report structure One basic financial report structure is ready to be updated according to your disclosure needs. You can directly add new chapters, replace the default cover page and back page with the one your future report, 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. However you can also 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. Then the default starter kit report is an interesting source of inspiration for configuration objects. Content of tables: Briefing Books and Data providers Data providers are used to fetch the data from the data repository. They correspond to a selection of data in one of the workbooks that make up the data repository, called the Briefing Books. SAP Disclosure Management, starter kit for IFRS is delivered with a set of predefined data providers which allow you to fetch and format the relevant data depending on the table in the various chapters of the report. Each predefined data provider is associated with one of the starter kit formatting templates (see Report Layout below ). 16

17 Based on this association, the line items of the table are linked either to the default leaf-level formatting style or to one of the total-level formatting style provided with the starter kit. 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. 17

18 Text Styles, Headers and Footers SAP Disclosure Management, starter kit for IFRS 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. 18

19 Validation Dashboard The starter kit for IFRS 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-a-glance 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. 19

20 20-F Form 20-F Structure The starter kit includes a report whose chapters structure corresponds to the 20-F form as defined by the U.S. Securities and Exchange Commission. When designing your 20-F filing in SAP Disclosure Management, you can start from this report and import your Microsoft Word files into this structure. 20

21 20-F Heading Form In addition to the 20-F form structure, a generic 20-F heading form template is available including placeholders dedicated to the information related to your company. 21

22 IFRS-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 Presentation Linkbase File name* comp xsd comp _cal.xml comp _def.xml comp _lab.xml comp _pre.xml *For a company identified with comp and for 2011 year end According to this EFM rule, for example for 2011 year end, the XBRL instance that you will create with your own data - once substituted to the starter kit s data - 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 database. Therefore they are centralized as with any Microsoft Office file used in the data repository or the financial report. A specific XBRL taxonomytype report has been created for this purpose for both period samples: IFRS2012-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. 22

23 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 Financial Position, Current/Non-current Statement - Income Statement, by Function of Expense Statement - Statement of Comprehensive Income Statement - Consolidated Statement of Cash Flows, Indirect Method Statement - Consolidated Statement of Changes in Equity Disclosure - Note 1 - Corporate Information and Statement of IFRS Compliance Disclosure - Note 2 - Accounting Policies, Changes in Accounting Estimates and Errors Disclosure - Note 3 - Business Combinations Disclosure - Note 4 - Intangible Assets Disclosure - Note 5 - Property, Plants and Equipment Disclosure - Note 6 - Consolidated and Separate Financial Statements Disclosure - Note 2 - Accounting Policies, Changes in Accounting Estimates and Errors (Policies) Disclosure - Note 3 - Business Combinations (Tables) Disclosure - Note 4 - Intangible Assets (Tables) Disclosure - Note 5 - Property, Plants and Equipment (Tables) Disclosure - Note 6 - Consolidated and Separate Financial Statements (Tables) Disclosure - Note 3 - Business Combinations (Details) Disclosure - Note 4 - Intangible Assets (Details) Disclosure - Note 5 - Property, Plants and Equipment (Details) Disclosure - Note 6 - Consolidated and Separate Financial Statements (Details) Disclosure - Note 6 - Consolidated and Separate Financial Statements (Details 1) Disclosure - Note 6 - Consolidated and Separate Financial Statements (Details 2) Statement - Common domain members 23

24 The descriptions of these presentation groups abide by the EFM rule ({SortCode} - {Type} - {Title}). The first presentation group (00000) includes mandatory concepts required to file document and entity related information (DEI) as per EFM such as the document type, the document fiscal year focus and the entity registrant name. The following five presentation groups (00100 to 00500) correspond to the 5 publishable financial statements. The next two presentation groups provide you with simple examples of usual textual notes disclosures. Finally the last presentation groups are examples notes: breaking down the variations in balance sheet items, list of consolidated entities with respective consolidation scope-related information. Organizing Concepts: Presentation, Calculation, Definition The vast majority of concepts used in the taxonomy for the financial statements listed above are IFRS concepts imported from the IFRS taxonomy released by the IFRS Foundation ( 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 IFRS taxonomy. Example 1: Statement of Financial Position Presentation view Example 2: Statement of Cash Flows, Indirect Method Calculation view 24

25 Example 3: Statement of Changes in Equity Definition view Example 4: Note Changes in Property, Plants and Equipment Definition view Example 5: Statement of Comprehensive Income Presentation view A few extension concepts have been created and inserted in the Statement of Comprehensive Income hierarchy. This illustrates how the taxonomy can be customized by mixing custom concepts with standard concepts within the existing taxonomy hierarchies. 25

26 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). 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 IFRS 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: Adding you own lines in the financial statements, Renaming reports and periods, Creating your own new chapters, Updating the pre-delivered text styles, Extending the default taxonomy, and Inserting your logo. It is always easier and safer to adapt an existing tried-and-tested configuration than designing one from scratch. Take advantage of SAP Disclosure Management, Starter Kit for IFRS 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 IFRS Installation guide How-to Guide: How to Migrate XBRL Tagging to a Newer Taxonomy Version 28

29 29