1. XBRL Instance Documents

2.  Financial Information Reported  By a Specific Entity  For a Specific Period of Time  In a Specific Currency ▪ How precise is the currency being reported  What taxonomy schema is the element defined in

3.  Rules and Syntax for  XBRL Instance Documents  XBRL taxonomies ▪ Defines the elements and relationships for financial reporting concepts ▪ Taxonomy Schema for each specific reporting purpose ▪ Commercial & Industrial type company ▪ Banking type company ▪ … ▪ Linkbases ▪ Relationships between the elements 3

4.  Instance Document  Contains the data items which represent the financial data in financial reports ▪ Financial Statements ▪ Disclosures  Taxonomy  Defines elements and relationships ▪ Schema for a particular reporting group ▪ Banking & Savings ▪ Brokers & Dealers ▪ Commercial & Industrial ▪ Insurance ▪ Real Estate ▪ Linkbases ▪ Presentation, Calculation, Reference, Label & Dimension

5.  Schedule of Investments  Used to supplement investment holdings for unaffiliated investments  Industry Entry Points  Commercial and Industrial  Banking and Savings Institutions  Brokers and Dealers  Insurance  Real Estate 5

6.  Non-GAAP  Record of Credit Rating Taxonomy  U.S. Mutual Fund Risk/Return Taxonomy  Management Reports  Management Discussion and Analysis  Document and Entity Informaiton 6

7. Source:

8. 8

9.  Reference  relationships between elements and external regulations or standards  Label  elements are connected to human readable labels  Presentation  How elements appear  Calculation  How elements are used in calculations  Dimensions  How to create tables for footnote disclosures

10. Source: Charlie Hoffman, http://xbrl.squarespace.com/journal/2009/6/21/high-level-model-of-xbrl.html

11.  Attributes include:  What entity is the data for (contextRef)  What period of time is the data for (contextRef)  What currency is being reported (UnitRef)  What precision is the currency in (decimals)  Which taxonomy is the fact defined in (namespace prefix) 11

12. XBRL Element NameDefinitionCardinality xbrlAn XBRL instance documentRequired root element schemaRef Identifies an XBRL taxonomy schema & links it to this XBRL instance document1.. N context Establishes the "reporting context" of an XBRL instance document (a complex element)1.. N Must contain: id attribute (a unique identifier); entity (to identify the reporting entity); period (to identify the reporting period) unit Identifies the numerical unit of measure (e.g. USD) (a complex element)0.. N Must contain: id attribute (a unique identifier); measure (to identify the unit of measure) An XBRL itemAt least one reported XBRL item1.. N Must contain: contextRef attribute (to identify the context that applies to this item); For numeric items: unitRef attribute (to identify the unit of measure that applies to this item); decimals attribute (to designate the reporting precision that applies to this item) 12

13. 1. Root Element  NameSpace Declarations 2. References  Schema Declarations 3. Context  Who’s financial data  What Period 4. Unit  Currency  Shares 5. Items  Elements of the Financial Statement

14.  Element Name = xbrl  All namespace declarations  XBRL usually will contain many ▪ xmlns:us-gaap=“http://xbrl.fasb.org/us-gaap/2013” ▪ xmlns:link=“http://www.w3.org/2003/linkbase” ▪ xmlns:xbrli=“http://www.xbrl.org/2003/instance” ▪ xmlns:xlink=“http://www.w3.org/1999/xlink” ▪ xmlns:iso4217=“http://www.xbrl.org/2003/iso4217 “http://www.xbrl.org/2003/iso4217

15.  xbrli  Content and structure of XBRL instance  link  Content and structure of linkbases  iso4217  Standard currency codes  xlink  Xlink schema  US GAAP taxonomy 15

16.  Was maintained by XBRL-US organization  Now maintained by FASBFASB  Namespaces and Schema URI’s Namespaces and Schema URI 16

17.  Used to link a taxonomy schema to the instance document  Must be at least one Taxonomy Reference used to validate the Instance Document  First Child Element  schemaRef ▪ Attributes: ▪ xlink:type=“simple” ▪ xlink:href=“URI” 

