Revenue leakage in healthcare: missed charges explained
Revenue leakage is revenue a healthcare organization earned but never collects. In coding, the largest source is missed charges — billable services that were performed and documented but never made it onto a claim. It's insidious because, unlike a denied claim, a missed charge generates no error and no alert: the money simply never arrives, and the loss goes undetected.
Why leakage is so hard to see
Most revenue-cycle tooling is built to work errors — denials, edits, rejections — things that show up on a worklist. A missed charge is the opposite: there's no rejection to work because the charge was never submitted. The service happened, the chart supports it, and the revenue just quietly never arrives. At scale, a few missed codes per visit compounds into a seven-figure annual leak that never appears in any denial report.
| Denial | Missed charge (leakage) | |
|---|---|---|
| Visibility | Generates an error you can see and work | Silent — no error, no alert |
| Where it shows up | Denial / edit worklist | Nowhere — the charge was never submitted |
| How it's found | Payer tells you | Only by re-reading the documentation |
What causes professional charge-capture leakage
On the professional (physician) side — where Capsa works — leakage tends to come from a handful of recurring patterns:
- Easy-to-miss ancillary services. Vaccines, their components, and developmental or health screenings are documented in the note but frequently not all captured as charges. (See vaccine administration coding and developmental screening coding.)
- Inconsistency between coders. The same documented work gets captured differently by different people on different days.
- Handoffs. Documentation that's delayed, amended late, or lost between systems never becomes a charge.
- Sampling, not completeness. When only a fraction of charts are reviewed, the misses in the un-reviewed majority are never found.
The two-sided risk: don't overcorrect
The fix for leakage isn't “bill more.” Chasing recall by recommending unsupported codes just trades a revenue problem for an audit and clawback problem. The goal is the right amount, provably — every code supported by the chart. That's why leakage can't be managed by a single number; it takes both recall (did we catch everything?) and precision (is everything we caught supported?). See how to measure coding accuracy.
How to stop it
- Review every encounter, not a sample. Reading the documentation on 100% of visits is the only way to find silent misses.
- Read the documentation directly. The evidence for a missed charge lives in the note — surface the code and the chart text that supports it.
- Measure recall against what was billed. Turn “are we leaking?” into a tracked number instead of a guess.
How Capsa addresses revenue leakage
Capsa Charge Capture is built around exactly this problem on the professional side. It reviews every signed note, recommends every billable professional code the chart supports — each cited to verbatim chart text — and reports scope-aware recall (the leakage metric) alongside precision (the audit-risk metric), measured against what your coders actually billed. Its currently validated skills are pediatric ambulatory vaccine administration and health screening, the categories where these silent misses are most common.