Insights · Coding
What a Coding Audit Tells You
In short: a good coding audit finds revenue you’re missing and risk you’re carrying. Both matter, and the fix is usually training, not blame.
Two kinds of audit
| Type | When | Best for |
|---|---|---|
| Prospective | Before claims go out | Catching errors before they become denials |
| Retrospective | After payment | Finding patterns, under-coding and compliance risk |
What auditors look at
- Evaluation and management (E/M) levels: whether each visit level matches the documentation, and how a provider’s mix compares with peers.
- Modifiers: especially 25 and 59, which payers watch closely.
- Diagnosis codes: specific enough to support medical necessity.
- Documentation: whether the note supports every code billed.
What the results tell you
- Under-coding: revenue you earned but didn’t bill.
- Over-coding: compliance risk and possible paybacks.
- Patterns by provider or specialty: where training will pay off most.
Turning findings into fixes
- Share results provider by provider, with real chart examples.
- Train on the two or three issues that matter most.
- Re-audit a sample later to confirm the change stuck.
Audit checklist
- A sample from every provider, not just high billers
- Clear scoring: correct, under-coded, over-coded
- Dollar impact of each finding
- A follow-up audit date
When did you last audit your coding?
We audit, share clear findings and train your team.
Talk to our teamThis guide is general information, not legal or billing advice. Payer rules change often; always check the current policy and your contracts.