30 August 2011

FAQs


XBRL is a language for the electronic communication of business and financial data which is revolutionising business reporting around the world. It provides major benefits in the preparation, analysis and communication of business information. It offers cost savings, greater efficiency and improved accuracy and reliability to all those involved in supplying or using financial data. It is an open standard, free of licence fees, being developed by a non-profit making international consortium. Other pages on this web site provide detailed information on XBRL, its technical features and its business opportunities.

TOP    
XBRL can be applied to a very wide range of business and financial data. Among other things, it can handle:-

  • Company internal and external financial reporting.
  • Business reporting to all types of regulators, including tax and financial authorities, central banks and governments.
  • Filing of loan reports and applications; credit risk assessments.
  • Exchange of information between government departments or between other institutions, such as central banks.
  • Authoritative accounting literature – providing a standard way of describing accounting documents provided by authoritative bodies.


TOP    
All types of organisations can use XBRL to save costs and improve efficiency in handling business and financial information. Because XBRL is extensible and flexible, it can be adapted to a wide variety of different requirements. All participants in the financial information supply chain can benefit, whether they are preparers, transmitters or users of business data.

TOP    
XBRL is set to become the standard way of recording, storing and transmitting business financial information. It is capable of use throughout the world, whatever the language of the country concerned, for a wide variety of business purposes. It will deliver major cost savings and gains in efficiency, improving processes in companies, governments and other organisations.

TOP    
XBRL is being developed by an international non-profit consortium of major companies, organisations and government agencies. These include the world’s leading accounting, technology, government and financial services bodies.

TOP    
XBRL increases the usability of financial statement information. The need to re-key financial data for analytical and other purposes can be eliminated. By presenting its statements in XBRL, a company can benefit investors and raise its profile. It will also meet the requirements of regulators, lenders and others consumers of financial information, who are increasingly demanding reporting in XBRL. This will improve business relations and lead to a range of benefits.

With full adoption of XBRL, companies can automate data collection. For example, data from different company divisions with different accounting systems can be assembled quickly, cheaply and efficiently. Once data is gathered in XBRL, different types of reports using varying subsets of the data can be produced with minimum effort. A company finance division, for example, could quickly and reliably generate internal management reports, financial statements for publication, tax and other regulatory filings, as well as credit reports for lenders. Not only can data handling be automated, removing time-consuming, error-prone processes, but the data can be checked by software for accuracy.

TOP    
  • XBRL-aware accounting software products are becoming available which will support the export of data in XBRL form. These tools allow users to map charts of accounts and other structures to XBRL tags.
  • Statements can be mapped into XBRL using XBRL software tools designed for this purpose.
  • Data from accounting databases can be extracted in XBRL format. It is not strictly necessary for an accounting software vendor to use XBRL; third party products can achieve the transformation of the data to XBRL.
  • Applications can transform data in particular formats into XBRL. For example, web sites are in operation that can transform filings into XBRL format

The route which an individual company may take will depend on its requirements and the accounting software and systems it currently uses, among other factors.

TOP    
Several software vendors are developing such tools in India and the companies are free to choose the one that suits them to create XBRL document.

TOP    
A core purpose of Accounting Institutes around the world is to enhance the access, quality and breadth of financial information available to the investing public. XBRL will help achieve this. Institutes also believe that the development of XBRL will help position their members as valued knowledge providers for their clients. Businesses, large and small, are undergoing fundamental change. Accountants, as the managers of the underlying language of business, can help organisations fit into the new digital world, solve business issues and capitilise on opportunities.

TOP    
No.   XBRL is simply a language for transmitting information. It must accurately reflect data reported under different standards – it does not change them.

TOP    
XBRL benefits comparability by helping to identify data which is genuinely alike and distinguishing information which is not comparable.

TOP    


Technical FAQs


The value of the xlink:href attribute in the schemaRef element in the instance document must be http://www.mca.gov.in/XBRL/2011/05/25/Taxonomy/CnI/ci/in-gaap-ci-2011-03-31.xsd.

TOP    
HTML (Hypertext Markup Language) is a standard way of marking up a document so it can be published on the World Wide Web and viewed in a browser. It provides a set of pre-defined tags describe on how content appears in a browser. For example, it describes the font and colour of text. It gives little information on meaning or context. XML (Extensible Markup Language) uses tags to identify the meaning, context and structure of data.

XML is a standard language which is maintained by the World Wide Web Consortium (W3C). XML does not replace HTML; it is a complementary format that is platform independent, allowing XML data to be rendered on any device such as a computer, cell phone, PDA or tablet device. It enables rich, structured data to be delivered in a standard, consistent way. Whereas HTML offers a fixed, pre-defined number of tags, XML neither defines nor limits tags. Instead, XML provides a framework for defining tags (i.e. taxonomy) and the relationship between them (i.e. schema).

XBRL is an XML-based schema that focuses specifically on the requirements of business reporting. XBRL builds upon XML, allowing accountants and regulatory bodies to identify items that are unique to the business reporting environment. The XBRL schema defines how to create XBRL documents and XBRL taxonomies, providing users with a set of business information tags that allows users to identify business information in a consistent way. XBRL is also extensible in that users are able to create their own XBRL taxonomies that define and describe tags unique to a given environment.

TOP    
Many of the pages constitute the XML Schemas defining XBRL, and the change log. In the remaining pages, there are many more examples, fragments included from the defining schemas, greater detail about pre-existing XBRL 2.0 features, and detailed explanations of the new features.

TOP    
There have always been restrictions on what is a meaningful taxonomy schema, meaningful linkbase, and meaningful instances. In the past many of these criteria were implicit; these criteria are now part of the specification. In some cases, they may be enforced using XML Schema, requiring no new code to be written, and in other cases the specification enables vendors to write correct validation code. Examples of these technical enhancements include: a detailed exposition of handling variable precision numbers, prohibitions on certain kinds of loops in relationships, and prohibition of duplicated data in instances. The meaning of calculation links and their ability to express relationships between items in different tuples has been specified precisely.

TOP    
Domain experts and application developers can now encode more precise information about financial reporting concepts in XBRL taxonomies. They can also define the handling of new relationships not defined by XBRL itself. New relationships allow taxonomy authors to connect taxonomy definitions to authoritative definitions and other supporting documentation.

TOP    
Yes, we expect taxonomy authors gradually to upgrade their taxonomies to 2.1. This is a prerequisite for conformance with the Financial Reporting Taxonomies Architecture (FRTA) 1.0. However, 2.0 versions of these taxonomies may also be made available at the discretion of the taxonomy authors.

TOP    
The conformance suite consists of over 250 example taxonomy fragments (XML Schema and XLink files) and instance documents, containing both valid and invalid usage. It will help application developers ensure their software processes XBRL correctly.

TOP    
The XBRL International Domain Working Group developed a detailed set of requirements which were then implemented by the XBRL International Specification Working Group.

TOP    
The XBRL 2.1 Conformance Suite is posted in a large (more than 5MB) zip file on the XBRL International web site, alongside the XBRL 2.1 specification. The Conformance Suite contains over 250 separate XBRL instances. Although the instances are small, there is a subset of them that are specifically designed to exercise each feature of an XBRL instance and their interactions.

TOP    
XBRL is a format for exchanging information between applications. Therefore each application will store data in whatever form is most effective for its own requirements and import and export information in XBRL format so that it can be readily imported or exported in turn by other applications. In some applications, for example, the XBRL formatted information being used may be mostly tabular numeric information, hence easily manipulated in a relational database. In other applications, the XBRL information may consist of narrative document-like structures with a lot of text, so that a native XML database may be more appropriate. There is no mandatory relationship between XBRL and any particular database or other processing or storage architecture.

TOP    


MCA Specific FAQs



XBRL instance document creation software has to be purchased from the software vendors in the market. This software is used to create XBRL instance documents that would be uploaded on the MCA portal. MCA21 system shall provide a facility for validation of the instance document and filing of the same. MCA is not recommending any specific XBRL software.

TOP    
ICAI, which is assisting MCA with conduct of XBRL training, has been instructed to develop standard Training module as well identify resource persons in consultation with XBRL training partners located at different parts on the country. It is proposed to engage leading chambers of industry and other professional institutes, namely, ICWAI and ICSI in future trainings. Training will be held over the next few months in most leading cities of India. Details of the same will be available on our website www.mca.gov.in/www.xbrl.icai.org.

TOP    
Existing Form 23AC and 23ACA shall continue to be there for filing by companies to which XBRL filing is not applicable; and for filing of earlier year’s documents.

