XML 23 R9.htm IDEA: XBRL DOCUMENT
v3.19.2

REVENUE RECOGNITION | 3 Months Ended
--- | ---
Jun. 30, 2019
Revenue from Contract with Customer [Abstract] |
REVENUE RECOGNITION | REVENUE RECOGNITION Revenue Recognition The Company recognizes service revenue, mainly from subscription services to its cloud-based voice, call center, video and collaboration solutions using the five-step model as prescribed by ASC 606: • Identification of the contract, or contracts, with a customer; • Identification of the performance obligations in the contract; • Determination of the transaction price; • Allocation of the transaction price to the performance obligations in the contract; and • Recognition of revenue when or as, the Company satisfies a performance obligation. The Company identifies performance obligations in contracts with customers, which may include subscription services and related usage, product revenue and professional services. The transaction price is determined based on the amount the Company expects to be entitled to receive in exchange for transferring the promised services or products to the customer. The transaction price in the contract is allocated to each distinct performance obligation in an amount that represents the relative amount of consideration expected to be received in exchange for satisfying each performance obligation. Revenue is recognized when performance obligations are satisfied. Revenues are recorded based on the transaction price excluding amounts collected on behalf of third parties such as sales and telecommunication taxes, which are collected on behalf of and remitted to governmental authorities. The Company usually bills its customers on a monthly basis. Contracts typically range from annual to multi-year agreements with payment terms of net 30 days or less. The Company occasionally allows a 30-day period to cancel a subscription and return products shipped for a full refund. Judgments and Estimates The estimation of variable consideration for each performance obligation requires the Company to make subjective judgments. The Company has service-level agreements with customers warranting defined levels of uptime reliability and performance. Customers may get credits or refunds if the Company fails to meet such levels. If the services do not meet certain criteria, fees are subject to adjustment or refund representing a form of variable consideration. The Company may impose minimum revenue commitments ("MRC") on its customers at the inception of the contract. Thus, in estimating variable consideration for each of these performance obligations, the Company assesses both the probability of MRC occurring and the collectability of the MRC, of which both represent a form of variable consideration. The Company enters into contracts with customers that regularly include promises to transfer multiple services and products, such as subscriptions, products, and professional services. For arrangements with multiple services, the Company evaluates whether the individual services qualify as distinct performance obligations. In its assessment of whether a service is a distinct performance obligation, the Company determines whether the customer can benefit from the service on its own or with other readily available resources, and whether the service is separately identifiable from other services in the contract. This evaluation requires the Company to assess the nature of each individual service offering and how the services are provided in the context of the contract, including whether the services are significantly integrated, highly interrelated, or significantly modify each other, which may require judgment based on the facts and circumstances of the contract. When agreements involve multiple distinct performance obligations, the Company allocates arrangement consideration to all performance obligations at the inception of an arrangement based on the relative standalone selling prices ("SSP") of each performance obligation. Usage fees deemed to be variable consideration meet the allocation exception for variable consideration. Where the Company has standalone sales data for its performance obligations which are indicative of the price at which the Company sells a promised good or service separately to a customer, such data is used to establish SSP. In instances where standalone sales data is not available for a particular performance obligation, the Company estimates SSP by the use of observable market and cost-based inputs. The Company continues to review the factors used to establish list price and will adjust standalone selling price methodologies as necessary on a prospective basis. Service Revenue Service revenue from subscriptions to the Company's cloud-based technology platform is recognized over time on a ratable basis over the contractual subscription term beginning on the date that the platform is made available to the customer. Payments received in advance of subscription services being rendered are recorded as a deferred revenue. Usage fees, either bundled or not bundled, are recognized when the Company has a right to invoice. Professional services for configuration, system integration, optimization, customer training or education are primarily billed on a fixed-fee basis and are performed by the Company directly or, alternatively, customers may also choose to perform these services themselves or engage their own third-party service providers. Professional services revenue is recognized over time as the services are rendered. When a contract with a customer is signed, the Company assesses whether collection of the fees under the arrangement is probable. The Company estimates the amount to reserve for uncollectible amounts based on the aging of the contract balance, current and historical customer trends, and communications with its customers. These reserves are recorded as operating expenses against the contract asset (Accounts Receivable). In the normal course of business, the Company records revenue reductions for customer credits. Product Revenue The Company recognizes product revenue for telephony equipment at a point in time, when transfer of control has occurred, which is generally upon shipment. Sales returns are recorded as a reduction to revenue estimated based on historical experience. Contract Assets Contract assets are recorded for those parts of the contract consideration not yet invoiced but for which the performance obligations are completed. The revenue is recognized when the customer receives services or equipment for a reduced consideration at the onset of an arrangement, for example, when the initial month's services or equipment are discounted. Contract assets are included in other current or non-current assets in the condensed consolidated balance sheets, depending on if their reduction will be recognized during the succeeding twelve-month period or beyond. Deferred Revenue Deferred revenues represent billings or payments received in advance of revenue recognition and is recognized upon transfer of control. Balances consist primarily of annual plan subscription services and professional and training services not yet provided as of the balance sheet date. Deferred revenues that will be recognized during the succeeding twelve-month period are recorded as current deferred revenues in the condensed consolidated balance sheets, with the remainder recorded as other non-current liabilities in the condensed consolidated balance sheets. Costs to Obtain a Customer Contract Sales commissions and related expenses are considered incremental and recoverable costs of acquiring customer contracts. These costs are capitalized as current or non-current assets and amortized on a straight-line basis over the anticipated benefit period, which is five years. The benefit period was estimated by taking into consideration the length of customer contracts, technology lifecycle, and other factors. This amortization expense is recorded in sales and marketing expense within the Company's condensed consolidated statement of operations. Disaggregation of Revenue The Company disaggregates its revenue by geographic region. See Note 12 for more information. Contract Balances The following table provides information about receivables, contract assets and deferred revenues from contracts with customers (in thousands):
| June 30, 2019
Accounts receivable, net | $ | 23,361 |
Contract assets | $ | 9,375 |
Deferred revenue - current | $ | 4,088 |
Deferred revenue - non-current | $ | 67 |
Changes in the contract assets and the deferred revenue balances during the three months ended June 30, 2019 are as follows (in thousands):
|  | June 30, 2019 |  | March 31, 2019 |  | $ Change
Contract assets |  | $ | 9,375 |  |  | $ | 5,717 |  |  | $ | 3,658 |
Deferred revenue |  | $ | 4,155 |  |  | $ | 3,342 |  |  | $ | 813 |
The change in contract assets was primarily driven by the recognition of revenue that has not yet been billed. The increase in deferred revenues was due to billings in advance of performance obligations being satisfied. Revenues of $2.7 million recognized during the three months ended June 30, 2019, were included in the deferred revenues balance at the beginning of the period, which was offset by additional deferrals during the period.

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 -Publisher FASB -Name Accounting Standards Codification -Topic 606 -URI http://asc.fasb.org/topic&trid=49130388 + Details
Name: | us-gaap_RevenueFromContractWithCustomerTextBlock
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration