← All insights

Compliance

How to run a small internal coding audit in one week

You do not need an external audit to find coding problems. A structured sample of encounters, reviewed against documentation, reveals most of them.

7 min read

A focused internal audit can uncover under-coding that leaves revenue on the table and over-coding that creates compliance risk. The goal is to compare what was billed with what the documentation supports, and to learn where the gaps come from.

Plan the sample

Select a random sample of encounters from one provider or one service line, covering a single month. Twenty to thirty encounters is enough to reveal patterns. Include both high-volume and high-value services, because errors cluster in both.

Review each encounter

Turn findings into education

Share results with providers in a neutral way, focused on patterns rather than individuals. A single page that shows the three most common issues, with a short example of each, usually produces more change than a long report. Repeat the audit after a quarter to confirm improvement.

This article is general guidance. Coding rules change, so confirm current requirements with a qualified coding professional or compliance advisor.

Want a second opinion?

Bring us your denial and A/R reports.

We will review them with you and tell you which problems are process issues and which are one-off losses.

Book a free review

Let's talk

Ready to recover revenue you have already earned?

Book a free consultation. We will review your current billing setup and tell you where the money is leaking.

Book a consultation