Xbrl assurance

2012 © NextGen Knowledge Solutions Private Ltd.

XBRL & Financial Reporting

Risks in XBRL Environment

Internal Controls

Assurance over XBRL Instance Document

Q & A

2

2012 © NextGen Knowledge Solutions Private Ltd. 3


4

The computer language for the electronic communication of internal and external business report information

International supply chain standardization effort backed by over 1000+ being adopted by regulators/companies across the world

Cross-platform, software-agonistic, Internet-friendly global standard based on XML (eXtensible Mark-up Language)

Improves data accuracy by reducing manual efforts and subjectivity

Available to all type of business information: Financial, Non-financial, rules, formulas, summarized, detailed

<in-gaap:Inventories =”contextRef=I2012” unitRef =“INR” decimal=“0”>6,12,962<in-gaap:Inventories>

Balance Sheet (Audited)

March 31, 2012 (Rs.)

March 31, 2011 (Rs.)

Inventories 6,12,962 5,57,111

Trade Receivables 4,49,173 3,77,347


Balance Sheet

(Audited) March 31, 2012

(Rs. in Thousands) March 31, 2011

(Rs. in Thousands)

Inventories 612 557

Trade Receivables 449 377

Numeric Unit INR

Time Period March 31, 2012

Accounting Concept Inventories

Accounting Standard Indian GAAP

Precision Thousands

Label Inventories

Indian GAAP Taxonomy

Commercial & Industrial <in-gaap: Inventories contextRef=I2012” unitRef

=“INR” decimal=“-3”>612000<in-gaap: Inventories>


Mapping • Identify base taxonomy.

• Map financial facts to XBRL elements.

• Identify financials facts that do not match to base taxonomy elements.

From Traditional Financial Reporting

Process

Tagging • Create an instance document by:

associating the fact values being reported in a given filing with specific elements in the taxonomies.

defining periods, units of measures, and other aspects specific to that report.

Reviewing Validate the instance document against the

regulatory requirements.

Rendering the instance document.

6





XBRL Format Machine Readable

Traditional Format Human Readable


Potential to replace traditional format and electronic version (PDF &

HTML) of financial statements

Attestation of financial statements doesn’t apply to XBRL Reports

Misconception about XBRL

Auditor’s Conservatism

XBRL is a new risk

Challenges in audit of XBRL: Resources, Software & Standards

11


Audit and Examination Engagements - Reasonable Reliance

Review Engagements – Limited Reliance

Agreed-upon-procedures (AUP) – No Reliance

12


AICPA – "Performing Agreed Upon Procedures Engagements That

Address The Completeness, Accuracy, or Consistency of XBRL Tagged

Data“

AICPA – “Principles and Criteria for XBRL Formatted Information”

ICAEW – "Guidance For Performing Agreed Upon Procedures That

Address XBRL Tagged Data Included Within Financial Statements

Prepared in iXBRL Format"

JICPA – "Agreed Upon Procedures Engagements of XBRL Data"

ICAI – "Guidance Note on Certification of XBRL Financial Statements"

13



Information on Identity of reporting entity

Nature of financial data

Information on reporting period

Currency

Precision or Scaling

Segment information

15


Technical reference information

Base reference information

XBRL Validation

Selection of wrong tags

Reporting wrong data

Failing to mark-up a concept

16


Closed taxonomy risks

Accuracy of data

Alterations in taxonomy

Taxonomy version

17


Open taxonomy risks

Duplicate taxonomy element

Taxonomy elements not making true representation

Misleading Labels

Extensions not compliant with XBRL specifications

Prohibited names

18



Source : ISACA, COBIT 4.1, USA, 2007


Completeness

Mapping

- Identification of base taxonomy - Mapping of facts with taxonomy elements - Mapping of facts with residuary tags

21

Tagging

Reviewing

- Defining Contexts - Associating fact values with specific taxonomy elements

- Validation for Technical Specifications - Validation on regulator’s Validation Tool - Rendering



Completeness

Mapping

Accuracy

Structure

23

Source : ICAI Guidance Note


All required information & data as required by the entity’s reporting requirement is formatted in the XBRL Instance Document & is complete in all respect

Completeness

Solution Requirements

Mapping

Accuracy

Structure

24

All facts that are required to be formatted are formatted

Existence of facts or presentation or calculation relationships in source

documents

Other required information


Completeness Solution Requirements

Mapping

Mapping

Structure

The elements Viz. : line items, domain members & axis selected in the XBRL file are consistent with the associated concepts in the source document

25

Taxonomy referenced in the Instance document is correct

Element Attributes are consistent with source information

Selected element is consistent with the concept in source information

Most specific element is used for Other required information

Same element is used for facts appearing multiple times

Same element is used for each period

New element is created only when no suitable element exist in

taxonomy


Completeness

Mapping

Accuracy

Structure

The amount, date & other attributes e.g. monetary units are consistent with the source information

26

Contextual information is consistent with the source information

- Reporting Period

- Decimal Values

- Units

- Entity Identifier

Formatted amounts have appropriate sign

Rendered text block information is consistent with source information


Completeness

Mapping

Accuracy

Structure


27

Labels are consistent with the captions in the source information

Calculations reflected in the source information are included in

Calculation Linkbase

All formatted data is consistent with the underlying source information

Extension elements for accounting concepts with debit or credit balance

include balance attribute


Completeness

Mapping

Accuracy

Structure


28

Extension elements for currency amounts for non-accounting concepts

include :-

(i) a debit or credit balance attribute; or

(ii) a documentation label for meaning of positive or negative value


Completeness

Structure XBRL files are structured in accordance with the requirements of the entity’s reporting environment

29

All information is organized using required presentation groupings

Entity Identifier & Scheme for each context is identical

Instance document should pass Validation Test on regulator’s Validation

Tool e.g. MCA Validation Tool

New Table structure are only created when no suitable table structure

exists in standard taxonomy

Name of extension elements do not contain prohibited information


Practitioners' Independence

Management Assertions

Agreement on Procedures

Responsibility for sufficiency of procedures

Criteria for determination of findings

Evidential matter

Materiality limit

Restriction on use of report

30




"The focal point of XBRL Assurance is the evaluation of the accuracy

and validity of the XBRL tags applied to the line items in the financial

statements of reporting entity. In order to perform these evaluation,

the auditor needs to have the knowledge of what constitutes an error,

what is the risk in XBRL Instance document, how control tests &

substantive tests should be applied in XBRL environment and how

materiality should be conceived and applied to XBRL Instance

document."

33


“No matter how complex things are,

basically everything is simple.”

34


Vinod Kashyap

[email protected]

http://www.nextgenknowledge.com

NextGen Knowledge Solutions Private Ltd.

http://www.br-ag.eu/

Economy & Finance

Xbrl assurance