18.  Element Name = Context  id attribute ▪ Used later to associate meta-data with financial reporting item ▪ Can be anything, but must start with a letter ▪ Like a namespace prefix  Complex element with 4 parent elements  Entity ▪ Uniquely identifies the entity  Period ▪ Instant ▪ Duration  Scenario ▪ What types of facts ▪ Actual, Restated, Budgeted, etc.  Segment ▪ Information about segment being reported

19.  Entity (Parent Element)  Identifier (Child Element)  (attribute) scheme ▪ Depends on reporting purpose ▪ SEC identifier, NYSE symbol, etc. SEC CIK id

20. 2007-11-06 or... 2007-01-01 2007-12-31 or... element can be used Must use yyyy-mm-dd format

21. Unit (Parent Element) id attribute Used as a reference Can be anything, usually logical & human readable Measure element (child element) Value describing unit of measure USD EUR JPY xbrli:shares

22.  Currency <xbrli:unit id=“USD” iso4217:USD  Shares xbrli:shares

23. iso4217:USD xbrli:shares 23

24.  Single Fact being reported  Element name comes from US GAAP taxonomy  Determine element names from viewerfrom viewer  Attributes  contextRef (points to context id for fact being reported)  unitRef (points to unit id for fact being reported)  decimals ▪ To how many decimal places is a fact accurate  or precision ▪ How many digits are significant  label ▪ How should element be named in report* *When doing homework for chapter 4 use the label attribute

25. in thousanddecimals="-3" in milliondecimals="-6" accurate valuedecimals="INF" or decimals="2" percentdecimals="2" Source: http://www.xbrlwiki.info/index.php?title=Best_Practices_on_Data_Definitions

26. ....

27. Source: Charlie Hoffman, http://xbrl.squarespace.com/journal/2009/6/ 22/xbrl-instance-graphic.html

28. 28

29.  Four Levels:  As of June 2013 all companies are required to include all 4 levels  Each Footnote disclosure is required to have a contextRef for the entire reporting period ( )  Level 1 ▪ Block Tagging ▪ Each complete footnote along with formatting is tagged within XBRL Instance  Level 2 ▪ Tag each accounting policy within the Significant Accounting Policies footnote, along with formatting  Level 3 ▪ Tag each table, along with its formatting  Level 4 ▪ Tag each monetary value, % and number in the footnotes. 29

30.   The rest of the footnote The rest of the footnote  This is what the footnote looks like This is what the footnote looks like 30

31.  Note 3:  Purchased goodwill related to the five acquisitions which closed in the first nine months of 2010 totaled $43 million, less than $1 million of which is deductible for tax purposes. The acquisition activity in the following table also includes the impacts of contingent consideration for pre-2009 acquisitions, which increased goodwill by $1 million. The amounts in the “Translation and other” column in the following table primarily relate to changes in foreign currency exchange rates. The goodwill balance by business segment as of December 31, 2009 and September 30, 2010, follow: 31

32.  Note 3:  Purchased goodwill related to the five acquisitions which closed in the first nine months of 2010 totaled $43 million, less than $1 million of which is deductible for tax purposes. The acquisition activity in the following table also includes the impacts of contingent consideration for pre-2009 acquisitions, which increased goodwill by $1 million. The amounts in the “Translation and other” column in the following table primarily relate to changes in foreign currency exchange rates. The goodwill balance by business segment as of December 31, 2009 and September 30, 2010, follow: 32

33. 43000000 1000000 33

34.  Goodwill table from footnote Goodwill table from footnote 34

35. 1783000000 1007000000 155000000 990000000 1220000000 677000000 35

36. 8000000 1000000 24000000 11000000 36

37. 15000000 -11000000 6000000 4000000 26000000 -17000000 37

38. 1806000000 997000000 185000000 994000000 1257000000 660000000 38

39.  SEC Requires filers to use an extension taxonomy  Includes only those elements that a company uses for their financial reporting  Naming Convention ▪ Shortcompnayname:ccyy-mm-dd

