Recent Accounting Pronouncements (Policies)
|6 Months Ended|
Jun. 30, 2018
|Accounting Changes and Error Corrections [Abstract]|
|Recent Accounting Pronouncements||
Recent Accounting Pronouncements
In February 2016, the Financial Accounting Standards Board (the "FASB") issued ASU 2016-02, Leases (Topic 842) ("ASU 2016-02"). ASU 2016-02 requires the lessee to recognize assets and liabilities for leases with lease terms of more than twelve months. For leases with a term of twelve months or less, the Company is permitted to make an accounting policy election by class of underlying asset not to recognize lease assets and lease liabilities. Further, ASU 2016-02 requires a finance lease to be recognized as both an interest expense and an amortization of the associated asset. Operating leases generally recognize the associated expense on a straight line basis. ASU 2016-02 requires the Company to adopt the standard using a modified retrospective approach and becomes effective on January 1, 2019. The Company is currently evaluating the impact that ASU 2016-02 will have on its financial position, results of operations and cash flows.
The Company offers its subscribers professional alarm monitoring services, as well as interactive and home automation services, through equipment at the subscriber's site that communicates with the Company’s central monitoring station and interfaces with other equipment at the site and third party technology companies for interactive and home automation services. These services are typically provided under alarm monitoring agreements (“AMAs”) between the Company and the subscriber. The equipment at the site is either obtained independently from the Company’s network of third party Authorized Dealers or directly from the Company, via its direct-to-consumer sales channel. The Company also offers equipment sales and installation services and, to its existing subscribers, maintenance services on existing alarm equipment. The Company also collects fees for contract monitoring, which are services provided to other security alarm companies for monitoring their accounts on a wholesale basis and other fees from subscribers for late fee or insufficient fund charges.
Revenue under subscriber AMAs is allocated to alarm monitoring revenue and, if applicable, product and installation revenue based on the stand alone selling prices (“SSP”) of each performance obligation as a percentage of the total SSP of all performance obligations. Allocated alarm monitoring revenue is recognized as the monthly service is provided. Allocated product and installation revenue is recognized when the product sale is complete or shipped and the installation service is provided, typically at inception of the AMA. Product and installation revenue is not applicable to AMA's acquired from Authorized Dealers in their initial term. Any cash not received from the subscriber at the time of product sale and installation is recognized as a contract asset at inception of the AMA and is subsequently amortized over the subscriber contract term as a reduction of the amounts billed for professional alarm monitoring, interactive and home automation services. If a subscriber cancels the AMA within the negotiated term, any existing contract asset is determined to be impaired and is immediately expensed in full to Selling, general and administrative expense on the condensed consolidated statement of operations.
Maintenance services are billed and recognized as revenue when the services are completed in the home and agreed to by the subscriber under the subscriber AMA. Contract monitoring fees are recognized as alarm monitoring revenue as the monitoring service is provided. Other fees are recognized as other revenue when billed to the subscriber which coincides with the timing of when the services are provided.
Disclosure of accounting policy pertaining to new accounting pronouncements that may impact the entity's financial reporting. Includes, but is not limited to, quantification of the expected or actual impact.
No definition available.
Disclosure of accounting policy for revenue from contract with customer.
Reference 1: http://www.xbrl.org/2003/role/exampleRef