Revenue Recognition

6 Months Ended

Jun. 30, 2023

Revenue from Contract with Customer [Abstract]

Revenue Recognition

Note 2 – Revenue Recognition

We recognize revenue in accordance with Accounting Standards Codification (“ASC”) Topic 606, “Revenue from Contracts with Customers” (“ASC 606”). Under ASC 606, we apply the following five step model:

1. Identify the contract with the customer;

2. Identify the performance obligations in the contract;

3. Determine the transaction price;

4. Allocate the transaction price to the performance obligations in the contract; and

5. Recognize revenue when (or as) each performance obligation is satisfied.

We categorize revenue as software licenses, software maintenance, or services and other. Revenue from software licenses is recognized at a point in time upon delivery, provided all other revenue recognition criteria are met. We recognize software maintenance revenue over time on a straight-line basis over the contract period. Services revenue is recognized over time as the services are delivered using an input method (i.e., labor hours incurred as a percentage of total labor hours budgeted), provided all other revenue recognition criteria are met. Other revenue, includes hardware sales that may be included in a software license, is recognized at a point in time upon delivery provided all other revenue recognition criteria are met.

In addition to selling software licenses, software maintenance and software services on a standalone basis, a significant portion of our contracts include multiple performance obligations, which require an allocation of the transaction price to each distinct performance obligation based on a relative standalone selling price

(“SSP”) basis. The SSP is the price at which we would sell a promised good or service separately to a customer. The best estimate of SSP is the observable price of a good or service when we sell that good or service separately. A contractually stated price or a list price for a good or service may be the SSP of that good or service. We use a range of selling prices to estimate SSP when we sell each of the goods and services separately and need to determine whether there is a discount that needs to be allocated based on the relative SSP of the various goods and services within multiple performance obligation arrangements. In instances where SSP is not directly observable, such as when we do not sell the product or service separately, we typically determine the SSP using an adjusted market assessment approach using information that may include market conditions and other observable inputs. We typically have more than one SSP for individual goods and services due to the stratification of those goods and services by customer. In these instances, we may use information such as the nature of the customer and distribution channel in determining the SSP.

When software licenses and significant customization engineering services are sold together, they are accounted for as a combined performance obligation, as the software licenses are generally highly dependent on, and interrelated with, the associated customization services and therefore are not distinct performance obligations. Revenue for the combined performance obligation is recognized over time as the services are delivered using an input method (i.e., labor hours incurred as a percentage of total labor hours budgeted).

When subscription-based software is sold, the subscription-based software and software maintenance are generally considered distinct performance obligations. The transaction price is allocated to subscription-based software and the software maintenance based on the relative SSP of each performance obligation. We sell subscription-based software for a fixed fee and/or a usage-based royalty fee, sometimes subject to a minimum guarantee. When the amount is in the form of a fixed fee, including the guaranteed minimum in subscription-based royalties, revenue is allocated to the subscription-based software and recognized at a point in time upon delivery, provided all other revenue recognition criteria are met. Revenue allocated to the software maintenance is recognized over the contract term on a straight-line basis. Any subscription-based software fees earned not subject to the guaranteed minimum or earned in excess of the minimum amount are recognized as revenue when the subsequent usage occurs.

Our contracts can include variable fees, such as the option to purchase additional usage of a previously delivered software license. We may also provide pricing concessions to clients, a business practice that also gives rise to variable fees in contracts. We include variable fees in the determination of total transaction price if it is not probable that a future significant reversal of revenue will occur. We use the expected value or most likely value amount, whichever is more appropriate for specific circumstances, to estimate variable consideration, and the estimates are based on the level of historical price concessions offered to clients.

The amount of consideration is not adjusted for a significant financing component if the time between payment and the transfer of the related good or service is expected to be one year or less under the practical expedient in the guidance. Our revenue arrangements are typically accounted for under such expedient, as payment is typically due within 30 to 60 days. During the periods ended June 30, 2023 and 2022, none of our contracts contained a significant financing component.

Also, to the extent relevant in future periods with our acquisition of FortressID and adaption of our current products to be delivered in a hosted environment with AwareID, we expect to recognize revenue from our SaaS offerings in future periods. SaaS offerings will be recognized ratably over the subscription period. For the three and six months ended June 30, 2023 and 2022 we did not generate revenue from SaaS contracts.

Disaggregation of Revenues

We organize ourselves into a single segment that reports to the Chief Executive Officer who is our chief operating decision maker. We conduct our operations in the United States and sell our products and

services to domestic and international customers. Revenue generated from the following geographic regions was (in thousands):

	Three Months Ended June 30,				Six Months Ended June 30,
	2023		2022		2023		2022
United States	$	2,064	$	2,274	$	4,118	$	4,310
Germany		59		635		119		653
Rest of World		1,061		1,329		3,253		3,967
	$	3,184	$	4,238	$	7,490	$	8,930

Revenue by timing of transfer of goods or services was (in thousands):

	Three Months Ended June 30,				Six Months Ended June 30,
	2023		2022		2023		2022
Goods or services transferred at a point in time	$	733	$	2,020	$	2,502	$	4,713
Goods or services transferred over time		2,451		2,218		4,988		4,217
	$	3,184	$	4,238	$	7,490	$	8,930

Revenue by product group was (in thousands):

	Three Months Ended June 30,				Six Months Ended June 30,
	2023		2022		2023		2022
License and service contracts	$	2,748	$	3,884	$	5,605	$	7,215
Subscription-based contracts		436		354		1,885		1,715
	$	3,184	$	4,238	$	7,490	$	8,930

Revenue from subscription-based contracts include revenue that may be recognized at a point in time or over time and be part of a fixed fee and or minimum guarantee as well as fees earned and allocated to software maintenance.

Contract Balances

When the timing of our delivery of goods or services is different from the timing of payments made by customers, we recognize either a contract asset (performance precedes contractual due date) or a contract liability (customer payment precedes performance). Customers that prepay are represented by the deferred revenue below until the performance obligation is satisfied.

Our contract assets consist of unbilled receivables. Our contract liabilities consist of deferred (unearned) revenue, which is generally related to software maintenance contracts. We classify deferred revenue as current or noncurrent based on the timing of when we expect to recognize revenue.

The following tables present changes in our contract assets and liabilities during the three and six months ended June 30, 2023 and 2022 (in thousands):

	Balance at Beginning of Period		Revenue Recognized In Advance of Billings		Billings			Balance at End of Period
Three months ended June 30, 2023
Contract assets:
Unbilled receivables	$	3,483	$	620	$	(1,283	)	$	2,820
Three months ended June 30, 2022
Contract assets:
Unbilled receivables	$	3,175	$	1,515	$	(1,260	)	$	3,430
	Balance at Beginning of Period		Billings		Revenue Recognized			Balance at End of Period
Three months ended June 30, 2023
Contract liabilities:
Deferred revenue	$	3,796	$	2,330	$	(1,767	)	$	4,359
Three months ended June 30, 2022
Contract liabilities:
Deferred revenue	$	3,300	$	2,052	$	(1,819	)	$	3,533

	Balance at Beginning of Period		Revenue Recognized In Advance of Billings		Billings			Balance at End of Period
Six months ended June 30, 2023
Contract assets:
Unbilled receivables	$	2,929	$	2,960	$	(3,069	)	$	2,820
Six months ended June 30, 2022
Contract assets:
Unbilled receivables	$	3,087	$	3,001	$	(2,658	)	$	3,430
	Balance at Beginning of Period		Billings		Revenue Recognized			Balance at End of Period
Six months ended June 30, 2023
Contract liabilities:
Deferred revenue	$	3,733	$	4,228	$	(3,602	)	$	4,359
Six months ended June 30, 2022
Contract liabilities:
Deferred revenue	$	3,740	$	3,274	$	(3,481	)	$	3,533

Remaining Performance Obligations

Remaining performance obligations represent the transaction prices from contracts for which work has not been performed or goods and services have not been delivered. We expect to recognize revenue on approximately 85% of the remaining deferred revenue over the next 12 months, with the remainder

recognized thereafter. As of June 30, 2023, the aggregate amount of the transaction prices allocated to remaining performance obligations for contracts with a duration greater than one year was $ 4.0 million.