40.  Extending XBRL  New element names  Each Company has its preferred 1. Line Item Name 2. Hierarchy of line items on the F/S 3. Unique items that do not correspond to an element in the taxonomy  Items 1 & 2 do NOT impact comparability and reuse 40

41. 1. Follow U.S. GAAP taxonomy whenever possible 2. If you don’t see an element in the F/S section, look in the disclosures 3. If you don’t like the label, use the U.S. GAAP element anyway and add a label to the label linkbase (i.e. don’t make up elements because you don’t like the label) 4. For footnotes use proper tags for respective levels 41

42. Tutorial 42

43. Use to find element names to use for tagging data and disclosures There are 16,000+ elements! Financial Statement and Disclosures In choosing an element: Choose the element with the narrowest definition of the fact you are reporting If more than one element is available use the element that is part of the financial statement vs. a disclosure element If using a disclosure element, use software to move it as a financial statement line element. Types of elements: Abstract – do not use as a tag in instance doc. Financial Reporting Concepts  For each element (not abstract items)  Labels ▪ Standard ▪ Documentation ▪ Total  References ▪ To authoritative literature  Properties ▪ Element name ▪ Namespace ▪ Type (monetary, shares, etc.) ▪ Normal Balance (debit or credit) ▪ Time (instant or period)

44. 44

45. 45

46. 46

47. <reference xlink:type="resource" xlink:role="http://www.xbrl.org/2003/role/presentationRef" xlink:label="CashFlowsFromUsedInOperationsTotal_ref"> IAS 7 14 <reference xlink:type="resource" xlink:role="http://www.xbrl.org/2003/role/measurementRef" xlink:label="CashF lowsFromUsedInOperationsTotal_ref"> IAS 7 18 a

48. <label xlink:type="resource" xlink:role="http://www.xbrl.org/2003/role/label" xlink:label="ifrs_AssetsTotal_lbl" xml:lang="en">Assets, Total <label xlink:type="resource" xlink:role="http://www.xbrl.org/2003/role/label" xlink:label="ifrs_AssetsTotal_lbl" xml:lang="de">Vermögenswerte, Gesamt <label xlink:type="resource" xlink:role="http://www.xbrl.org/2003/role/label" xlink:label="ifrs_AssetsTotal_lbl" xml:lang="pl">Aktywa, Razem

49.  uses parent-child relations to organize elements  Assets  Current ▪ Cash ▪ Receivables ▪ Accounts ▪ Interest ▪ Inventory  Long-Term ▪ Property, Plant and Equipment ▪ Intangible Assets ▪ Notes Receivable  The “order” attribute of the presentationArc specifies the order in which child concepts should appear with respect to their sibling concepts.

50. http://snipr.com/lc15r [www_sec_gov]

51.  Gross Profit = Revenue – CGS Linkbase  Gross Profit Revenue (1) CGS (-1) Lower level elements sum up to or are subtracted from upper level elements

52.  weight is a required attribute on calculationArc elements; it must have a non-zero decimal value; for summation-item arcs, the weight attribute indicates the multiplier to be applied to a numeric item value (content) when accumulating numeric values from item elements to summation elements; a value of "1.0" means that 1.0 times the numeric value of the item is applied to the parent item; a weight of "-1.0" means that 1.0 times the numeric value is subtracted from the summation item; there are also rules that are applied to the calculation of elements possessing opposite balance attribute values ('credit' and 'debit');attributecalculationArcelements summation-itemarcsnumeric itemcontentbalance

53. <link:calculationArc order="6.0" weight="1.0" xlink:arcrole="http://www.xbrl.org/2003/arcrole/summation-item" xlink:from="lbl_AssetsCurrent" xlink:to="lbl_

54. Used to create tables Simple Pivot type Utilizes the Context element to define the table using: Segment element which defines: Axes Dimension Characteristics of a fact (e.g. deferred revenue from x) Domains Contains a set of members Members  Column Headers (horizontal axis) Line Items Row Header (vertical axis)