Paid, but Underpaid: Where Revenue Leakage Hides When Claims Don’t Deny

Amanda McGurk

11 min read · November 18, 2026

Photograph of a hand resting on a thick chart folder beside a single thin printed sheet on a desk, representing the gap between what the medical record documented and what the claim reported

Paid, but Underpaid: Where Revenue Leakage Hides When Claims Don’t Deny

Revenue leakage in medical coding occurs when a claim reports a lower level of service or fewer supported procedures than the medical record justifies. These claims can pass payer edits and receive payment, making undercoding difficult to identify through denial reports alone.

The gap opens in the note and in the code selection that follows it. It shows up in office and emergency department visit levels, where CPT moved level selection to medical decision making, and on ASC claims, where Medicare ranks covered procedures by payment rate. Each is a place where a paid claim can still be an underpaid claim.

Why doesn’t undercoding show up on a denial report?

A denial report lists claims a payer refused. Medical coding underbilling produces the opposite event. The claim is complete, the code valid, the edits pass, the money arrives. Nothing in the remittance says the encounter was worth more.

So run the arithmetic on your own book instead, one visit at a time.

Take A, your monthly volume of established-patient office visits. Take B, the share of those visits your last medical coding audit found leveled below what the medical decision making supported. Take C, the difference between your own 99214 and 99213 allowable, weighted across your payer mix. Multiply the three, then multiply by 12 for the annual figure leadership will ask for. Run the same inputs again for 99215 against 99214, and for your ED professional-fee book at 99284 against 99283.

Treat the result as an estimate built from audited coding differences and your own payer-specific allowable amounts, not as guaranteed recoverable revenue. Charts already adjudicated may sit outside any correction window. It sizes revenue cycle leakage that no report on your desk prints.

E/M levels are the easiest place to see this, not the only one. Missed add-on codes, an omitted modifier 25 on a significant, separately identifiable E/M, and separately reportable procedures folded into the primary one all pay short without reaching a denial report.

Where does the gap start in the note?

For a billing office manager, the mechanism matters more than the arithmetic, because you can change the mechanism.

Three things have to line up. The physician documents what they addressed, reviewed and decided. The coder finds all three in the record. The code selected reflects all three.

The work has to be findable by a coder moving at pace and defensible to a payer reviewer. Sitting somewhere in the chart meets neither test. A diagnosis addressed in the visit but written only as a problem-list carry-forward reads as stable. A dose change that sits in an order, with nothing in the plan tying it to an assessed problem, is in the record and still easy to miss and hard to defend. Labs reviewed and acted on, but never named in the note, leave no evidence that anyone reviewed them. In each case the coder is doing the right thing with the record in front of them, and the record came up short.

The reasons records come up short are their own subject, and incomplete clinical documentation covers them. This post sizes what they cost you.

What did the 2021 E/M rewrite change about where the level comes from?

Before 2021, a thorough history and exam could carry an office-visit level. That stopped. The AMA’s revision made the level a function of medical decision making or total time on the date of the encounter, and said history and exam “alone should not determine the appropriate code level.” Both are still required and still documented, at the level that is medically appropriate ( AMA ).

Either method is permitted for 99202 through 99215, so outpatient E/M coding does not have to run through MDM on every visit. Where MDM is the basis, two of its three elements must be met or exceeded to reach a level ( AAPC ).

The emergency department went further in 2023. ACEP reports that ED visits 99281 through 99285 “will be based only on medical decision making,” with no time component ( ACEP ).

For office visits, the documentation supporting MDM must establish the problems addressed, the data reviewed and analyzed, and the risk associated with patient management. These elements may be documented across different parts of the medical record.

What does an undercoded encounter look like, step by step?

The walkthrough below is illustrative. It is a coding exercise rather than a client account, and it shows how the elements are weighed rather than how any particular chart should be coded.

An established patient presents for follow-up. The assessment names type 2 diabetes with worsening control and new proteinuria. The physician reviews an A1c and a basic metabolic panel drawn at an outside lab, neither ordered by this practice, then records an insulin dose increase in the plan.

Read against the MDM elements, that record offers a chronic illness with progression, data reviewed and analyzed, and prescription drug management. Whether each element is countable, at what level, and whether two of three are met is a judgment on the documentation in front of the reviewer. An insulin order alone does not establish a level.

Now change only the note. The assessment reads “diabetes, stable, continue current regimen.” The dose change sits in the order with nothing in the plan linking it to the diabetes, and the outside results sit in a tab the note never references. The work is still in the chart, but none of it is tied to an assessed problem, so a coder may not find it and a payer reviewer may not credit it. The record supports a lower level than the visit earned.

The visit and the work are identical, and the claim is smaller. That repeats every time the documentation does.

