Healthcare Financial Due Diligence
Executive Summary
Key Takeaways
- ✓ Quality of earnings testing for a healthcare target should specifically examine whether reported earnings depend on a reimbursement rate, payer mix, or case mix combination that may not be sustainable, not just standard normalisation adjustments applied in any sector.
- ✓ Revenue cycle health should be tested as a distinct diligence workstream, since a target's reported revenue can be materially overstated if collection performance is deteriorating in a way not yet fully reflected in reported financials.
- ✓ Reserve adequacy for clinical liabilities, malpractice exposure, workers' compensation, and similar clinical-operations-specific liabilities, should be tested explicitly, since these liability categories carry sector-specific actuarial characteristics a generic reserve adequacy review may not capture.
- ✓ This guide addresses the financial diligence workstream generally; transaction-specific risk factors, synergy realisation, payer contract transferability, and clinical staff retention, are addressed separately in Healthcare Investment Models.
Objective¶
This guide covers how to conduct financial due diligence on a healthcare provider within Healthcare Financial Modelling, extending the general diligence discipline in Financial Model Due Diligence with sector-specific quality of earnings, revenue cycle, and clinical liability testing.
Quality of Earnings Testing¶
Quality of earnings testing for a healthcare target should specifically examine whether reported earnings depend on a reimbursement rate, payer mix, or case mix combination that may not be sustainable going forward, beyond the standard normalisation adjustments, one-off items, non-recurring expenses, applied in any sector. This means testing the target's actual revenue driver decomposition, following Hospital Financial Models, rather than accepting reported EBITDA at face value.
Revenue Cycle Health as a Distinct Workstream¶
Revenue cycle health should be tested as its own diligence workstream, since a target's reported revenue can be materially overstated if collection performance, denial rates, days in accounts receivable, is deteriorating in a way not yet fully reflected in reported financials. This lag effect, where a revenue cycle deterioration takes time to fully appear in reported results, is a distinct risk a purely historical financial statement review would not surface without a dedicated assessment following the mechanics in Revenue Cycle Modelling.
Clinical Liability Reserve Adequacy¶
Malpractice exposure, workers' compensation, and similar clinical-operations-specific liabilities should be tested for reserve adequacy explicitly, since these liability categories carry actuarial characteristics, long-tail claim development, clinical-specialty-specific risk profiles, that a generic reserve adequacy review applied across any industry may not adequately capture. Diligence should verify that the target's reserve methodology reflects its actual clinical service mix and claims history, not an industry-generic reserving benchmark.
Relationship to Transaction-Specific Diligence¶
This guide addresses the general financial diligence workstream. Transaction-specific risk factors, synergy realisation, payer contract transferability, and clinical staff retention, are addressed separately in Healthcare Investment Models, and the two workstreams should be conducted as complementary parts of a complete healthcare transaction diligence process.
Common Construction Pitfalls¶
EBITDA accepted without driver testing. Failing to decompose reported earnings into volume, case mix, and payer mix components can miss an unsustainable reimbursement or payer mix combination.
Revenue cycle deterioration missed. Relying on historical financial statements alone, without a dedicated revenue cycle health assessment, can miss an emerging collection performance deterioration not yet fully reflected in reported results.
Generic reserve benchmark applied. Testing clinical liability reserve adequacy against a generic industry benchmark, rather than the target's own clinical service mix and claims history, can miss a genuine reserve shortfall.
Recommended Practices¶
- Test reported earnings against the target's actual volume, case mix, and payer mix decomposition.
- Conduct a dedicated revenue cycle health assessment as part of diligence.
- Test clinical liability reserve adequacy against the target's own service mix and claims history.
- Coordinate this general diligence workstream with the transaction-specific testing in Healthcare Investment Models.
Continue Reading¶
Related Pillars¶
Related Technical Guides¶
How OXXON tests thisRun a free structural check with FMAE
Frequently Asked Questions
How does quality of earnings testing differ for a healthcare target?
Beyond standard normalisation adjustments applied in any sector, quality of earnings testing for a healthcare target should specifically examine whether reported earnings depend on a reimbursement rate, payer mix, or case mix combination that may not be sustainable going forward, testing the target's actual revenue driver decomposition rather than accepting reported EBITDA at face value.
Why should revenue cycle health be tested as its own diligence workstream?
Because a target's reported revenue can be materially overstated if collection performance, denial rates, days in accounts receivable, is deteriorating in a way not yet fully reflected in reported financials, a lag effect that a purely historical financial statement review would not surface without a dedicated revenue cycle health assessment.
What clinical liability reserves warrant specific diligence attention?
Malpractice exposure, workers' compensation, and similar clinical-operations-specific liabilities, which carry actuarial characteristics, long-tail claim development, clinical-specialty-specific risk profiles, that a generic reserve adequacy review applied across any industry may not adequately capture.
How does this guide relate to Healthcare Investment Models?
This guide addresses the general financial diligence workstream, quality of earnings, revenue cycle health, and clinical liability reserves. Healthcare Investment Models addresses transaction-specific risk factors, synergy realisation, payer contract transferability, and clinical staff retention, that apply once a transaction structure is under consideration. The two are complementary diligence workstreams.
Related Articles
Healthcare Financial Modelling
Healthcare financial modelling is the discipline of modelling a healthcare provider's revenue, cost, and capital structure from its clinical and operational drivers, patient volume, case mix, payer mix, and clinical staffing and equipment, rather than the generic market-price and headcount-growth drivers used in most corporate models. This page is the hub for the Knowledge Centre's healthcare and life sciences financial modelling content: how a hospital or provider operating model is structured, how the revenue cycle converts gross charges into collected cash, how service line and cost models are built, and how sector-specific business models, occupancy dynamics, and governance practice apply as this domain expands to cover the full range of healthcare and life sciences sub-sectors.
Healthcare Investment Models
Healthcare investment and acquisition modelling applies standard valuation and returns analysis to a provider target, but requires diligence-specific attention to synergy realisation risk, payer contract transferability, and clinical staff retention, three drivers that determine whether a target's standalone financial performance will actually be realised post-transaction. This guide covers how each should be tested and reflected in the investment model, building on the provider operating model architecture used throughout this pillar.
Revenue Cycle Modelling
The revenue cycle module translates gross billed charges into net patient service revenue and, ultimately, collected cash, through contractual allowances, claims denial and resubmission, and the resulting accounts receivable balance. This guide covers how to build that module: the gross-to-net waterfall, how denial and collection assumptions should be sourced and tested, and how days in accounts receivable feeds the working capital forecast.
Financial Model Due Diligence
Financial model due diligence is the discipline of testing whether the financial model used to price, structure, or finance a transaction is itself structurally sound — a distinct question from whether the target business's historical financials are reliable (the domain of financial due diligence) or whether its commercial prospects are durable (commercial due diligence). A model can be structurally unsound — an untraceable synergy figure, a broken purchase price allocation link, a hardcoded override masking the true output of a formula — independent of whether the underlying business is fundamentally healthy, and this risk is what financial model due diligence is specifically built to catch. This page is the hub for the Knowledge Centre's model-risk-in-transactions content: how model review differs by audience (independent, lender, investor, vendor), how it differs from a quality of earnings review, and how transaction-specific model risk maps onto FMAE's own structural rule set.
M&A and Transaction Due Diligence
Transaction due diligence is the structured process by which a party to a proposed transaction — most often a buyer, but also a seller preparing for sale or a lender financing the deal — investigates a target business before committing capital. It is organized into distinct workstreams (financial, commercial, operational, technical, legal, tax, ESG), run from one of three process postures (buy-side, sell-side, or vendor), and its findings feed directly into the financial model used to price the transaction and support the investment decision. This page is the hub for the Knowledge Centre's transaction due diligence content: what due diligence is, how each workstream and process posture differs, and how model risk specifically enters a transaction — the angle this platform is built to address in depth.