XML 32 R21.htm IDEA: XBRL DOCUMENT v3.20.2
Organization and Significant Accounting Policies (Policies)
6 Months Ended
Jun. 30, 2020
Accounting Policies [Abstract]  
Basis of Presentation
Basis of Presentation
The accompanying Condensed Consolidated Financial Statements include our accounts and the accounts of our wholly owned direct and indirect subsidiaries. All significant intercompany accounts and transactions have been eliminated in consolidation. Our Condensed Consolidated Financial Statements have been prepared in accordance with accounting principles generally accepted in the United States (“GAAP”) and the rules and regulations of the United States Securities and Exchange Commission (the “SEC”). In management's opinion, the unaudited Condensed Consolidated Financial Statements include all adjustments and accruals that are necessary for the presentation of the results of all interim periods reported herein and all such adjustments are of a normal, recurring nature with the exception of our adoption of Accounting Standards Update ("ASU") No. 2016-13, Financial Instruments - Credit Losses (Topic 326), Measurement of Credit Losses on Financial Instruments, often referred to as Current Expected Credit Losses ("CECL"). For additional details refer to Note 3, "Recent Accounting Standards".
Amounts shown on the Condensed Consolidated Statements of Operations within the operating expense categories of Cost of revenue; Research and development; Technology operations; Selling and marketing; and General and administrative are recorded exclusive of depreciation, amortization and accretion.
The financial information included herein, other than the Condensed Consolidated Balance Sheet as of December 31, 2019, is unaudited. The Condensed Consolidated Balance Sheet at December 31, 2019 has been derived from, but does not include all, the disclosures contained in the audited Consolidated Financial Statements as of and for the year ended December 31, 2019.
These Condensed Consolidated Financial Statements should be read in conjunction with the Consolidated Financial Statements and accompanying notes included in the Company's Annual Report on Form 10-K for the year ended December 31, 2019 (the “2019 Annual Report”). The Condensed Consolidated Statement of Operations for the interim periods presented are not necessarily indicative of the results that may be expected for a full year.
Use of Estimates
Use of Estimates
The preparation of these Condensed Consolidated Financial Statements requires management to make estimates and judgments that affect the reported amounts of assets, liabilities, revenues, expenses and related disclosures. On an on-going basis, we evaluate estimates and assumptions, including, but not limited to, those related to the impairment of long-lived assets; intangible assets subject to amortization and goodwill; accounts receivable allowances; revenue recognition; determining standalone selling price ("SSP") of performance obligations; variable consideration; depreciation expense; asset retirement obligations; income taxes; and capitalization of software costs. We base our estimates on historical experience and various other assumptions that are believed to be reasonable under the circumstances, the results of which form the basis for making judgments about the carrying values of assets and liabilities that are not readily apparent from other sources. Actual results may differ from these estimates under different assumptions or conditions.
Recent Accounting Standards RECENT ACCOUNTING STANDARDS
Recently Adopted
Credit Losses - In June 2016, the Financial Accounting Standards Board ("FASB") issued ASU No. 2016-13, or CECL. CECL requires early recognition of credit losses on financial assets held at the reporting date based on historical experience, current conditions, and reasonable and supportable forecasts. This guidance is effective for fiscal years beginning after December 15, 2019.

On January 1, 2020 we adopted ASU No. 2016-13 which resulted in an immaterial adjustment to the beginning balance of retained earnings and an increase to allowance for doubtful accounts.
Research and Development
Research and Development
Certain costs related to the development of Spok Go qualified for capitalization beginning in the first quarter of 2020.
In accordance with ASC 985-20, Software to be Sold, Leased, or Marketed, certain software development costs are charged to operations and expensed as incurred until technological feasibility has been established. Material costs incurred after technological feasibility is established and before the product is ready for general release are capitalized and amortized on a straight-line basis over the estimated remaining economic life of the product or the ratio of current revenues to total projected product revenues, whichever is greater. To date, the time between technological feasibility and general release to the public has been extremely short and consequently expenses available for capitalization have been immaterial. Accordingly, all research and developments costs incurred to date, accounted for in accordance with ASC 985-20, have been expensed as incurred.
In accordance with ASC 350-40, Internal-use Software, certain software development costs are capitalized while in the application development stage related to software developed for internal use or software sold in a Software-as-a-service ("SaaS") arrangement. This includes certain development costs for Spok Go. All other costs incurred during the preliminary project stage or the post-implementation stage, are expensed as incurred. Capitalized software development is amortized on a straight-line basis over the estimated useful life of the asset, typically three years, beginning when those development efforts have been placed into service (e.g., generally once made commercially available). Determining the estimated useful life requires significant judgment as we consider factors such as the rapid and continuous developments in software technology, obsolescence and anticipated life of the service offering before enhancements are necessary. In a SaaS environment, customer needs are rapidly evolving and a shorter useful life is generally expected.