What a Coding Audit Actually Finds — And Why Most Practices Never Run One

A paid claim is not the same thing as a correct claim.

Payment is not a payer's verdict on your accuracy. It is an advance, issued on the assumption that your documentation supports what you submitted — and it stays reversible long after the deposit clears.

Which is why a practice can have a healthy clean claim rate, a low denial rate, and steady deposits while carrying exposure that nothing in its monthly reporting would show. In our experience, the practices with the most exposure are rarely the disorganized ones. They are the ones running smoothly enough that no one has had a reason to look.

It Is Not the Same as a Billing Audit

A billing audit asks whether the revenue you earned actually got collected — unbilled procedures, unworked denials, receivables nobody is chasing.

A medical coding audit asks something narrower and harder: does the documentation in the chart support the code that was submitted? It doesn't look at claim volume or denial rates. It compares the note to the code, one encounter at a time — which is why it runs either pre-bill, before the claim goes out, or post-bill, on encounters already paid.

A practice can pass one and fail the other.

What It Examines

E/M level validation. Does the documented medical decision making support the level billed? Highest-volume codes, highest-volume risk — and the finding we encounter most often. It is also the first of the five billing mistakes we see most across practices, for the same reason: volume multiplies whatever the pattern is.

Modifier support. Every modifier 25 needs a separately identifiable service visible in the note, not implied by two charges on a claim. Every 59 needs distinct anatomy, session, or encounter. Modifiers appended by workflow habit are easy for a payer to spot in aggregate.

Medical necessity. Does the diagnosis reported establish necessity for the service performed, or was it selected to clear an edit?

Copy-forward documentation. The finding that surprises practices most. A note that grows more detailed every visit while the patient's complexity stays flat is a pattern visible from outside the practice, and it weakens every level built on top of it. Usually a workflow artifact rather than intent — but that is far easier to explain before a payer raises it than after.

Incident-to billing. Whether those encounters actually meet supervision and establishment requirements, or whether the billing provider was assigned by habit.

Caught before submission, these are corrections. Caught after, they are refunds.

The Findings Run in Both Directions

Owners avoid coding audits because they expect one outcome: a number they owe back. That expectation is what keeps the review off the calendar year after year.

In practice, the findings split. Undercoding out of caution is at least as common — and it is expensive in a way that produces no signal at all. No denial. No appeal. Nothing in any report. The practice simply under-collects, permanently, on every encounter matching the pattern.

A provider who levels conservatively out of fear of an audit can cost a practice more over a year than an occasional overcoded claim ever would.

Three Questions Worth Asking

When did anyone last compare a note to the code billed? Not the charge ticket to the claim — the clinical documentation to the submitted code. For most practices, the honest answer is never.

How do your providers' E/M distributions compare to each other? Same practice, same patient population. Outliers in either direction are worth understanding.

Who reviews a modifier 25 before the claim goes out? If the EHR appends it by rule, the documentation supporting it has never been verified.

Correct It Before Someone Else Finds It

Auditing is a distinct discipline from billing and coding, which is why it carries its own certification. HEMBILLING's audits are led by a Certified Professional Medical Auditor (CPMA) and serve practices across South Florida — and a useful audit report does not hand you a score. It identifies each finding with the encounter behind it, explains what the documentation would have needed to support the code billed, and separates what to correct going forward from what may warrant a broader look.

Practices that review their own coding on a regular schedule are rarely the ones facing a repayment demand. The corrections happen while they are still small, and still prospective.

If you have never had an independent review of your coding, see what an independent audit covers — a defined sample, a flat fee, and a written finding, with no commitment beyond the audit. We will tell you honestly what we are seeing — and just as honestly if we don't think an audit would find enough to be worth your money.