XML 34 R23.htm IDEA: XBRL DOCUMENT
v3.10.0.1

ACCOUNTING STANDARDS (Policies) | 6 Months Ended
--- | ---
Jun. 30, 2018
Revenue, Initial Application Period Cumulative Effect Transition [Abstract] |
Revenue Recognition, Policy [Policy Text Block] | Revenue Recognition Substantially all of our revenues are from orders received from our customers for the purchase of wearable technology components that can be integrated to create headset systems. We also have development contracts for the design, manufacture and modification of products for the U.S. government or a prime contractor for the U.S. government (“U.S. government”) or for a customer that sells into the industrial or consumer markets. The Company's contracts with the U.S. government are typically subject to the Federal Acquisition Regulations (“FAR”) and are priced based on estimated or actual costs of producing goods. The FAR provides guidance on the types of costs that are allowable in establishing prices for goods provided under U.S. government contracts. The pricing for non-U.S. government contracts is based on the specific negotiations with each customer. Our fixed-price contracts with the U.S. government may result in revenue recognized in excess of amounts actually billed. We disclose the in excess of revenues over amounts actually billed as Contract assets on the balance sheet. Amounts billed and due from our customers are classified as accounts receivable on the balance sheet. In some instances, the U.S. government retains a small portion of the contract price until completion of the contract. The portion of the payments retained until final contract settlement is not considered a significant financing component because the intent is to protect the customer. For contracts with the U.S. government, we typically receive interim payments either as work progresses, we achieve certain milestones or based on a schedule in the contract. We recognize a liability for these advance payments in excess of revenue recognized and present it as billings in excess of revenue earned on the balance sheet. The advanced payment typically is not considered a significant financing component because it is used to meet working capital demands that can be higher in the early stages of a contract and to protect us from the other party failing to adequately complete some or all of its obligations under the contract. For industrial and consumer purchase orders, we typically receive payments within 30 to 60 days of shipments of the product, although for some purchase orders, we may require an advanced payment prior to shipment of the product. To determine the proper revenue recognition method for complex contracts with the same customer, we evaluate whether two or more contracts should be combined and accounted for as one single contract and whether the combined or single contract should be accounted for as more than one performance obligation. This evaluation requires significant judgment and the decision to combine a group of contracts or separate the combined or single contract into multiple performance obligations could change the amount of revenue and profit recorded in a given period. For most of our development contracts and contracts with the U.S government, the customer contracts with us to provide a significant service of integrating a set of components into a single unit. Hence, the entire contract is accounted for as one performance obligation. Less common, however, we may promise to provide distinct goods or services within a contract in which case we separate the contract into more than one performance obligation. If a contract is separated into more than one performance obligation, we allocate the total transaction price to each performance obligation in an amount based on the estimated relative standalone selling prices of the promised goods or services underlying each performance obligation. In cases where we sell standard products, the observable standalone sales are used to determine the standalone selling price. The Company recognizes revenue from a contract when it has approval and commitment from both parties, the rights of the parties are identified, payment terms are identified, the contract has commercial substance and collectability of consideration is probable. For certain contracts that meet the foregoing requirements, primarily international direct commercial and military sale contracts, we recognize revenue once we have obtained all regulatory approvals. Commencing in 2018 for certain contracts with the U.S. government, the Company recognizes revenue over time as we perform because of continuous transfer of control to the customer and the lack of an alternative use for the product. The continuous transfer of control to the customer is supported by liability clauses in the contract that allow the U.S. government to unilaterally terminate the contract for convenience, pay us for costs incurred plus a reasonable profit and take control of any work in process. For contracts with commercial customers while the contract may have a similar liability clause, our products historically have an alternative use and thus, revenue is recognized at a point in time. In situations where control transfers over time, revenue is recognized based on the extent of progress towards completion of the performance obligation. We generally use the cost-to-cost approach to measure the extent of progress towards completion of the performance obligation for our contracts because we believe it best depicts the transfer of assets to the customer, which occurs as we incur costs on our contracts. Under the cost-to-cost measure approach, the extent of progress towards completion is measured based on the ratio of costs incurred to date to the total estimated costs at completion of the performance obligation. Revenues are recorded proportionally as costs are incurred. Accounting for design, development and production contracts requires judgment relative to assessing risks, estimating contract revenues and costs, and making assumptions for schedule and technical issues. Due to the size and nature of the work required to be performed on many of our contracts, the estimation of total revenue and cost at completion is complicated and subject to many variables. Contract costs include material, labor and subcontracting costs, as well as an allocation of indirect costs. We have to make assumptions regarding the number of labor hours required to complete a task, the complexity of the work to be performed, the availability and cost of materials, and performance by our subcontractors. For contract change orders, claims or similar items, we apply judgment in estimating the amounts and assessing the potential for realization. These amounts are only included in contract value when they can be reliably estimated and realization is considered probable. If our estimate of total contract costs or our determination of whether the customer agrees that a milestone is achieved is incorrect, our revenue could be overstated or understated and the profits or loss reported could be wrong. For our commercial customers, the Company's revenue is recognized when obligations under the terms of a contract with our customer is satisfied; generally this occurs with the transfer of control of the Company's products or services. Revenue is recorded as the amount of consideration we expect to receive in exchange for transferring goods or providing services. Provisions for product returns and allowances are recorded in the same period as the related revenues. We analyze historical returns, current economic trends and changes in customer demand and acceptance of product when evaluating the adequacy of sales returns and other allowances. Certain product sales are made to distributors under agreements allowing for a limited right of return on unsold products. Sales to distributors are primarily made for sales to the distributors' customers and not for stocking of inventory. We delay revenue recognition for our estimate of distributor claims of right of return on unsold products based upon our historical experience with our products and specific analysis of amounts subject to return based upon discussions with our distributors or their customers. Sales, value add and other taxes we collect concurrent with revenue-producing activities are excluded from revenue. The rights and benefits to the Company's intellectual property are conveyed to certain customers through technology license agreements. These agreements may include other performance obligations including the sale of product to the customer. When the license is distinct from other obligations in the agreement, the Company treats the license and other performance obligations as separate performance obligations. Accordingly, the license is recognized at a point in time or over time based on the standalone selling price. The sale of materials are recognized at a point in time, which occurs with the transfer of control of the Company's products or services. In certain instances, the Company is entitled to sales-based royalties under license agreements. These sales-based royalties are recognized when they are earned. The cumulative effect of the changes made to the Company's consolidated December 31, 2017 balance sheet for the adoption of ASU 2014-09, Revenue from Contracts with Customers (Topic 606) was as follows:
Balance Sheet | Balance at December 30, 2017 |  | Adjustments due to Topic 606 |  | Balance at December 31, 2017
Assets |  |  |  |  |
Contract assets and unbilled receivables | $ | 704,863 |  |  | $ | 2,850,274 |  |  | $ | 3,555,137 |
Inventory | 5,080,797 |  |  | (1,082,629 | ) |  | 3,998,168 |
Other assets | 3,842,068 |  |  | 400,000 |  |  | 4,242,068 |
Liabilities |  |  |  |  |
Contract liabilities and billings in excess of revenue earned | 1,555,883 |  |  | (891,737 | ) |  | 664,146 |
Stockholders’ equity |  |  |  |  |
Accumulated Deficit | $ | (240,121,901 | ) |  | $ | 3,059,382 |  |  | $ | (237,062,519 | )
In accordance with the new revenue standard requirements, the impact of adoption on the Company's condensed consolidated statement of operations was as follows:
| Three Months Ended June 30, 2018
Statement of Operations | As Reported |  | Balances Without Adoption of Topic 606 |  | Effect of Change Higher/(Lower)
Net product revenues | $ | 4,472,079 |  |  | $ | 4,483,933 |  |  | $ | (11,854 | )
Research and development revenues | 1,471,819 |  |  | 1,558,363 |  |  | (86,544 | )
Cost of product revenues | 3,497,750 |  |  | 3,495,042 |  |  | 2,708 |
Net loss attributable to Kopin Corporation | $ | (9,240,957 | ) |  | $ | (9,139,851 | ) |  | $ | (101,106 | )
| Six Months Ended June 30, 2018
Statement of Operations | As Reported |  | Balances Without Adoption of Topic 606 |  | Effect of Change Higher/(Lower)
Net product revenues | $ | 9,516,888 |  |  | $ | 10,989,276 |  |  | $ | (1,472,388 | )
Research and development revenues | 2,080,630 |  |  | 2,253,718 |  |  | (173,088 | )
Cost of product revenues | 7,559,941 |  |  | 8,500,121 |  |  | (940,180 | )
Net loss attributable to Kopin Corporation | $ | (14,777,235 | ) |  | $ | (14,071,939 | ) |  | $ | (705,296 | )
See Note 11. Segments and Disaggregation of Revenue for additional information regarding the disaggregation of the Company's revenue by major source and the Company's updated accounting policy for revenue recognition. Contract Assets Contract assets include unbilled amounts typically resulting from sales under contracts when the cost-to-cost method of revenue recognition is utilized and revenue recognized from customer arrangements, including licensing, exceeds the amount billed to the customer, and right to payment is not just subject to the passage of time. Amounts may not exceed their net realizable value. Contract assets are generally classified as current. The Company classifies the noncurrent portion of contract assets under other assets in its condensed consolidated balance sheets. Contract Liabilities Contract liabilities consist of advance payments and billings in excess of cost incurred and deferred revenue. Performance Obligations The Company's performance obligations that were satisfied at a point in time accounted for 59% and 84% for the three months ended June 30, 2018 and July 1, 2017, respectively, and 63% and 86% for the six months ended June 30, 2018 and July 1, 2017, respectively. The Company's performance obligations that were satisfied at over time accounted for 41% and 16% for the three months ended June 30, 2018 and July 1, 2017, respectively, and 37% and 14% for the six months ended June 30, 2018 and July 1, 2017, respectively. Remaining performance obligations represent the transaction price of orders for which work has not been performed and excludes unexercised contract options and potential orders under ordering-type contracts (e.g., indefinite-delivery, indefinite-quantity ("IDIQ")). As of June 30, 2018, the aggregate amount of the transaction price allocated to remaining performance obligations was $6.0 million. The Company expects to recognize revenue on the remaining performance obligations of $6.0 million over the next 2 years.

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

