Note 3. Revenue Recognition

We primarily derive revenue from the following sources: (1) royalty-based software license arrangements, (2) connected services, and (3) professional services. Revenue is reported net of applicable sales and use tax, value-added tax and other transaction taxes imposed on the related transaction including mandatory government charges that are passed through to our customers. We account for a contract when both parties have approved and committed to the contract, the rights of the parties are identified, payment terms are identified, the contract has commercial substance and collectability of consideration is probable.

Our arrangements with customers may contain multiple products and services. We account for individual products and services separately if they are distinct—that is, if a product or service is separately identifiable from other items in the contract and if a customer can benefit from it on its own or with other resources that are readily available to the customer.

We currently recognize revenue after applying the following five steps:

We allocate the transaction price of the arrangement based on the relative estimated standalone selling price (“SSP”) of each distinct performance obligation. In determining SSP, we maximize observable inputs, when possible. Since prices vary from customer to customer based on customer relationship, volume discount and contract type, in instances where the SSP is not directly observable, we estimate SSP by considering a number of data points, including cost of developing and supplying each performance obligation; types of offerings; and gross margin objectives and pricing practices, such as contractually stated prices, discounts offered, and applicable price lists.

We only include estimated amounts in the transaction price to the extent it is probable that a significant reversal of cumulative revenue recognized will not occur when the uncertainty associated with the variable consideration is resolved. We reduce transaction prices for estimated returns and other allowances that represent variable consideration under Accounting Standards Codification (“ASC”) 606, which we estimate based on historical return experience and other relevant factors, and record a corresponding refund liability as a component of Accrued expenses and other current liabilities. Other forms of contingent revenue or variable consideration are infrequent.

Revenue is recognized when control of these products or services are transferred to our customers, in an amount that reflects the consideration we expect to be entitled to in exchange for those products or services.

We assess the timing of the transfer of products or services to the customer as compared to the timing of payments to determine whether a significant financing component exists. In accordance with the practical expedient in ASC 606-10-32-18, we do not assess the existence of a significant financing component when the difference between payment and transfer of deliverables is a year or less. If the difference in timing arises for reasons other than the provision of finance to either the customer or us, no financing component is deemed to exist. The primary purpose of our invoicing terms is to provide customers with simplified and predictable ways of purchasing our services, not to receive or provide financing from or to customers. We do not consider set-up fees nor other upfront fees paid by our customers to represent a financing component.

Reimbursements for out-of-pocket costs generally include, but are not limited to, costs related to transportation, lodging and meals. Revenue from reimbursed out-of-pocket costs is accounted for as variable consideration.

(a) Performance Obligations

Licenses

Embedded software and technology licenses operate without access to the external networks and information. Embedded licenses sold with non-distinct professional services to customize and/or integrate the underlying software and technology are accounted for as a combined performance obligation. Revenue from the combined performance obligation is recognized over time based upon the progress towards completion of the project, which is measured based on the labor hours already incurred to date as compared to the total estimated labor hours.

Revenue from distinct embedded software and technology licenses, which do not require professional services to customize and/or integrate the software license, is recognized at the point in time when the software and technology is made available to the customer and control is transferred. For income statement presentation purposes, we separate distinct embedded license revenue from professional services revenue based on their relative SSPs.

Revenue from embedded software and technology licenses sold on a royalty basis, where the license of non-exclusive intellectual property is the predominant item to which the royalty relates, is recognized in the period the usage occurs in accordance with ASC 606-10-55-65(A).

For royalty arrangements that include fixed consideration related to minimum purchase commitment deals, the fixed consideration is recognized when the software is made available to the customer.

Connected Services

Connected services, which allow our customers to use the hosted software over the contract period without taking possession of the software, are provided on a usage basis as consumed or on a fixed fee subscription basis. Subscription basis revenue represents a single promise to stand-ready to provide access to our connected services. Our connected services contract terms generally range from one to five years.

As each day of providing services is substantially the same and the customer simultaneously receives and consumes the benefits as access is provided, we have determined that our connected services arrangements are a single performance obligation comprised of a series of distinct services. These services include variable consideration, typically a function of usage. We recognize revenue as each distinct service period is performed (i.e., recognized as incurred).

Our connected service arrangements generally include services to develop, customize, and stand-up applications for each customer. In determining whether these services are distinct, we consider dependence of the cloud service on the up-front development and stand-up, as well as availability of the services from other vendors. We have concluded that the up-front development, stand-up and customization services are not distinct performance obligations, and as such, revenue for these activities is recognized over the period during which the cloud-connected services are provided, and is included within connected services revenue. There can be instances where the customer purchases a software license that allows them to take possession of the software to enable hosting by the customer or a third-party. For such arrangements, the performance obligation of the license is completed at a point in time once the customer takes possession of the software.

Professional Services

Revenue from distinct professional services, including training, is recognized over time based upon the progress towards completion of the project, which is measured based on the labor hours already incurred to date as compared to the total estimated labor hours.

(b) Significant Judgments

Determining whether products and services are considered distinct performance obligations that should be accounted for separately versus together may require significant judgment. Our license contracts often include professional services to customize and/or integrate the licenses into the customer’s environment. Judgment is required to determine whether the license is considered distinct and accounted for separately, or not distinct and accounted for together with professional services. Furthermore, hybrid contracts that contain both embedded and connected license and professional services are analyzed to determine if the products and services are distinct or have stand-alone functionality to determine the revenue treatment.

