Revenue Leakage Audit

Five Major Leakage Areas

Most practices experience revenue loss as a vague sense that collections could be better. The reality is more specific: leakage happens at five identifiable points, each with its own causes and its own fix.

• Front-End Leakage — Eligibility, benefits, authorization and patient information gaps that cost you claims before care is even delivered. See Insurance Eligibility & Verification.
• Clinical-to-Billing Leakage — Documentation, coding and charge-capture misses where clinical work never fully translates into billable revenue. See Documentation Review & Coding and Charge Posting.
• Claims Leakage — Rejections, denials, filing issues and payer-specific problems that stall or block reimbursement. See Denial Management & Appeals.
• AR Leakage — Aging balances, follow-up gaps, underpayments and missed recovery opportunities sitting in your AR. See AR Optimization.
• Process Leakage — Manual work, workflow gaps, duplication and avoidable administrative effort draining staff time and revenue. See RPA for Healthcare RCM.

Why Leakage Goes Unnoticed

Each leakage area on its own looks like a manageable, isolated problem — one denied claim, one slow-paying payer, one overworked front-desk staffer. It’s only when you map all five areas together, against 12 months of data, that the pattern — and the dollar figure — becomes visible.

The Result

Our audit answers four questions for every leak we find: what is wrong, why it is happening, where money is being lost, and what should be fixed first. For a deeper walkthrough of the assessment itself, see our Revenue Cycle Health Check guide or start with the RCM Audit directly.

How Leakage Is Measured: Lost, Delayed and Underpaid

Leakage is the difference between the revenue your services should have produced under your payer contracts and the revenue you actually collected. It takes three forms, and each is measured differently.

The distinction matters because the response differs. Lost revenue needs prevention. Delayed revenue needs workflow and follow-up. Underpaid revenue needs payer disputes backed by evidence. An audit that lumps these together under one number cannot tell you what to do next.

A simple working formula is: leakage = expected allowed amount (contract rate x units billed) minus amount collected, plus the carrying cost of delay. The expected amount comes from fee schedules; the collected amount comes from posted 835 data.

Front-End Leakage: What Breaks and How to Spot It

Front-end problems are the cheapest to prevent and the most expensive to fix later, because a claim built on wrong coverage information can never be corrected by billing alone.

The test in an audit is simple: for a sample of visits, find the eligibility response in the system, read what it said about coverage, deductible and authorization requirements, and check whether the registration and billing workflow acted on it.

Clinical-to-Billing Leakage: Charge Capture, Coding and Documentation

This is where clinical work fails to become billable revenue. It is also the area where audits must look in both directions: undercoding loses revenue, and overcoding creates compliance exposure.

1. Encounter-to-charge reconciliation. Match the appointment schedule and completed encounters against charges entered. Visits with no charge, and open or unsigned encounters, are direct leakage.
2. Procedure and supply completeness. Compare documentation to charges for in-office procedures, injections, drug administration and supplies. Drug claims often need correct HCPCS J-codes, units, and NDC details where the payer requires them.
3. E/M level distribution. Compare each provider's mix of E/M levels to specialty peers. Since the 2021 office and outpatient E/M changes, level selection can use medical decision making or total time on the date of the encounter, and documentation should support whichever is used.
4. Modifier use. Review modifier 25 on E/M visits billed with procedures, modifier 59 and the X{EPSU} modifiers where NCCI edits apply, and global-period modifiers for surgical practices. Missing modifiers trigger bundling denials such as CO-97; unsupported ones are a compliance risk.
5. Documentation support. For medical necessity denials such as CO-50, check whether the diagnosis, note and order support the service billed.

Claims Leakage: Rejections, Denials and the Codes Behind Them

A rejection happens before adjudication, at the clearinghouse or the payer's front-end edits, and the claim never enters the payer's processing. A denial happens after adjudication and appears on the 835 with CARC and RARC codes. The two are tracked separately because they have different fixes. Rejections are visible in the 999 and 277CA acknowledgments and must be worked daily; denials are visible in the 835 and are worked by cause.

Filing and appeal windows decide whether a claims leak is recoverable. Timely filing limits commonly run from 90 days to one year depending on the payer, with Medicare at one calendar year from the date of service. First-level appeal deadlines vary widely by payer and contract, and Medicare fee-for-service allows 120 days for a first-level appeal (redetermination). The audit flags every denial still inside its window.

AR and Payment Leakage

Revenue in accounts receivable can leak through neglect, not just denial. The audit looks at four things:

• Aging shape: distribution across 0 to 30, 31 to 60, 61 to 90, 91 to 120 and 120+ day buckets, by payer. Dollars drifting right are the first sign of follow-up gaps.
• Underpayments: each 835 line is compared to the contracted rate for the CPT and payer. A repeating variance on the same code usually means a loaded fee schedule is wrong.
• Posting accuracy: denials posted as contractual adjustments (for example, CO-45 used to absorb a denied balance) hide recoverable money from every report.
• Credit balances and small-balance write-offs: credits owed back to payers or patients are a compliance issue, and write-offs without an approval threshold quietly remove collectible balances.

Process Leakage: Manual Work and Ownership Gaps

Process leakage is harder to see because it appears as staff time, not as a denied claim. Typical patterns are work queues with no owner, eligibility checks done by phone when a 270/271 transaction would do, claim status checked one claim at a time, ERA posted by hand, and reports rebuilt manually each month.

• Ownership: every denial type, aging bucket and rejection queue needs a named owner and a target turnaround.
• Repetitive checks: eligibility inquiries, claim status checks (276/277) and ERA posting are rule-based and are the usual candidates for automation. See RPA for Healthcare RCM.
• Handoffs: every handoff between front desk, clinical staff, coders and billers is a place information gets lost. The audit maps handoffs and checks which ones lack a defined status or deadline.

Sizing a Leak: An Illustrative Example

Suppose the audit finds 240 claims in twelve months denied CO-197 with an average allowed amount of $150. Gross exposure is 240 x $150 = $36,000. If half of those are recoverable by retro-authorization or appeal inside the payer's window, recoverable revenue is about $18,000. The other half is lost, but the more important result is prevention: an authorization check at scheduling stops the same loss recurring next year.

Each finding in the report follows this same pattern: the volume, the average value, the recoverable share, the root cause and the fix. Findings are then ranked by recoverable dollars, time remaining in the filing or appeal window, and how easily the fix can be made.