C) Revenue Recognition. Effective January 1, 2018, we adopted Accounting Standards Codification (“ASC”), Topic 606, Revenue from Contracts with Customers (“ASC 606”), using the full retrospective transition method.

In accordance with ASC 606, revenue is recognized when a customer obtains control of promised goods and services. The amount of revenue recognized reflects the consideration to which we expect to be entitled to receive in exchange for these goods and services. In addition, ASC 606 requires disclosures of the nature, amount, timing, and uncertainty of revenue and cash flows arising from contracts with customers.

The core principle of the standard is that we recognize revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration to which we expect to be entitled in exchange for those goods or services. To achieve that core principle, we apply the following five step model:

Identify the contract with the customer;

Identify the performance obligations in the contract;

Determine the transaction price;

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

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

1) Identify the contract with the customer

A contract with a customer exists when (i) we enter into an enforceable contract with a customer that defines each party’s rights regarding the goods or services to be transferred and identifies the related payment terms, (ii) the contract has commercial substance, and (iii) we determine that collection of substantially all consideration for goods and services that are transferred is probable based on the customer’s intent and ability to pay the promised consideration. We apply judgment in determining the customer’s intent and ability to pay, which is based on a variety of factors including the customer’s historical payment experience, or in the case of a new customer, published credit and financial information pertaining to the customer.

We evaluate contract modifications for the impact on revenue recognition if they have been approved by both parties such that the enforceable rights and obligations under the contract have changed. Contract modifications are either accounted for using a cumulative effect adjustment or prospectively over the remaining term of the arrangement. The determination of which method is more appropriate depends on the nature of the modification, which we evaluate on a case-by-case basis.

We combine two or more contracts entered into at or near the same time with the same customer and account for them as a single contract if (i) the contracts are negotiated as a package with a common commercial objective, (ii) the amount of consideration to be paid in one contract depends on the price or performance of the other contract, or (iii) some or all of the goods or services in one contract would be combined with some or all of the goods and services in the other contract into a single performance obligation. If two or more contracts are combined, the consideration to be paid is aggregated and allocated to the individual performance obligations without regard to the consideration specified in the individual contracts.

2) Identify the performance obligations in the contract

Performance obligations promised in a contract are identified based on the goods and services that will be transferred to the customer that are both capable of being distinct, whereby the customer can benefit from the good or service either on its own or together with other available resources, and are distinct in the context of the contract, whereby the transfer of the good or service is separately identifiable from other promises in the contract. To the extent a contract includes multiple promised goods and services, we apply judgment to determine whether promised goods and services are capable of being distinct and distinct in the context of the contract. If these criteria are not met, the promised goods and services are accounted for as a combined performance obligation. To identify performance obligations, we consider all of the goods or services promised in a contract regardless of whether they are explicitly stated or are implied by customary business practices.

3) Determine the transaction price

The transaction price is determined based on the consideration we expect to be entitled in exchange for transferring promised goods and services to the customer. Determining the transaction price requires significant judgment. To the extent the transaction price includes variable consideration, we estimate the amount of variable consideration that should be included in the transaction price utilizing either the expected value method or the most likely amount method depending on the nature of the variable consideration. Variable consideration is included in the transaction price if, in our judgment, it is probable that a significant future reversal of cumulative revenue recognized under the contract will not occur. Any estimates, including the effect of the constraint on variable consideration, are evaluated at each reporting period. 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 ASC 606‑10‑32‑18. Our revenue arrangements are typically accounted for under such expedient, as payment is typically due within 30 to 60 days. As of September 30, 2019 and 2018, none of our contracts contained a significant financing component.

4) Allocate the transaction price to performance obligations in the contract

If the contract contains a single performance obligation, the entire transaction price is allocated to the single performance obligation. Contracts that contain multiple performance obligations require an allocation of the transaction price to each performance obligation based on a relative standalone selling price (“SSP”) basis unless the transaction price is variable and meets the criteria to be allocated entirely to a performance obligation or to a distinct service that forms part of a single performance obligation. The consideration to be received is allocated among the separate performance obligations based on relative SSPs. 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 amounts 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. 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 customers and circumstances. In these instances, we may use information such as the nature of the customer and distribution channel in determining the SSP.

5) Recognize revenue when or as we satisfy a performance obligation

We satisfy performance obligations either over time or at a point in time as discussed in further detail below. Revenue is recognized over time if 1) the customer simultaneously receives and consumes the benefits provided by our performance, 2) our performance creates or enhances an asset that the customer controls as the asset is created or enhanced, or 3) our performance does not create an asset with an alternative use to us and we have an enforceable right to payment for performance completed to date. If we do not satisfy a performance obligation over time, the related performance obligation is satisfied at a point in time by transferring the control of a promised good or service to a customer.

We categorize revenue as software licenses, software maintenance, or services. In addition to the general revenue recognition policies described above, specific revenue recognition policies apply to each category of revenue.

Software licenses

Software licenses consist of revenue from the sale of software licenses for biometrics and imaging applications. Our software licenses are functional intellectual property and typically provide customers with the right to use our software under a perpetual license or subscription based model for either a fixed term or in perpetuity as it exists when made available to the customer. We recognize revenue from software licenses at a point in time upon delivery, provided all other revenue recognition criteria are met.

Software maintenance

Software maintenance consists of revenue from the sale of software maintenance contracts for biometrics and imaging software. Software maintenance contracts entitle customers to receive software support and software updates, if and when they become available, during the term of the maintenance contract. Software support and software updates are considered distinct services. However, these distinct services are considered a single performance obligation consisting of a series of distinct services that are substantially the same and have the same pattern of transfer to the customer. We recognize software maintenance revenue over time on a straight-line basis over the contract period.

Services

Service revenue consists of fees from biometrics customers for software engineering services we provide to them. We recognize services revenue 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.

Refer to Note G – Business Segments for further information on the disaggregation of revenue, including revenue by geography and category.

Arrangements with multiple performance obligations

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. The various combinations of multiple performance obligations and our revenue recognition for each are described as follows:

Software licenses and software maintenance. When software licenses and software maintenance contracts are sold together, the software licenses and software maintenance are generally considered distinct performance obligations. The transaction price is allocated to the software licenses and the software maintenance based on relative SSP. Revenue allocated to the software licenses is recognized at a point in time upon delivery, provided all other revenue recognition criteria are met. Revenue allocated to the software maintenance is recognized on a straight-line basis over the contract period.

Software licenses and services. 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 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 software licenses and standard implementation or consulting-type services are sold together, they are generally considered distinct performance obligations as the software licenses are not dependent on or interrelated with the associated services. The transaction price in these arrangements is allocated to the software licenses and services based on relative SSP. Revenue allocated to the software licenses is recognized at a point in time upon delivery, provided all other revenue recognition criteria are met. Revenue allocated to the services is recognized over time using an input method (i.e., labor hours incurred as a percentage of total labor hours budgeted). In arrangements with both software licenses and services, the software license portion of the arrangement is classified as software license revenue and the services portion is classified as services revenue in our consolidated statements of operations.

Software licenses, software maintenance and services. When we sell software licenses, software maintenance and software services together, we account for the individual performance obligations separately if they are distinct. The transaction price is allocated to the separate performance obligations based on relative SSP. Revenue allocated to the software licenses is recognized at a point in time upon delivery. Revenue allocated to the services is recognized over time using an input method (i.e., labor hours incurred as a percentage of total labor hours budgeted). Revenue for the software maintenance is recognized on a straight-line basis over the contract period. However, if the software services are significant customization engineering services, they are accounted for with the software licenses as a combined performance obligation, as stated above. Revenue for the combined performance obligation is recognized over time using an input method (i.e., labor hours incurred as a percentage of total labor hours budgeted).

Returns

We do not offer rights of return for our products and services in the normal course of business.

Customer Acceptance

Our contracts with customers generally do not include customer acceptance clauses.

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. Contract assets represent arrangements in which the good or service has been delivered but payment is not yet due. Our contract assets consist of unbilled receivables. Our contract liabilities consisted 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 table presents changes in our contract assets and liabilities during the three and nine months ended September 30, 2018 and 2019 (in thousands):


			Revenue
	Balance at		Recognized
	Beginning of		In Advance of				Balance at End of
	Period		Billings		Billings		Period
Three months ended September 30, 2018
Contract assets:
Unbilled receivables	$	1,542	$	1,170	$	(557)	$	2,155

Three months ended September 30, 2019
Contract assets:
Unbilled receivables	$	3,659	$	796	$	(200)	$	4,255


	Balance at
	Beginning of				Revenue		Balance at End of
	Period		Billings		Recognized		Period
Three months ended September 30, 2018
Contract liabilities:
Deferred revenue	$	2,421	$	1,991	$	(1,297)	$	3,115

Three months ended September 30, 2019
Contract liabilities:
Deferred revenue	$	2,424	$	2,514	$	(1,290)	$	3,648


			Revenue
	Balance at		Recognized
	Beginning of		In Advance of				Balance at End of
	Period		Billings		Billings		Period
Nine months ended September 30, 2018
Contract assets:
Unbilled receivables	$	1,429	$	1,745	$	(1,019)	$	2,155

Nine months ended September 30, 2019
Contract assets:
Unbilled receivables	$	3,279	$	2,264	$	(1,288)	$	4,255


	Balance at
	Beginning of				Revenue		Balance at End of
	Period		Billings		Recognized		Period
Nine months ended September 30, 2018
Contract liabilities:
Deferred revenue	$	2,932	$	4,176	$	(3,993)	$	3,115

Nine months ended September 30, 2019
Contract liabilities:
Deferred revenue	$	3,099	$	4,514	$	(3,965)	$	3,648

Remaining Performance Obligations

Remaining performance obligations represent the transaction price from contracts for which work has not been performed or goods and services have not been delivered. We expect to recognize revenue on approximately 97% of the remaining performance obligations over the next 12 months, with the remainder recognized thereafter. As of September 30, 2019 and December 31, 2018, the aggregate amount of the transaction price allocated to remaining performance obligations for software maintenance contracts with a duration greater than one year was $0.1 million.

Contract Costs

We recognize an other asset for the incremental costs of obtaining a contract with a customer if we expect the benefit of those costs to be longer than one year. We have determined that certain sales commissions meet the requirements to be capitalized, and we amortize these costs on a consistent basis with the pattern of transfer of the goods and services in the contract. Total capitalized costs to obtain a contract were immaterial during the periods presented and are included in other current and long-term assets on our consolidated balance sheets.

We apply a practical expedient to expense costs as incurred for costs to obtain a contract when the amortization period is one year or less. These costs include sales commissions on software maintenance contracts with a contract period of one year or less as sales commissions paid on contract renewals are commensurate with those paid on the initial contract.