Significant Accounting Policies

9 Months Ended

Sep. 30, 2012

Significant Accounting Policies [Abstract]

SIGNIFICANT ACCOUNTING POLICIES

1. SIGNIFICANT ACCOUNTING POLICIES

Description of Business

Immersion Corporation (the “Company”) was incorporated in 1993 in California and reincorporated in Delaware in 1999 and develops, manufactures, licenses, and supports a wide range of hardware and software technologies and products that enhance digital devices with touch interaction.

Principles of Consolidation and Basis of Presentation

The condensed consolidated financial statements include the accounts of Immersion Corporation and its wholly-owned subsidiaries: Immersion Canada Inc.; Immersion International, LLC; Immersion Medical, Inc.; Immersion Japan K.K.; Immersion Ltd.; Immersion Software Ireland Ltd.; and Haptify, Inc. All intercompany accounts, transactions, and balances have been eliminated in consolidation.

The accompanying condensed consolidated financial statements have been prepared in accordance with accounting principles generally accepted in the United States of America (“GAAP”) for interim financial information and with the instructions for Form 10-Q and Article 10 of Regulation S-X and, therefore, do not include all information and footnotes necessary for a complete presentation of the financial position, results of operations, and cash flows, in conformity with GAAP. These condensed consolidated financial statements should be read in conjunction with the Company’s audited consolidated financial statements included in the Company’s Annual Report on Form 10-K, for the fiscal year ended December 31, 2011. In the opinion of management, all adjustments consisting of only normal and recurring items necessary for the fair presentation of the financial position and results of operations for the interim periods presented have been included.

The results of operations for the interim periods ended September 30, 2012 are not necessarily indicative of the results to be expected for the full year.

Revenue Recognition

The Company recognizes revenues in accordance with applicable accounting standards, including Accounting Standards Codification (“ASC”) 605-10-S99, “Revenue Recognition” (“ASC 605-10-S99”); ASC 605-25, “Multiple Element Arrangements” (“ASC 605-25”); and ASC 985-605, “Software-Revenue Recognition” (“ASC 985-605”). The Company derives its revenues from three principal sources: royalty and license fees, product sales, and development contracts. As described below, management judgments and estimates must be made and used in connection with the revenue recognized in any accounting period. Material differences may result in the amount and timing of revenue for any period based on the judgments and estimates made by management. Specifically, in connection with each transaction, the Company must evaluate whether: (i) persuasive evidence of an arrangement exists, (ii) delivery has occurred, (iii) the fee is fixed or determinable, and (iv) collectibility is probable. The Company applies these criteria as discussed below.

• Persuasive evidence of an arrangement exists: For a license arrangement, the Company requires a written contract, signed by both the customer and the Company. For a stand-alone product sale, the Company requires a purchase order or other form of written agreement with the customer.

• Delivery has occurred. The Company delivers software and product to customers physically and also delivers software electronically. For physical deliveries not related to software, the transfer terms typically include transfer of title and risk of loss at the Company’s shipping location. For electronic deliveries, delivery occurs when the Company provides the customer access codes or “keys” that allow the customer to take immediate possession of the software.

• The fee is fixed or determinable. The Company’s arrangement fee is based on the use of standard payment terms which are those that are generally extended to the majority of customers. For transactions involving extended payment terms, the Company deems these fees not to be fixed or determinable for revenue recognition purposes and revenue is deferred until the fees become due and payable.

• Collectibility is probable. To recognize revenue, the Company must judge collectibility of the arrangement fees, which is done on a customer-by-customer basis pursuant to the credit review policy. The Company typically sells to customers with whom there is a history of successful collection. For new customers, the Company evaluates the customer’s financial condition and ability to pay. If it is determined that collectibility is not probable based upon the credit review process or the customer’s payment history, revenue is recognized when payment is received.

Royalty and license revenue — The Company licenses its portfolio of patents to customers in a variety of industries such as mobility, gaming, automotive, and medical devices. A majority of these are variable fee arrangements where the royalties earned by the Company are based on unit or sales volumes of the respective licensees. The Company also enters into fixed license fee arrangements. However, the terms of the royalty agreements generally require licensees to give notification of royalties due to the Company within 30 – 45 days of the end of the quarter during which their related sales occur. As the Company is unable to estimate the licensees’ sales in any given quarter to determine the royalties due to it, the Company recognizes royalty revenues based on royalties reported by licensees during the quarter and when all revenue recognition criteria are met. The Company recognizes fixed license fee revenue for licenses to intellectual property when earned under the terms of the agreements, which is generally recognized when all deliverables including services are completed or recognized on a straight-line basis over the expected term of the license. Certain royalties are based upon customer shipments or revenues and could be subject to change and may result in out of period adjustments.

