3. Recently Issued Accounting Standards
In June 2011, the Financial Accounting Standards Board (FASB) issued Accounting Standards Update (ASU) 2011-05, Presentation of Comprehensive Income, which improves the comparability, consistency, and transparency of financial reporting and increases the prominence of items reported in other comprehensive income (OCI) by eliminating the option to present components of OCI as part of the statement of changes in stockholders equity. The amendments included in this standard require that all nonowner changes in stockholders equity be presented either in a single continuous statement of comprehensive income or in two separate but consecutive statements. Under either method, an entity is required to present reclassification adjustments for items on the face of the financial statements. The Company adopted this updated guidance with no impact on its consolidated financial position or results of operations.
In May 2011, the FASB issued ASU 2011-04, Amendments to Achieve Common Fair Value Measurement and Disclosure Requirements in U.S. GAAP and IFRSs (ASU 2011-04), which amends current guidance to require common fair value measurement and disclosures between accounting principles generally accepted in the United States and International Financial Reporting Standards. The amendments explain how to measure fair value. They do not require additional fair value measurements and are not intended to establish valuation standards or affect valuation practices outside of financial reporting. The amendments change the wording used to describe fair value measurement requirements and disclosures, but often do not result in a change in the application of current guidance. The amendments in ASU 2011-04 are effective for interim and annual periods beginning after December 15, 2011. The company does not believe that the adoption of the provisions of ASU 2011-04 will have a material impact on the Companys consolidated financial position or results of operations.
In April 2010, the FASB issued ASU 2010-17, Revenue Recognition Milestone Method (ASU 2010-17). ASU 2010-17 provides guidance on the criteria that should be met for determining whether the milestone method of revenue recognition is appropriate. A vendor can recognize consideration that is contingent upon achievement of a milestone in its entirety as revenue in the period in which the milestone is achieved only if the milestone meets all criteria to be considered substantive: the following criteria must be met for a milestone to be considered substantive. The consideration earned by achieving the milestone should be: (1) commensurate with either the level of effort required to achieve the milestone or the enhancement of the value of the item delivered as a result of a specific outcome resulting from the vendors performance to achieve the milestone; (2) related solely to past performance and (3) reasonable relative to all deliverables and payment terms in the arrangement. No split of an individual milestone is allowed, and there can be more than one milestone in an arrangement. Accordingly, an arrangement may contain both substantive and non-substantive milestones. ASU 2010-17 is effective on a prospective basis for milestones achieved in fiscal years, and interim periods within those years, beginning on or after June 15, 2010. The Company adopted this updated guidance with no impact on its consolidated financial position or results of operations.
In September 2009, the FASB issued updated guidance of Accounting Standards Codification (ASC) 605, Revenue Recognition, for establishing the criteria for separating consideration in multiple element arrangements. The updated guidance is effective for fiscal years beginning on or after June 15, 2010 and requires companies allocating the overall consideration to each deliverable to use an estimated selling price of individual deliverables in the arrangement in the absence of vendor specific evidence or other third party evidence of the selling price for the deliverables. The updated guidance also provides additional factors that should be considered when determining whether software in a tangible product is essential to its functionality. The Company adopted this updated guidance with no impact on its consolidated financial position or results of operations.
|