What does revenue leakage look like on an ASC claim?

In an ASC, the leak usually comes from a procedure the claim never reported, or one reported less specifically than the operative note supports, rather than from a visit level.

Medicare pays in full for the procedure with the highest national unadjusted ASC payment rate, then pays “50 percent of the applicable ASC payment amount” for the other covered surgical procedures on the claim ( 42 CFR 416.172 ). The payer applies that ranking by payment rate, not by the order the lines sit in on your claim, and the payment indicator on each line governs whether the discount applies to it at all. Miss a procedure that would have ranked highest, or code it less specifically than the note supports, and you change the ranking itself. The claim pays, and it pays less than the record supported.

How do you find it before the claim goes out?

A retrospective medical coding audit finds the pattern weeks later, after the claims have paid.

The alternative is to apply coding and compliance checks during the first pass, with each chart routed according to its documentation and review requirements. That is where AI medical coding earns its place, with consistency at volume on the part of the record that decides the level.

MediCodio AI runs it as one dual-mode product, routed per chart. Complete charts flow through AutoPilot for fully autonomous coding. Charts where the documentation is thin or contradictory stay in CoPilot, where certified coders review and finalize the output. Every code ships with its documentation passage and the compliance rule behind it, which is what makes a level defensible in either direction, and MediCodio AI carries a 100% code-level audit trail.

MediCodio AI delivers 98%+ coded right the first time. This represents first-pass accuracy across deployments since 2023, measured at the code level on production charts before correction, against reference reviews by AAPC- and AHIMA-credentialed coders applying official guidelines and payer policy to the same documentation.

Nothing runs autonomous on day one. Everything starts in review, and the autonomous lane widens one specialty, surgeon, or case type at a time as accuracy is proven on your own charts by your own team. It narrows again at any point.

Want to see the documentation-to-reimbursement connection end to end?

Jessica Miller, MHA, CPC, CPC-I, and Amanda McGurk walk through where documentation and coding decide reimbursement, with Naveen Vaidyamath moderating. Thirty minutes, then fifteen minutes of live questions.

The Documentation-to-Reimbursement Connection

Thursday, December 10, 2026, 1:30 PM ET

Webinar Registration - Zoom

FAQ

What is revenue leakage in medical coding?

Revenue leakage in medical coding is the difference between the service the documentation supported and the service the claim reported. Undercoding is the form that leaves no trace in the revenue cycle, because the claim is clean, passes edits, and pays. It is found by auditing coded charts against their documentation, not by reading denial reports.

Is undercoding in medical billing a compliance problem, or only a revenue problem?

It is both. The code reported is supposed to describe the service the record supports. A pattern of levels that sit below the documented decision making misstates the encounter in the same way a pattern above it does, and it distorts the provider profile payers build from your claims. Treat accuracy as the target in both directions rather than a higher average level.

How can outpatient practices identify undercoding before claims are submitted?

Review the documentation before the claim goes out rather than after. Confirm the record establishes the problems addressed, the data reviewed and analyzed, and the risk associated with patient management, then check that the code selected reflects it. Run the compliance checks at the same point, while the claim is still being built. Charts with thin or contradictory documentation should route to a certified coder.

Sources

See it in action

Ready to transform your medical coding?

See how MediCodio's AI platform delivers 98%+ accuracy across deployments since 2023, with turnaround under 24 hours at enterprise volume, inclusive of coder review, across 35+ specialties.

Loading posts...

Frequently Asked Questions

What is revenue leakage in medical coding?
Revenue leakage in medical coding is the difference between the service the documentation supported and the service the claim reported. Undercoding is the form that leaves no trace in the revenue cycle, because the claim is clean, passes edits, and pays. It is found by auditing coded charts against their documentation, not by reading denial reports.
Is undercoding in medical billing a compliance problem, or only a revenue problem?
It is both. The code reported is supposed to describe the service the record supports. A pattern of levels that sit below the documented decision making misstates the encounter in the same way a pattern above it does, and it distorts the provider profile payers build from your claims. Treat accuracy as the target in both directions rather than a higher average level.
How can outpatient practices identify undercoding before claims are submitted?
Review the documentation before the claim goes out rather than after. Confirm the record establishes the problems addressed, the data reviewed and analyzed, and the risk associated with patient management, then check that the code selected reflects it. Run the compliance checks at the same point, while the claim is still being built. Charts with thin or contradictory documentation should route to a certified coder.
How often should we run a medical coding audit?
Set the cadence against your own risk rather than a calendar habit. New providers, new service lines, a change in specialty mix, and payer policy updates are the events worth auditing after. Your compliance team should own the sampling plan, including how many charts per provider and how the sample is drawn.