Revenue is recognized upon transfer of control of promised products or services to customers in an amount that reflects the consideration the Company expects to receive in exchange for those products or services. The Company enters into contracts that can include various combinations of its products, software licenses, and services, which are generally capable of being distinct and accounted for as separate performance obligations. For contracts with multiple performance obligations, the Company allocates the transaction price of the contract to each performance obligation, generally on a relative basis using its standalone selling price. The stated contract value is generally the transaction price to be allocated to the separate performance obligations. Revenue is recognized net of any taxes collected from customers that are subsequently remitted to governmental authorities.

The Company derives revenues primarily from sales of hardware products, software licenses, professional services, software maintenance and support, and extended hardware warranties.

Hardware Product Revenues — The Company generally has two performance obligations in arrangements involving the sale of hardware products. The first performance obligation is to transfer the hardware product (which includes software integral to the functionality of the hardware product). The second performance obligation is to provide assurance that the product complies with its agreed-upon specifications and is free from defects in material and workmanship for a period of one to three years (i.e. assurance warranty). The entire transaction price is allocated to the hardware product and is generally recognized as revenue at the time of delivery because the customer obtains control of the product at that point in time. The Company has concluded that control generally transfers at that point in time because the customer has title to the hardware, physical possession, and a present obligation to pay for the hardware. None of the transaction price is allocated to the assurance warranty component, as the Company accounts for these product warranty costs in accordance with Accounting Standards Codification ("ASC”) 460, Guarantees (“ASC 460”). Payments for hardware contracts are generally due 30 to 60 days after shipment of the hardware product.

Software License Revenues — The Company’s license arrangements grant customers the perpetual right to access and use the licensed software products at the outset of an arrangement. Technical support and software updates are generally made available throughout the term of the support agreement, which is generally one to three years. The Company accounts for these arrangements as two performance obligations: (1) the software licenses, and (2) the related updates and technical support. The software license revenue is recognized upon delivery of the license to the customer, while the software updates and technical support revenue is recognized over the term of the support contract. Payments are generally due 30 to 60 days after delivery of the software licenses.

Professional Services Revenues — Professional services revenues consist primarily of programming customization services performed relating to the integration of the Company’s software products with the customers other systems, such as HR systems. Professional services contracts are generally billed on a time and materials basis and revenue is recognized as the services are performed. Payments for services are generally due when services are performed.

Software Maintenance and Support Revenues — Support and maintenance contract revenues consist of the services provided to support the specialized programming applications performed by the Company’s professional services group. Support and maintenance contracts are typically billed at inception of the contract and recognized as revenue over the contract period, typically over a one to three year period.

Extended Hardware Warranties Revenues — Sales of the Company’s hardware products may also include optional extended hardware warranties, which typically provide assurance that the product will continue function as initially intended. Extended hardware warranty contracts are typically billed at inception of the contract and recognized as revenue over the respective contract period, typically over one to two year periods after the expiration of the original assurance warranty.

Performance Obligation	When Performance Obligation is Typically Satisfied	When Payment is Typically Due	How Standalone Selling Price is Typically Estimated
Hardware products	When customer obtains control of the product (point-in-time)	Within 30-60 days of shipment	Observable in transactions without multiple performance obligations
Software licenses	When license is delivered to customer or made available for download, and the applicable license period has begun (point-in-time)	Within 30-60 days of the beginning of license period	Established pricing practices for software licenses bundled with software maintenance, which are separately observable in renewal transactions
Professional services	As services are performed and/or when contract is fulfilled (point-in-time)	Within 30-60 days of delivery	Observable in transactions without multiple performance obligations
Software maintenance and support services	Ratably over the course of the support contract (over time)	Within 30-60 days of the beginning of the contract period	Observable in renewal transactions
Extended hardware warranties	Ratably over the course of the support contract (over time)	Within 30-60 days of the beginning of the contract period	Observable in renewal transactions

The Company’s contracts with customers often include promises to transfer multiple products and services to a customer. For such arrangements, the Company allocates revenues to each performance obligation based on its relative standalone selling price (“SSP”).

Judgment is required to determine the SSP for each distinct performance obligation in a contract. For the majority of items, the Company estimates SSP using historical transaction data. The Company uses a range of amounts to estimate SSP when it sells each of the products and services separately and needs to determine whether there is a discount to be allocated based on the relative SSP of the various products and services. In instances where SSP is not directly observable, such as when the product or service is not sold separately, the Company determines the SSP using information that may include market conditions and other observable inputs.

The determination of SSP is an ongoing process and information is reviewed regularly in order to ensure SSPs reflect the most current information or trends.

The Company disaggregates revenue from contracts with customers based on the timing of transfer of goods or services to customers (point-in-time or over time) and geographic region based on the shipping location of the customer. The geographic regions that are tracked are the Americas, Europe and the Middle East, and Asia-Pacific regions. The Company operates as two operating segments.

Total net revenue based on the disaggregation criteria described above are as follows (in thousands):

	Three Months Ended June 30,
	2019						2018
	Point-in- Time		Over Time		Total		Point-in- Time		Over Time		Total
Americas	$	14,760	$	1,185	$	15,945	$	14,732	$	1,173	$	15,905
Europe and the Middle East		3,332		91		3,423		2,510		13		2,523
Asia-Pacific		2,869		—		2,869		1,866		—		1,866
Total	$	20,961	$	1,276	$	22,237	$	19,108	$	1,186	$	20,294

	Six Months Ended June 30,
	2019						2018
	Point-in- Time		Over Time		Total		Point-in- Time		Over Time		Total
Americas	$	28,284	$	2,386	$	30,670	$	27,220	$	1,917	$	29,137
Europe and the Middle East		6,197		156		6,353		4,804		27		4,831
Asia-Pacific		4,736		—		4,736		2,854		—		2,854
Total	$	39,217	$	2,542	$	41,759	$	34,878	$	1,944	$	36,822

Amounts invoiced in advance of services being provided are accounted for as deferred revenue. Nearly all of the Company’s deferred revenue balance is related to software maintenance contracts. Payment terms and conditions vary by contract type, although payment is typically due within 30 to 90 days of contract inception. In instances where the timing of revenue recognition differs from the timing of invoicing, the Company has determined its contracts generally do not include a significant financing component.

Changes in deferred revenue during the six months ended June 30, 2019 were as follows (in thousands):

Revenue expected to be recognized in future periods related to remaining performance obligations, excluding revenue pertaining to contracts that have an original expected duration of one year or less, and contracts where revenue is recognized as invoiced, was approximately $1.4 million as of June 30, 2019. Since the Company typically invoices customers at contract inception, this amount is included in its deferred revenue balance. As of June 30, 2019, the Company expects to recognize approximately 59% of the revenue related to these unsatisfied performance obligations during the remainder of 2019, 30% during 2020, and 11% thereafter.

The Company recognizes an asset for the incremental costs of obtaining a contract with a customer if it expects the benefit of those costs to be longer than one year. The Company has determined that certain sales incentive programs (i.e. commissions) meet the requirements to be capitalized. Capitalized incremental costs related to contracts are amortized over the respective contract periods. For the six months ended June 30, 2019, total capitalized costs to obtain contracts were immaterial.