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

Accounting Standards and Significant Accounting Policies | 9 Months Ended
--- | ---
Sep. 30, 2025
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, 2024, filed with the SEC on February 19, 2025, that have had a material impact on our condensed consolidated financial statements and related notes. See Recently Pronounced Accounting Standard below. REVENUE RECOGNITION Nature of Products and Services We account for revenue in accordance with Accounting Standards Codification (“ASC”) 606, Revenue from Contracts with Customers. We earn the majority of our revenues from subscription-based services and post-contract client 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 clients 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 client •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 Our software arrangements with clients contain multiple performance obligations that range from software license deliveries; installation, training, consulting, software modification and customization to meet specific client 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, client 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 client over time using progress-to-completion methods. Depending on the contract, we measure progress-to-completion primarily using labor hours incurred. 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. Subscription-Based Services Subscription-based services consist primarily of revenues derived from software as a service (“SaaS”) arrangements and transaction-based fees. For SaaS arrangements, we evaluate whether the client has the contractual right to take possession of our software at any time during the hosting period without significant penalty and whether the client can feasibly maintain the software on the client’s hardware or enter into another arrangement with a third-party to host the software. We recognize SaaS services ratably over the term of the arrangement, which range from one to 10 years, but most arrangements are typically for periods of one to three years. For professional services associated with certain SaaS arrangements, we have concluded that the services are not distinct, and we recognize the revenue ratably over the remaining contractual period once we have provided the client access to the software. Transaction-based fees primarily relate to digital government services and online payment services, which are sometimes offered with the assistance of third-party vendors. 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 client) and record the net amount as revenue. For transaction-based revenues from digital government services and online payments, we have the right to charge the client an amount that directly corresponds with the value to the client of our performance to date. Therefore, we recognize revenues for these services over time based on the amount billable to the client. In some cases, we are paid on a fixed-fee basis and recognize the revenue ratably over the contractual period. Typically, the structure of our arrangements does not give rise to variable consideration. However, in those instances where variable consideration exists, we include in our estimates additional revenues for variable consideration when we believe we have an enforceable right, the amount can be estimated reliably, and its realization is probable. Costs of performing services under subscription-based arrangements are expensed as incurred, except for certain direct and incremental contract origination costs associated with SaaS arrangements. Such direct and incremental costs are capitalized and amortized ratably over the period of benefit. Post-Contract Client Support (Maintenance) Our clients 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. PCS is considered distinct when purchased with our software licenses. Our PCS agreements are typically renewable annually. PCS is recognized over time on a straight-line basis over the period the PCS is provided. All significant costs and expenses associated with PCS are expensed as incurred. Professional Services When professional services are distinct, the fee allocable to the service element is recognized over the time we perform the services and is billed on a time and material or milestone basis. Contract fees are typically billed on a milestone basis as defined within contract terms. 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. Revenue is recognized net of allowances for sales adjustments and any taxes collected from clients, 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 clients. 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 clients annually at the beginning of each annual coverage period. Accounts receivable is as follows:
| September 30, 2025 |  | December 31, 2024
Accounts receivable - current | $ | 661,986 |  |  | $ | 587,634 |
Accounts receivable - long term | 6,855 |  |  | 7,153 |
Total accounts receivable | $ | 668,841 |  |  | $ | 594,787 |
Total accounts receivable, including total current and long-term accounts receivable, net of allowance for losses and sales adjustments, was $668.8 million and $594.8 million, as of September 30, 2025, and December 31, 2024, respectively. We have recorded unbilled receivables of $110.4 million and $115.6 million as of September 30, 2025, and December 31, 2024, respectively. 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 the long-term portion of accounts receivable in the accompanying condensed consolidated balance sheets. Unbilled receivables also include retention receivables of $11.7 million and $11.4 million as of September 30, 2025, and December 31, 2024, respectively, which become payable upon the completion of the contract or completion of our fieldwork and formal hearings. 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 $23.0 million and $17.3 million as of September 30, 2025, and December 31, 2024, respectively. GOODWILL AND OTHER INTANGIBLE ASSETS Goodwill We perform an impairment assessment annually on October 1, or more frequently if indicators of potential impairment exist, which includes evaluating qualitative and quantitative factors to assess the likelihood of an impairment of each reporting unit’s goodwill. If the conclusion of an impairment assessment is that it is more likely than not that the fair value of the reporting unit is more than its carrying value, goodwill is not considered impaired, and we are not required to perform the quantitative goodwill impairment test. If the conclusion of an impairment assessment is that it is more likely than not that the fair value is less than its carrying value, we perform the quantitative goodwill impairment test, which compares the fair value of the reporting unit to its carrying value. Impairments, if any, are based on the excess of the carrying amount over the fair value. 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. Client base and acquired software each comprise approximately half of our purchased intangible assets other than goodwill. We review our client turnover each year for indications of impairment. 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. For the three and nine months ended September 30, 2025, no triggering event or changes to circumstances indicated that a potential impairment had occurred for goodwill or other intangible assets. RECENTLY PRONOUNCED ACCOUNTING STANDARDS In September 2025, the Financial Accounting Standards Board (the “FASB”) issued Accounting Standards Update (“ASU”) 2025-06 - Intangibles-Goodwill and Other-Internal-Use Software (Subtopic 350-40): Targeted Improvements to the Accounting for Internal-Use Software. This update removes the prescriptive software development “project stages” and requires capitalization of software costs once (1) management authorizes and commits funding and (2) completion and use are probable. Entities must evaluate significant development uncertainty related to technological innovations or performance requirements. The amendments also require Subtopic 360-10 disclosures for all capitalized internal-use software costs and clarify that intangible asset disclosures under Subtopic 350-30 are not required. The standard is effective for annual periods beginning after December 15, 2027, and interim periods within those annual reporting periods, with early adoption permitted. The Company is currently evaluating the impact of this guidance on the Company’s financial statements. In July 2025, the FASB issued ASU 2025-05 - Financial Instruments-Credit Losses (Topic 326): Measurement of Credit Losses for Accounts Receivable and Contract Assets. This guidance provides a practical expedient available to all entities to simplify the estimation of the expected credit losses for current accounts receivables and current contract assets arising from revenue contracts under ASC 606. It is effective for annual reporting periods beginning after December 15, 2025, and interim periods within those annual reporting periods, with early adoption permitted. 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 payment; as such, we do not expect this new standard to have a material impact on the Company’s financial statements. In November 2024, the FASB issued ASU 2024-04 - Debt - Debt with Conversion and Other Options (Subtopic 470-20): Induced Conversions of Convertible Debt Instruments. This guidance clarifies the requirements for determining whether certain settlements of convertible debt instruments should be accounted for as an induced conversion. It is effective for annual reporting periods beginning after December 15, 2025, and interim periods within those annual reporting periods, with early adoption permitted. As of January 1, 2025, we have early-adopted this standard, and the new standard did not have a material impact on the Company’s financial statements. In November 2024, the FASB issued ASU 2024-03 - Income Statement - Reporting Comprehensive Income - Expense Disaggregation Disclosures (Subtopic 220-40): Disaggregation of Income Statement Expenses. This guidance requires public entities to disclose additional information about specific expense categories in the notes to the financial statements on an interim and annual basis. It is effective for annual reporting periods beginning after December 15, 2026, and interim periods beginning after December 15, 2027, with early adoption permitted. This guidance is not expected to have a material impact on the Company’s 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 with early adoption permitted. This guidance is not expected to have a material impact on the Company’s 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://www.xbrl.org/2003/role/disclosureRef -Topic 235 -Name Accounting Standards Codification -Publisher FASB -URI https://asc.fasb.org/235/tableOfContent Reference 2: 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 + Details
Name: | us-gaap_SignificantAccountingPoliciesTextBlock
Namespace Prefix: | us-gaap_
Data Type: | dtr-types:textBlockItemType
Balance Type: | na
Period Type: | duration