XML 18 R7.htm IDEA: XBRL DOCUMENT v3.7.0.1
Description of Business, Basis of Presentation and Consolidation and Significant Accounting Policies
6 Months Ended
Jun. 30, 2017
Accounting Policies [Abstract]  
Description of Business, Basis of Presentation and Consolidation and Significant Accounting Policies
Description of Business, Basis of Presentation and Consolidation and Significant Accounting Policies
Description of Business
Rapid7, Inc. and subsidiaries (“we,” “us” or “our”) is a leading provider of analytics for security and IT operations solutions that enable organizations to implement an active, analytics-driven approach to cyber security and IT operations.
Basis of Presentation and Consolidation
The accompanying unaudited consolidated financial statements have been prepared by us in accordance with accounting principles generally accepted in the United States of America (GAAP) as well as pursuant to the rules and regulations of the Securities and Exchange Commission (SEC) regarding interim financial reporting. Accordingly, certain information and note disclosures normally included in the financial statements prepared in accordance with GAAP have been condensed or omitted pursuant to such rules and regulations. These consolidated financial statements should be read in conjunction with the consolidated financial statements and related notes included in our Annual Report on Form 10-K for the year ended December 31, 2016 filed with the SEC on March 9, 2017.
The consolidated financial statements include our results of operations and those of our wholly-owned subsidiaries and reflect all adjustments (consisting solely of normal, recurring adjustments) which are, in the opinion of management, necessary for a fair statement of results for the interim periods presented. All intercompany transactions and balances have been eliminated in consolidation. The results of operations for the three and six months ended June 30, 2017 are not necessarily indicative of the results to be expected for any future period or the entire fiscal year.

Significant Accounting Policies

There have been no significant changes to our significant accounting policies as of and for the three and six months ended June 30, 2017, as compared to the significant accounting policies described in our Annual Report on Form 10-K for the year ended December 31, 2016.
Recent Accounting Pronouncements

In May 2017, the Financial Accounting Standards Board (FASB) issued Accounting Standards Update (ASU) 2017-09, Compensation-Stock Compensation (Topic 718): Scope of Modification Accounting, clarifying when a change to the terms or conditions of a share-based payment award must be accounted for as a modification. The ASU requires modification accounting if the fair value, vesting condition or the classification of the award is not the same immediately before and after a change to the terms and conditions of the award. The ASU will be effective for us on a prospective basis beginning on January 1, 2018, with early adoption permitted. This ASU is not expected to have an impact on our consolidated financial statements.
In October 2016, the FASB issued ASU 2016-16, Income Taxes (Topic 740): Intra-Entity Transfers of Assets Other Than Inventory. The ASU is intended to improve the accounting for the income tax consequences of intra-entity transfers of assets other than inventory. Current GAAP prohibits the recognition of current and deferred income taxes for an intra-entity asset transfer until the asset has been sold to an outside party. The ASU will allow an entity to recognize the income tax consequences of these transfers when the transfers occur. The ASU will be effective for us in the first quarter of 2018. We are currently evaluating the impact that the adoption of this ASU will have on our consolidated financial statements.
In March 2016, the FASB issued ASU 2016-09, Compensation-Stock Compensation (Topic 718): Improvements to Employee Share-Based Payment Accounting. The ASU is intended to simplify several aspects of the accounting for share-based payment transactions, including the accounting for income taxes, forfeitures and statutory tax withholding requirements, as well as classification on the statement of cash flows. We adopted this ASU on January 1, 2017 and as a result, we have made an accounting policy election to account for forfeitures as they occur. This change has been applied on a modified retrospective basis, resulting in a cumulative-effect adjustment to increase accumulated deficit by $0.1 million as of January 1, 2017. The adoption of this ASU also requires excess tax benefits and tax deficiencies be recorded in the income statement as opposed to additional paid-in capital when the awards vest or are settled, and has been applied on a prospective basis. In connection with the adoption of this ASU, we recorded a cumulative-effect adjustment as of January 1, 2017 to increase gross deferred tax assets and the related valuation allowance against deferred tax assets by $3.4 million. The provisions related to classification of excess tax benefits in the statement of cash flows were adopted prospectively, and as such, the prior periods were not retrospectively adjusted.
In February 2016, the FASB issued ASU 2016-02, Leases (Topic 842). The ASU requires companies to recognize on the balance sheet the assets and liabilities for the rights and obligations created by leased assets. The ASU will be effective for us in the first quarter of 2019, with early adoption permitted. We are currently evaluating the impact that the adoption of this ASU will have on our consolidated financial statements.
In May 2014, the FASB issued ASU 2014-09, Revenue from Contracts with Customers (Topic 606). The ASU outlines a single, comprehensive model for accounting for revenue from contracts with customers and requires more detailed disclosure to enable users of financial statements to understand the nature, amount, timing and uncertainty of revenue and cash flows arising from such contracts. In August 2015, the FASB issued ASU 2015-14, which provides a one-year deferral in the effective date of ASU 2014-09. ASU 2014-09 will now be effective for us beginning January 1, 2018; however, early adoption will be permitted as of the original effective date. We plan to adopt ASU 2014-09 in the first quarter of 2018 and expect to adopt on a modified retrospective basis. Under this method of adoption, we would recognize the cumulative effect of initially applying the standard as an adjustment to the opening balance of retained earnings in the period of initial application. Comparative prior year periods would not be adjusted.
We are currently evaluating the potential impact of this standard on our financial position and results of operations. Based on our analysis performed to date, we expect recognition of total revenue related to our term software licenses, managed services, cloud-based subscriptions and stand-alone professional services to remain substantially unchanged. We expect that revenue related to the sale of our AppSpider perpetual software licenses will be recognized at the time of license delivery because software licenses are not dependent on the continued delivery of content subscriptions. We currently recognize revenue related to the sale of our AppSpider perpetual software licenses over the contractual period of maintenance and support due to the lack of vendor-specific objective evidence (VSOE) of selling price of the maintenance and support. We expect that revenue related to the sale of our Nexpose and Metasploit perpetual software licenses will be combined with their related content subscriptions as a single performance obligation when our contracts contain a material right with respect to renewal options. As a result, we expect to recognize the revenue related to the sale of Nexpose and Metasploit perpetual software licenses ratably over the customer's estimated economic life, rather than over the contractual period of maintenance and support.
In addition, under the new standard, for software licenses that are sold with professional services in a multiple-element arrangement, the professional services will likely represent a separate performance obligation and we will recognize revenue associated with the professional services as such services are performed. Revenue associated with professional services in a multiple-element arrangement is currently recognized ratably over the related contractual period of maintenance and support (typically one to three years) due to the lack of VSOE of selling price for the contractual elements. In addition, under the new standard, we expect the allocation of contract consideration for multiple-element arrangements to be on a relative fair value basis which may impact both the timing of income recognition and the presentation of revenue by class.
Further, under the new standard, we expect to capitalize certain direct and incremental commission costs to obtain a contract and amortize such costs over the customer's estimated economic life rather than expensing them as incurred in the period that the commissions are earned by our employees (which is typically upon signing of an arrangement).