XML 19 R7.htm IDEA: XBRL DOCUMENT
v3.6.0.2

Summary of Significant Accounting Policies | 12 Months Ended
--- | ---
Dec. 31, 2016
Accounting Policies [Abstract] |
Summary of Significant Accounting Policies | SUMMARY OF SIGNIFICANT ACCOUNTING POLICIES DESCRIPTION OF BUSINESS We provide integrated software systems and related services for the public sector, with a focus on local governments. We develop and market a broad line of software solutions and services to address the information technology (“IT”) needs of cities, counties, schools and other local government entities. In addition, we provide professional IT services, including software and hardware installation, data conversion, training, and for certain customers, product modifications, along with continuing maintenance and support for customers using our systems. We also provide subscription-based services such as software as a service (“SaaS”) arrangements, which utilize the Tyler private cloud, and electronic document filing solutions (“e-filing”). In addition, we provide property appraisal outsourcing services for taxing jurisdictions. PRINCIPLES OF CONSOLIDATION The consolidated financial statements include our parent company and a subsidiary, which is wholly-owned. All significant intercompany balances and transactions have been eliminated in consolidation. Comprehensive income (loss) is defined as the change in equity of a business enterprise during a period from transactions, and other events and circumstances from non-owner sources and includes all components of net income (loss) and other comprehensive income (loss). We had no items of other comprehensive income (loss) during the years ended December 31, 2016, 2015 and 2014. CASH AND CASH EQUIVALENTS Cash in excess of that necessary for operating requirements is invested in short-term, highly liquid, income-producing investments. Investments with original maturities of three months or less are classified as cash and cash equivalents, which primarily consist of cash on deposit with several banks and money market funds. Cash and cash equivalents are stated at cost, which approximates market value. REVENUE RECOGNITION We earn revenue from software licenses, royalties, subscription-based services, software services, post-contract customer support (“PCS” or “maintenance”), hardware, and appraisal services. Software Arrangements: For the majority of our software arrangements, we provide services that range from installation, training, and basic consulting to software modification and customization to meet specific customer needs. If the arrangement does not require significant production, modification or customization or where the software services are not considered essential to the functionality of the software, revenue is recognized when all of the following conditions are met
• | persuasive evidence of an arrangement exists
• | delivery has occurred
• | our fee is fixed or determinable
• | collectability is probable
For multiple element arrangements, each element of the arrangement is analyzed and we allocate a portion of the total arrangement fee to the elements based on the relative fair value of the element using vendor-specific objective evidence of fair value (“VSOE”), regardless of any separate prices stated within the contract for each element. Fair value is considered the price a customer would be required to pay if the element was sold separately based on our historical experience of stand-alone sales of these elements to third-parties. For PCS, we use renewal rates for continued support arrangements to determine fair value. For software services, we use the fair value we charge our customers when those services are sold separately. We monitor our transactions to determine that we maintain and periodically revise VSOE to reflect fair value. In software arrangements in which we have the fair value of all undelivered elements but not of a delivered element, we apply the “residual method,” in compliance with Accounting Standards Codification (“ASC”) 985-605, Software Revenue Recognition. Under the residual method, if the fair value of all undelivered elements is determinable, the fair value of the undelivered elements is deferred and the remaining portion of the arrangement fee is allocated to the delivered element(s) and is recognized as revenue assuming the other revenue recognition criteria are met. In software arrangements in which we do not have VSOE for all undelivered elements, revenue is deferred until fair value is determined or all elements for which we do not have VSOE have been delivered. Alternatively, if sufficient VSOE does not exist and the only undelivered element is services that do not involve significant modification or customization of the software, the entire fee is recognized over the period during which the services are expected to be performed. Software Licenses and Royalties We recognize the revenue allocable to software licenses and specified upgrades upon delivery of the software product or upgrade to the customer, unless the fee is not fixed or determinable or collectability is not probable. If the fee is not fixed or determinable, software license revenue is generally recognized as payments become due from the customer. If collectability is not considered probable, revenue is recognized when the fee is collected. Arrangements that include software services, such as training or installation, are evaluated to determine whether those services are essential to the product’s functionality. A majority of our software arrangements involve “off-the-shelf” software. We consider software to be off-the-shelf software if it can be added to an arrangement with minor changes in the underlying code and it can be used by the customer for the customer’s purpose upon installation. For off-the-shelf software arrangements, we recognize the software license fee as revenue after delivery has occurred, customer acceptance is reasonably assured, that portion of the fee represents a non-refundable enforceable claim and is probable of collection, and the remaining services such as training are not considered essential to the product’s functionality. For arrangements that involve significant production, modification or customization of the software, or where software services are otherwise considered essential, we recognize revenue using contract accounting and apply the provisions of the Construction type and Production type Contracts as discussed in ASC 605-35. We generally use the percentage-of-completion method to recognize revenue from these arrangements. We measure progress-to-completion primarily using labor hours incurred, or value added. The percentage-of-completion method generally results in the recognition of reasonably consistent profit margins over the life of a contract because we have the ability to produce reasonably dependable estimates of contract billings and contract costs. We use the level of profit margin that is most likely to occur on a contract. If the most likely profit margin cannot be precisely determined, the lowest probable level of profit margin in the range of estimates is used until the results can be estimated more precisely. These arrangements are often implemented over an extended time period and occasionally require us to revise total cost estimates. Amounts recognized in revenue are calculated using the progress-to-completion measurement after giving effect to any changes in our cost estimates. Changes to total estimated contract costs, if any, are recorded in the period they are determined. Estimated losses on uncompleted contracts are recorded in the period in which we first determine that a loss is apparent. For arrangements that include new product releases for which it is difficult to estimate final profitability except to assume that no loss will ultimately be incurred, we recognize revenue under the completed contract method. Under the completed contract method, revenue is recognized only when a contract is completed or substantially complete. Historically these amounts have been immaterial. We recognize royalty revenue when earned under the terms of our third party royalty arrangements, provided the fees are considered fixed or determinable and realization of payment is probable. Currently, our third party royalties are variable in nature and such amounts are not considered fixed or determinable until we receive notice of amounts earned. Typically, we receive notice of royalty revenues earned on a quarterly basis in the immediate quarter following the royalty reporting period. Software Services Some of our software arrangements include services considered essential for the customer to use the software for the customer’s purposes. For these software arrangements, both the software license revenue and the services revenue are recognized as the services are performed using the percentage-of-completion contract accounting method. When software services are not considered essential, the fee allocable to the service element is recognized as revenue as we perform the services. Computer Hardware Equipment Revenue allocable to computer hardware equipment is recognized when we deliver the equipment and collection is probable. Post-Contract Customer Support Our customers generally enter into PCS agreements when they purchase our software licenses. PCS includes telephone support, bug fixes, and rights to upgrades on a when-and-if available basis. Our PCS agreements are typically renewable annually. Revenue allocated to PCS is recognized on a straight-line basis over the period the PCS is provided. All significant costs and expenses associated with PCS are expensed as incurred. Subscription-Based Services: Subscription-based services consist of revenues derived from SaaS arrangements, which utilize the Tyler private cloud, and electronic filing transactions. For SaaS arrangements, we evaluate whether the customer has the contractual right to take possession of our software at any time during the hosting period without significant penalty and whether the customer can feasibly maintain the software on the customer’s hardware or enter into another arrangement with a third-party to host the software. In cases where the customer has the contractual right to take possession of our software at any time during the hosting period without significant penalty and the customer can feasibly maintain the software on the customer’s hardware or enter into another arrangement with a third-party to host the software, we recognize the license, professional services and hosting services revenues pursuant to ASC 985-605, Software Revenue Recognition. For SaaS arrangements that do not meet the criteria for recognition under ASC 985-605, we account for the elements under ASC 605-25, Multiple Element Arrangements, using all applicable facts and circumstances, including whether (i) the element has stand-alone value, (ii) there is a general right of return and (iii) the revenue is contingent on delivery of other elements. We allocate contract value to each element of the arrangement that qualifies for treatment as a separate element based on VSOE, and if VSOE is not available, third-party evidence, and if third-party evidence is unavailable, estimated selling price. We recognize hosting services ratably over the term of the arrangement, which range from one to 10 years but are typically for a period of five to seven years. For professional services associated with SaaS arrangements that we determine do not have stand-alone value to the customer or are contingent on delivery of other elements, we recognize the services revenue ratably over the remaining contractual period once we have provided the customer access to the software and we may begin billing for hosting services. We record amounts that have been invoiced in accounts receivable and in deferred revenue or revenues, depending on whether the revenue recognition criteria have been met. Electronic filing transaction fees primarily pertain to documents filed with the courts by attorneys and other third-parties via our e-filing services and retrieval of filed documents via our access services. The elements for these arrangements are accounted for under ASC 605-25. For each document filed with a court, the filer generally pays a transaction fee and a court filing fee to us and we remit a portion of the transaction fee and the filing fee to the court. We record as revenue the transaction fee, while the portion of the transaction fee remitted to the courts is recorded as cost of sales as we are acting as a principal in the arrangement. Court filing fees collected on behalf of the courts and remitted to the courts are recorded on a net basis and thus do not affect the statement of comprehensive income. In some cases, we are paid on a fixed fee basis and recognize the revenue ratably over the contractual period. Costs of performing services under subscription-based arrangements are expensed as incurred, except for certain direct and incremental contract origination and set-up costs associated with SaaS arrangements. Such direct and incremental costs are capitalized and amortized ratably over the related SaaS hosting term. Appraisal Services: For our property appraisal projects, we recognize revenue using the proportional performance method of revenue recognition since many of these projects are implemented over one to three year periods and consist of various unique activities. Under this method of revenue recognition, we identify each activity for the appraisal project, with a typical project generally calling for bonding, office set up, training, routing of map information, data entry, data collection, data verification, informal hearings, appeals and project management. Each activity or act is specifically identified and assigned an estimated cost. Costs which are considered to be associated with indirect activities, such as bonding costs and office set up, are expensed as incurred. These costs are typically billed as incurred and are recognized as revenue equal to cost. Direct contract fulfillment activities and related supervisory costs such as data collection, data entry and verification are expensed as incurred. The direct costs for these activities are determined and the total contract value is then allocated to each activity based on a consistent profit margin. Each activity is assigned a consistent unit of measure to determine progress towards completion and revenue is recognized for each activity based upon the percentage complete as applied to the estimated revenue for that activity. Progress for the fulfillment activities is typically based on labor hours or an output measure such as the number of parcel counts completed for that activity. Estimated losses on uncompleted contracts are recorded in the period in which we first determine that a loss is apparent. Allocation of Revenue in Statements of Comprehensive Income In our statements of comprehensive income, we allocate revenue to software licenses, software services, maintenance and hardware and other based on the VSOE of fair value for elements in each revenue arrangement and the application of the residual method for arrangements in which we have established VSOE of fair value for all undelivered elements. In arrangements where we are not able to establish VSOE of fair value for all undelivered elements, revenue is first allocated to any undelivered elements for which VSOE of fair value has been established. We then allocate revenue to any undelivered elements for which VSOE of fair value has not been established based upon management’s best estimate of fair value of those undelivered elements and apply a residual method to determine the license fee. Management’s best estimate of fair value of undelivered elements for which VSOE of fair value has not been established is based upon the VSOE of similar offerings and other objective criteria. Other The majority of deferred revenue consists of unearned maintenance revenue that has been billed based on contractual terms in the underlying arrangement with the remaining balance consisting of payments received in advance of revenue being earned under software licensing, subscription-based services, software and appraisal services and hardware installation. Unbilled revenue is not billable at the balance sheet date but is recoverable over the remaining life of the contract through billings made in accordance with contractual agreements. The termination clauses in our contracts generally provide for the payment for the value of products delivered and services performed in the event of an early termination. Prepaid expenses and other current assets include direct and incremental costs such as commissions associated with arrangements for which revenue recognition has been deferred. Such costs are expensed at the time the related revenue is recognized. USE OF ESTIMATES The preparation of our financial statements in conformity with accounting principles generally accepted in the United States (“GAAP”) requires us to make estimates and assumptions that affect the reported amounts of assets and liabilities and disclosure of contingent assets and liabilities at the date of the financial statements and the reported amounts of revenues and expenses during the reporting period. Significant items subject to such estimates and assumptions include the application of the percentage-of-completion and proportional performance methods of revenue recognition, the carrying amount and estimated useful lives of intangible assets, determination of share-based compensation expense and valuation allowance for receivables. Actual results could differ from estimates. PROPERTY AND EQUIPMENT, NET Property, equipment and purchased software are recorded at original cost and increased by the cost of any significant improvements after purchase. We expense maintenance and repairs when incurred. Depreciation and amortization is calculated using the straight-line method over the shorter of the asset’s estimated useful life or the term of the lease in the case of leasehold improvements. For income tax purposes, we use accelerated depreciation methods as allowed by tax laws. RESEARCH AND DEVELOPMENT COSTS We expensed research and development costs of $43.2 million during 2016, $29.9 million during 2015, and $25.7 million during 2014. INCOME TAXES Income taxes are accounted for under the asset and liability method. Deferred taxes arise because of different treatment between financial statement accounting and tax accounting, known as “temporary differences.” We record the tax effect of these temporary differences as “deferred tax assets” (generally items that can be used as a tax deduction or credit in the future periods) and “deferred tax liabilities” (generally items that we received a tax deduction for, which have not yet been recorded in the income statement). The deferred tax assets and liabilities are measured using enacted tax rules and laws that are expected to be in effect when the temporary differences are expected to be recovered or settled. A valuation allowance would be established to reduce deferred tax assets if it is more likely than not that a deferred tax asset will not be "realized." SHARE-BASED COMPENSATION We have a stock option plan that provides for the grant of stock options to key employees, directors and non-employee consultants. Stock options generally vest after three to six years of continuous service from the date of grant and have a contractual term of 10 years. We account for share-based compensation utilizing the fair value recognition pursuant to ASC 718, Stock Compensation. See Note 9 – “Share-Based Compensation” for further information. During fourth quarter of 2016, we adopted Accounting Standards Update ("ASU") No. 2016-09 "Compensation-Stock Compensation (Topic 718): Improvements to Employee Share-Based Payment Accounting," See "New Accounting Pronouncements" below for further information. GOODWILL AND OTHER INTANGIBLE ASSETS Goodwill Goodwill represents the excess of the purchase price over the fair value of net assets acquired, including identifiable intangible assets, in connection with our business combinations. Upon acquisition, goodwill is assigned to the reporting unit that is expected to benefit from the synergies of the business combination, which is the reporting unit to which the related acquired technology is assigned. A reporting unit is the operating segment, or a business unit one level below that operating segment, for which discrete financial information is prepared and regularly reviewed by executive management. We assess goodwill for impairment annually as of April, or more frequently whenever events or changes in circumstances indicate its carrying value may not be recoverable. When testing goodwill for impairment quantitatively, we first compare the fair value of each reporting unit with its carrying amount. If the carrying amount of a reporting unit exceeds its fair value, a second step is performed to measure the amount of potential impairment. In the second step, we compare the implied fair value of reporting unit goodwill with the carrying amount of the reporting unit’s goodwill. If the carrying amount of reporting unit goodwill exceeds the implied fair value of that goodwill, an impairment loss is recognized. The fair values calculated in our impairment tests are determined using discounted cash flow models involving several assumptions. The assumptions that are used are based upon what we believe a hypothetical marketplace participant would use in estimating fair value. We evaluate the reasonableness of the fair value calculations of our reporting units by comparing the total of the fair value of all of our reporting units to our total market capitalization. Our annual goodwill impairment analysis, which we performed quantitatively during the second quarter of 2016, did not result in an impairment charge. Other Intangible Assets We make judgments about the recoverability of purchased intangible assets other than goodwill whenever events or changes in circumstances indicate that an impairment may exist. Customer base and acquired software each comprise approximately half of our purchased intangible assets other than goodwill. We review our customer turnover each year for indications of impairment. Our customer turnover has historically been very low. There have been no significant impairments of intangible assets in any of the periods presented. If indications of impairment are determined to exist, we measure the recoverability of assets by a comparison of the carrying amount of the asset to the estimated undiscounted future cash flows expected to be generated by the asset. If the carrying amount of the assets exceeds their estimated future cash flows, an impairment charge is recognized for the amount by which the carrying amount of the assets exceeds the fair value of the assets. IMPAIRMENT OF LONG-LIVED ASSETS We periodically evaluate whether current facts or circumstances indicate that the carrying value of our property and equipment or other long-lived assets to be held and used may not be recoverable. If such circumstances are determined to exist, we measure the recoverability of assets to be held and used by a comparison of the carrying amount of the asset or appropriate grouping of assets and the estimated undiscounted future cash flows expected to be generated by the assets. If the carrying amount of the assets exceeds their estimated future cash flows, an impairment charge is recognized for the amount by which the carrying amount of the assets exceeds the fair value of the assets. Assets to be disposed of would be separately presented in the balance sheet and reported at the lower of the carrying amount or fair value less costs to sell, and are no longer depreciated. The assets and liabilities of a disposed group classified as held for sale would be presented separately in the appropriate asset and liability sections of the balance sheet. There have been no significant impairments of long-lived assets in any of the periods presented. COSTS OF COMPUTER SOFTWARE We capitalize software development costs upon the establishment of technological feasibility and prior to the availability of the product for general release to customers. Software development costs primarily consist of personnel costs and rent for related office space. We begin to amortize capitalized costs when a product is available for general release to customers. Amortization expense is determined on a product-by-product basis at a rate not less than straight-line basis over the product’s remaining estimated economic life. We have not capitalized any internal software development costs in any of the periods presented. FAIR VALUE OF FINANCIAL INSTRUMENTS Cash and cash equivalents, accounts receivables, accounts payables, short-term obligations and certain other assets at cost approximate fair value because of the short maturity of these instruments. The fair value of our revolving line of credit approximates book value as of December 31, 2016, because our interest rates reset approximately every 30 days or less. See Note 6 – “Revolving Line of Credit” for further discussion. As of December 31, 2016, we have $33.5 million in investment grade corporate and municipal bonds with maturity dates ranging from 2016 through mid-2018. We intend to hold these bonds to maturity and have classified them as such. We believe cost approximates fair value because of the relatively short duration of these investments. The fair values of these securities are considered Level II as they are based on inputs from quoted prices in markets that are not active or from other observable market data. These investments are included in short-term investments and non-current investments and other assets. As of December 31, 2016, we have $15.0 million invested in convertible preferred stock representing a 20% interest in Record Holdings Pty Limited, a privately held Australian company specializing in digitizing the spoken word in court and legal proceedings. The fair value of this investment is based on valuations using Level III, unobservable inputs that are supported by little or no market value activity and that are significant to the fair value of the investment. CONCENTRATIONS OF CREDIT RISK AND UNBILLED RECEIVABLES Financial instruments that potentially subject us to significant concentrations of credit risk consist principally of cash and cash equivalents, accounts receivable from trade customers, and investments in marketable securities. Our cash and cash equivalents primarily consists of operating account balances and money market funds, which are maintained at several major domestic financial institutions and the balances often exceed insured amounts. As of December 31, 2016, we had cash and cash equivalents of $36.2 million. We perform periodic evaluations of the credit standing of these financial institutions. Concentrations of credit risk with respect to receivables are limited due to the size and geographical diversity of our customer base. Historically, our credit losses have not been significant. As a result, we do not believe we have any significant concentrations of credit risk as of December 31, 2016. We maintain allowances for doubtful accounts and sales adjustments, which are provided at the time the revenue is recognized. Since most of our customers are domestic governmental entities, we rarely incur a loss resulting from the inability of a customer to make required payments. Events or changes in circumstances that indicate that the carrying amount for the allowances for doubtful accounts and sales adjustments may require revision, include, but are not limited to, deterioration of a customer’s financial condition, failure to manage our customer’s expectations regarding the scope of the services to be delivered, and defects or errors in new versions or enhancements of our software products. The following table summarizes the changes in the allowances for doubtful accounts and sales adjustments:
| Years Ended December 31,
| 2016 |  | 2015 |  | 2014
Balance at beginning of year | $ | 1,640 |  |  | $ | 1,725 |  |  | $ | 1,113 |
Provisions for losses - accounts receivable | 4,484 |  |  | 1,756 |  |  | 1,897 |
Collection of accounts previously written off | — |  |  | 153 |  |  | — |
Deductions for accounts charged off or credits issued | (2,728 | ) |  | (1,994 | ) |  | (1,285 | )
Balance at end of year | $ | 3,396 |  |  | $ | 1,640 |  |  | $ | 1,725 |
The termination clauses in most of our contracts provide for the payment for the value of products delivered or services performed in the event of early termination. Our property appraisal outsourcing service contracts can range up to three years and, in a few cases, as long as five years, in duration. In connection with these contracts, as well as certain software service contracts, we may perform work prior to when the software and services are billable and/or payable pursuant to the contract. We have historically recorded such unbilled receivables (costs and estimated profit in excess of billings) in connection with (1) property appraisal services contracts accounted for using proportional performance accounting in which the revenue is earned based upon activities performed in one accounting period but the billing normally occurs subsequently and may span another accounting period; (2) software services contracts accounted for using the percentage-of-completion method of revenue recognition using labor hours as a measure of progress towards completion in which the services are performed in one accounting period but the billing for the software element of the arrangement may be based upon the specific phase of the implementation; (3) software revenue for which we have objective evidence that the customer-specified objective criteria has been met but the billing has not yet been submitted to the customer; (4) some of our contracts provide for an amount to be withheld from a progress billing (generally between 5% and 20% retention) until final and satisfactory project completion is achieved; and (5) in a limited number of cases, we may grant extended payment terms, generally to existing customers with whom we have a long-term relationship and favorable collection history. We have recorded unbilled receivables of $33.6 million and $29.7 million at December 31, 2016 and 2015, respectively. Included in unbilled receivables are retention receivables of $5.0 million and $4.7 million at December 31, 2016 and 2015, respectively, and these retentions become payable upon the completion of the contract or completion of our fieldwork and formal hearings. Unbilled receivables and retention receivables expected to be collected in excess of one year have been included with accounts receivable, long-term portion in the accompanying consolidated balance sheets. INDEMNIFICATION Most of our software license agreements indemnify our customers in the event that the software sold infringes upon the intellectual property rights of a third-party. These agreements typically provide that in such event we will either modify or replace the software so that it becomes non-infringing or procure for the customer the right to use the software. We have recorded no liability associated with these indemnifications, as we are not aware of any pending or threatened infringement actions that are possible losses. We believe the estimated fair value of these intellectual property indemnification clauses is minimal. We have also agreed to indemnify our officers and board members if they are named or threatened to be named as a party to any proceeding by reason of the fact that they acted in such capacity. We maintain directors’ and officers’ liability insurance coverage to protect against any such losses. We have recorded no liability associated with these indemnifications. Because of our insurance coverage, we believe the estimated fair value of these indemnification agreements is minimal. RECLASSIFICATIONS Certain amounts for previous years have been reclassified to conform to the current year presentation. NEW ACCOUNTING PRONOUNCEMENTS New Accounting Pronouncements Adopted in 2016 Improvements to Employee Share-Based Payment Accountin g. In March 2016, the Financial Accounting Standards Board ("FASB") issued ASU No. 2016-09, "Compensation-Stock Compensation (Topic 718): Improvements to Employee Share-Based Payment Accounting" which simplifies several aspects of the accounting for employee share-based payment transactions, including the accounting for income taxes, forfeitures, and statutory tax withholding requirements, as well as classification in the statement of cash flows. This standard is effective for our interim and annual reporting periods beginning December 15, 2016, and early adoption is permitted. We elected to early adopt this standard in fourth quarter of 2016. The impact of the early adoption was as follows:
• | The standard eliminates additional paid in capital ("APIC") pools and requires excess tax benefits and tax deficiencies to be recorded in the income statement as a discrete item when the awards vest or are settled. The adoption of this guidance on a prospective basis resulted in the recognition of excess tax benefits in our provision for income taxes.
• | The standard requires excess tax benefits to be recognized regardless of whether the benefit reduces taxes payable. The adoption of this guidance is applied on a modified retrospective basis; however, it did not have an impact on our retained earnings as of January 1, 2016, as we had previously recognized all our excess tax benefits.
• | As permitted, we have elected to continue to estimate forfeitures expected to occur to determine the amount of stock-based compensation cost to be recognized in each period. As such, the guidance relating to forfeitures did not have an impact on our retained earnings as of January 1, 2016.
• | The new guidance changes the calculation of common stock equivalents for earnings per share purposes.
• | As permitted, we elected to apply the statement of cash flows guidance that cash flows related to excess tax benefits be presented as an operating activity retrospectively.
Adoption of the new standard resulted in the recognition of excess tax benefits in our provision for income taxes rather than APIC of $29.6 million for the period ended December 31, 2016. As of December 31, 2016, the change in the calculation of common stock equivalents added approximately 519,000 weighted average shares for the diluted earnings per share calculations. The impact to our previously reported quarterly results for fiscal year 2016 is as follows:
| Three Months Ended |  | Three Months Ended |  | Three Months Ended
| March 31, 2016 |  | June 30, 2016 |  | September 30, 2016
(In thousands, except per share amounts) | As Reported |  | As Adjusted |  | As Reported |  | As Adjusted |  | As Reported |  | As Adjusted
Income statements: |  |  |  |  |  |  |  |  |  |  |
Income tax provision | $ | 10,495 |  |  | $ | 9,350 |  |  | $ | 11,323 |  |  | $ | 5,188 |  |  | $ | 14,155 |  |  | $ | 989 |
Net income | $ | 17,079 |  |  | $ | 18,224 |  |  | $ | 18,872 |  |  | $ | 25,007 |  |  | $ | 22,264 |  |  | $ | 35,430 |
Basic earnings per common share | $ | 0.47 |  |  | $ | 0.50 |  |  | $ | 0.52 |  |  | $ | 0.69 |  |  | $ | 0.61 |  |  | $ | 0.97 |
Diluted earnings per common share | $ | 0.44 |  |  | $ | 0.47 |  |  | $ | 0.49 |  |  | $ | 0.65 |  |  | $ | 0.58 |  |  | $ | 0.91 |
Diluted weighted average common shares outstanding | 38,557 |  |  | 39,071 |  |  | 38,196 |  |  | 38,738 |  |  | 38,506 |  |  | 39,062 |
Statement of cash flows: |  |  |  |  |  |  |  |  |  |  |
Net cash provided by operating activities | $ | 40,270 |  |  | $ | 41,321 |  |  | $ | 13,877 |  |  | $ | 19,520 |  |  | $ | 67,091 |  |  | $ | 79,213 |
Net cash (used) provided by financing activities | $ | (15,860 | ) |  | $ | (16,911 | ) |  | $ | 5,668 |  |  | $ | 25 |  |  | $ | (77,973 | ) |  | $ | (90,095 | )
Presentation of Financial Statements - Going Concern. In August 2014, the FASB issued ASU No. 2014-15, "Presentation of Financial Statements - Going Concern (Subtopic 205-40): Disclosure of Uncertainties about an Entity’s Ability to Continue as a Going Concern." The guidance requires an entity to evaluate whether there are conditions or events, in the aggregate, that raise substantial doubt about the entity’s ability to continue as a going concern within one year after the date that the financial statements are issued (or within one year after the financial statements are available to be issued when applicable) and to provide related footnote disclosures in certain circumstances. The guidance is effective for the annual period ending after December 15, 2016, and for annual and interim periods thereafter. We adopted this standard in the fourth quarter of 2016 and its adoption did not have an impact on our consolidated financial statements. Recent Accounting Guidance not yet Adopted Revenue from Contracts with Customers. On May 28, 2014, the FASB issued ASU No. 2014-09, “Revenue from Contracts with Customers.” This ASU is the result of a convergence project between the FASB and the International Accounting Standards Board. The core principle behind ASU No. 2014-09 is that an entity should recognize revenue to depict the transfer of promised goods and services to customers in an amount that reflects the consideration to which the entity expects to be entitled in exchange for delivering those goods and services. This model involves a five-step process that includes identifying the contract with the customer, identifying the performance obligations in the contract, determining the transaction price, allocating the transaction price to the performance obligations in the contract and recognizing revenue when (or as) the entity satisfies the performance obligations. The ASU allows two methods of adoption: a full retrospective approach where three years of financial information are presented in accordance with the new standard, and a modified retrospective approach where the ASU is applied to the most current period presented in the financial statements. We currently anticipate adopting the standard using the full retrospective method to restate each prior reporting period presented. Our ability to adopt using the full retrospective method is dependent on system readiness, including software procured from third-party providers, and the completion of our analysis of information necessary to restate prior period financial statements. The new standard requires application no later than annual reporting periods beginning after December 15, 2017, including interim reporting periods therein; however, public entities are permitted to elect to early adopt the new standard. We are assessing the financial impact of adopting the new standard and the methods of adoption; however, we are currently unable to provide a reasonable estimate regarding the financial impact. We will adopt the new standard in fiscal year 2018. We anticipate this standard will have a material impact on our consolidated financial statements. While we are continuing to assess all potential impacts of the standard, we currently believe the most significant impact relates to our accounting for software license fees, installation fees, and incremental cost of obtaining a contract. Specifically, under the new standard we expect software license fees under perpetual agreements will no longer be subject to 100% discount allocations from other elements in the contract. Discounts in arrangements will be allocated across all deliverables increasing license revenues and decreasing revenues allocated to other performance obligations. In addition, in most cases, net license fees (total license fees less any allocated discounts) will be recognized at the point in time that control of the software license transfers to the customer versus our current policy of recognizing revenue only to the extent billable per the contractual terms. Time-based license fees currently recognized over the license term will no longer be recognized over the period of the license and will instead be recognized at the point in time that control of the software license transfers to the customer. Installation fees will no longer be considered distinct performance obligations and therefore will be recognized over the term of the arrangement or life of the performance obligation. We expect revenue related to our SaaS offerings and professional services to remain substantially unchanged. Due to the complexity of certain contracts, the actual revenue recognition treatment required under the standard will be dependent on contract-specific terms and may vary in some instances from recognition at the time of billing. Application of the new standard requires that incremental costs directly related to obtaining a contract (typically sales commissions plus any associated fringe benefits) must be recognized as an asset and expensed over the expected life of the arrangement, unless that life is less than one year. Currently, we defer sales commissions and recognize expense over the relevant initial contractual term. With the adoption the new standard, we expect amortization periods to extend past the initial term. Leases. On February 25, 2016, the FASB issued its new lease accounting guidance in ASU No. 2016-02, “Leases (Topic 842).” Under the new guidance, lessees will be required to recognize the following for all leases (with the exception of short-term leases) at the commencement date:
• | A lease liability, which is a lessee‘s obligation to make lease payments arising from a lease, measured on a discounted basis; and
• | A right-of-use asset, which is an asset that represents the lessee’s right to use, or control the use of, a specified asset for the lease term.
Lessees (for capital and operating leases) and lessors (for sales-type, direct financing, and operating leases) must apply a modified retrospective transition approach for leases existing at, or entered into after, the beginning of the earliest comparative period presented in the financial statements. The modified retrospective approach would not require any transition accounting for leases that expired before the earliest comparative period presented. Lessees and lessors may not apply a full retrospective transition approach. The ASU is effective for fiscal years beginning after December 15, 2018, including interim periods therein. Early application is permitted for all business entities upon issuance. We are assessing the financial impact of adopting the new standard; however, we are currently unable to provide a reasonable estimate regarding the financial impact. We expect to adopt the new standard in fiscal year 2019.

X
- References No definition available. + Details
Name: | us-gaap_AccountingPoliciesAbstract
Namespace Prefix: | us-gaap_
Data Type: | xbrli:stringItemType
Balance Type: | na
Period Type: | duration

X
- Definition The entire disclosure for all significant accounting policies of the reporting entity. + References Reference 1: http://www.xbrl.org/2003/role/presentationRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -SubTopic 10 -Section 50 -Paragraph 6 -URI http://asc.fasb.org/extlink&oid=51655414&loc=d3e18861-107790 Reference 2: http://www.xbrl.org/2003/role/presentationRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -SubTopic 10 -Section 50 -Paragraph 3 -URI http://asc.fasb.org/extlink&oid=51655414&loc=d3e18780-107790 Reference 3: http://www.xbrl.org/2003/role/presentationRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -SubTopic 10 -Section 50 -Paragraph 1 -URI http://asc.fasb.org/extlink&oid=51655414&loc=d3e18726-107790 Reference 4: http://www.xbrl.org/2003/role/presentationRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -SubTopic 10 -Section 50 -Paragraph 2 -URI http://asc.fasb.org/extlink&oid=51655414&loc=d3e18743-107790 Reference 5: http://www.xbrl.org/2003/role/presentationRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -SubTopic 10 -Section 50 -Paragraph 5 -URI http://asc.fasb.org/extlink&oid=51655414&loc=d3e18854-107790 + Details
Name: | us-gaap_SignificantAccountingPoliciesTextBlock
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration