XML 15 R6.htm IDEA: XBRL DOCUMENT
v3.5.0.2

SIGNIFICANT ACCOUNTING POLICIES | 6 Months Ended
--- | ---
Jun. 30, 2016
Accounting Policies [Abstract] |
SIGNIFICANT ACCOUNTING POLICIES | SIGNIFICANT ACCOUNTING POLICIES Description of Business Immersion Corporation (the “Company”) was incorporated in 1993 in California and reincorporated in Delaware in 1999. The Company focuses on the creation, design, development, and licensing of innovative haptic technologies that allow people to use their sense of touch more fully as they engage with cutting-edge products and experience the digital world around them. The Company has adopted a “hybrid” business model, under which it provides advanced tactile software, related tools, and technical assistance to certain customers; and offers licenses to the Company's patented intellectual property (“IP”) to other customers. 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 Corporation; Immersion International, LLC; Immersion Medical, Inc.; Immersion Japan K.K.; Immersion Ltd.; Immersion Software Ireland Ltd.; Haptify, Inc.; Immersion (Shanghai) Science & Technology Company, Ltd.; and Immersion Technology International Ltd. 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, 2015. 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 three months and six months ended June 30, 2016 are not necessarily indicative of the results to be expected for the full year. Segment Information The Company develops, licenses, and supports a wide range of software and IP that more fully engage users’ sense of touch when operating digital devices. The Company focuses on the following target application areas: mobility and consumer electronics, automotive, gaming, commercial and industrial, and medical. The Company’s chief operating decision maker (“CODM”) is the Chief Executive Officer. The CODM allocates resources to and assesses the performance of the Company using information about its financial results as one operating and reporting segment. Revenue Recognition The Company recognizes revenues in accordance with applicable accounting standards, including 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 two principal sources: royalty and license fees, and development contract and service fees. As described below, management judgments, assumptions, 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.
• | Delivery has occurred. The Company delivers software to customers physically and also delivers software electronically. 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 offered 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 fees, which is done on a customer-by-customer basis pursuant to the Company’s 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 patents and software to customers in a variety of industries such as mobility, gaming, automotive, and medical devices. Certain 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. 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 reliably 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 and when all revenue recognition criteria are met. Certain royalties are based upon customer shipments or revenues and could be subject to change and may result in out of period adjustments. The Company recognizes fixed license fee revenue for licenses when earned under the terms of the agreements, which is generally recognized on a straight-line basis over the expected term of the license. Development, services, and other revenue — Development, services, and other revenue are composed of engineering services (engineering services and/or development contracts), and in limited cases, post contract customer support (“PCS”). Engineering 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. Revenue from PCS is typically recognized over the period of the ongoing obligation, which is generally consistent with the contractual term. Multiple element arrangements — The Company enters into multiple element arrangements in which customers purchase time-based non-exclusive licenses that cannot be resold to others, which include a combination of software and/or IP licenses, engineering services, and in limited cases PCS. For arrangements that are software based and include software and engineering services, the services are generally not essential to the functionality of the software, and customers may purchase engineering services to facilitate the adoption of the Company’s technology, but they may also decide to use their own resources or appoint other engineering service organizations to perform these services. For arrangements that are in substance subscription arrangements, the entire arrangement fee is recognized ratably over the contract term, subject to any limitations related to extended payment terms. For arrangements involving upfront fees for services and royalties earned by the Company based on unit or sales volumes of the respective licensees, and the services are performed ratably over the arrangement or are front-end loaded, the upfront fees are recognized ratably over the contract term and royalties based on unit or sales volume are recognized when they become fixed and determinable. As the Company is unable to reliably estimate the licensees’ sales in any given quarter to determine the royalties due to it, the Company recognizes per unit or sales volume driven royalty revenues based on royalties reported by licensees and when all revenue recognition criteria are met. Recent Accounting Pronouncements In May 2014, the Financial Accounting Standards Board (“FASB”) issued Accounting Standards Update (“ASU”) No. 2014-09 “Revenue from Contracts with Customers: Topic 606” (“ASU 2014-09”) which will supersede the current revenue recognition requirements in Topic 605, Revenue Recognition, and most industry-specific guidance. The core principle of ASU 2014-09 is that an entity should recognize revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration to which the entity expects to be entitled in exchange for those goods or services. Further, the guidance requires improved disclosures to help users of financial statements better understand the nature, amount, timing, and uncertainty of revenue that is recognized. In August 2015, the FASB issued ASU No. 2015-14 “Revenue from Contracts with Customers: Deferral of the Effective Date”, which deferred the effective date of ASU 2014-09 for periods beginning after December 15, 2016 to December 15, 2017, with early adoption permitted but not earlier than the original effective date. In April 2016, the FASB issued ASU 2016-10 "Revenue from Contracts with Customers (Topic 606), Identifying Performance Obligations and Licensing" ("ASU 2016-10"), which further provides additional updates to revenue recognition guidance relating to performance obligations and accounting for licensing revenue. In May 2016, the FASB issued ASU 2016-12 "Revenue from Contracts with Customers (Topic 606), Narrow-Scope Improvements and Practical Expedients" ("ASU 2016-12") which further provides updates to revenue recognition guidance relating to scope and practical expedients for revenue recognition. Accordingly, ASU 2014-09, ASU 2016-10, and ASU 2016-12 are effective for the Company and are expected to be adopted in the first quarter of fiscal 2018. These standards permit companies to either apply the requirements retrospectively to all prior periods presented, or apply the requirements in the year of adoption through a cumulative adjustment. The Company is in the process of determining the method of adoption and evaluating the impact on its consolidated financial statements. In February 2016, the FASB issued ASU 2016-02 “Leases: Topic 842” (“ASU 2016-02”), which supersedes the existing guidance for lease accounting in Topic 840, Leases. The FASB issued the ASU to increase transparency and comparability among organizations by recognizing lease assets and lease liabilities on the balance sheet and disclosing key information about leasing arrangements. ASU 2016-02 requires lessees to recognize a lease liability and a right-of-use asset for all leases. Lessor accounting remains largely unchanged. The amendments of this ASU are effective for periods beginning after December 15, 2018, with early adoption permitted. An entity will be required to recognize and measure leases at the beginning of the earliest period presented using a modified retrospective approach. The Company is currently in the process of evaluating the impact of this standard on its consolidated financial statements. In March 2016, the FASB issued ASU 2016-09 “Compensation - Stock Compensation: Topic 718” (“ASU 2016-09”) which simplifies several aspects of the accounting for share-based payment transactions, including income tax consequences, classification of awards as either equity or liabilities, and classification in the statement of cash flows. The standard is effective for periods beginning after December 15, 2016, with early adoption permitted. The Company is currently in the process of evaluating the impact of this standard on its consolidated financial statements.

X
- References No definition available. + Details
Name: | us-gaap_AccountingPoliciesAbstract
Namespace Prefix: | us-gaap_
Data Type: | xbrli:stringItemType
Balance Type: | na
Period Type: | duration

X
- Definition The entire disclosure for all significant accounting policies of the reporting entity. + References Reference 1: http://www.xbrl.org/2003/role/presentationRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -SubTopic 10 -Section 50 -Paragraph 6 -URI http://asc.fasb.org/extlink&oid=68058157&loc=d3e18861-107790 Reference 2: http://www.xbrl.org/2003/role/presentationRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -SubTopic 10 -Section 50 -Paragraph 3 -URI http://asc.fasb.org/extlink&oid=68058157&loc=d3e18780-107790 Reference 3: http://www.xbrl.org/2003/role/presentationRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -SubTopic 10 -Section 50 -Paragraph 1 -URI http://asc.fasb.org/extlink&oid=68058157&loc=d3e18726-107790 Reference 4: http://www.xbrl.org/2003/role/presentationRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -SubTopic 10 -Section 50 -Paragraph 2 -URI http://asc.fasb.org/extlink&oid=68058157&loc=d3e18743-107790 Reference 5: http://www.xbrl.org/2003/role/presentationRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -SubTopic 10 -Section 50 -Paragraph 5 -URI http://asc.fasb.org/extlink&oid=68058157&loc=d3e18854-107790 + Details
Name: | us-gaap_SignificantAccountingPoliciesTextBlock
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration