XML 19 R9.htm IDEA: XBRL DOCUMENT
v3.24.3

Accounting Standards and Significant Accounting Policies | 9 Months Ended
--- | ---
Sep. 30, 2024
Accounting Policies [Abstract] |
Accounting Standards and Significant Accounting Policies | Accounting Standards and Significant Accounting Policies SUMMARY OF SIGNIFICANT ACCOUNTING POLICIES 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, 2023, filed with the SEC on February 21, 2024, that have had a material impact on our condensed consolidated financial statements and related notes. See Recently Adopted Accounting Pronouncements below. REVENUE RECOGNITION Nature of Products and Services We earn the majority of our revenues from subscription-based services and post-contract customer support (“PCS” or “maintenance”). Other sources of revenue are professional services, software licenses and royalties, and hardware and other. 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 Subscription-based services consist primarily of revenues derived from software as a service (“SaaS”) arrangements and transactions from digital government services; payment processing; and electronic filing (‘‘e-filing”). We recognize SaaS arrangements ratably over the terms of the arrangements, which range from one to 10 years, but are typically for periods of generally one to three years. In certain cases, we have concluded that some services with SaaS arrangements are not distinct and therefore we recognize the revenue ratably of the remaining contractual period once we have provided the customer assess to the SaaS deliverable. 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. In those instances where 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. For transaction-based fees, we have the right to charge the customer an amount that directly corresponds with the value to the customer of our performance to date. Therefore, we recognize revenue for these services as invoiced based on the amount billable to the customer. In some cases, we are paid on a fixed-fee basis and recognize the revenue ratably over the contractual period. Transaction-based fees primarily relate to digital government services and online payment services, which are sometimes offered with the assistance of third-party vendors. In general, when we are the principal in a transaction, we record the revenue and related costs on a gross basis. Otherwise, we net the cost of revenue associated with the service against the gross revenue (amount billed to the customer) and record the net amount as revenue. Other software arrangements with customers contain multiple performance obligations that range from software licenses; services such as installation, training, consulting, software modification and customization to meet specific customer needs; 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 professional services, such as training or installation, are evaluated to determine whether those services are highly interdependent or interrelated to the product’s functionality. The transaction price is allocated to the distinct performance obligations on a relative standalone selling price (“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. For arrangements that involve significant production, modification, or customization of the software, or where professional 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. 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. Revenue is recognized net of allowances for sales adjustments and any taxes collected from customers, which are subsequently remitted to governmental authorities. Refer to Note 4, “Disaggregation of Revenue” for further information, including the economic factors that affect the nature, amount, timing, and uncertainty of revenues 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 invoicing occurs prior to revenue recognition. For multi-year agreements, we generally invoice customers annually at the beginning of each annual coverage period. As of September 30, 2024, and December 31, 2023, total current and long-term accounts receivable, net of allowance for losses and sales adjustments was $626.8 million and $628.7 million, respectively. We have recorded unbilled receivables of $114.3 million and $119.2 million as of September 30, 2024, and December 31, 2023, respectively. Included in unbilled receivables are retention receivables of $11.1 million and $9.8 million as of September 30, 2024, and December 31, 2023, 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 the current portion of accounts receivable in the accompanying condensed consolidated balance sheets. Unbilled receivables and retention receivables expected to be collected past one year have been included with long-term portion of accounts receivable in the accompanying condensed consolidated balance sheets. We maintain allowances for losses and sales adjustments, which losses are recorded against revenue at the time the loss is incurred. Because most of our clients are domestic governmental entities, we rarely incur a credit loss resulting from the inability of a client to make required payments. Consequently, we have not recorded a reserve for credit losses. 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 allowances for losses and sales adjustments are $18.4 million and $22.8 million as of September 30, 2024, and December 31, 2023, respectively. GOODWILL AND OTHER INTANGIBLE ASSETS Goodwill We assess goodwill for impairment annually, or more frequently whenever events or changes in circumstances indicate its carrying value may not be recoverable. We begin with the qualitative assessment of the likelihood of impairment of each reporting unit. If the conclusion of this assessment is that it is more likely than not that a reporting unit's fair value is more than its carrying value, we are not required to perform a quantitative impairment test. When testing goodwill for impairment quantitatively, we first compare the estimated fair value of each reporting unit with its carrying amount. If the carrying amount of a reporting unit exceeds the fair value of that reporting unit, an impairment loss is recognized. The fair values calculated in our impairment tests are determined using discounted cash flow models involving several assumptions (Level 3 inputs). The assumptions that are used are based upon what we believe a hypothetical marketplace participant would use in estimating fair value. We base our fair value estimates on assumptions we believe to be reasonable but that are unpredictable and inherently uncertain. Determining the fair value of our reporting units involves the use of significant estimates and assumptions and considerable management judgment. We base our fair value estimates on assumptions we believe to be reasonable at the time, but such assumptions are subject to inherent uncertainty, such as weighted average cost of capital and revenue growth rates which are forward-looking and affected by expectations about future market or economic conditions. Similarly, in a specific period, a reporting unit could significantly underperform relative to its historic or projected future operating results. Either situation could result in a meaningfully different estimate of the fair value of our reporting units, and a consequent future impairment charge. For the three and nine months ended September 30, 2024, no triggering event or changes to circumstances indicated that a potential impairment had occurred. RECENTLY PRONOUNCED ACCOUNTING STANDARDS In November 2023, the FASB issued Accounting Standards Update (ASU) 2023-07 - Segment Reporting (Topic 280), Improvements to Reportable Segment Disclosures. ASU 2023-07 enhances the disclosures required for reportable segments in annual and interim consolidated financial statements. The guidance is effective for fiscal years beginning after December 15, 2023, and interim periods within fiscal years beginning after December 15, 2024. Early adoption is permitted. We are currently evaluating the impact that the new guidance will have on our consolidated financial statements. In December 2023, the FASB issued ASU 2023-09 – Income Taxes (Topic ASC 740) Income Taxes. The ASU improves the transparency of income tax disclosures by requiring (1) consistent categories and greater disaggregation of information in the rate reconciliation and (2) income taxes paid disaggregated by jurisdiction. It also includes certain other amendments to improve the effectiveness of income tax disclosures. ASU 2023-09 is effective for annual periods beginning after December 15, 2024. Early adoption is permitted. T his guidance will not have a material impact upon our financial position and results of operations.

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/disclosureRef -Topic 235 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 1 -Publisher FASB -URI https://asc.fasb.org/1943274/2147483426/235-10-50-1 Reference 2: http://fasb.org/us-gaap/role/ref/legacyRef -Topic 235 -Name Accounting Standards Codification -Publisher FASB -URI https://asc.fasb.org/235/tableOfContent + Details
Name: | us-gaap_SignificantAccountingPoliciesTextBlock
Namespace Prefix: | us-gaap_
Data Type: | dtr-types:textBlockItemType
Balance Type: | na
Period Type: | duration