Development contracts and other revenue — Development contracts and other revenue are comprised of professional services (consulting services and/or development contracts). Professional services revenues are recognized under the proportional performance accounting method based on physical completion of the work to be performed or completed performance method. A provision for losses on contracts is made, if necessary, in the period in which the loss becomes probable and can be reasonably estimated. Revisions in estimates are reflected in the period in which the conditions become known. To date, such losses have not been significant.

Multiple element arrangements — The Company enters into multiple element arrangements in which customers purchase time-based licenses, which include a combination of software and/or intellectual property licenses, professional services and in limited cases, post contract customer support. For arrangements that are software based and include software and professional services, the services are generally not essential to the functionality of the software, and customers may purchase consulting services to facilitate the adoption of the Company’s technology, but they may also decide to use their own resources or appoint other professional service organizations to perform these services. For these arrangements, including those with post contract customer support, revenue is recognized either over the period of the ongoing obligation which is generally consistent with the contractual term, or when all deliverables including services have been completed.

Also affecting revenue recognition for contracts that have multiple element arrangements are two Accounting Standards Updates (“ASU”). In September 2009, the Financial Accounting Standards Board (“FASB”) ratified ASU 2009-13 (update to ASC 605), “Revenue Arrangements with Multiple Deliverables” (“ASU 2009-13 (update to ASC 605)”). This guidance addresses criteria for separating the consideration in multiple-element arrangements. ASU 2009-13 (update to ASC 605) requires companies to allocate the overall consideration to each deliverable by using a best estimate of the selling price of individual deliverables in the arrangement in the absence of vendor-specific objective evidence or other third-party evidence of the selling price. ASU 2009-13 (update to ASC 605) was effective prospectively for revenue arrangements entered into or materially modified in fiscal years beginning on or after June 15, 2010. The Company adopted ASU 2009-13 (update to ASC 605) as of January 1, 2011, and its application has had no impact on the Company’s condensed consolidated financial statements to date. In September 2009, the FASB ratified ASU 2009-14 (update to ASC 605), “Certain Revenue Arrangements That Include Software Elements” (“ASU 2009-14 (update to ASC 605)”). ASU 2009-14 (update to ASC 605) provides guidance to exclude (a) non-software components of tangible products and (b) software components of tangible products that are sold, licensed, or leased with tangible products when the software components and non-software components of the tangible product function together to deliver the tangible product’s essential functionally. ASC 2009-14 (update to ASC 605) had an effective date that is consistent with ASU 2009-13 (update to ASC 605) above. The Company adopted ASC 2009-14 (update to ASC 605) as of January 1, 2011, and its application has had no impact on the Company’s condensed consolidated financial statements to date.

Product sales — The Company recognizes revenue from the sale of products and the license of associated software, if any, and expenses all related costs of products sold, once delivery has occurred and customer acceptance, if required, has been achieved. The Company has determined that the license of software for its medical simulation products is incidental to the product as a whole. The Company typically grants to customers a warranty which guarantees that products will substantially conform to the Company’s current specifications for generally three to twelve months from the delivery date pursuant to the terms of the arrangement. Historically, warranty-related costs have not been significant.

Recent Accounting Pronouncements

In June 2011, the FASB ratified ASU 2011-05 “Comprehensive Income (Topic 220): Presentation of Comprehensive Income.” ASU 2011-05 requires 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, eliminating the option to present other comprehensive income in the statement of changes in equity. Under either choice, items that are reclassified from other comprehensive income to net income are required to be presented on the face of the financial statements where the components of net income and the components of other comprehensive income are presented. In December 2011 the FASB ratified ASU 2011-12 “Comprehensive Income (Topic 220): Deferral of the Effective Date for Amendments to the Presentation of Reclassifications of Items Out of Accumulated Other Comprehensive Income in Accounting Standards Update No. 2011-05.” ASU 2011-12 defers those changes in ASU 2011-05 that relate to the presentation of reclassification adjustments. These amendments are effective for reporting periods beginning after December 15, 2011, and have been applied retrospectively. These amendments have changed the manner in which the Company presents comprehensive income by reporting comprehensive income information in the condensed consolidated statements of operations and comprehensive loss.