XML 23 R12.htm IDEA: XBRL DOCUMENT
v3.23.1

4. REVENUE RECOGNITION | 3 Months Ended
--- | ---
Mar. 31, 2023
Revenue from Contract with Customer [Abstract] |
4. REVENUE RECOGNITION | 4 . REVENUE RECOGNITION The following is a description of principal activities from which we generate revenue. Revenues are recognized when control of the promised goods or services are transferred to our customers, in an amount that reflects the consideration that we expect to receive in exchange for those goods or services. We generate all of our revenue from contracts with customers. We evaluate contracts based on the 5-step model as stated in Topic 606 as follows: (i) identify the contract, (ii) identify the performance obligations, (iii) determine the transaction price, (iv) allocate the transaction price, and (v) recognize revenue when (or as) performance obligations are satisfied. A contract contains a promise (or promises) to transfer goods or services to a customer. A performance obligation is a promise (or a group of promises) that is distinct, as defined in the revenue standard. The transaction price is the amount of consideration an entity expects to be entitled to from a customer in exchange for providing the goods or services. A number of factors should be considered to determine the transaction price, including whether there is variable consideration, a significant financing component, noncash consideration, or amounts payable to the customer. The determination of variable consideration will require a significant amount of judgment. In estimating the transaction price we will use either the expected value method or the most likely amount method. The transaction price is allocated to the separate performance obligations in the contract based on relative standalone selling prices. Determining the relative standalone selling price can be challenging when goods or services are not sold on a standalone basis. The revenue standard sets out several methods that can be used to estimate a standalone selling price when one is not directly observable. Allocating discounts and variable consideration must also be considered. Allocating the transaction price can require significant judgement on our part. Revenue is recognized when (or as) the customer obtains control of the good or service/performance obligations are satisfied. Topic 606 provides guidance to help determine if a performance obligation is satisfied at a point in time or over time. Where a performance obligation is satisfied over time, the related revenue is also recognized over time. Disaggregation of revenue The following table provides information about disaggregated revenue by timing of revenue recognition (in thousands):
|  | Three Months Ended March 31, 2023 |
|  | Product |  |  | Royalty |  |  | Contract |  |  |  |
|  | revenue |  |  | revenue |  |  | revenue |  |  | Total |
Timing of revenue recognition: |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
Products transferred at a point in time |  | $ | 590 |  |  | $ | — |  |  | $ | — |  |  | $ | 590 |
Product and services transferred over time |  |  | — |  |  |  | — |  |  |  | 192 |  |  |  | 192 |
Total |  | $ | 590 |  |  | $ | — |  |  | $ | 192 |  |  | $ | 782 |
|  | Three Months Ended March 31, 2022 |
|  | Product |  |  | Royalty |  |  | Contract |  |  |  |
|  | revenue |  |  | revenue |  |  | revenue |  |  | Total |
Timing of revenue recognition: |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
Products transferred at a point in time |  | $ | — |  |  | $ | 350 |  |  | $ | — |  |  | $ | 350 |
Product and services transferred over time |  |  | — |  |  |  | — |  |  |  | — |  |  |  | — |
Total |  | $ | — |  |  | $ | 350 |  |  | $ | — |  |  | $ | 350 |
Contract balances Under Topic 606, our rights to consideration are presented separately depending on whether those rights are conditional or unconditional. We present our unconditional rights to consideration as “accounts receivable” in our Balance Sheet. Significant changes in the contract assets and the contract liabilities balances during the period are as follows (in thousands, except percentages):
|  | March 31, 2023 |  |  | December 31, 2022 |  |  | $ Change |  |  | % Change |
Contract assets |  | $ | 192 |  |  | $ | — |  |  | $ | 192 |  |  |  | — |
Contract liabilities |  |  | (5,676 | ) |  |  | (4,601 | ) |  |  | (1,075 | ) |  |  | 23.4 |
Net contract assets (liabilities) |  | $ | (5,484 | ) |  | $ | (4,601 | ) |  | $ | (883 | ) |  |  | 19.2 |
In April 2017, we signed a contract with Microsoft Corporation to develop an LBS display system. Under the agreement, we received an upfront payment of $10.0 million. As of December 31, 2022, we had applied $5.4 million against the contract liability. During the three months ended March 31, 2023, we applied $0 against the contract liability with this customer. In connection with our January 2023 acquisition of assets from Ibeo, we assumed contract liabilities totaling approximately $1.2 million. During the three months ended March 31, 2023, we recognized revenue totaling $ 110,000 related to these contract liabilities. Contract acquisition costs We are required to capitalize certain contract acquisition costs consisting primarily of commissions paid when contracts are signed. We currently do not pay any commissions upon the signing of a contract; therefore, no commission cost has been incurred as of March 31, 2023. Transaction price allocated to the remaining performance obligations The $10.0 million upfront payment received from our customer as noted above was being recognized as revenue as component sales were transferred to the customer. Under the new arrangement reached in March 2020, the royalties we expect to earn will be applied against the remaining prepayment. Because we do not have information on projected future shipments by our customer, we are not able to estimate the timing of revenue recognition related to the remaining performance obligations. The $4.6 million contract liability at March 31, 2023 is classified as a current liability on our balance sheet. It is likely that recognition of revenue may extend beyond the next twelve months. The remaining balance of the contract liabilities assumed in our acquisition of assets from Ibeo was approximately $1.1 million as of March 31, 2023. The following table provides information about the estimated timing of revenue recognition (in thousands):
|  | Remainder of 2023 |  |  | 2024 |
Revenue |  | $ | 1,075 |  |  | $ | — |

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

X
- Definition The entire disclosure of revenue from contract with customer to transfer good or service and to transfer nonfinancial asset. Includes, but is not limited to, disaggregation of revenue, credit loss recognized from contract with customer, judgment and change in judgment related to contract with customer, and asset recognized from cost incurred to obtain or fulfill contract with customer. Excludes insurance and lease contracts. + References Reference 1: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -URI https://asc.fasb.org/topic&trid=49130388 Reference 2: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -SubTopic 10 -Section 50 -Paragraph 10 -URI https://asc.fasb.org/extlink&oid=126920106&loc=SL49130551-203045 Reference 3: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -SubTopic 10 -Section 50 -Paragraph 13 -Subparagraph (b)(2) -URI https://asc.fasb.org/extlink&oid=126920106&loc=SL49130556-203045 Reference 4: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -SubTopic 10 -Section 50 -Paragraph 12 -Subparagraph (b) -URI https://asc.fasb.org/extlink&oid=126920106&loc=SL49130554-203045 Reference 5: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -SubTopic 10 -Section 50 -Paragraph 9 -URI https://asc.fasb.org/extlink&oid=126920106&loc=SL49130550-203045 Reference 6: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -SubTopic 10 -Section 50 -Paragraph 12 -Subparagraph (e) -URI https://asc.fasb.org/extlink&oid=126920106&loc=SL49130554-203045 Reference 7: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -SubTopic 10 -Section 50 -Paragraph 12 -Subparagraph (a) -URI https://asc.fasb.org/extlink&oid=126920106&loc=SL49130554-203045 Reference 8: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -SubTopic 10 -Section 50 -Paragraph 12 -Subparagraph (d) -URI https://asc.fasb.org/extlink&oid=126920106&loc=SL49130554-203045 Reference 9: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -SubTopic 10 -Section 50 -Paragraph 15 -URI https://asc.fasb.org/extlink&oid=126920106&loc=SL49130558-203045 Reference 10: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -SubTopic 10 -Section 50 -Paragraph 12 -Subparagraph (c) -URI https://asc.fasb.org/extlink&oid=126920106&loc=SL49130554-203045 + Details
Name: | us-gaap_RevenueFromContractWithCustomerTextBlock
Namespace Prefix: | us-gaap_
Data Type: | dtr-types:textBlockItemType
Balance Type: | na
Period Type: | duration