Revenue Leakage in Medical Practices: How to Find It and Fix It

Revenue leakage — money that a practice has earned but failed to collect — is one of the most persistent financial problems in independent medicine. Unlike obvious losses such as bad debt or write-offs, revenue leakage is often invisible. Claims are submitted, payers process them, and a partial payment arrives. Without a systematic process for comparing expected reimbursement to actual reimbursement, the gap simply accumulates quietly over time.

Industry estimates suggest that the average medical practice loses between five and ten percent of earned revenue to leakage. For a practice billing $2 million annually, that is $100,000 to $200,000 in revenue that was earned but not collected. For small independent practices with tight margins, this is not a rounding error — it is often the difference between a viable practice and a struggling one.

Where revenue leakage comes from

Revenue leakage has several distinct sources, each requiring a different response.

Underpaid claims. A payer processes the claim but pays less than the contracted rate. This can happen because the claim was processed under the wrong fee schedule, the modifier was misapplied, or the payer simply paid less than owed. Without comparing the payment to the expected amount, underpayment is easy to miss — the claim was paid, so it looks resolved.

Denied claims not followed up. A denial is issued, the claim is acknowledged, and then nothing happens. The appeal window closes. The revenue is gone. Denial follow-up is a high-volume, repetitive task — which means it is exactly the kind of work that falls behind when staff are stretched thin.

Claims not submitted. Services provided but not billed. This is more common than most practice administrators expect, particularly in practices where clinical documentation is completed by physicians at the end of a long day.

Pre-authorization failures. A service is provided without an active authorization, the claim is denied for lack of authorization, and the practice is unable to retroactively obtain one. This is an upstream problem with a downstream revenue impact.

Timely filing limits missed. Payers have filing deadlines. Claims submitted after the deadline are denied for timely filing, with no recourse. This typically happens when claim submission is delayed due to documentation issues or workflow gaps.

How to identify revenue leakage in your practice

Most practice management platforms contain the data needed to identify revenue leakage — but they do not surface it automatically. Finding leakage requires asking specific questions of your claims data.

Start with underpayment analysis. Pull claims for the past 12 months and compare what payers paid to what was contracted. Sorted by payer and CPT code, this analysis typically reveals patterns quickly: a specific payer consistently underpaying a specific procedure code, or a category of services where actual collections are significantly below expected.

Identify unpaid claims by age. Any claim that is more than 90 days old without a payment or a denial deserves attention. Payer adjudication typically occurs within 30–45 days. A claim that has been sitting for 90 days or more is either lost, stuck in a payer system, or waiting on information the payer has not communicated clearly.

Analyze denial patterns. Look at your denial rate by payer and by denial reason code. A high denial rate from a specific payer for a specific reason often indicates a systematic problem — incorrect billing practice, missing documentation, or a payer policy change that has not been incorporated into your workflow.

Review zero-paid claims. Claims that went through adjudication and returned a payment of zero deserve specific attention. These are different from denials — the claim was processed, and the payer determined that zero was owed. This sometimes indicates a coverage issue, a coordination-of-benefits problem, or a duplicate claim flag.

The challenge of recovery

Identifying revenue leakage is the easier part. Recovery requires someone to actually follow up — calling payer provider relations lines, submitting corrected claims, filing appeals within the appropriate window, and tracking each item through to resolution.

This is time-consuming work. It requires knowledge of payer-specific appeal procedures, familiarity with claim correction processes, and enough persistence to follow a single claim through multiple touchpoints. For practices without a dedicated revenue cycle staff member, this work often does not get done consistently.

There are a few ways practices address this operationally.

Dedicated RCM support. Some practices outsource revenue cycle management to a billing service or RCM vendor. This can work well if the vendor provides clear reporting on what they recovered and what they pursued. The risk is limited visibility into what the vendor is actually doing.

In-house staff with structured follow-up. Assigning a staff member to claims follow-up as a defined, scheduled responsibility — rather than an "as-time-allows" task — improves consistency. The key is having a clear list of what needs follow-up, which requires the analytics to generate that list in the first place.

Automated identification with human follow-up. The most efficient model is one where technology identifies what needs attention — generating a list of underpaid claims, aging unpaid items, and high-priority denials — and a dedicated person or virtual assistant works through that list systematically.

Building a sustainable process

The practices that consistently minimize revenue leakage treat it as an ongoing operational discipline, not a periodic clean-up project.

This means reviewing claims analytics monthly rather than annually, assigning clear ownership for follow-up on specific denial categories, and building the habit of comparing actual collections to expected reimbursement at the payer and CPT-code level.

It also means having the tools to surface the relevant information without requiring manual analysis. Revenue intelligence that is buried in a reports module no one opens is not useful. The information needs to be visible, current, and actionable.

Revenue leakage is recoverable. But recovering it requires knowing where to look — and having a process that ensures someone actually does the work.