Summary of Significant Accounting Policies | 2. Summary of Significant Accounting Policies Principles of Consolidation These consolidated financial statements have been prepared in accordance with U.S. generally accepted accounting principles (“GAAP”). The consolidated financial statements include the accounts of the Company and its wholly owned subsidiaries. All intercompany accounts and transactions have been eliminated in consolidation. We are not the primary beneficiary of, nor do we have a controlling financial interest in, any variable interest entity. Accordingly, we have not consolidated any variable interest entity. Interim Unaudited Consolidated Financial Information The accompanying unaudited consolidated financial statements and footnotes have been prepared in accordance with GAAP as contained in the Financial Accounting Standards Board (“FASB”) Accounting Standards Codification (the “Codification” or “ASC”) for interim financial information, and with Article 10 of Regulation S-X. Accordingly, they do not include all of the information and footnotes required by GAAP for complete financial statements. In the opinion of management, the interim financial information includes all adjustments of a normal recurring nature necessary for a fair presentation of the results of operations, financial position, changes in stockholders’ equity and cash flows. The results of operations for the Use of Estimates The preparation of financial statements in conformity with GAAP requires the Company to make estimates and assumptions that affect the reported amounts in the consolidated financial statements and accompanying notes. Such estimates include revenue recognition and the customer relationship period, allowances for doubtful accounts and returns, valuations of deferred income taxes, long-lived assets, warrants, capitalizable software development costs and the related amortization, stock-based compensation, the determination of the useful lives of assets, and the impairment assessment of acquired intangibles and goodwill. Determination of these transactions and account balances are based on the Company’s estimates and judgments. These estimates are based on the Company’s knowledge of current events and actions it may undertake in the future as well as on various other assumptions that it believes to be reasonable. Actual results could differ materially from these estimates. Revenue and Deferred Revenue The Company derives the majority of its revenue from software services fees, which consist primarily of monthly subscription fees paid by customers for access to and usage of the Company’s cloud-based benefits software solutions for a specified contract term. The Company also derives revenue from professional services which primarily include fees related to the integration of customers’ systems with the Company’s platform, which typically includes discovery, configuration, deployment, testing, and training. The Company recognizes revenue when there is persuasive evidence of an arrangement, the service has been provided, the fees to be paid by the customer are fixed and determinable and collectability is reasonably assured. The Company considers delivery of its cloud-based software services has commenced once access to a configured and live instance to its platform has been granted to the customer. The Company’s arrangements generally contain multiple elements comprised of software services and professional services. The Company evaluates each element in an arrangement to determine whether it represents a separate unit of accounting. An element constitutes a separate unit of accounting when the delivered item has standalone value and delivery of the undelivered element is probable and within the Company’s control. When multiple deliverables included in an arrangement are separable into different units of accounting, the arrangement consideration is allocated to the identified units of accounting based on their relative selling price. Multiple deliverable arrangements accounting guidance provides a hierarchy to use when determining the relative selling price for each unit of accounting. Vendor-specific objective evidence (“VSOE”) of selling price, based on the price at which the item is regularly sold by the vendor on a standalone basis, should be used if it exists. If VSOE of selling price is not available, third-party evidence (“TPE”) of selling price is used to establish the selling price if it exists. VSOE and TPE do not currently exist for any of the Company’s deliverables. Accordingly, for arrangements with multiple deliverables that can be separated into different units of accounting, the arrangement consideration is allocated to the separate units of accounting based on the Company’s best estimate of selling price. The amount of arrangement consideration allocated is limited by contingent revenues, if any. The Company has established standalone value for Benefitfocus Marketplace implementation services in the Employer segment. Accordingly, revenues related to implementation services for the Benefitfocus Marketplace solution in the Employer segment are recognized separately from the revenues earned from the Employer software subscription services. Revenues related to such implementation services are recognized at the time that the professional services have been completed. Certain of the Company’s other professional services, including implementation services related to the Carrier segment, are not sold separately from the software services and there is no alternative use for them. As such, the Company has determined that those professional services do not have standalone value. Accordingly, software services and professional services are combined and recognized as a single unit of accounting. The Company generally recognizes software services fees monthly based on the number of employees covered by the relevant benefits plans at contracted rates for a specified period of time, once the criteria for revenue recognition described above have been satisfied. The Company recognizes revenue on Benefitfocus Marketplace implementation services in the Employer segment that have standalone value at the time the services have been completed and the related software services have commenced. The Company defers recognition of revenue for fees from professional services that do not have standalone value and begins recognizing such revenue once the services are delivered and the related software services have commenced, ratably over the longer of the contract term or the estimated expected life of the customer relationship. Costs incurred by the Company in connection with providing such professional services are charged to expense as incurred and are included in “Cost of revenue.” Concentrations of Credit Risk The Company’s financial instruments that are exposed to concentrations of credit risk consist primarily of cash equivalents, marketable securities and accounts receivable. All of the Company’s cash and cash equivalents are held at financial institutions that management believes to be of high credit quality. The bank deposits of the Company might, at times, exceed federally insured limits and are generally uninsured and uncollateralized. The Company has not experienced any losses on cash and cash equivalents to date. To manage credit risk related to marketable securities, the Company invests in various types of highly rated corporate bonds, commercial paper, and various U.S. government backed securities with maturities of less than two years. The weighted average maturity of the portfolio of investments must not exceed nine months, per the Company’s investment policy. To manage accounts receivable risk, the Company evaluates the creditworthiness of its customers and maintains an allowance for doubtful accounts. Accounts receivable are unsecured and derived from revenue earned from customers located in the United States. Mercer LLC (“Mercer”), a related party, represented approximately 14% of the total accounts receivable at December 31, 2016. Revenue from Mercer was approximately 10% and 12% of the total revenue for the three months ended June 30, 2017 and 2016, respectively and 11% in each of the six-month periods ended June 30, 2017 and 2016. For more information regarding Mercer revenue, please see Note 11. Accounts receivable from one other customer approximated 13% of the total accounts receivable at December 31, 2016. Accounts Receivable and Allowance for Doubtful Accounts and Returns Accounts receivable are stated at realizable value, net of allowances for doubtful accounts and returns. The Company utilizes the allowance method to provide for doubtful accounts based on management’s evaluation of the collectability of amounts due, and other relevant factors. Bad debt expense is recorded in general and administrative expense on the consolidated statements of operations and comprehensive loss. The Company’s estimate is based on historical collection experience and a review of the current status of accounts receivable. Historically, actual write-offs for uncollectible accounts have not significantly differed from the Company’s estimates. The Company removes recorded receivables and the associated allowances when they are deemed permanently uncollectible. However, if bad debts are higher than expected, future write-offs will be greater than the Company’s estimates. The allowance for doubtful accounts was $708 and $691 as of June 30, 2017 and December 31, 2016, respectively. The allowances for returns are accounted for as reductions of revenue and are estimated based on the Company’s periodic assessment of historical experience and trends. The Company considers factors such as the time lag since the initiation of revenue recognition, historical reasons for adjustments, new customer volume, complexity of billing arrangements, timing of software availability, and past due customer billings. The allowance for returns was $3,312 and $3,904 as of June 30, 2017 and December 31, 2016, respectively. Capitalized Software Development Costs The Company capitalizes certain costs related to its software developed or obtained for internal use. Costs related to preliminary project activities and post-implementation activities are expensed as incurred. Internal and external costs incurred during the application development stage, including upgrades and enhancements representing modifications that will result in significant additional functionality, are capitalized. Software maintenance and training costs are expensed as incurred. Capitalized costs are recorded as part of property and equipment and are amortized on a straight-line basis to cost of revenue over the software’s estimated useful life, which is three years. The Company evaluates these assets for impairment whenever events or changes in circumstances occur that could impact the recoverability of these assets. In the three months ended June 30, 2017 and 2016, the Company capitalized software development costs of $1,102 and $1,501, respectively, and amortized capitalized software development costs of $794 and $693, respectively. In the six months ended June 30, 2017 and 2016, the Company capitalized software development costs of $2,329 and $2,985, respectively, and amortized capitalized software development costs of $1,625 and $1,319, respectively. The net book value of capitalized software development costs was $7,139 and $6,435 at June 30, 2017 and December 31, 2016, respectively. Comprehensive Loss The Company’s net loss equals comprehensive loss for all periods presented. Recently Adopted Accounting Standards The Company adopted the guidance in Accounting Standards Update ("ASU") 2016-09, “Compensation - Stock Compensation (Topic 718) - Improvements to Employee Share-Based Payment Accounting,” on January 1, 2017. Under this ASU, entities are permitted to make an accounting policy election to either estimate forfeitures on share-based payment awards, as previously required, or to recognize forfeitures as they occur. The Company has elected to recognize forfeitures as they occur and the impact of that change in accounting policy has been recorded as a $391 cumulative effect adjustment to its accumulated deficit as of January 1, 2017. Additionally, ASU 2016-09 requires that all income tax effects related to settlements of share-based payment awards be reported in earnings as an increase or decrease to income tax expense (benefit), net. Previously, income tax benefits at settlement of an award were reported as an increase (or decrease) to additional paid-in capital to the extent that those benefits were greater than (or less than) the income tax benefits reported in earnings during the award's vesting period. The requirement to report those income tax effects in earnings has been applied on a prospective basis to settlements occurring on or after January 1, 2017 and the impact of applying that guidance was not material to the condensed consolidated financial statements for the three and six months ended June 30, 2017. ASU 2016-09 also requires that all income tax-related cash flows resulting from share-based payments be reported as operating activities in the statement of cash flows. Previously, income tax benefits at settlement of an award were reported as a reduction to operating cash flows and an increase to financing cash flows to the extent that those benefits exceeded the income tax benefits reported in earnings during the award's vesting period. The Company has elected to apply that change in cash flow classification on a prospective basis. However, there is no impact to the statement of cash flows for the three and six months ended June 30, 2017 as the Company did not have any cash flows related to excess tax benefits during that time. The remaining provisions of ASU 2016-09 did not have a material impact on the accompanying consolidated financial statements. Accounting Standards Not Yet Adopted In May 2017, the FASB issued ASU No. 2017-09, “Compensation—Stock Compensation (Topic 718): Scope of Modification Accounting.” The purpose of this ASU is to reduce both the diversity in practice and the cost and complexity when applying Topic 718 to a change to the terms and conditions of share-based payment awards. This guidance is effective for the Company beginning January 1, 2018. Early adoption is permitted. The amendments in this ASU should be applied prospectively to an award modified on or after the adoption date. The Company is currently evaluating the impact of this updated standard on its consolidated financial statements. In June 2016, the FASB issued ASU No. 2016-13, “Financial Instruments – Credit Losses (Topic 326): Measurement of Credit Losses on Financial Instruments.” The purpose of this ASU is to require a financial asset measured at amortized cost basis to be presented at the net amount expected to be collected. Credit losses relating to available-for-sale debt securities should be recorded through an allowance for credit losses. This ASU is effective for interim and annual reporting periods starting January 1, 2020. The Company is currently evaluating the impact of this guidance on its consolidated financial statements. In February 2016, the FASB issued ASU No. 2016-02, “Leases (Topic 842).” The amendments in this update require lessees, among other things, to recognize lease assets and lease liabilities on the balance sheet for those leases classified as operating leases under previous authoritative guidance. This update also introduces new disclosure requirements for leasing arrangements. ASU 2016-02 will be effective for the Company beginning January 1, 2019, but early adoption is permitted. The Company is currently evaluating the impact of this update on the consolidated financial statements. In May 2014, the FASB issued ASU No. 2014-09, “Revenue from Contracts with Customers (Topic 606)”, which amends the revenue recognition requirements in the FASB Accounting Standards Codification. Under the new standard, revenue is recognized when a customer obtains control of promised goods or services and is recognized in an amount that reflects the consideration that the entity expects to receive in exchange for those goods and services. In addition, the standard requires disclosure of the nature, amount, timing, and uncertainty of revenue and cash flows arising from contracts with customers. The FASB has recently issued several amendments to the standard, including clarification on accounting for licenses of intellectual property and identifying performance obligations. The standard permits two methods of adoption: retrospectively to each prior reporting period presented (full retrospective), or retrospectively with the cumulative effect of initially applying this statement recognized at the date of initial application (modified retrospective transition method). The new standard will be effective for the Company beginning January 1, 2018, with an option to early adopt. The Company plans to adopt the standard on the effective date but has not made a determination on the adoption method. The Company is currently assessing the impact of the new standard on its accounting policies, processes, and controls, including system requirements, and has assigned internal resources and engaged third party service providers to assist in its assessment. Based on the Company’s current assessment, areas affected by the Company’s adoption of the revenue recognition standard will be related to the estimation of variable consideration, the accounting for contract modifications, and the allocation of the transaction price to the Company’s multiple performance obligations. In addition, the Company expects an impact from the adoption of the new standard related to the Company’s costs to fulfill certain contracts as well as its costs to obtain contracts with customers, which are both currently expensed as incurred. The Company is also continuing to review the impact of this standard on potential disclosure changes in its consolidated financial statements as well as the transition approach that will be applied. While the Company continues to assess the potential impacts of the new standard, including the areas described above, and anticipates the standard could have a material impact on its consolidated financial statements, the Company does not know or cannot reasonably estimate quantitative information related to the impact of the new standard on the Company’s financial statements at this time. |