The Company and Summary of Significant Accounting Policies and Estimates | The Company and Summary of Significant Accounting Policies Company Guidewire Software, Inc., a Delaware corporation, was incorporated on September 20, 2001. Guidewire Software, Inc. together with its subsidiaries (the “Company”) provides a technology platform which consists of three key elements: core transaction processing, data management and analytics, and digital engagement. The Company’s technology platform supports core insurance operations, including underwriting, policy administration, claim management and billing, enables new insights into data that can improve business decision making and supports digital sales, service and claims experiences for policyholders, agents, and other key stakeholders. The Company’s customers are primarily insurance carriers for property and casualty insurance. Basis of Presentation and Consolidation Our consolidated financial statements have been prepared in accordance with generally accepted accounting principles in the United States of America (“U.S. GAAP”). The consolidated financial statements include the accounts of Guidewire Software, Inc. and its wholly-owned subsidiaries. All inter-company balances and transactions have been eliminated in consolidation. Use of Estimates The preparation of the accompanying consolidated financial statements in conformity with U.S. GAAP requires management to make estimates and assumptions about future events that affect the amounts of assets and liabilities reported, disclosures about contingent assets and liabilities, and reported amounts of revenues and expenses. Significant items subject to such estimates include, but are not limited to, revenue recognition, the useful lives of property and equipment and intangible assets, allowance for doubtful accounts, valuation allowance for deferred tax assets, stock-based compensation, annual bonus attainment, income tax uncertainties, valuation of goodwill and intangible assets, and contingencies. These estimates and assumptions are based on management’s best estimates and judgment. Management regularly evaluates its estimates and assumptions using historical experience and other factors; however, actual results could differ from these estimates. Foreign Currency The functional currency of the Company’s foreign subsidiaries is their respective local currency. The Company translates all assets and liabilities of foreign subsidiaries to U.S. dollars at the current exchange rate as of the applicable balance sheet date. Revenues and expenses are translated at the average exchange rate prevailing during the period in which the transactions occur. The effects of foreign currency translations are recorded in accumulated other comprehensive income/loss as a separate component of stockholders’ equity in the accompanying consolidated statements of stockholders’ equity. Transaction gains and losses from foreign currency transactions that arise from exchange rate fluctuations on transactions denominated in a currency other than the local functional currency are recorded as other income (expense) in the consolidated statements of operations. Cash and Cash Equivalents Cash and cash equivalents are comprised of cash and highly liquid investments with remaining maturities of 90 days or less at the date of purchase. Cash equivalents primarily consist of commercial paper and money market funds. Investments Management determines the appropriate classification of investments at the time of purchase based upon management’s intent with regard to such investments. All investments are classified as available-for-sale. The Company classifies investments as short-term when they have remaining contractual maturities of one year or less from the balance sheet date, and as long-term when the investments have remaining contractual maturities of more than one year from the balance sheet date. All investments are recorded at fair value with unrealized holding gains and losses included in accumulated other comprehensive (loss) income. Property and Equipment Property and equipment are stated at cost less accumulated depreciation and amortization. Depreciation is calculated on a straight-line basis over the estimated useful lives of the assets. Leasehold improvements are amortized over the shorter of the lease term or the estimated useful lives of the related assets. Maintenance and repairs that do not extend the life or improve an asset are expensed in the period incurred. The estimated useful lives of property and equipment are as follows: Computer hardware 3 years Purchased software 3 years Furniture and fixtures 3 years Leasehold improvements Shorter of the lease term or estimated useful life Software Development Costs Certain software development costs incurred subsequent to the establishment of technological feasibility are subject to capitalization and amortized over the estimated lives of the related products. Technological feasibility is established upon completion of a working model. Through July 31, 2017, costs incurred subsequent to the establishment of technological feasibility have not been material, and therefore, all software development costs have been charged to research and development expense in the accompanying consolidated statements of operations as incurred. For qualifying costs incurred for computer software developed for internal use, the Company begins to capitalize its costs to develop software when preliminary development efforts are successfully completed, management has authorized and committed project funding, and it is probable that the project will be completed and the software will be used as intended. These capitalized costs are amortized to expense over the estimated useful life of the related asset, generally estimated to be three years. Costs incurred prior to meeting these capitalization criteria and costs incurred for training and maintenance are expensed as incurred and recorded in research and development expense on the Company’s consolidated statements of operations. Capitalized software development costs are recorded in property and equipment on the Company’s consolidated balance sheet as of July 31, 2017. Business Combinations The Company uses its best estimates and assumptions to assign fair value to the tangible and intangible assets acquired and liabilities assumed at the acquisition date. Goodwill is calculated as the difference between the acquisition-date fair value of the consideration transferred and the values assigned to the assets acquired and liabilities assumed. The Company’s estimates of fair value are based upon assumptions believed to be reasonable, but which are inherently uncertain and subject to refinement and, as a result, actual results may differ from estimates. During the measurement period, which may be up to one year from the acquisition date, if new information is obtained about facts and circumstances that existed as of the acquisition date, the Company may record adjustments to the fair value of these assets and liabilities, with the corresponding offset to goodwill. During the year ended July 31, 2016, the Company adopted ASU 2015-16, “Simplifying the Accounting for Measurement-Period Adjustments (Topic 805)” (“ASU 2015-16”), which requires the cumulative impact of measurement period adjustments (including the impact on prior periods) to be recognized in the reporting period in which the adjustments are identified. Upon the conclusion of the measurement period or final determination of the fair value of assets acquired or liabilities assumed, whichever comes first, any subsequent adjustments are recorded to the Company’s consolidated statements of operations. Impairment of Long-Lived Assets, Intangible Assets and Goodwill The Company evaluates its long-lived assets, consisting of property and equipment and intangible assets, for indicators of possible impairment when events or changes in circumstances indicate that the carrying amount of certain assets may not be recoverable. Impairment exists if the carrying amounts of such assets exceed the estimates of future net undiscounted cash flows expected to be generated by such assets. Should impairment exist, the impairment loss would be measured based on the excess carrying value of the assets over the estimated fair value of the assets. The Company has not written down any of its long-lived assets as a result of impairment during any of the periods presented. The Company tests goodwill for impairment annually during the fourth quarter of each fiscal year and in the interim whenever events or changes in circumstances indicate that the carrying amount may not be recoverable. The Company evaluates qualitative factors to determine whether it is more likely than not that the fair value of a reporting unit is less than its carrying amount as a basis for determining whether it is necessary to perform the two-step goodwill impairment test. In performing the qualitative assessment, the Company considers events and circumstances, including but not limited to, macroeconomic conditions, industry and market considerations, cost factors, overall financial performance, changes in management or key personnel, changes in strategy, changes in customers, changes in the composition or carrying amount of a reporting unit’s net assets and changes in the price of the Company’s common stock. If, after assessing the totality of events or circumstances, the Company determines that it is more likely than not that the fair value of a reporting unit is greater than its carrying amount, then the two-step goodwill impairment test is not performed. There have been no goodwill impairments during any of the periods presented. Concentration of Credit Risk Financial instruments that potentially subject the Company to concentrations of credit risk consist of cash, cash equivalents, investments and accounts receivable. The Company maintains its cash, cash equivalents and investments with high quality financial institutions. The Company is exposed to credit risk for cash held in financial institutions in the event of a default to the extent that such amounts recorded on the balance sheet are in excess of amounts that are insured by the Federal Deposit Insurance Corporation (“FDIC”). No customer individually accounted for 10% or more of the Company’s revenues for the years ended July 31, 2017 , 2016 and 2015 . As of July 31, 2017 , one customer accounted for 11% of the Company’s total accounts receivable. As of July 31, 2016, No customer individually accounted for 10% or more of the Company’s total accounts receivable. Accounts Receivable and Allowance for Doubtful Accounts Accounts receivable are recorded at invoiced amounts, net of the Company’s estimated allowances for doubtful accounts. The allowance for doubtful accounts is estimated based on an assessment of the Company’s ability to collect on customer accounts receivable, and there is judgment involved in such assessment. The Company regularly reviews the allowance by considering relevant factors such as historical experience, industry data, credit quality, age of accounts receivable balances, customers’ financial condition and current economic conditions that may affect a customer’s ability to pay. The Company has had no allowance for doubtful accounts in any of the periods presented. The Company’s accounts receivable are not collateralized by any security. Revenue Recognition The Company enters into arrangements to deliver multiple products or services (multiple-elements). For a substantial majority of its sales, the Company applies software revenue recognition rules and allocates the total revenues among elements based on vendor-specific objective evidence (“VSOE”) of the fair value of each element. The Company recognizes revenue on a net basis excluding indirect taxes, such as sales tax and value added tax, collected from customers and remitted to government authorities. Revenues are derived from three sources: (i) License fees, related to term (or time-based) licenses, perpetual software licenses, and other software subscription models including those from recently acquired companies; (ii) Maintenance fees, related to email and phone support, bug fixes and unspecified software updates and upgrades released when, and if available during the maintenance term; and (iii) Services fees from professional services related to implementation of the Company’s software, reimbursable travel and training. Revenues are recognized when all of the following criteria are met: • Persuasive evidence of an arrangement exists. Evidence of an arrangement consists of a written contract signed by both the customer and management prior to the end of the period. • Delivery or performance has occurred . The Company’s software is delivered electronically to the customer. Delivery is considered to have occurred when the Company provides the customer access to the software along with login credentials. • Fees are fixed or determinable. The Company assesses whether a fee is fixed or determinable at the outset of the arrangement, primarily based on the payment terms associated with the transaction. Fees from term licenses are invoiced in annual or quarterly installments over the term of the agreement beginning on the effective date of the license. A significant majority are invoiced annually. Perpetual license fees are generally due between 30 and 60 days from delivery of software. Generally, the Company offers extended payment terms to its customers for term licenses. As a result, term license fees are not considered to be fixed and determinable until they become due or payment is received. • Collectability is probable. Collectability is assessed on a customer-by-customer basis, based primarily on creditworthiness as determined by credit checks and analysis, as well as customer payment history. Payment terms generally range from 30 to 90 days from invoice date. If it is determined prior to revenue recognition that collection of an arrangement fee is not probable, revenues are deferred until collection becomes probable or cash is collected, assuming all other revenue recognition criteria are satisfied. VSOE of fair value does not exist for the Company’s software licenses; therefore, the Company allocates revenues to software licenses using the residual method. Under the residual method, the amount recognized for license fees is the difference between the total fixed and determinable fees and the VSOE of fair value for the undelivered elements under the arrangement. The VSOE of fair value for elements of an arrangement is based upon the normal pricing and discounting practices for those elements when sold separately. VSOE of fair value for maintenance is established using the stated maintenance renewal rate in the customer’s contract. For term licenses with duration of one year or less, no VSOE of fair value for maintenance exists. VSOE of fair value for services is established if a substantial majority of historical stand-alone selling prices for a service fall within a reasonably narrow price range. If the undelivered elements are all service elements and VSOE of fair value does not exist for one or more service element, the total arrangement fee is recognized ratably over the longest service period starting at software delivery, assuming all the related services have been made available to the customer. Substantially all of the Company’s professional services engagements are billed on a time and materials basis. Services are typically not considered to be essential to the functionality of the software and the related revenues and costs are recognized in the period incurred. In select situations, the Company will contract its professional services on a fixed fee basis. In these situations, if reliable estimates of total project costs are available, the Company recognizes services revenues on a proportional performance basis as the performance obligations are completed by using the ratio of labor hours to date as an input measure compared to total estimated labor hours for the consulting services. If reliable estimates of total project costs cannot be made, the zero gross margin or the completed contract method is applied to revenues and direct costs. Under the zero gross margin method, revenues recognized are limited to the direct costs incurred for the implementation services. Under the completed contract method, revenues and direct costs are deferred until the project is complete. When the zero gross margin method is applied for lack of reliable project estimates and subsequently project estimates become reliable, the Company switches to the percentage-of-completion method, resulting in a cumulative effect adjustment for deferred license revenues to the extent of progress toward completion, and the related portion of the deferred professional service margin is recognized in full as revenues. In the limited cases where professional services are deemed to be essential to the functionality of the software, the arrangement is accounted for using contract accounting until the essential services are complete. If reliable estimates of total project costs can be made, the Company applies the percentage-of-completion method whereby percentage toward completion is measured by using the ratio of service billings to date compared to total estimated service billings for the consulting services. Service billings approximate labor hours as an input measure since they are generally billed monthly on a time and material basis. The fees related to the maintenance are recognized over the period the maintenance is provided. The Company sells some of its software licenses on a subscription basis and the related revenues are recognized ratably over the term of the arrangement typically upon provisioning the products. As noted above, the Company generally invoices fees for licenses and maintenance to its customers in annual or quarterly installments payable in advance. Deferred revenues represent amounts, which are billed to or collected from creditworthy customers for which one or more of the revenue recognition criteria have not been met. The deferred revenues balance does not represent the total contract value of annual or multi-year, non-cancellable arrangements. Sales Commissions Sales commissions are recognized as an expense when earned by the sales representative, generally occurring at the time the customer order is signed. Substantially all of the effort by the sales force is expended through the time of closing the sale, with limited to no involvement thereafter. Warranties The Company generally provides a warranty for its software products and services to its customers for periods ranging from 3 to 12 months . The Company’s software products are generally warranted to be free of defects in materials and workmanship under normal use and to substantially perform as described in published documentation. The Company’s services are generally warranted to be performed in a professional manner and to materially conform to the specifications set forth in the related customer contract. In the event there is a failure of such warranties, the Company generally will correct the problem or provide a reasonable workaround or replacement product. If the Company cannot correct the problem or provide a workaround or replacement product, then the customer’s remedy is generally limited to refund of the fees paid for the nonconforming product or services. Warranty expense has been insignificant to date. Advertising Costs Advertising costs are expensed as incurred and amounts incurred were not material during the years ended July 31, 2017 , 2016 and 2015 . Stock-Based Compensation The Company accounts for stock-based compensation using the fair value method, which requires the Company to measure the stock-based compensation based on the grant-date fair value of the awards and recognize the compensation expense over the requisite service period. The Company recognizes compensation expense net of estimated forfeitures. To date, the Company has granted stock options, time-based restricted stock units (“RSUs”), performance-based restricted stock units (“PSUs”), and beginning in the first quarter of fiscal 2017, restricted stock units that may be earned subject to the Company’s total shareholder return ranking relative to the software companies in the S&P Software and Services Select Industry Index for a specified performance period or specified performance periods, service periods, and in select cases, subject to certain performance conditions (“TSR PSUs”). The Company recognizes compensation expense for awards which contain only service conditions on a straight-line basis over the requisite service period, which is generally the vesting period of the respective awards. The Company recognizes the compensation cost for awards that contain either a performance condition, market conditions, or both using the graded vesting method. The fair value of the Company’s RSUs and PSUs equals the market value of the Company’s common stock on the date of grant. The Company estimates the grant date fair value of the Company’s stock options using the Black-Scholes option-pricing model. These awards are subject to time-based vesting, which generally occurs over a period of four years. The fair value of the Company’s TSR PSUs are estimated at the grant date using a Monte Carlo simulation method. The assumptions utilized in this simulation require judgments and estimates. Changes in these inputs and assumptions could affect the measurement of the estimated fair value of the related compensation expense. Compensation expense associated with these TSR PSUs will be recognized over the vesting period regardless of whether the market condition is ultimately satisfied, however, the expense will be reversed if a grantee terminates prior to satisfying the requisite service period. For TSR PSUs containing an additional performance condition, a portion of the expense will fluctuate depending on the achievement of the performance conditions. All TSR PSUs will vest at the end of a three-year period. Income Taxes Income taxes are accounted for under the asset and liability method. Under this method, the Company determines deferred tax assets and liabilities on the basis of the differences between the financial statement carrying amounts of existing assets and liabilities by using enacted tax rates in effect for the year in which the difference is expected to reverse. All deferred tax assets and liabilities are classified as non-current on its consolidated financial statements. Deferred tax assets related to excess tax benefits are recorded when utilized. The effect on deferred tax assets and liabilities of a change in tax rates is recognized in income in the period that includes the enactment date. A valuation allowance against deferred tax assets is recorded when it is more likely than not that some portion or all of such deferred tax assets will not be realized and is based on the positive and negative evidence about the future including future reversals of existing taxable temporary differences, projected future taxable income, tax-planning strategies, and results of recent operations. The effective tax rate in any given financial statement period may differ materially from the statutory rate. These differences may be caused by changes in the mix and level of income or losses, changes in the expected outcome of tax audits, changes in tax regulations, or changes in the deferred tax valuation allowance. The Company records interest and penalties related to unrecognized tax benefits as income tax expense in its consolidated statement of operations. Recent Accounting Pronouncements Improvements on Employee Share-Based Payment Accounting In March 2016, the FASB issued Accounting Standards Update No. 2016-09, Improvements on Employee Share-Based Payment Accounting (Topic 718) (“ASU 2016-09”), which simplifies several aspects of the accounting for employee share-based payment transactions for both public and nonpublic entities, including the accounting for income taxes, forfeitures, and statutory tax withholding requirements, as well as classification in the statement of cash flows. The guidance requires all of the tax effects related to share based payments to be recorded through the income statement. The guidance also removes the present requirement to delay recognition of a windfall tax benefit until it reduces current taxes payable; instead it is recognized at the time of settlement, subject to normal valuation allowance consideration. The standard is effective for public business entities for annual reporting periods beginning after December 15, 2016, and interim periods within that reporting period. Early adoption is permitted. The Company will adopt this standard effective on August 1, 2017. Upon adoption of this guidance the Company will change its accounting policy to account for forfeitures for share based awards as they occur and will record a cumulative effect adjustment to opening retained earnings. The amendments related to accounting for previously unrecognized excess tax benefits as deferred tax assets will be adopted on a modified retrospective basis with a cumulative effect adjustment to opening retained earnings, subject to valuation allowance considerations that we are still evaluating. Revenue from Contracts with Customers In May 2014, the FASB issued ASU No. 2014-09, Revenue from Contracts with Customers (Topic 606) (“ASU 2014-09”), which provides guidance for revenue recognition. This ASU affects any entity that either enters into contracts with customers to transfer goods or services or enters into contracts for the transfer of non-financial assets. This ASU will supersede the revenue recognition requirements in Topic 605, Revenue Recognition, and most industry-specific guidance. In August 2015, the FASB issued ASU No. 2015-14, Revenue from Contracts with Customers (Topic 606): Deferral of the Effective Date (“ASU 2015-14”), deferring the effective date of this standard. As a result, the ASU and related amendments will be effective for the Company for its fiscal year beginning August 1, 2018, including interim periods within that fiscal year. Early adoption is permitted, but not before the original effective date of the ASU, August 1, 2017. Subsequently, the FASB issued ASU No. 2016-08, Principal Versus Agent Consideration (or Reporting Revenue Gross versus Net) (“ASU 2016-08”) in March 2016, ASU No. 2016-10, Identifying Performance Obligations and Licensing in April 2016, and ASU No. 2016-12, Narrow-Scope Improvements and Practical Expedients in May 2016. These amendments clarified certain aspects of Topic 606 and have the same effective date as ASU 2014-09. The Company will adopt these ASUs (collectively, Topic 606) on August 1, 2018. Topic 606 permits two methods of adoption: retrospectively to each prior reporting period presented (the “Full Retrospective Method”), or retrospectively with the cumulative effect of initially applying the guidance recognized at the date of initial application (the “Modified Retrospective Method”). The Company currently intends to apply the Modified Retrospective Method. The Company has evaluated the potential impact of Topic 606 on its revenue recognition policy and practices and has concluded that Topic 606 will impact the pattern of its revenue recognition associated with its software licenses. The Company’s term licenses require payments to be made annually or quarterly in advance and are subject to extended payment terms. Currently, revenues associated with the payment for term software licenses are recognized in the earlier of the period in which the payments are due or are actually made. Under Topic 606, the Company will be required to recognize the revenue associated with such payments not when they are made or due, but when control of the software license is transferred to the customer, which occurs at or near the time a contract with a customer is executed. As a result, under Topic 606, all contractually obligated payments under a term license that the Company reasonably expects to collect would be recognized upon delivery. In conjunction with its evaluation of this new standard, the Company began revising its contracting practices and amending existing agreements with certain customers primarily by shortening the initial, non-refundable term of its licenses. Since fiscal 2016, a substantial majority of new contracts feature a two-year initial term with subsequent one-year auto renewal options. The Company has engaged with its existing and prospective customers on its new licensing model. The Company continues to evaluate the other potential impacts that Topic 606 will have on its consolidated financial statements, internal controls, business processes, and information technology systems including, for example, how to account for commission expense and revenue models acquired from recent acquisitions. Business Combinations (Topic 805): Clarifying the Definition of a Business In January 2017, the FASB issued ASU No. 2017-01, Business Combinations (Topic 805): Clarifying the Definition of a Business (“ASU 2017-01”), which provides a more robust framework to use in determining when a set of assets and activities is a business. The standard will be effective for the Company beginning August 1, 2018. Based on its current assessment, the Company does not expect the adoption of this update to have a material impact on its consolidated financial statements. Financial Instruments In January 2016, the FASB issued ASU 2016-01, Financial Instruments, which impacts certain aspects of recognition, measurement, presentation and disclosure of financial instruments. The standard will be effective for the Company beginning August 1, 2018. The Company is currently evaluating the effect the updated standard will have on its consolidated financial statements and related disclosures. Statement of Cash Flows (Topic 230): Restricted Cash In November 2016, the FASB issued ASU No. 2016-18, Statement of Cash Flows (Topic 230): Restricted Cash (“ASU 2016-18”), which requires the statement of cash flows to report changes in cash, cash equivalents, and restricted cash. The standard will be effective for the Company beginning August 1, 2018. Based on its current assessment, the Company does not expect the adoption of this update to have a material impact on its consolidated financial statements. Statement of Cash Flows (Topic 230): Classification of Certain Cash Receipts and Cash Payments In August 2016, the FASB issued ASU No. 2016-15, Statement of Cash Flows (Topic 230): Classification of Certain Cash Receipts and Cash Payments (“ASU 2016-15”), which clarifies how companies present and classify certain cash receipts and cash payments in the statement of cash flows. The standard will be effective for the Company beginning August 1, 2018. Based on its current assessment, the Company does not expect the adoption of this update to have a material impact on its consolidated financial statements. Income Tax Consequences of an Intra-Entity Transfer of Assets Other Than Inventory In October 2016, the FASB issued ASU No. 2016-16, Income Taxes - Intra-Entity Transfers of Assets Other Than Inventory (“ASU 2016-16”), which requires entities to recognize the income tax consequences of an intra-entity transfer of an asset other than inventory when the transfer occurs. The new standard must be adopted using a modified retrospective transition method which is a cumulative-effective adjustment to retained earnings as of the beginning of the first effective reporting period. The standard will be effective for the Company beginning August 1, 2018. Based on its current assessment, the Company does not expect the adoption of this update to have a material impact on its consolidated financial statements. Scope of Modification Accounting In May 2017, the FASB issued ASU No. 2017-09, Scope of Modification Accounting (Topic 718) (“ASU 2017-09”), which amends the scope of modification accounting for share-based payment arrangements. ASU 2017-09 provides guidance on the types of changes to the terms or conditions of share-based payment awards to which an entity would be required to apply modification accounting under ASC 718. Specifically, an entity would not apply modification accounting if the fair value, vesting conditions, and classification of the awards are the same immediately before and after the modification. The new standard is effective for annual periods beginning after December 15, 2017 and interim periods within those years. Early adoption is permitted. The standard will be |