X
- Definition Disclosure of accounting policy for revenue recognition. If the entity has different policies for different types of revenue transactions, the policy for each material type of transaction is generally disclosed. If a sales transaction has multiple element arrangements (for example, delivery of multiple products, services or the rights to use assets) the disclosure may indicate the accounting policy for each unit of accounting as well as how units of accounting are determined and valued. The disclosure may encompass important judgment as to appropriateness of principles related to recognition of revenue. The disclosure also may indicate the entity's treatment of any unearned or deferred revenue that arises from the transaction. + References Reference 1: http://fasb.org/us-gaap/role/ref/otherTransitionRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -SubTopic 10 -Section 50 -Paragraph 3 -URI http://asc.fasb.org/extlink&oid=84158767&loc=d3e18780-107790 Reference 2: http://fasb.org/us-gaap/role/ref/otherTransitionRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -SubTopic 10 -Section 50 -Paragraph 1 -URI http://asc.fasb.org/extlink&oid=84158767&loc=d3e18726-107790 Reference 3: http://fasb.org/us-gaap/role/ref/otherTransitionRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -SubTopic 10 -Section 50 -Paragraph 4 -URI http://asc.fasb.org/extlink&oid=84158767&loc=d3e18823-107790 + Details
Name: | us-gaap_RevenueRecognitionPolicyTextBlock
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration