XML 32 R22.htm IDEA: XBRL DOCUMENT v3.19.1
Accounting Standards and Significant Accounting Policies (Policies)
 3 Months Ended
Mar. 31, 2019
Accounting Policies [Abstract]  
Use of estimates 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, and 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 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.
Contract balances Contract Balances:
Accounts receivable and allowance for doubtful accounts
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, 2019 and December 31, 2018, total current and long-term accounts receivable, net of allowance for doubtful accounts, was $321.8 million and $314.9 million, respectively. We have recorded unbilled receivables of $113.1 million and $104.2 million at March 31, 2019, and December 31, 2018, respectively. Included in unbilled receivables are retention receivables of $13.4 million and $12.2 million at March 31, 2019, and December 31, 2018, 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 doubtful accounts, 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 the carrying amount for the allowances for doubtful accounts 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.
Leases LEASES
We determine if an arrangement is a lease at inception. Operating leases are included in operating lease right-of-use (“ROU”) assets, other current liabilities, and operating lease liabilities on our consolidated balance sheets. We currently do not have any finance lease arrangements.
Operating lease ROU assets and operating lease liabilities are recognized based on the present value of the future minimum lease payments over the lease term at commencement date. As most of our leases do not provide an implicit rate, we use our incremental borrowing rate based on the information available at commencement date of the lease in determining the present value of future payments. The operating lease ROU asset also includes any lease payments made and excludes lease incentives and initial direct costs incurred. Our lease terms may include options to extend or terminate the lease when it is reasonably certain that we will exercise that option. Lease expense for minimum lease payments is recognized on a straight-line basis over the lease term. Leases with an initial term of 12 months or less are not recorded on the balance sheet; we recognize lease expense for these leases on a straight-line basis over the lease term. We have lease agreements with lease and non-lease components, which are generally accounted as a single lease component.
Recently adopted accounting pronouncements RECENTLY ADOPTED ACCOUNTING PRONOUNCEMENTS
Leases. We adopted Topic 842 using the transition method that allows us to initially apply the guidance at the adoption date of January 1, 2019, and recognized a cumulative-effect adjustment to the opening balance of retained earnings in the period of adoption. We used the package of practical expedients that allows us to not reassess: (1) lease classification for any expired or existing leases and (2) initial direct costs for any expired or existing leases. We did not elect to use the hindsight application for evaluating the life of the lease arrangement. The impacts of adoption are reflected in the financial information herein. For additional details, see Note 10 to our condensed consolidated financial statements.
The impact of Topic 842 on our consolidated balance sheet beginning January 1, 2019, included the recognition of ROU assets and lease liabilities for operating leases, while our accounting for finance leases remained substantially unchanged. We had no finance leases prior to the adoption of Topic 842 and currently do not have any.