5 Hidden Causes of Revenue Leakage

Revenue leakage is rarely dramatic. There is no single catastrophic event - just a steady, quiet loss of a few percent that never appears as a line item on any report. Most practices discover it only when they compare what they should have collected against what actually landed in the bank.

Here are the five leaks we find most often, and how to close each one.

1. Eligibility checked, but not verified

Running an automated eligibility check and reading the response are two different activities. An automated check confirms the policy is active. It does not confirm that the specific service is covered, that the plan is primary, that the deductible has been met, or that the patient's plan requires a referral.

The fix is a tiered process: automated batch checks 72 hours ahead for everyone, plus manual verification for high-dollar procedures, new patients, and any response that returns an ambiguous status.

2. Prior authorizations that expire before the service

Authorizations carry validity windows and unit limits. When a procedure gets rescheduled - and procedures get rescheduled constantly - the authorization does not follow it. The claim then denies for no authorization even though one was obtained.

The control is simple and almost never implemented: every reschedule triggers an authorization re-check. Tie it to the scheduling event, not to a person remembering.

3. Charges that are never captured

Missing charges are invisible by definition. Nothing denies, because nothing was ever billed. Common sources include procedures performed at the end of a long day, services rendered by a covering provider, supplies and injectables administered in-office, and anything documented in a free-text note rather than an order.

The detection method is reconciliation: compare the schedule against posted charges every single day. Every appointment with a completed status should have either a charge or a documented reason there is none. A daily reconciliation takes a few minutes; a monthly one takes hours and recovers less, because the timely filing clock has been running.

4. Underpayments that pass silently through posting

This is the largest and least visible leak. A claim is paid, the payment posts, the balance closes, and the encounter disappears from every work queue. Nobody notices the payment was 18 percent below the contracted rate.

Detecting underpayments requires the contracted fee schedule loaded into the system and an automated variance check at posting. Without that, payment posting is simply recording whatever the payer decided to send.

• Load and maintain fee schedules for every contracted payer.
• Flag any remittance below the expected allowable by more than a set tolerance.
• Track variance by payer over time - patterns are far more valuable than individual instances, because they support renegotiation.

5. Denials that are written off instead of worked

A meaningful share of denials are never appealed. Sometimes the balance is below an informal write-off threshold; more often the denial lands in a queue nobody owns. Small-balance denials matter because they are usually systemic - the same root cause repeating across hundreds of claims.

Two changes fix most of this:

• Categorize every denial by root cause, not just by payer code. Registration, authorization, coding, and clinical documentation are different problems with different owners.
• Route by cause, not by dollar value. A $40 denial appearing 300 times is a $12,000 process defect, and fixing the cause prevents the next 300.

Where to start

Do not attempt all five at once. Start with underpayment detection, because it requires no clinical workflow change and typically surfaces recoverable dollars within the first month. Then move upstream to charge capture, then to authorization controls. Fixing the front end is more durable, but fixing the back end funds the effort.