TOP    
Kindly see the document ‘Steps for filing XBRL in MCA21.doc’ on the website.

TOP    
This shall be catered by the XBRL instance document creation software

TOP    
Subsidiary of listed company is required to file in XBRL format, irrespective of its paid up capital.

TOP    
XBRL is a collection of standardized, machine-readable “tags” for line items in financial statements, including footnotes and schedules. It is similar in concept to bar codes used to identify products. Using XBRL, each line in a financial statement is assigned a standardized data tag.
XBRL is a standards-based way to communicate business and financial information. These communications are defined by metadata set out in taxonomies. Taxonomies capture the definition of individual reporting concepts as well as the relationships between concepts and other semantic meaning.
The taxonomy comprises of the following components:-
  • Schema – Defines the elements used in the linkbases
  • Presentation linkbase – Which defines the structure for displaying the data, along with the preferred label attribute.
  • Calculation linkbase – Establishes the arithmetical relationship of simple addition and subtraction, which is done by way of a weight attribute (1 or -1)
  • Label linkbase – Stores the labels about the concepts (it is the human readable name of the element)
Kindly see relevant section on the website for more on XBRL.

TOP    
The XML and XSDs actually make the real taxonomy. The excel sheet is just for you to view it. An XBRL processor (a computer software that understands and/or manipulates XBRL documents) will need those XML and XSD documents.

TOP    
XBRL is a standards-based way to communicate business and financial information. These communications are defined by metadata set out in taxonomies. Taxonomies capture the definition of individual reporting concepts as well as the relationships between concepts and other semantic meaning.


Questions from Stakeholders


The companies whose Balance Sheet date is 31.03.2011 or onwards, need to file their financial statements in XBRL provided they qualify the criteria laid as per Ministry’s general Circular 37/2011 dated 07.06.2011.

TOP    
The holding company has to file consolidated financial statement in XBRL. Its subsidiaries also need to file their financials in XBRL.

TOP    
If the Subsidiary company meets the criteria of phase-I category of companies, they have to file in the XBRL mode.

TOP    
Yes encouraged, such a company need not file the Financial Statements in PDF Format.

TOP    
All such companies, whose financial statements are generated as per accounting requirements other than Schedule VI of the Company Act, 1956 have been exempted from XBRL filing for year 2010-11. The companies regulated by any other act like Electricity Act, 2003, Banking Regulation Act, 1949, Insurance Act, etc are exempted from XBRL filing in the Phase-I filings. Similarly, companies registered as a NBFC have been exempted from XBRL filing for year 2010-11.

TOP    
The certification of XBRL filing would be done by the professional as before. The professional may use XBRL viewer tool to satisfy himself about the authenticity of XBRL document as per the audited financial statements.

TOP    
Yes, all the subsidiaries (including subsidiary of a subsidiary of a listed company) of a listed company in India need to file their financial statements in XBRL this year.

TOP    
Applicability of XBRL filing would as under



TAXONOMY



Scope and Level of Tagging


Instance Document

An XBRL instance document is a business report in an electronic format created according to the rules of XBRL. It contains facts that are defined by the elements in the taxonomy it refers to, together with their values and an explanation of the context in which they are placed. XBRL Instances contain the reported data with their values and “contexts”. Instance document must be linked to at least one taxonomy, which defines the contexts, labels or references.
Tag
The elements as defined in taxonomy are also referred as XBRL tags or only tags. E.g. SourcesOfFunds, InterestCharges etc. Mark-up languages such as XBRL and XML use tags to describe data, for example 1000 – the word Asset together with the brackets < and > is called a tag; there are opening tags: <…> and closing tags: .
Fact
The values included in the instance document, which correspond to the concepts included in the taxonomy, are called as facts. These facts can either be numeric (monetary, shares or other numeric information) or non-numeric (string, date or text block). E.g.

ConceptFact
Intangible Assets100000
Name of subsidiarySample company ltd.
Date of board meeting2011-04-30
Earnings per share2.33


Context
The reporting period, information about reporting entity and other information which is required to uniquely identify any fact value is considered as context. It documents the entity, the period and the scenario that collectively give the appropriate context for understanding the values of items. Context ids have to be created based on the rules specified in the filing manual.
Scheme
The criteria used for recognizing the entity, which is unique and accepted to the authority to which the instance is to be submitted. Companies filing to MCA have to follow the scheme as mentioned in the filing manual.
Decimals attribute
This attribute is to be defined for numeric items in the instance document. It specifies the number of decimal places to which the value of the fact represented may be considered accurate, possibly as a result of rounding or truncations; it shall be an integer or possess the value INF meaning that the number expressed is the exact value of the fact.
Unit element
An element that appears in instance documents and specifies the units in which numeric items (that refer to its required ID attribute using a unitRef attribute) have been measured; it may define simple units using a measure element and complex units providing divide element and its sub-elements (unitNumerator and unitDenominator); there are several constraints imposed on this element, its children and their content; for example monetary concepts shall refer to ISO 4217 currency codes.
Footnote
Appears in instance documents and provides additional information about facts; for example, several facts may be linked to the sentence Including the effect of merger with Sample Company; to express these connections XBRL utilises a footnoteLink extended link element; footnoteLinks act as a kind of linkbase and enclose locators to the instance documents’ facts; footnotes use footnoteArcs with an arcrole value set to connect facts to additional information.
 

Tagging


MCA Taxonomy
The taxonomy developed by the MCA. The taxonomy is based on Schedule VI requirements, Accounting Standards issued by ICAI, MCA specific requirements and other regulatory requirements. . The current version of taxonomy is for Commercial and Industrial companies. The details of MCA taxonomy and the entry-point are explained in the taxonomy section of the filing manual.
Line items
The concepts as reported by the company in its reports are also referred as line items.
Tagging
It is the process of assigning tags (referred as elements in taxonomy) from the taxonomy to the company specific reporting concepts. Along with XBRL tags, other information like reporting period, currency, scale etc. also needs to be specified for all the reported concepts which are to be included in the taxonomy. Tagging required appropriate selection of elements from the taxonomy based on its attributes, documentation and relationships with other elements.
Text Block Tagging
This indicates capturing a group of information as one single fact, using one single tag from the taxonomy. Presently, information given in Notes to Accounts which appear in many paragraphs will be tagged completely under the data type Text Block.
Detailed tagging
This implies capturing the granular information or the specific information as reported by the companies. The filing manual lists down all the information requirements which have to be tagged and captured in detail in the instance documents. This information should be captured by entities, if it is applicable to them and prepared by them as part of annual report or annual returns as submitted to MCA
Minimum tagging requirement
The scope of information that is at least to be captured in XBRL format in the instance document. The information prescribed as minimum tagging requirement in this filing manual, should be captured by entities, if it is applicable to them and prepared by them as part of annual report or annual returns as submitted to MCA
Mandatory tags
The tags as included in the MCA taxonomy, for which values have to be necessarily included in the instance document. If there is no corresponding value for the tag, then “0” should be entered.
Calculation inconsistency error
The taxonomy has predefined mathematical rules between accounting concepts, which is stored in calculation linkbase. The values which are included in instance documents are checked for correctness based on the rules defined in calculation relationship. If the values for totals and sub-totals do not match as per calculation linkbase, the XBRL software will highlight the same as calculation inconsistency
 

Glossary


Taxonomy
Taxonomy in general means a catalogue or set of rules for classification; in XBRL, taxonomy can be referred as an electronic dictionary of the reporting concepts containing computer-readable definitions of business reporting terms as well relationships between them and links connecting them to resources. A typical taxonomy consists of a schema (or schemas) and linkbases;
Schema
XBRL Schemas together with linkbases define XBRL taxonomy. The purpose of XBRL schemas is to define financial and accounting concepts in system understandable manner. Each concept is given a unique name and its characteristics are defined. Schema also binds together the different parts of taxonomy.
DTS
Discoverable taxonomy set (DTS) is a collection of taxonomy schema documents and linkbases. The DTS includes all taxonomy schemas and linkbases that can be discovered by following links or references in the taxonomy schemas and linkbases included in the DTS.
Entry point
A DTS contains many schema and linkbase documents A schema which imports the base (or as required) schema and necessary linkbases, is called entry-point. Entry-point schema is usually used to browse or view the taxonomy.
Namespace
An XML namespace is a collection of names, defined as a uniform resource identifier (URI) and gives information regarding the ownership and or location of the taxonomy. The namespace for taxonomy usually contains the authority defining the taxonomy, date of taxonomy, in the form of web URL. The namespace specification however does not require nor suggest that the namespace URI be used to retrieve information; it is simply treated by an XML parser as a string.
Prefix
When declaring namespaces, a short name to identify the namespace is also defined and this is called as prefix. The schema components are associated with prefix belonging to that namespace. Prefixes precede names of elements, attributes and some of their predefined values provide an indication of where to find definitions of these properties.
Elements
An element is a business or a financial concept which is defined in the taxonomy according to XBRL specifications. Each element has a type, is identified by name and may have a set of attribute specifications as per the XBRL standards.
Abstract attribute
An abstract attribute appears on item definitions in schemas and the possible values are true and false; true indicates that the item shall not appear in instance documents, while false indicates that the concepts will hold value. Abstract elements (elements with abstract as true) are defined to bind concepts in a hierarchical manner in the taxonomy.
Data type attribute
This attribute indicates the data expected for concepts. Most common data types are monetary, shares, string etc. In addition, taxonomy developers may create their own data types to represent the information in a more efficient manner. Brief explanation of data types used in MCA taxonomy
  • monetaryItem Type
  • This data type is used for all the financial concepts which denote an amount represented in a currency; an instance document when uses an element with monetaryItem data type, the user need to define the unit reference ( currency unit) in which the content is measured. Eg. Accumulated depreciation, Total income etc.
  • sharesItem Type This data type is used for financial concepts which are measured in shares. Eg. Number of shares authorized shares etc.
  • stringItem Type This data type is used for concepts which contain textual information. Eg. Name of subsidiary, Accounting Policy changes etc.
  • PerShareItem Type This data type is used for concepts which are measured in per share. The unit reference in instance document needs the mentioning of currency as numerator and share as denominator. So the final value of measurement may come out as USD per share or Rupee per share. E.g. Earnings per share.
  • percentItem Type This data type is used for concepts that are denoted as percentage. Eg. Percentage of shares held by government
  • PureItem Type This data type is used for financial concepts that are denoted as ratio or proportions. Eg. Proportion Of Voting Power In Subsidiary
  • decimalItem Type This data type is used for concepts which are generally represent any kind of number other than mentioned above Eg. Number of debentures
  • Text blockItem Type This data type is used for concept which would describe a block of information. Usually for capturing a paragraph or notes which contain both textual and numerical information, this data type is used. Eg. Disclosure of Contingent Liabilities
  • DateItem Type This data type is used for concepts which represent date. E.g. Date of Board meeting
  • MCA specific data types

    Data typeAttribute
    CINNumberItemTypeMaximum length 21 characters. If there is fixed pattern, the same can also be incorporated
    SRNNumberItemTypeLength 9 characters. 
    Pattern : first character is alphabet, and remaining 8 are numbers
    DINNumberItemTypeLength 8 characters. 
    All numbers
    NatureOfReportEnumerations : Standalone, Consolidated
    ContentOfReportEnumerations : Balance Sheet, Profit and Loss Statement
    LevelOfRoundingEnumerations : Actual, Thousands, Lakhs, Millions, Crores, Billions
    IndustryTypeEnumerations : Commercial and Industrial, Bank, NBFC, Power
    CountryNamePattern : Should be as per ISO 3166-1 format
    TypeOfSubsidiaryEnumerations : Section 4(1)(a), Section 4(1)(b), Section 4(1)c, Section 4(6), (Section 4(7)
    TypeOfBalanceSheetEnumerations : Sources and application, total assets and liabilities format
    TypeOfIncomeStatementEnumerations : Main, Alternative
    TypeOfCashFlowStatementEnumerations : Direct Method, Indirect Method
    ShareTypeEnumerations : Equity, Preference

SubstitutionGroup attribute
Appears on element definitions in schemas; XBRL defines four basic substitution groups, items , tuples, dimensions ( axes) and hypercubes ( tables); its purpose is to indicate which type can be substituted for the actual definition. The following substitution groups are used in MCA taxonomy
  • Item
    Item is an element used to define a concept which will hold single value in the given period. Most of the concepts represent one value in one period, and hence are defined as items. E.g. Total assets, depreciation etc.
  • Tuple
    Concepts which can have multiple values for the same period or if elements are required together to make the information more meaningful and complete, the substitution group is defined as tuple. E.g. Subsidiary information – there would be multiple values for name, shares held for any given period.
PeriodType attribute
It is used to describe the measurement period of the concept and may be assigned one of two values – instant and duration. Instant indicates that the concepts are measured as at a particular date, while duration indicates concepts hold value for a period.
Extended link element (also referred to as ELR)
These are logical grouping of elements. Extended links represent a set of relationships between concepts and are defined in schema. The extended links are then used in linkbases to build the relationships. Extended links contain locators, arcs, arcroles and resources
Linkbase
XBRL linkbases and XBRL Schemas define together XBRL taxonomy. Schema defines the core elements and its characteristics, while the purpose of XBRL linkbases is to combine labels and references to the concepts as well as define relationships between those concepts. There are various types of linkbases different kinds of linkbases and each has a special purpose.
Locator
It provides a reference to the taxonomy schema element definitions that uniquely identify each concept; they provide an anchor for extended link arcs.
Arc
Arc are used to connect two or more locators. According to the XBRL Specification 2.1, arcs link concepts to each other by associating their locators; they also link concepts with resources by linking the concept locators to the resources themselves; arcs are also used to link fact locators to footnote resources in footnote extended links; arcs have a set of attributes that document the nature of the expressed relationships; in particular they posses attributes: type (whose value shall be arc), from, to and arcrole.
Arcrole attribute
It defines the use of arc. It documents the kind of relationship that the arc expresses; there is a set of standard arcroles defined for specific arcs (labelArc, referenceArc, calculationArc; definitionArc, presentationArc and footnoteArc); the value of arcrole shall be an absolute URI, (eg in the presentation linkbase on a presentationArc it is ).
Presentation linkbase
Business reports are in general organized into identifiable data structures e.g. a Balance Sheet. The presentation linkbase stores information about relationships between elements in order to properly organize the taxonomy content. The arcrole used in presentation linkbase is .
Order Attribute
This attribute is defined on arcs and used to determine the sequence of relationship. In presentation linkbase, it is of prime importance as the display of elements will be based on the order as defined for every element.
Calculation linkbase
The idea of a calculation linkbase is to improve quality of an XBRL report (XBRL instance). The calculation linkbase defines basic calculation validation rules (addition/subtraction), which must apply for all instances of the taxonomy. The arcrole for calculation relationships. It represents relationships between concepts that are of numeric nature and have similar period type. The weight attribute defines the algebraic sign of the operation.
Weight attribute
A required attribute on calculationArc elements and 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).
Definition linkbase
The definition linkbase stores other pre-defined or self-defined relationships between elements. For example a relationship can be defined that the occurrence of one concept within an XBRL instance mandates the occurrence of other concepts, or relationships describing elements of general nature and elements which are very specific or elements which can be categorized based on parameters etc.
Label linkbase
The goal of the XBRL Consortium is to create and develop a world-wide standard for electronic business reporting. This requires the taxonomies to represent business data in multiple language. Therefore it is possible to create an element (concept) in the taxonomy with labels in different languages and or for different purposes e.g. a short label PPE compared to its long label Property, plant and equipment. Those labels are stored and linked to their respective elements in a label linkbase.
Reference linkbase
Most of the elements appearing in taxonomies refer to particular concepts defined by authoritative literature. The reference linkbase stores the relationships between elements and the references e.g. Schedule VI, Part A or Accounting standard 23, para 2 etc. . The layer does not store the regulations themselves but the source identification names and paragraphs.
Formula linkbase
A formula is a specification is that is being developed by XBRL International; it aims to satisfy the formula linkbase requirements document by providing a generalised mechanism to build formulae based on XBRL concepts and XBRL dimensions; formulae can be used to describe business rules for creating new XBRL facts in new instance documents and for describing consistency checks for instance documents.


Specification


XBRL Specification
It defines the rules and fundamentals of the language; it is designed to communicate information to IT professionals who develop applications and tools intended to be XBRL-compatible, and to a lesser extent it assists taxonomy developers.
To find out more and obtain the latest version of the XBRL Specification 2.1 visit the XBRL International website (http://www.xbrl.org).
FRTA
Financial Reporting Taxonomy Architecture; it is a document published by the XBRL International Consortium that recommends architectural rules and establishes conventions that assist in the comprehension, usage and performance of different financial reporting taxonomies; it is mainly intended for application by public taxonomy developers (authorities).
FRIS
Financial Reporting Instance Standards; it is a document published by the XBRL International Consortium that recommends the rules and conventions for creating an instance document
 
 

XBRL Filing Manual


Filing Manual

Steps for filing financial statements in XBRL form in MCA21 system
Step 1 – Creation of XBRL instance document:



A. Map company’s each financial statement element to a corresponding element in published taxonomy
Companies have the option to create their own XBRL documents in house or to engage a third party to convert their financial statements into XBRL form.
The first step in creation of an instance document is to do tagging of the XBRL taxonomy elements with the various accounting heads in the books of accounts of the company. This would create the mapping of the taxonomy elements with the accounting heads so that the accounting information can be converted into XBRL form.
Mapping is the process of comparing the concepts in the financial statements to the elements in the published taxonomy, assigning a taxonomy element to each financial statement concept.
Selecting the appropriate elements for some financial statement elements may require a significant amount of judgment. For that reason those in the company who are most familiar with the financial statements should be involved in matching financial statements concepts to taxonomy elements. The mapping should be reviewed before proceeding further as the complete reporting would be dependant on the mapping.
B. Create instance document for Balance sheet and Profit and loss Account-
Once the tagging of financial statement elements with the published taxonomy elements is done, the next step is to create the instance document. An instance document is a XML file that contains business reporting information and represents a collection of financial facts and report-specific information using tags from the XBRL taxonomy.
It is to be noted that no extensions to the core Taxonomy will be allowed.
Separate instance documents need to be created for the following:
(i) Stand Alone Balance sheet of the company
(ii) Stand Alone Profit and Loss Account of the company
(iii) Consolidated Balance sheet of the company
(iv) Consolidated Profit and Loss Account of the company
The instance document should contain the financial information for both the current as well as the previous financial year.
Consolidated balance sheet and Profit and Loss instance documents to be created only in case the same is applicable to the company.
The following are the specifications to be followed while preparing the instance document –
  1. The value of the xlink:href attribute in the schemaRef element in the instance document must be http://www.mca.gov.in/XBRL/2011/05/25/Taxonomy/CnI/ci/in-gaap-ci-2011-03-31.xsd.
  2. An XBRL instance document must be schema valid according to all schemas in the DTS(Discoverable Taxonomy Set)
  3. The value of the scheme attribute of the identity element in the context must be http://www.mca.gov.in/CIN
  4. The value of identity element in the context must all be x-equal and must be the CIN of the company.
  5. Context must not have segment or scenario element present
  6. An instance must not contain duplicate xbrli:context elements.
  7. Every xbrli:context element must appear in at least one contextRef attribute in the same instance.
  8. An instance must not have more than one fact having the same element name and equal contextRef attributes
  9. All monetary facts must have the same unitRef attribute.
  10. The facts corresponding to a single concept must not have contextRef attributes pointing to contexts with overlapping time period. In case of periodType=”instant”, it means to have same date, and in case of periodType=”duration”, it means to have a duration that overlap. For example: The following contexts have overlapping duration, this would not be allowed.
    <xbrli:context id=”D2010″>
            <xbrli:entity>
                <xbrli:identifier scheme="http://www.mca.gov.in/CIN">
                    L24223MH1946PLC005434
                </xbrli:identifier>
            </xbrli:entity>
            <xbrli:period>
                <xbrli:startDate>2009-04-01</xbrli:startDate>
                <xbrli:endDate>2010-03-31</xbrli:endDate>
            </xbrli:period>
    </xbrli:context>
    <xbrli:context id=”I2010″>
            <xbrli:entity>
                    <xbrli:identifier scheme="http://www.mca.gov.in/CIN">
                        L24223MH1946PLC005434
                    </xbrli:identifier>
            </xbrli:entity>
            <xbrli:period>
                <xbrli:startDate>2009-08-01</xbrli:startDate>
                <xbrli:endDate>2010-07-31</xbrli:endDate>
            </xbrli:period>
            </xbrli:context>
            </xbrli:period>
    </xbrli:context>
  11. A link:footnoteLink element must have no children other than link:loc, link:footnote, and link:footnoteArc.
  12. A link:footnoteLink link:loc xlink:href attribute must start with the sharp sign “#”.
  13. Every nonempty link:footnote element must be linked to at least one fact
  14. Non significant digits for values for numeric facts MUST be equal to “0″.
  15. An instance document must not contain unused units
  16. If the unescaped content of a fact with base type nonnum:escapedItemType contains the “<” character followed by a QName and whitespace, “/>” or “>”, then the un-escaped content must contain only a sequence of text and XML nodes.
  17. The value of a fact must be in plain text. HTML/RTF are not allowed
  18. A fact is defined to have a footnote if it has an id attribute and a link:footnoteArc to a nonempty link:footnote in the same instance.
  19. The filing is required to reference certain recognized schemas and linkbase. Filings must always refer to recognized files at the specified URI locations. A reference to a local copy will not be allowed.
  20. In an instance, the sub-elements of a tuple must have the contextRef attribute with values x-equal to each other.
  21. The xsi:nil=”true” attribute must be used only to convey a value that is different from both “zero” and different from not reporting the fact at all, or to identify a fact detailed only by a link:footnote.
  22. The value of the decimals/precision attribute of a fact must correspond to the accuracy of the corresponding amount as reported in the financial statements.
  23. The content of a numeric fact never has a scale factor
  24. When choosing the most appropriate element for facts in one or more periods, the element’s xbrli:periodType attribute takes precedence over the type attribute, which takes precedence over the element’s documentation string, which in turn takes precedence over the label string, which in turn takes precedence over link:reference elements.
  25. Do not define or use units that imply a scale factor on a currency.
  26. Text that is shown in the financial statements at the bottom of a page or at the bottom of a table preceded by a superscript must appear in the instance as the text of a link:footnote element.
  27. Each unit should appear with only one scale factor in a given instance.
  28. Every numeric fact (such as ‘Number of shares’) must also have an associated unit (e.g. xbrli:shares) and the unit must be declared.
  29. XBRL document names must be unique in the disclosure system
  30. Filers must use one of the taxonomies as specified in the disclosure system as their standard taxonomy.
  31. Encoding of all XBRL documents must be “UTF8“
  32. The xbrli:xbrl element must not have any facts with the precision attribute.
  33. Priority for selection of element must be in following order, Period type, data type, documentation, label and reference.
C. Review and verify the instance document
Once the instance document is prepared, it needs to be ensured that the instance document is a valid instance document and all the information has been correctly captured in the instance document.
Step 2 – Download XBRL validation tool from MCA portal
There shall be a tool provided at the MCA portal for validating the generated XBRL instance document. Validating the instance document is a pre requisite before filing the balance sheet and profit & loss account on MCA portal. You are required to download the tool from the MCA website and validate the instance document before uploading. There shall also be a facility to view and search the taxonomy.
Step 3 – Use the tool to validate the instance document
Once the tool has been downloaded, the next step is to validate the instance document. The following validations shall be performed by the tool-
  • Validating that the instance document is as per the latest and correct version of taxonomy prescribed by MCA
  • All mandatory elements have been entered
  • Other validations as per taxonomy
Step 4: Perform pre-scrutiny of the validated instance document through the tool
Once the instance document is successfully validated from the tool, the next step is to pre-scrutinise the validated instance document with the help of the same tool. For pre-scrutinizing the instance document, a working internet connection shall be required. In the Pre-scrutiny, the server side validations (i.e. validations which are to be validated from the MCA21 system) shall be performed.
Also, there shall be a feature provided in the tool to verify the appearance of the generated XBRL instance document using the built in Viewer. It is imperative that the company should use this feature to verify the accuracy of the instance document.
Step 5: Attach instance document to the Form 23AC and Form 23ACA
There shall be a separate set of Form 23AC and Form 23ACA available on the MCA portal for filing in XBRL form. First fill up the Form 23AC and Form 23ACA. Thereafter, attach the validated and pre-scrutinised instance document for Balance sheet to Form 23AC. Similarly, the instance document for Profit and Loss account is to be attached to Form 23ACA. Separate instance documents need to be attached w.r.t. Standalone financial statements and consolidated financial statements.
Step 6: Submitting the Form 23ACA and Form 23ACA on the MCA portal
After the forms are filled, you are required to perform pre-scrutiny of the form, sign the form and then upload the same as per the normal eForm filing process. It shall be validated that the attached instance documents are validated and pre-scrutinised from the XBRL validation tool.
Viewing of balance sheet and profit and loss submitted in XBRL form on MCA portal: The XBRL instance documents submitted along with Form 23AC and 23ACA are in machine readable format. Therefore, for viewing the same in a human readable format, these shall be converted into human readable format by the MCA21 system. For viewing the same on MCA21 portal and for taking certified copies of the same, these converted documents shall be made available.