XML 18 R10.htm IDEA: XBRL DOCUMENT
v3.24.2

Revenue Recognition | 3 Months Ended
--- | ---
Jun. 30, 2024
Revenue from Contract with Customer [Abstract] |
Revenue Recognition | 3. Revenue Recognition Our customary business practice is to enter into legally enforceable written contracts with our customers. The majority of our contracts are governed by a master service agreement between us and the customer, which sets forth the general terms and conditions of any individual contract between the parties, which is then supplemented by a customer order to specify the different goods and services, the associated prices, and any additional terms for an individual contract. Performance obligations specific to each individual contract are defined within the terms of each order. Each performance obligation is identified based on the goods and services that will be transferred to our customer that are both capable of being distinct and are distinct within the context of the contract. The transaction price is determined based on the consideration to which we will be entitled and expect to receive in exchange for transferring goods or services to the customer. Typically, our contracts do not provide our customer with any right of return or refund; we do not constrain the contract price as it is probable that there will not be a significant revenue reversal due to a return or refund. Typically, our customer contracts contain one or more of the following goods or services which constitute performance obligations. Our proprietary software licenses typically provide for a perpetual right to use our software. Generally, our contracts do not provide significant services of integration and customization and installation services are not required to be purchased directly from us. The software is delivered before related services are provided and is functional without professional services, updates and technical support. We have concluded that the software license is distinct as the customer can benefit from the software on its own. Software revenue is typically recognized when the software is delivered or made available for download to the customer. We recognize revenue for hardware sales when the product is shipped to the customer and when obligations that affect the customer’s final acceptance of the arrangement have been fulfilled. Hardware is purchased from suppliers and provided to the end-user customers via drop-ship or from inventory. We are responsible for negotiating price both with the supplier and the customer, payment to the supplier, establishing payment terms and product returns with the customer, and we bear the credit risk if the customer does not pay for the goods. As the principal contact with the customer, we recognize revenue and cost of goods sold when we ship or are notified by the supplier that the product has been shipped. In certain limited instances, as shipping terms dictate, revenue is recognized upon receipt at the point of destination or upon installation at the customer site. Our subscription service revenue is comprised of fees for contracts that provide customers a right to access our software for a subscribed period. We do not provide the customer the contractual right to license the software at any time outside of the subscription period under these contracts. Our subscription service revenue is primarily based on rates per location, including rates per points of sale and per room. We recognize certain subscription service revenue on a per-transaction basis. The customer can only benefit from the software and software maintenance when provided the right to access the software. Accordingly, each of the rights to access the software, the maintenance services, any hosting services, and any transaction-based services is not considered a distinct performance obligation in the context of the contract and should be combined into a single performance obligation to be recognized over the contract period. The Company recognizes subscription revenue over a one-month period based on the typical monthly invoicing and renewal cycle in accordance with our customer agreement terms. We derive maintenance service revenue from providing unspecified updates, upgrades, bug fixes, and technical support services for our proprietary software. These services represent a stand-ready obligation that is concurrently delivered and has the same pattern of transfer to the customer; we account for these maintenance services as a single performance obligation. Maintenance revenue includes the same services provided by third-parties for remarketed software. We recognize substantially all maintenance revenue over the contract period of the maintenance agreement. We also recognize certain maintenance service revenue based on the volume of payment transactions processed by third parties through access to our software. Professional services revenues primarily consist of fees for consulting, implementation, installation, integration, development and training and are generally recognized over time as the customer simultaneously receives and consumes the benefits of the professional services as the services are being performed. Certain professional development services are recognized upon delivery of the developed solutions to the customer. At the end of each reporting period, we recognize the most likely amount of variable consideration on any contract holdbacks we expect to bill for development services delivered. Professional services can be provided by internal or external providers, do not significantly affect the customer’s ability to access or use other provided goods or services, and provide a measure of benefit beyond that of other promised goods or services in the contract. As a result, professional services are considered distinct in the context of the contract and represent a separate performance obligation. Professional services that are billed on a time and materials basis are recognized over time as the services are performed. For contracts billed on a fixed price basis, revenue is recognized over time using an input method based on labor hours expended to date relative to the total labor hours expected to be required to satisfy the related performance obligation. We use the market approach to derive standalone selling price (“SSP”) by maximizing observable data points (in the form of recently executed customer contracts) to determine the price customers are willing to pay for the goods and services transferred. If the contract contains a single performance obligation, the entire transaction price is allocated to that performance obligation. Contracts that contain multiple performance obligations require an allocation of the transaction price to each performance obligation based on a relative SSP basis. Shipping and handling fees billed to customers are recognized as revenue and the related costs are recognized in cost of goods sold. Revenue is recorded net of any applicable taxes collected and remitted to governmental agencies. Disaggregation of Revenue We derive and report our revenue from the sale of products (proprietary software licenses, third party hardware and operating systems), subscription and maintenance, and professional services. Products revenue recognized at a point in time totaled $9.9 million and $12.8 million for the three months ended June 30, 2024 and 2023, respectively. Subscription, maintenance, and substantially all professional services revenue recognized over time totaled $53.6 million and $43.3 million for the three months ended June 30, 2024 and 2023, respectively. Contract Balances Contract assets are rights to consideration in exchange for goods or services that we have transferred to a customer when that right is conditional on something other than the passage of time. The majority of our contract assets represent unbilled amounts related to products and professional services. We expect billing and collection of our contract assets to occur within the next twelve months. We receive payments from customers based upon contractual billing schedules and accounts receivable are recorded when the right to consideration becomes unconditional. Contract liabilities represent consideration received or consideration which is unconditionally due from customers prior to transferring goods or services to the customer under the terms of the contract. Revenue recognized from amounts included in contract liabilities at the beginning of the period was $26.8 million and $22.1 million for the three months ended June 30, 2024 and 2023, respectively. Because the right to the transaction became unconditional, we transferred to accounts receivable from contract assets at the beginning of the period, $1.9 million and $1.6 million for the three months ended June 30, 2024 and 2023, respectively. Our arrangements are for a period of one year or less. As a result, unsatisfied performance obligations as of June 30, 2024 are expected to be satisfied and the allocated transaction price recognized in revenue within a period of 12 months or less. Assets Recognized from Costs to Obtain a Contract Sales commission expenses that would not have occurred absent the customer contracts are considered incremental costs to obtain a contract. We expense the incremental costs to obtain a contract as incurred when the expected benefit and amortization period is one year or less. For subscription contracts that are renewed monthly based on an agreement term, we capitalize commission expenses and amortize as we satisfy the underlying performance obligations, generally based on the contract terms and anticipated renewals. Other sales commission expenses have a period of benefit of one year or less and are therefore expensed as incurred in line with the practical expedient elected. We had $4.8 million and $4.0 million of capitalized sales incentive costs as of June 30, 2024 and 2023, respectively. These balances are included in other non-current assets on our condensed consolidated balance sheets. During the three months ended June 30, 2024 and 2023, we expensed $0.9 million and $0.9 million, respectively, of sales commissions, which included amortization of capitalized amounts of $0.4 million and $0.4 million, respectively. These expenses are included in operating expenses – sales and marketing in our condensed consolidated statement of operations. All other costs to obtain a contract are not considered incremental and therefore are expensed as incurred.

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 -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 9 -Publisher FASB -URI https://asc.fasb.org/1943274/2147479806/606-10-50-9 Reference 2: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 10 -Publisher FASB -URI https://asc.fasb.org/1943274/2147479806/606-10-50-10 Reference 3: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 15 -Publisher FASB -URI https://asc.fasb.org/1943274/2147479806/606-10-50-15 Reference 4: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 12 -Subparagraph (a) -Publisher FASB -URI https://asc.fasb.org/1943274/2147479806/606-10-50-12 Reference 5: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 12 -Subparagraph (b) -Publisher FASB -URI https://asc.fasb.org/1943274/2147479806/606-10-50-12 Reference 6: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 12 -Subparagraph (c) -Publisher FASB -URI https://asc.fasb.org/1943274/2147479806/606-10-50-12 Reference 7: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 12 -Subparagraph (d) -Publisher FASB -URI https://asc.fasb.org/1943274/2147479806/606-10-50-12 Reference 8: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 12 -Subparagraph (e) -Publisher FASB -URI https://asc.fasb.org/1943274/2147479806/606-10-50-12 Reference 9: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 13 -Subparagraph (b)(2) -Publisher FASB -URI https://asc.fasb.org/1943274/2147479806/606-10-50-13 Reference 10: http://www.xbrl.org/2003/role/disclosureRef -Name Accounting Standards Codification -Topic 606 -Publisher FASB -URI https://asc.fasb.org/606/tableOfContent + Details
Name: | us-gaap_RevenueFromContractWithCustomerTextBlock
Namespace Prefix: | us-gaap_
Data Type: | dtr-types:textBlockItemType
Balance Type: | na
Period Type: | duration