We allocate the transaction price of the arrangement based on the relative estimated SSP of each distinct performance obligation. Judgment is required to determine the SSP for each distinct performance obligation. In determining SSP, we maximize observable inputs, when possible. Since our prices vary from customer to customer based on customer relationship, volume discount and contract type, there are instances where the SSP is not directly observable. In such instances, we estimate SSP by considering a number of data points, including cost of developing and supplying each performance obligation; types of offerings; and gross margin objectives and pricing practices, such as contractually stated prices, discounts offered, and applicable price lists. These factors may vary over time, depending upon the unique facts and circumstances related to each deliverable. We review the SSP for each distinct performance obligation on a periodic basis, or when the underlying factors are deemed to have changed, and make updates when appropriate.

(c) Disaggregated Revenue

Revenues within the United States, Germany, and Japan accounted for more than 10% of revenue, respectively, for all periods presented. For the three months ended December 31, 2022, revenues within China were $9.6 million, which were over 10% of revenues.

Revenues relating to two customers accounted for $21.4 million, or 25.6%, and $10.0 million, or 12.0%, of revenues for the three months ended December 31, 2022.

Revenues relating to two customers accounted for $24.2 million, or 25.7%, and $17.9 million, or 19.0%, of revenues for the three months ended December 31, 2021. During the three months ended December 31, 2021, certain existing variable long-term contracts with our largest customer were converted into minimum purchase commitment deals. The estimated future revenues related to these long-term contracts were previously included in our variable backlog, which includes estimated future revenues from variable forecasted revenues related to our embedded and connected business. These minimum purchase commitment deals accounted for $20.1 million of revenues during the three months ended December 31, 2021. The cash associated with these deals is expected to be collected over the distribution period, which could be up to five years.

(d) Contract Acquisition Costs

In conjunction with the adoption of ASC 606, we are required to capitalize certain contract acquisition costs. The capitalized costs primarily relate to paid commissions. In accordance with the practical expedient in ASC 606-10-10-4, we apply a portfolio approach to estimate contract acquisition costs for groups of customer contracts. We elect to apply the practical expedient in ASC 340-40-25-4 and will expense contract acquisition costs as incurred where the expected period of benefit is one year or less. Contract acquisition costs are deferred and amortized on a straight-line basis over the period of benefit, which we have estimated to be, on average, between one and eight years. The period of benefit was determined based on an average customer contract term, expected contract renewals, changes in technology and our ability to retain customers, including canceled contracts. We assess the amortization term for all major transactions based on specific facts and circumstances. Contract acquisition costs are classified as current or noncurrent assets based on when the expense will be recognized. The current and noncurrent portions of contract acquisition costs are included in Prepaid expenses and other current assets and Other assets, respectively. As of December 31, 2022 and September 30, 2022, we had $8.8 million and $8.3 million of contract acquisition costs, respectively. We had amortization expense of $0.8 million and $0.6 million related to these costs during the three months ended December 31, 2022 and 2021, respectively. There was no impairment related to contract acquisition costs.

(e) Capitalized Contract Costs

We capitalize incremental costs incurred to fulfill our contracts that (i) relate directly to the contract, (ii) are expected to generate resources that will be used to satisfy our performance obligation under the contract, and (iii) are expected to be recovered through revenue generated under the contract. Our capitalized costs consist primarily of setup costs, such as costs to standup, customize and develop applications for each customer, which are incurred to satisfy our stand-ready obligation to provide access to our connected offerings. These contract costs are expensed to cost of revenue as we satisfy our stand-ready obligation over the contract term which we estimate to be between one and eight years, on average. The contract term was determined based on an average customer contract term, expected contract renewals, changes in technology, and our ability to retain customers, including canceled contracts. We classify these costs as current or noncurrent based on the timing of when we expect to recognize the expense. The current and noncurrent portions of capitalized contract fulfillment costs are presented as Deferred costs.

We had amortization expense of $2.7 million and $2.8 million related to these costs during the three months ended December 31, 2022 and 2021, respectively. There was no impairment related to contract costs capitalized.

(f) Trade Accounts Receivable and Contract Balances

We classify our right to consideration in exchange for deliverables as either a receivable or a contract asset. A receivable is a right to consideration that is unconditional (i.e., only the passage of time is required before payment is due). We present such receivables in Accounts receivable, net at their net estimated realizable value. We maintain an allowance for credit losses to provide for the estimated amount of receivables and contract assets that may not be collected.

Our contract assets and liabilities are reported in a net position on a contract-by-contract basis at the end of each reporting period.

Contract assets include unbilled amounts from long-term contracts when revenue recognized exceeds the amount billed to the customer, and right to payment is not solely subject to the passage of time. The current and noncurrent portions of contract assets are included in Prepaid expenses and other current assets and Other assets, respectively. The table below shows significant changes in contract assets (dollars in thousands):

Our contract liabilities, which we present as Deferred revenue, consist of advance payments and billings in excess of revenues recognized. We classify deferred revenue as current or noncurrent based on when we expect to recognize the revenues. The table below shows significant changes in deferred revenue (dollars in thousands):

(g) Remaining Performance Obligations

The table above includes fixed backlogs and does not include variable backlogs derived from contingent usage-based activities, such as royalties and usage-based connected services.