XML 27 R8.htm IDEA: XBRL DOCUMENT
v3.20.1

Accounting Standards and Significant Accounting Policies | 3 Months Ended
--- | ---
Mar. 31, 2020
Accounting Policies [Abstract] |
Accounting Standards and Significant Accounting Policies | Accounting Standards and Significant Accounting Policies SUMMARY OF SIGNIFICANT ACCOUNTING POLICIES Except for the accounting policies for ASU 2016-13, Financial Instruments - Credit Losses, (“ASU 2016-13”), there have been no changes to our significant accounting policies described in the Annual Report on Form 10-K for the year ended December 31, 2019, filed with the SEC on February 19, 2020, that have had a material impact on our condensed consolidated financial statements and related notes. Impact of the COVID-19 Pandemic In March 2020, the World Health Organization declared the outbreak of COVID -19 a pandemic, which continues to spread throughout the U.S. and the world and has resulted in authorities implementing numerous measures to contain the virus, including travel bans and restrictions, quarantines, shelter-in-place orders, and business limitations and shutdowns. While we are unable to accurately predict the full impact that COVID-19 will have on our results from operations, financial condition, liquidity and cash flows due to numerous uncertainties, including the duration and severity of the pandemic and containment measures and associated compliance, we do expect the current environment will negatively impact our revenues and other financial results for fiscal 2020. However, for the first quarter of 2020, we did not experience a material negative impact on our financial results associated with the pandemic. Because an increasing portion of our revenues are recurring, the effect of COVID-19 on our results of operations may also not be fully reflected for some time. We expect to see some impact on our business in the near term, with possible delays in government procurement processes and delays in implementations caused by travel restrictions, closed offices, or clients shifting focus to more pressing issues. We are working to address those challenges through adapting the way we do business – encouraging web and video conferencing, conducting sales demonstrations and delivering professional services remotely. Our priorities during this crisis are protecting the health and safety of our employees and our clients. Our IT systems and applications support a remote workforce. Prior to the pandemic, many of our employees worked remotely. In response to the pandemic, we encouraged all employees who are able to do so to work from home, equipping them with resources necessary to continue uninterrupted. We were able to transition the vast majority of our employees to this work-from-home posture. This reduces the number of team members in our offices to those uniquely needed for essential on-site services, such as network operations support staff, and allows for “social distancing” as directed by the Centers for Disease Control ("CDC"). The pandemic has delayed some government procurement processes and is expected to impact our ability to complete certain implementations, negatively impacting our revenue. It could also negatively impact the timing of client payments to us. We continue to monitor these trends in order to respond to the ever-changing impact of COVID-19 on our clients and Tyler’s operations. Recurring revenues, from subscriptions and maintenance revenues, for the three months ended March 31, 2020, comprise 71% of our total consolidated revenue, and include newer transaction-based revenue streams such as e-filing and online payments. As of March 31, 2020, we had $392.6 million in cash and investments and no outstanding borrowings under our credit facility. We also have substantial additional liquidity available through our undrawn $400.0 million credit facility, which can be expanded through an accordion feature. For the first quarter of 2020, the negative impact of the COVID-19 pandemic was not material to our operating results. No asset impairments were recorded as of the balance sheet date as no triggering events or changes in circumstances occurred as of period-end to require such an impairment; however, due to significant uncertainty surrounding the pandemic, management’s judgment regarding this could change in the future. 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 revenue recognition, determining the nature and timing of satisfaction of performance obligations, determining the standalone selling price ("SSP") of performance obligations, variable consideration, and other obligations such as returns and refunds; loss contingencies; the estimated useful life of deferred commissions; the carrying amount and estimated useful lives of intangible assets; the carrying amount of operating lease right-of-use assets and operating lease liabilities; determining share-based compensation expense; the valuation allowance for receivables; and determining the potential outcome of future tax consequences of events that have been recognized on our consolidated financial statements or tax returns. Actual results could differ from estimates. REVENUE RECOGNITION Nature of Products and Services: We earn revenue from software licenses, royalties, subscription-based services, software services, post-contract customer support (“PCS” or “maintenance”), hardware, and appraisal services. Revenue is recognized upon transfer of control of promised products or services to customers in an amount that reflects the consideration we expect to receive in exchange for those products or services. We determine revenue recognition through the following steps: •Identification of the contract, or contracts with a customer •Identification of the performance obligations in the contract •Determination of the transaction price •Allocation of the transaction price to the performance obligations in the contract •Recognition of revenue when, or as, we satisfy a performance obligation Most of our software arrangements with customers contain multiple performance obligations that range from software licenses, installation, training, and consulting to software modification and customization to meet specific customer needs (services), hosting, and PCS. For these contracts, we account for individual performance obligations separately when they are distinct. We evaluate whether separate performance obligations can be distinct or should be accounted for as one performance obligation. Arrangements that include software services, such as training or installation, are evaluated to determine whether the customer can benefit from the services either on their own or together with other resources readily available to the customer and whether the services are separately identifiable from other promises in the contract. The transaction price is allocated to the distinct performance obligations on a relative SSP basis. We determine the SSP based on our overall pricing objectives, taking into consideration market conditions and other factors, including the value of our contracts, the applications sold, customer demographics, and the number and types of users within our contracts. Revenue is recognized net of allowances for sales adjustments and any taxes collected from customers, which are subsequently remitted to governmental authorities. Significant Judgments: Our contracts with customers often include multiple performance obligations to a customer. When a software arrangement (license or subscription) includes both software licenses and software services, judgment is required to determine whether the software license is considered distinct and accounted for separately, or not distinct and accounted for together with the software services and recognized over time. The transaction price is allocated to the separate performance obligations on a relative SSP basis. We determine the SSP based on our overall pricing objectives, taking into consideration market conditions and other factors, including the value of our contracts, the applications sold, customer demographics, and the number and types of users within our contracts. We use a range of amounts to estimate SSP when we sell each of the products and services separately and need to determine whether there is a discount to be allocated based on the relative SSP of the various products and services. In instances where SSP is not directly observable, such as when we do not sell the product or service separately, we determine SSP using the expected cost-plus margin approach. For arrangements that involve significant production, modification or customization of the software, or where software services otherwise cannot be considered distinct, we recognize revenue as control is transferred to the customer over time using progress-to-completion methods. Depending on the contract, we measure progress-to-completion primarily using labor hours incurred, or value added. The progress-to-completion method generally results in the recognition of reasonably consistent profit margins over the life of a contract because we can provide 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. Typically, the structure of our arrangements does not give rise to variable consideration. However, in those instances whereby variable consideration exists, we include in our estimates additional revenue for variable consideration when we believe we have an enforceable right, the amount can be estimated reliably and its realization is probable. Refer to Note 13 - "Disaggregation of Revenue" for further information, including the economic factors that affect the nature, amount, timing, and uncertainty of revenue and cash flows of our various revenue categories. Contract Balances: Accounts receivable and allowance for losses and sales adjustments Timing of revenue recognition may differ from the timing of invoicing to customers. We record an unbilled receivable when revenue is recognized prior to invoicing, or deferred revenue when revenue is recognized subsequent to invoicing. For multi-year agreements, we generally invoice customers annually at the beginning of each annual coverage period. We record an unbilled receivable related to revenue recognized for on-premises licenses as we have an unconditional right to invoice and receive payment in the future related to those licenses. At March 31, 2020, and December 31, 2019, total current and long-term accounts receivable, net of allowance for losses and sales adjustments, was $339.5 million and $396.5 million, respectively. We have recorded unbilled receivables of $134.5 million and $134.0 million at March 31, 2020, and December 31, 2019, respectively. Included in unbilled receivables are retention receivables of $12.5 million and $13.1 million at March 31, 2020, and December 31, 2019, respectively, which become payable upon the completion of the contract or completion of our fieldwork and formal hearings. Unbilled receivables expected to be collected within one year have been included with accounts receivable, current portion in the accompanying condensed consolidated balance sheets. Unbilled receivables and retention receivables expected to be collected past one year have been included with accounts receivable, long-term portion in the accompanying condensed consolidated balance sheets. We maintain allowances for losses and sales adjustments, which losses are recorded against revenue at the time of the loss is incurred. Since most of our clients are domestic governmental entities, we rarely incur a loss resulting from the inability of a client to make required payments. Events or changes in circumstances that indicate the carrying amount for the allowances for losses and sales adjustments may require revision, include, but are not limited to, managing our client’s expectations regarding the scope of the services to be delivered and defects or errors in new versions or enhancements of our software products. Our allowance for losses and sales adjustments of $6.5 million at March 31, 2020, does not include provisions for credit losses. As of January 1, 2020, we adopted ASU 2016-13 Financial Instruments - Credit Losses and primarily evaluated our historical experience with credit losses related to trade and other receivables. Because we have not experienced any historical credit losses with the majority of our clients, we have no basis to record a reserve for credit losses as defined by the standard. RECENTLY ADOPTED ACCOUNTING PRONOUNCEMENTS In June 2016, the FASB issued ASU 2016-13, Financial Instruments - Credit Losses, (“ASU 2016-13”). ASU 2016-13 changes the impairment model for most financial assets and certain other instruments, including trade and other receivables, available for-sale debt securities, held-to-maturity debt securities and loans, and requires entities to use a new forward-looking expected loss model that will result in the earlier recognition of an allowance for losses. This update is effective for fiscal years beginning after December 15, 2019, including interim periods within those fiscal years. Early adoption is permitted for a fiscal year beginning after December 15, 2018, including interim periods within that fiscal year. Entities apply the standard’s provisions as a cumulative-effect adjustment to retained earnings as of the beginning of the first reporting period in which the guidance is adopted. As of January 1, 2020, we adopted the new standard with no material impact of credit losses to our trade and other receivables, held-to-maturity debt securities and retained earnings included in our condensed consolidated financial statements. RECENTLY ISSUED ACCOUNTING PRONOUNCEMENTS Accounting for Income Taxes In December 2019, the FASB issued ASU 2019-12, Simplifying the Accounting for Income Taxes, ("ASU 2019-12") which simplifies the accounting for income taxes, eliminates certain exceptions within ASC 740, Income Taxes, and clarifies certain aspects of the current guidance to promote consistency among reporting entities. The new standard is effective for fiscal years beginning after December 15, 2020. Most amendments within the standard are required to be applied on a prospective basis, while certain amendments must be applied on a retrospective or modified retrospective basis. The Company does not expect adoption of this standard to have a material effect on the Company’s consolidated financial statements.

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://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -URI http://asc.fasb.org/topic&trid=2122369 + Details
Name: | us-gaap_SignificantAccountingPoliciesTextBlock
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration