XML 57 R32.htm IDEA: XBRL DOCUMENT

SUMMARY OF SIGNIFICANT ACCOUNTING POLICIES (Policies)

12 Months Ended

Dec. 31, 2024

Accounting Policies [Abstract]

Principles of Consolidation

Principles of Consolidation

The consolidated financial statements of TruBridge include the accounts of the Company and its wholly-owned subsidiaries. All significant intercompany balances and transactions have been eliminated.

Cash and Cash Equivalents

Cash and Cash Equivalents

Cash and cash equivalents can include time deposits and certificates of deposit with original maturities of three months or less that are highly liquid and readily convertible to a known amount of cash. These assets are stated at cost, which approximates market value, due to their short duration or liquid nature.

Presentation

Reportable Segments Presentation Changes

In May 2024, the Company realigned its reporting structure due to certain organizational changes. As a result, the Company changed from three reportable segments of (i) Revenue Cycle Management (“RCM”), (ii) Electronic Health Records (“EHR”), and (iii) Patient Engagement to two reportable segments of (i) RCM and (ii) EHR. The Patient Engagement segment results have been transitioned into the EHR segment. As part of the realignment, the reportable segment naming convention was updated. The previously reported RCM segment has been updated to Financial Health, and the former EHR segment has been updated to Patient Care. The change in reportable segments is intended to improve connectivity and alignment between the two business units to better serve our clients and more accurately reflect how the Company’s management views and operates the business. All prior segment information has been recast to reflect the Company's new segment structure and current period presentation.

Accounts Receivable and Allowance for Credit Losses

Accounts Receivable and Allowance for Credit Losses

Trade accounts receivable are stated at the amount the Company expects to collect and generally do not bear interest. The Company establishes a general allowance for credit losses based on its historical collection experience, a review in each period of the aging status of the then-outstanding accounts receivable, and external market factors. To measure expected losses, account receivables are grouped by shared risk characteristics and the days past due. In the case of a bankruptcy filing or other similar event indicating the collectability of specific customer accounts is no longer probable, a specific allowance for credit losses may be recorded to reduce the related receivable to the amount expected to be recovered. Uncollectible receivables are written-off in the period that management believes it has exhausted its ability to collect payment from the customer.

Financing Receivables

Financing Receivables

Financing receivables are comprised of short-term payment plans and sales-type leases. Short-term payment plans are stated at the amount the Company expects to collect and do not bear interest. Sales-type leases are initially recorded at the present value of the related minimum lease payments.

An allowance for credit losses has been established for our financing receivables based on the historical level of customer defaults under such arrangements. In the case of a bankruptcy filing or other similar event indicating the collectability of specific customer accounts is no longer probable, a specific reserve may be recorded to reduce the related receivable to the amount expected to be recovered. Customer payments are considered past due if a scheduled payment is not received within contractually agreed upon terms, with amounts reclassified to accounts receivable when they become due. As a result, we evaluate the credit quality of our financing receivables on an ongoing basis utilizing an aging of receivables and write-offs, customer collection experience, the customer’s financial condition and known risk characteristics impacting the respective customer base, as well as existing economic conditions, to determine if any further allowance is necessary. Amounts are specifically charged off once all available means of collection have been exhausted.

Inventories

Inventories are stated at lower of cost or net realizable value using the average cost method. The Company’s inventories are comprised of computer equipment, forms and supplies.

Property and Equipment

Property and Equipment

Property and equipment is recorded at cost, less accumulated depreciation. Additions and improvements to property and equipment that materially increase productive capacity or extend the life of an asset are capitalized. Maintenance, repairs and minor renewals are expensed as incurred. Upon retirement or other disposition of such assets, the related costs and accumulated depreciation are removed from the respective accounts and any resulting gain or loss is included in the results of operations.

Depreciation expense is computed using the straight-line method over the asset’s useful life, which is generally 5 years for computer equipment, furniture, and fixtures and 30 years for buildings. Leasehold improvements are depreciated over the shorter of the asset’s useful life or the remaining lease term. The Company reviews for the possible impairment of long-lived assets whenever events or changes in circumstances indicate that the carrying amount of an asset may not be recoverable. Depreciation expense is included in operating expenses in the consolidated statements of operations.

Business Combinations

Business Combinations

We apply business combination accounting when we acquire a business. Business combinations are accounted for at fair value. The associated acquisition costs are expensed as incurred and recorded in general and administrative expenses; restructuring costs associated with a business combination are expensed as incurred; contingent consideration is measured at fair value at the acquisition date, with changes in fair value after the acquisition date affecting earnings; changes in deferred tax asset valuation allowances and income tax uncertainties after the measurement period affect income tax expense; and goodwill is determined as the excess of the fair value of the consideration conveyed in the acquisition over the fair value of the net assets acquired. The accounting for business combinations requires estimates and judgments as to expectations for future cash flows of the acquired business, and the allocation of those cash flows to identifiable intangible assets, in determining the estimated fair value for assets and liabilities acquired. The fair values assigned to tangible and intangible assets acquired and liabilities assumed, are based on management's estimates and assumptions, including valuations that utilize customary valuation procedures and techniques. If the actual results differ from the estimates and judgments used in these estimates, the amounts recorded in the financial statements could result in a possible impairment of the intangible assets and goodwill, or require acceleration of the amortization expense of finite-lived intangible assets. The results of the acquired businesses' operations are included in the Consolidated Statements of Operations of the combined entity beginning on the date of the acquisition. We have applied this acquisition method to the transactions described in Note 3 - Business Combinations and Disposals.

Goodwill

Goodwill is recorded as the difference, if any, between the aggregate consideration paid for an acquisition and the fair value of the identifiable net tangible and intangible assets acquired. Goodwill is not amortized but is evaluated for impairment annually or more frequently if indicators of impairment are present or changes in circumstances suggest that impairment may exist. We test annually for impairment as of October 1.

As part of our annual goodwill impairment test, we first assess qualitative factors to determine whether it is more likely than not that the fair value of a reporting unit is less than its carrying amount. If we conclude that it is more likely than not that the fair value of a reporting unit is less than its carrying amount, we conduct a quantitative goodwill impairment assessment, which compares the fair value of the reporting unit with its carrying amount, including goodwill. If the carrying amount of the reporting unit exceeds its fair value, an impairment charge is recognized for the amount by which the carrying amount exceeds the total amount of goodwill allocated to that reporting unit. If the fair value of the reporting unit exceeds its carrying amount, the goodwill of the reporting unit is not considered to be impaired.

Purchased Intangible Assets

Purchased Intangible Assets

Purchased intangible assets are acquired in connection with a business acquisition, and are amortized over their estimated useful lives based on the pattern of economic benefit expected from each asset. We concluded for certain purchased intangible assets that the pattern of economic benefit approximated the straight-line method, and therefore, the use of the straight-line method was appropriate, as the majority of the cash flows will be recognized ratably over the estimated useful lives and there is no degradation of the cash flows over time.

We assess the recoverability of intangible assets whenever events or changes in circumstances indicate that the carrying amount of the asset may not be recoverable. The carrying amount is not recoverable if it exceeds the undiscounted sum of cash flows expected to result from the use and eventual disposition of the asset. If the asset is not recoverable, the impairment loss is measured by the excess of the asset's carrying amount over its fair value.

Revenue Recognition

Revenue Recognition

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 and services. We enter into contracts that can include various combinations of products and services, which are generally distinct and accounted for as separate performance obligations. The Company employs the 5-step revenue recognition model under Accounting Standards Codification 606, Revenue from Contracts with Customers, to: (1) identify the contract with the client, (2) identify the performance obligations in the contract, (3) determine the transaction price, (4) allocate the transaction price to the performance obligations in the contract, and (5) recognize revenue when (or as) the entity satisfies a performance obligation.

Revenue is recognized net of shipping charges and any taxes collected from clients, which are subsequently remitted to governmental authorities.

•Financial Health

Our Financial Health business unit provides an array of revenue cycle management (“RCM”) services consisting of accounts receivable management, private pay services, insurance services, medical coding, electronic billing, statement processing, payroll processing, and contract management. Fees are recognized over the period of the client contractual relationship as the services are performed. We generally determine standalone selling prices (“SSP”) based on a standard list price for each product, taking into consideration certain factors, including contract length and the number of subscriptions or licenses purchased within the contract. Judgment is required in determining whether performance obligations are distinct, SSP, and the amount of variable consideration to reflect as transaction price. Fees for many of these services are invoiced, and revenue recognized accordingly, based on the volume of transactions or a percentage of client accounts

receivable collections. Payment is due monthly for RCM services with certain amounts varying based on utilization and/or volumes.

Our Financial Health business unit also provides professional IT services. Revenue from professional IT services is recognized as the services are performed based on SSP, which is determined by observable stand-alone selling prices. Payment is due monthly as services are performed.

Lastly, our Financial Health business unit also provides certain software solutions and related support under Software as a Service (“SaaS”) arrangements and time-based software licenses. Revenue from SaaS arrangements is recognized in a manner consistent with SaaS arrangements for electronic health records (“EHR”) software, as discussed below. Revenue from time-based software licenses is recognized upon delivery to the client (“point in time”) and revenue from non-license components (i.e., support) is recognized ratably over the respective contract term (“over time”). SSP for time-based licenses is determined using the residual approach, while the non-license component is based on cost plus reasonable margin.

•Patient Care

The Company enters into contractual obligations to sell perpetual software licenses, installation, conversion, and related training services, software application support, hardware, and hardware maintenance services to acute care hospitals. The Company also enters into contractual obligations to sell SaaS, time-based software licenses, implementation and customization professional services, and software application support services to a variety of healthcare organizations, including hospital systems, health ministries, and government and non-profit organizations.

•Non-recurring Revenues

•Perpetual software licenses and installation, conversion, and related training services for acute care customers are not considered separate and distinct performance obligations due to the proprietary nature of our software and are, therefore, accounted for as a single performance obligation on a module-by-module basis. Revenue is recognized as each module's implementation is completed based on the module's SSP, net of discounts. We determine each module's SSP using the residual method. Fees for licenses and installation, conversion, and related training services are typically due in three installments: (1) at placement of order, (2) upon installation of software and commencement of training, and (3) upon satisfactory completion of monthly accounting cycle or end-of-month operation by application and as applicable for each application. Often, short-term and/or long-term financing arrangements are provided for software implementations; refer to Note 11 - Financing Receivables for further information. EHR implementations include a system warranty that terminates thirty days from the software go-live date, the date which the client begins using the system in a live environment.

•Hardware revenue is recognized separately from software licenses at the point in time it is delivered to the client. The SSP of hardware is cost plus a reasonable margin and revenue is recognized on a gross basis. Payment is generally due upon delivery of the hardware to the client. Standard manufacturer warranties apply to hardware.

•Implementation and customization services are considered a separate and distinct performance obligation. Revenue is recognized over time based on SSP, which is generally directly observable. Payment for these professional services is typically due in two installments: (1) upon signature of the agreement and (2) upon customer acceptance of the delivered services.

•Recurring Revenues

•Software application support and hardware maintenance services sold with software licenses and hardware are separate and distinct performance obligations. Revenue for support and maintenance services is recognized based on SSP, which is the renewal price, ratably over the life of the contract, which is generally three to five years. Payment is due either monthly for support and maintenance services provided or for the full amount of annual support fees at the beginning of an annual license term.

•Subscriptions to third-party content revenue is recognized as a separate performance obligation ratably over the subscription term based on SSP, which is cost plus a reasonable margin, and revenue is recognized on a gross basis. Payment is due monthly for subscriptions to third party content.

•SaaS arrangements for EHR software and related conversion and training services are considered a single performance obligation. Revenue is recognized on a monthly basis as the SaaS service is provided to the client over the contract term. Payment is due monthly for SaaS services provided.

•Term-based software licenses are considered a separate and distinct performance obligation. Revenue is recognized based on SSP, which is directly observable, at the point in time the term-based licenses are delivered to the client or upon annual renewal. Payment is generally due upon delivery of licenses or upon annual renewal.

•Deferred Revenue

Deferred revenue represents amounts invoiced to clients for which the services under contract have not been completed and revenue has not been recognized, including annual renewals of certain software subscriptions and customer deposits for implementations to be performed at a later date. Revenue is recognized ratably over the life of the software subscriptions as services are provided and at the point-in-time when implementations have been completed.

The following table details deferred revenue for the years ended December 31, 2024 and 2023, included in the consolidated balance sheets:


			For years ended December 31,
(In thousands)			2024						2023
Beginning balance			$	8,677					$	11,590
Deferred revenue recorded			27,485						17,192

Less deferred revenue recognized as revenue			(25,509)						(20,105)
Ending balance			$	10,653					$	8,677

The deferred revenue recorded for the years ended December 31, 2024 and 2023 is comprised primarily of the annual renewals of certain software subscriptions billed during the first quarter of each year and deposits collected for future Patient Care installations. The deferred revenue recognized as revenue during the years ended December 31, 2024 and 2023 is comprised primarily of the periodic recognition of annual renewals that were deferred until earned and deposits for future Patient Care installations that were deferred until earned.

•Costs to Obtain and Fulfill a Contract with a Customer

Costs to obtain a contract include the commission costs related to SaaS and Financial Health arrangements, which are capitalized and amortized ratably over the expected life of the customer. As a practical expedient, we generally recognize the incremental costs of obtaining a contract as an expense when incurred if the amortization period of the asset would have been one year or less. Costs to obtain a contract are recorded within the caption “Expenses - Sales and marketing” in the accompanying consolidated statements of operations.

Contract fulfillment costs related to the implementation of SaaS arrangements are capitalized and amortized ratably over the expected life of the customer contract. Costs to fulfill contracts consist of the payroll costs for the implementation of SaaS arrangements, including time for training, conversions, and installation that is necessary for the software to be utilized. Contract fulfillment costs are recorded within the caption “Costs of revenue (exclusive of amortization and depreciation) - Patient Care” in the accompanying consolidated statements of operations.

Costs to obtain and fulfill contracts related to SaaS and Financial Health arrangements are included within the “Prepaid expenses and other current assets” and "Other assets, net of current portion" line items in our accompanying consolidated balance sheets.

The following table details costs to obtain and fulfill contracts with customers for the years ended December 31, 2024 and 2023, included in the consolidated balance sheets:


			For years ended December 31,
(In thousands)			2024						2023
Beginning balance			$	13,115					$	11,577
Costs to obtain and fulfill contracts capitalized			7,009						7,390
Less costs to obtain and fulfill contracts recognized as expense			(7,537)						(5,852)
Ending balance			$	12,587					$	13,115

•Significant Judgments

Our contracts with clients often include promises to transfer multiple products and services. Determining whether products and services are considered distinct performance obligations that should be accounted for separately versus together may require significant judgment.

Judgment is required to determine SSP for each distinct performance obligation. We use observable SSP for items that are sold on a stand-alone basis to similarly situated clients at unit prices within a sufficiently narrow range. For performance obligations that are sold to different clients for a broad range of amounts, or for performance obligations that are never sold on a stand-alone basis, the residual method in determining SSP is applied and requires significant judgment.

Allocating the transaction price, including estimating SSP of promised goods and services for contracts with discounts or variable consideration, may require significant judgment. Due to the short time frame of the implementation cycle, discount allocation is immaterial as revenue is recognized net of discounts within the same reporting period. In scenarios where the Company enters into a contract that includes both a software license and business processing services (“BPS”) or other services that are charged based on volume of services rendered, the Company allocates variable amounts entirely to a distinct good or service. The terms of the variable payment relate specifically to the entity’s efforts to satisfy that performance obligation.

Significant judgment is required in determining the expected life of a customer relationship, which is the amortization period for costs to obtain and fulfill a contract that have been capitalized. The Company determined that the expected life of the customer relationship is not materially different from the initial contract term based on the characteristics of the SaaS offering.

•Remaining Performance Obligations

Disclosures regarding remaining performance obligations are not considered material as the overwhelming majority of the Company's remaining performance obligations either (a) are related to contracts with an expected duration of one year or less, or (b) exhibit revenue recognition in the amount to which the Company has the right to invoice.

Although we believe that our approach to estimates and judgments regarding revenue recognition is reasonable, actual results could differ, and we may be exposed to increases or decreases in revenue that could be material.

Stock-Based Compensation

Stock-Based Compensation

The Company accounts for stock-based compensation according to the provisions of ASC 718, Compensation – Stock Compensation, which establishes accounting for stock-based awards exchanged for employee services. Accordingly, stock-based compensation cost is measured at the grant date based on the fair value of the award, and is recognized as an expense over the employee’s or non-employee director’s requisite service period.

Software Development Costs

Software Development Costs

Our software solutions are offered to our clients through SaaS delivery models, traditional perpetual licenses, and term licenses. Development costs associated with the solutions offered exclusively through a SaaS model are accounted for in accordance with ASC 350-40, Internal Use Software. All other client solution development costs are accounted for in accordance with ASC 985-20, Costs of Software to be Sold, Leased, or Marketed.

Under ASC 350-40, software development costs related to preliminary project activities and post-implementation and maintenance activities are expensed as incurred. We capitalize direct costs related to application development activities that are probable to result in additional functionality. Capitalized costs are amortized on a straight-line basis over five years. We test for impairment whenever events or changes in circumstances that could impact recoverability occur.

Under ASC 985-20, software development costs incurred in creating computer software solutions are expensed until technological feasibility has been established upon completion of a detailed program design or, in the absence of a detailed program design, upon completion of a product design and working model of the software product. Thereafter, all software development costs incurred through the software’s general release date are capitalized and subsequently recorded at the lower of amortized cost or net realizable value. Capitalized costs are amortized based on the current and expected future revenue for each software solution with minimum annual amortization equal to the straight-line amortization over the estimated economic life of the solution, which is estimated to be five years.

See Note 5 - Software Development for further information relating to our software development costs.

Income Taxes

We account for income taxes in accordance with ASC 740, Accounting for Income Taxes. Under this topic, deferred income taxes are determined utilizing the asset and liability approach. This method gives consideration to the future tax consequences associated with differences between financial accounting and tax bases of assets and liabilities. The effect on the deferred tax assets and liabilities of a change in tax rates is recognized in income in the period that includes the enactment date. We recognize interest and penalties accrued related to unrecognized tax benefits in the consolidated statements of operations as a component of the provision for income taxes.

We also make a provision for uncertain income tax positions in accordance with the ASC 740, Accounting for Income Taxes. These provisions require that a tax position taken in a tax return be recognized in the financial statements when it is more likely than not (i.e., a likelihood of more than fifty percent) that the position would be sustained upon examination by tax authorities. A recognized tax position is then measured at the largest amount of benefit that is greater than fifty percent likely of being realized upon settlement. The topic also requires that changes in judgment that result in subsequent recognition, derecognition, or change in a measurement date of a tax position taken in a prior annual period (including any related interest and penalties) be recognized as a discrete item in the interim period in which the change occurs.

Valuation allowances are recorded when, in the opinion of management, it is more likely than not that all or a portion of the deferred tax assets will not be realized. These valuation allowances can be impacted by changes in tax laws, changes to statutory tax rates, and future taxable income, and are based on our judgment, estimates, and assumptions.

Use of Estimates

Use of Estimates

The preparation of financial statements in conformity with U.S. GAAP requires that management make estimates and assumptions that affect the reported amounts of assets and liabilities, the disclosures of contingent assets and liabilities at the date of the financial statements, and the reported revenues and expenses during the reporting periods. Actual results could differ from those estimates.

Segment Reporting

Segment Reporting

Operating segments are identified as components of an enterprise about which separate discrete financial information is evaluated by the chief operating decision maker, which we refer to as the "CODM", or decision-making group in assessing performance and making decisions regarding resource allocation. The Company has prepared operating segment information based on the manner in which management disaggregates the Company's operations for making internal operating decisions. For more information, see Note 18 - Segment Reporting.

New Accounting Standards Adopted in 2024 and New Accounting Standards Yet to be Adopted

New Accounting Standards Adopted in 2024

In November 2023, the Financial Accounting Standard Board (“FASB”) issued Accounting Standard Update (“ASU”) 2023-07, “Segment Reporting (Topic 280): Improvements to Reportable Segment Disclosures” (“ASU 2023-07”), which is intended to improve reportable segment disclosure requirements, primarily through additional and more detailed information about a reportable segment's expenses. The guidance is effective for fiscal years beginning after December 15, 2023, and interim periods within fiscal years beginning after December 15, 2024, with early adoption permitted. The guidance is to be applied retrospectively to all prior periods presented in the financial statements. Upon transition, the segment expense categories and amounts disclosed in the prior periods should be based on the significant segment expense categories identified and disclosed in the period of adoption. The Company has evaluated the impact and determined there is no material impact with adopting ASU 2023-07. The Company has updated the presentation in Note 18 - Segment Reporting to adhere to the requirements.

New Accounting Standards Yet to be Adopted

In December 2023, the FASB issued ASU 2023-09, “Income Taxes (Topic 740): Improvements to Income Tax Disclosures” (“ASU 2023-09”), which requires public entities to provide disclosure of disaggregated information in the entity’s tax rate reconciliation, as well as disclosure of income taxes paid disaggregated by jurisdiction. ASU 2023-09 is effective for fiscal years beginning after December 15, 2024, with early adoption permitted. The Company is currently evaluating the impact of adopting ASU 2023-09.

In November 2024, the FASB issued ASU No. 2024-03, Income Statement—Reporting Comprehensive Income—Expense Disaggregation Disclosures, which requires additional disclosure of certain costs and expenses within the notes to the financial statements. The new standard is effective for annual periods beginning after December 15, 2026 and interim periods beginning in the first quarter of fiscal year 2028. Early adoption is permitted. The new standard is to be applied on a prospective basis, but retrospective application is permitted. The Company is currently evaluating the impact of adopting ASU 2024-03.

Subsequent Events

Subsequent Events

The Company has evaluated subsequent events through March 17, 2025, the date these consolidated financial statements were issued. The Company concluded that no subsequent events have occurred that would require recognition or disclosure in the consolidated financial statements.

Net Income Per Share

The Company presents basic and diluted earnings per share ("EPS") data for its common stock. Basic EPS is calculated by dividing the net income (loss) attributable to stockholders of the Company by the weighted average number of shares of common stock outstanding during the period. Diluted EPS is determined by adjusting the net income attributable to stockholders of the Company and the weighted average number of shares of common stock outstanding during the period for the effects of all dilutive potential common shares, including awards under stock-based compensation arrangements.

The Company's unvested restricted stock awards (see Note 9 - Stock-Based Compensation and Equity) are considered participating securities under ASC 260, Earnings Per Share, because they entitle holders to non-forfeitable rights to dividends until the awards vest or are forfeited. When a company has a security that qualifies as a "participating security," the Codification requires the use of the two-class method when computing basic EPS. The two-class method is an earnings allocation formula that determines EPS for each class of common stock and participating security according to dividends declared (or accumulated) and participation rights in undistributed earnings. In determining the amount of net income to allocate to common stockholders, income is allocated to both common stock and participating securities based on their respective weighted average shares outstanding for the period, with net income attributable to common stockholders ultimately equaling net income less net income attributable to participating securities. Diluted EPS for the Company's common stock is computed using the more dilutive of the two-class method or the treasury stock method.

ASC 820, Fair Value Measurements and Disclosures, establishes a framework for measuring fair value and expands financial statement disclosures about fair value measurements. Fair value is the price that would be received to sell an asset or paid to transfer a liability (an exit price) in the principal or most advantageous market for the asset or liability in an orderly transaction between market participants at the measurement date. The Codification topic does not require any new fair value measurements, but rather applies to all other accounting pronouncements that require or permit fair value measurements. The Codification topic requires that assets and liabilities carried at fair value be classified and disclosed in one of the following three categories:

Level 1: Quoted market prices in active markets for identical assets or liabilities.

Level 2: Observable market-based inputs or unobservable inputs that are corroborated by market data.

Level 3: Unobservable inputs that are not corroborated by market data.

The fair value of contingent consideration represents the potential earnout incentive for Viewgol’s former equity holders. We estimated the fair value of this contingent consideration based on the probability of Viewgol meeting EBITDA targets (subject to certain pro-forma adjustments). Management reviews the historical and projected performance of Viewgol and uses an option pricing method to revalue the contingent consideration. The revaluation requires management to make certain assumptions and represents management’s best estimate at the valuation date.