| Basis of Presentation | Basis of Presentation Company Overview - Progress Software Corporation ("Progress," the "Company," "we," "us," or "our") offers the leading platform for developing and deploying strategic business applications. We enable customers and partners to deliver modern, high-impact digital experiences with a fraction of the effort, time and cost. Progress offers powerful tools for easily building adaptive user experiences across any type of device or touchpoint, award-winning machine learning that enables cognitive capabilities to be a part of any application, the flexibility of a serverless cloud to deploy modern apps, business rules, web content management, plus leading data connectivity technology. Over 1,700 ISVs, 100,000 enterprise customers, and 2 million developers rely on Progress to power their applications. Our products are generally sold as perpetual licenses, but certain products also use term licensing models and our cloud-based offerings use a subscription-based model. More than half of our worldwide license revenue is realized through relationships with indirect channel partners, principally application partners and original equipment manufacturers ("OEMs"). Application partners are ISVs that develop and market applications using our technology and resell our products in conjunction with sales of their own products that incorporate our technology. OEMs are companies that embed our products into their own software products or devices. We operate in North America and Latin America (the "Americas"); Europe, the Middle East and Africa ("EMEA"); and the Asia Pacific region, through local subsidiaries as well as independent distributors. Basis of Presentation and Significant Accounting Policies - We prepared the accompanying unaudited condensed consolidated financial statements pursuant to the rules and regulations of the Securities and Exchange Commission ("SEC") regarding interim financial reporting. Accordingly, they do not include all of the information and footnotes required by accounting principles generally accepted in the United States of America ("GAAP") for complete financial statements and these unaudited financial statements should be read in conjunction with the audited financial statements included in our Annual Report on Form 10-K for the fiscal year ended November 30, 2018 , ("Annual Report on Form 10-K for the fiscal year ended November 30, 2018 "). We adopted Accounting Standards Update No. 2014-09, Revenue from Contracts with Customers ("ASC 606") effective December 1, 2018 using the full retrospective method, which required us to retroactively adjust comparative prior periods to conform to current presentation. See " Recently Adopted Accounting Pronouncements " below for further information. We made no material changes in the application of our significant accounting policies that were disclosed in our Annual Report on Form 10-K for the fiscal year ended November 30, 2018 , except as discussed below with respect to our adoption of ASC 606. We have prepared the accompanying unaudited condensed consolidated financial statements on the same basis as the audited financial statements included in our Annual Report on Form 10-K for the fiscal year ended November 30, 2018 , and these financial statements include all adjustments, consisting only of normal recurring adjustments, necessary for a fair presentation of the results of the interim periods presented. The operating results for the interim periods presented are not necessarily indicative of the results expected for the full fiscal year. Use of Estimates The preparation of financial statements requires management to make estimates and assumptions that affect the amounts reported in the financial statements and accompanying notes. On an on-going basis, management evaluates its estimates and records changes in estimates in the period in which they become known. These estimates are based on historical data and experience, as well as various other assumptions that management believes to be reasonable under the circumstances. The most significant estimates relate to: the timing and amounts of revenue recognition, including the determination of the nature and timing of the satisfaction of performance obligations, the standalone selling price of performance obligations, and the transaction price allocated to performance obligations; the realization of tax assets and estimates of tax liabilities; fair values of investments in marketable securities; assets held for sale; intangible assets and goodwill valuations; the recognition and disclosure of contingent liabilities; the collectability of accounts receivable; and assumptions used to determine the fair value of stock-based compensation. Actual results could differ from those estimates. Revenue Recognition Revenue Policy We derive our revenue primarily from software licenses and maintenance and services. Our license arrangements generally contain multiple performance obligations, including software maintenance services. Revenue is recognized when a customer obtains control of promised goods or services in an amount that reflects the consideration that we expect to receive in exchange for those goods or services. When an arrangement contains multiple performance obligations, we account for individual performance obligations separately if they are distinct. We recognize revenue through the application of the following steps: (i) identification of the contract(s) with a customer; (ii) identification of the performance obligations in the contract; (iii) determination of the transaction price; (iv) allocation of the transaction price to performance obligations in the contract; and (v) recognition of revenue when or as we satisfy the performance obligations. Sales taxes collected from customers and remitted to government authorities are excluded from revenue and we do not license our software with a right of return. Software Licenses Software licenses are on-premise and fully functional when made available to the customer. As the customer can use and benefit from the license on its own, on-premise software licenses represent distinct performance obligations. Revenue is recognized upfront at the point in time when control is transferred, which is defined as the point in time when the client can use and benefit from the license. Our licenses are sold as perpetual or term licenses, and the arrangements typically contain various combinations of maintenance and services, which are generally accounted for as separate performance obligations. We use the residual approach to allocate the transaction price to our software license performance obligations because, due to the pricing of our licenses being highly variable, they do not have an observable stand-alone selling price ("SSP"). As required, we evaluate the residual approach estimate compared to all available observable data in order to conclude the estimate is representative of its SSP. Perpetual licenses are generally invoiced upon execution of the contract and payable within 30 days. Term licenses are generally invoiced in advance on an annual basis over the term of the arrangement, which is typically one to three years. Any difference between the revenue recognized and the amount invoiced to the customer is recognized on our consolidated balance sheets as unbilled receivables until the customer is invoiced, at which point the amount is reclassed to accounts receivable. Maintenance Maintenance revenue is made up of technical support, bug fixes, and when-and-if available unspecified software upgrades. As these maintenance services are considered to be a series of distinct services that are substantially the same and have the same duration and measure of progress, we have concluded that they represent one combined performance obligation. Revenue is recognized ratably over the contract period. The SSP of maintenance services is a percentage of the net selling price of the related software license, which has remained within a tight range and is consistent with the stand-alone pricing of subsequent maintenance renewals. Maintenance services are generally invoiced in advance on an annual basis over the term of the arrangement, which is typically one to three years. Services Services revenue primarily includes consulting and customer education services. In general, services are distinct performance obligations. Services revenue is generally recognized as the services are delivered to the customer. We apply the practical expedient of recognizing revenue upon invoicing for time and materials-based arrangements as the invoiced amount corresponds to the value of the services provided. The SSP of services is based upon observable prices in similar transactions using the hourly rates sold in stand-alone services transactions. Services are either sold on a time and materials basis or prepaid upfront. We also offer products via a software-as-a-service ("SaaS") model, which is a subscription-based model. Our customers can use hosted software over the contract period without taking possession of it and the cloud services are available to them throughout the entire term, even if they do not use the service. Revenue related to SaaS offerings is recognized ratably over the contract period. The SSP of SaaS performance obligations is determined based upon observable prices in stand-alone SaaS transactions. SaaS arrangements are generally invoiced in advance on a monthly, quarterly, or annual basis over the term of the arrangement, which is typically one to three years. Arrangements with Multiple Performance Obligations When an arrangement contains multiple performance obligations, we account for individual performance obligations separately if they are distinct. We allocate the transaction price to each performance obligation in a contract based on its relative SSP. Although we do not have a history of offering these elements, prior to allocating the transaction price to each performance obligation, we consider whether the arrangement has any discounts, material rights, or specified future upgrades that may represent additional performance obligations. Determining whether products and services are distinct performance obligations and the determination of the SSP may require significant judgment. Contract Balances Unbilled Receivables and Contract Assets The timing of revenue recognition may differ from the timing of customer invoicing. When revenue is recognized prior to invoicing and the right to the amount due from customers is conditioned only on the passage of time, we record an unbilled receivable on our condensed consolidated balance sheets. Our multi-year term license arrangements, which are typically billed annually, result in revenue recognition in advance of invoicing and the recognition of unbilled receivables. As of February 28, 2019 , invoicing of our long-term unbilled receivables is expected to occur as follows (in thousands): 2020 $ 1,048 2021 1,089 2022 444 Total $ 2,581 Contract assets, which arise when revenue is recognized prior to invoicing and the right to the amount due from customers is conditioned on something other than the passage of time, such as the completion of a related performance obligation, were minimal as of February 28, 2019 and November 30, 2018. These amounts are included in unbilled receivables or long-term unbilled receivables on our condensed consolidated balance sheets. Deferred Revenue Deferred revenue is recorded when revenue is recognized subsequent to customer invoicing. Our deferred revenue balance is primarily made up of deferred maintenance from our OpenEdge and Application Development and Deployment segments. As of February 28, 2019 , the changes in deferred revenue were as follows (in thousands): Balance, December 1, 2018 As Adjusted (1) $ 135,940 Billings and other 95,792 Revenue recognized (89,549 ) Balance, February 28, 2019 $ 142,183 (1) The Company adopted ASC 606 effective December 1, 2018 using the full retrospective method. Transaction price allocated to remaining performance obligations represents contracted revenue that has not yet been recognized, which includes deferred revenue and amounts that will be invoiced and recognized as revenue in future periods. As of February 28, 2019 , transaction price allocated to remaining performance obligations was $143 million . We expect to recognize approximately 92% of the revenue within the next year and the remainder thereafter. Deferred Contract Costs Deferred contract costs, which include certain sales incentive programs, are incremental and recoverable costs of obtaining a contract with a customer. Incremental costs of obtaining a contract with a customer are recognized as an asset if the expected benefit of those costs are longer than one year. We have applied the practical expedient to expense costs as incurred for costs to obtain a contract with a customer when the amortization period would have been one year or less. These costs include a large majority of our sales incentive programs as we have determined that annual compensation is commensurate with annual sales activities. Certain of our sales incentive programs do meet the requirements to be capitalized. Depending upon the sales incentive program and the related revenue arrangement, such capitalized costs are amortized over the longer of (i) the product life, which is generally three to five years; or (ii) the term of the related revenue contract. We determined that a three to five year product life represents the period of benefit that we receive from these incremental costs based on both qualitative and quantitative factors, which include customer contracts, industry norms, and product upgrades. Total deferred contract costs were minimal as of February 28, 2019 and November 30, 2018 and are included in other current assets and other assets on our condensed consolidated balance sheets. Amortization of deferred contract costs is included in sales and marketing expense on our condensed consolidated statement of operations and was minimal in all periods presented. Recent Accounting Pronouncements Recently Adopted Accounting Pronouncements In October 2016, the FASB issued Accounting Standards Update No. 2016-16, Income Taxes (Topic 740), 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. Under legacy GAAP, the recognition of current and deferred income taxes for an intra-entity transfer was prohibited until the asset has been sold to an outside party. We adopted this standard at the beginning of the first quarter of fiscal year 2019. Upon adoption, we reclassified approximately $3.4 million from non-current prepaid taxes, which is included in other assets on our consolidated balance sheet, to retained earnings as of December 1, 2018. In May 2014, the FASB issued Accounting Standards Update No. 2014-09, Revenue from Contracts with Customers (Topic 606) ("ASC 606"). Under this standard, revenue is recognized when a customer obtains control of promised goods or services in an amount that reflects the consideration that the entity expects to receive in exchange for those goods or services. The standard also requires new disclosures regarding the nature, amount, timing, and uncertainty of revenue and cash flows arising from contracts with customers and provides guidance on the recognition of costs related to obtaining customer contracts. We adopted this ASU effective December 1, 2018 in accordance with the full retrospective approach, which required us to retrospectively adjust certain previously reported results in the comparative prior periods presented. Upon adoption, we recorded a cumulative $31 million increase to our 2017 beginning retained earnings balance, a $15 million decrease to deferred revenue, a $28 million increase to unbilled receivables, and a $12 million increase to deferred tax liabilities. The revenue recognition related to accounting for the following transactions is most impacted by our adoption of this standard: • Revenue from term licenses with extended payment terms over the term of the agreement within our Data Connectivity and Integration segment - Under the applicable revenue recognition guidance for fiscal years 2018 and prior, these transactions were recognized when the amounts were billed to the customer. In accordance with ASC 606, revenue from term license performance obligations is recognized upon delivery and revenue from maintenance performance obligations is expected to be recognized over the contract term. To the extent that we enter into these transactions, revenue from term licenses with extended payment terms will be recognized prior to the customer being billed and we will recognize an unbilled receivable on the balance sheet. Accordingly, the recognition of license revenue is accelerated under ASC 606 as we historically did not recognize revenue until the amounts had been billed to the customer. • Revenue from transactions with multiple elements within our Application Development and Deployment segment (i.e., sales of perpetual licenses with maintenance and/or support) - Under the applicable revenue recognition guidance for fiscal years 2018 and prior, these transactions were recognized ratably over the associated maintenance period as the Company did not have vendor specific objective evidence ("VSOE") for maintenance or support. Under ASC 606, the requirement to have VSOE for undelivered elements that existed under prior guidance is eliminated. Accordingly, the Company will recognize a portion of the sales price as revenue upon delivery of the license instead of recognizing the entire sales price ratably over the maintenance period. The impact of the adoption of this standard on our previously reported consolidated balance sheets and consolidated statements of operations is as follows: Consolidated Balance Sheets November 30, 2018 (in thousands) As Reported Adjustments As Adjusted Assets Accounts receivable, net $ 58,450 $ 1,265 $ 59,715 Short-term unbilled receivables — 1,421 1,421 Long-term unbilled receivables — 1,811 1,811 Deferred tax assets 1,922 (956 ) 966 Other assets (1) 580,237 — 580,237 Total assets $ 640,609 $ 3,541 $ 644,150 Liabilities and shareholders’ equity Short-term deferred revenue 133,194 (9,984 ) 123,210 Long-term deferred revenue 15,127 (2,397 ) 12,730 Deferred tax liabilities 3,797 2,002 5,799 Other liabilities (2) 178,409 — 178,409 Retained earnings 71,242 13,883 85,125 Accumulated other comprehensive loss (28,213 ) 37 (28,176 ) Other equity (3) 267,053 — 267,053 Total liabilities and shareholders’ equity $ 640,609 $ 3,541 $ 644,150 (1) Includes cash and cash equivalents, short-term investments, other current assets, assets held for sale, property and equipment, net, intangible assets, net, goodwill, and other assets. (2) Includes current portion of long-term debt, net, accounts payable, accrued compensation and related taxes, dividends payable, income taxes payable, other accrued liabilities, long-term debt, net, and other noncurrent liabilities. (3) Includes common stock and additional paid-in capital. Consolidated Statements of Income February 28, 2018 (in thousands) As Reported Adjustments As Adjusted Revenue: Software licenses $ 25,343 $ 711 $ 26,054 Maintenance and services 68,704 652 69,356 Total revenue 94,047 1,363 95,410 Costs of revenue 16,903 — 16,903 Gross Profit 77,144 1,363 78,507 Operating expenses 59,376 — 59,376 Income from operations 17,768 1,363 19,131 Other expense, net (1,585 ) — (1,585 ) Income before income taxes 16,183 1,363 17,546 Provision for income taxes 3,271 543 3,814 Net income $ 12,912 $ 820 $ 13,732 Earnings per share: Basic $ 0.28 $ 0.02 $ 0.30 Diluted $ 0.27 $ 0.02 $ 0.29 Weighted average shares outstanding: Basic 46,529 — 46,529 Diluted 47,476 — 47,476 The adoption of ASC 606 had no impact on total cash from or used in operating, financing, or investing activities on our consolidated cash flow statements. Recently Issued Accounting Pronouncements Not Yet Adopted In August 2018, the FASB issued Accounting Standards Update No. 2018-15, Intangibles - Goodwill and Other - Internal-Use Software (Subtopic 350-40), Customer's Accounting for Implementation Costs Incurred in a Cloud Computing Arrangement That Is a Service Contract ("ASU 2018-15"). ASU 2018-15 amends current guidance to align the accounting for costs incurred in a hosting arrangement that is a service contract with the requirements for capitalizing costs associated with developing or obtaining internal-use software. Capitalized implementation costs must be expensed over the term of the hosting arrangement and presented in the same line item in the statement of income as the fees associated with the hosting element (service) of the arrangement. The guidance in ASU 2018-15 is effective for annual reporting periods beginning after December 15, 2019, with early adoption permitted. We are currently accounting for costs incurred in a cloud computing arrangement in accordance with the guidance provided in ASU 2018-15. In August 2017, the FASB issued Accounting Standards Update No. 2017-12, Derivatives and Hedging (Topic 815), Targeted Improvements to Accounting for Hedging Activities ("ASU 2017-12"). ASU 2017-12 intends to better align an entity's risk management activities and financial reporting for hedging relationships through changes to both the designation and measurement guidance for qualifying hedging relationships and the presentation of hedge results. The amendments expand and refine hedge accounting for both nonfinancial and financial risk components and align the recognition and presentation of the effects of the hedging instrument and the hedged item in the financial statements. The guidance in ASU 2017-12 is required for annual reporting periods beginning after December 15, 2018, with early adoption permitted. We are currently evaluating the effect that implementation of this update will have upon adoption on our consolidated financial position and results of operations. In January 2017, the FASB issued Accounting Standards Update No. 2017-04, Intangibles - Goodwill and Other (Topic 350), Simplifying the Test for Goodwill Impairment ("ASU 2017-04"). ASU 2017-04 amends Topic 350 to simplify the subsequent measurement of goodwill by eliminating Step 2 from the goodwill impairment test. This update requires the performance of an annual, or interim, goodwill impairment test by comparing the fair value of a reporting unit with its carrying amount. An impairment charge should be recognized for the amount by which the carrying amount exceeds the reporting unit's fair value. However, the loss recognized should not exceed the total amount of goodwill allocated to that reporting unit. The guidance in ASU 2017-04 is required for annual reporting periods beginning after December 15, 2019, with early adoption permitted. We are currently considering whether to adopt this update prior to the required adoption date. In February 2016, the FASB issued Accounting Standards Update No. 2016-02, Leases (Topic 842) ("ASU 2016-02"), which requires lessees to record most leases on their balance sheets, recognizing a lease liability for the obligation to make lease payments and a right-to-use asset for the right to use the underlying asset for the lease term. The guidance in ASU 2016-02 is required for annual reporting periods beginning after December 15, 2018, with early adoption permitted. We currently expect that most of our operating lease commitments will be subject to the update and recognized as operating lease liabilities and right-of-use assets upon adoption. However, we are currently evaluating the effect that implementation of this update will have upon adoption on our consolidated financial position and results of operations. |
