Denial management is where the most revenue in medical billing gets won or lost. A clean, well-coded claim that sails through on the first submission needs almost no attention — but every practice has claims that don’t, and how systematically those get handled is one of the biggest differences between a healthy revenue cycle and one that’s quietly bleeding money. (For how denial management fits into the bigger picture, see our guide to Revenue Cycle Management.)
This playbook covers why claims actually get denied, the codes that tell you why, and the process that turns denial management from reactive firefighting into something that prevents the next round of denials before they happen.
Denial vs. rejection: know the difference first
These two get used interchangeably, but they’re not the same problem. A rejection happens before a payer ever really reviews the claim — usually a technical error (a missing field, an invalid code, a mismatched ID) caught by a clearinghouse or the payer’s front-end system. A denial happens after the payer has actually adjudicated the claim and decided, for a substantive reason, not to pay it. Rejections are almost always fixable in minutes; denials require actually understanding why the payer said no, which is what most of this guide is about.
Why claims get denied: the top reasons
Every denial arrives with a CARC (Claim Adjustment Reason Code) explaining why, sometimes alongside a RARC (Remittance Advice Remark Code) adding detail. See the glossary for the full definitions — here are the ones that show up constantly, and what actually prevents each one:
- CO-16 — Missing or invalid claim information. A required field is missing or a submission error slipped through. Prevented by claim scrubbing and a pre-submission checklist, not by catching it after the payer already has.
- CO-11 — Diagnosis doesn’t support the procedure. The ICD-10-CM code billed doesn’t clinically justify the CPT code billed. Prevented by code-pairing checks and, where documentation is ambiguous, a query back to the clinician before submission. See our ICD-10-CM Coding Guide for the specificity and guideline rules that most often cause this.
- CO-18 — Duplicate claim. The same service, same patient, same date was already submitted. Prevented by clear ownership of each claim and duplicate-detection in the billing system.
- CO-29 — Timely filing. The claim was submitted after the payer’s filing deadline — and once that deadline passes, the claim is often unrecoverable regardless of how legitimate it was. Prevented with automated alerts well before the deadline, not by tracking it manually.
- CO-45 — Charge exceeds fee schedule. Not really a “denial” in the adversarial sense — this is the standard contractual write-off between what was billed and what the payer’s contract allows.
- CO-50 — Not medically necessary as documented. The service may well have been necessary, but the documentation submitted didn’t demonstrate it. Prevented by strong clinical documentation practices and securing prior authorization where required.
- CO-97 — Bundled into another service. The payer considers this service part of another procedure already paid. Prevented by applying the correct modifier when the service genuinely was distinct.
- CO-22 — Coordination of benefits issue. The payer believes another insurer should be paying first. Prevented by verifying eligibility and coverage order at every visit, not just at intake.
- CO-167 — Diagnosis not covered. The specific diagnosis billed is excluded under the patient’s plan. Prevented by checking payer coverage policies before the service, especially for anything elective or borderline.
- PR-200 — No active coverage on date of service. The patient wasn’t actually covered when the service happened. Prevented by real-time eligibility verification, ideally re-checked at every visit rather than once at signup.
Most denials are preventable, and the pattern is the same across almost every practice: the fix for a given denial reason almost always lives earlier in the revenue cycle than the point where the denial actually shows up. That’s why denial management works best as a feedback loop into the front-end and mid-cycle stages, not as an isolated back-office task.
A systematic denial management process
1. Identify and triage. Every denial gets logged, with its CARC/RARC code, as soon as the remittance arrives — not batched up and dealt with weeks later, by which point the timely-filing clock is running out.
2. Categorize by root cause. Group denials by reason, not just by claim. This is what turns “we had 40 denials this month” into “32 of them were eligibility issues from one specific front-desk workflow” — an actionable finding instead of a vague problem.
3. Prioritize by recoverable value. Not every denial is worth the same effort. A high-dollar claim with a strong case for appeal gets worked first; a low-dollar claim with a weak case might reasonably be written off.
4. Correct and resubmit, or appeal. A denial caused by a fixable error (a wrong code, a missing modifier) usually just needs correction and resubmission. A denial where the payer’s decision is genuinely being contested needs a formal appeal.
5. Track outcomes and feed them back upstream. The categorized reasons from step 2 should actively change what happens at scheduling, coding, and claim scrubbing — otherwise the same denials keep recurring every month.
Writing an appeal that actually gets read
An appeal is only as strong as the specific argument it makes against the specific reason the claim was denied — a letter that just says “please reconsider” gets treated the same as the original claim. At minimum, a strong appeal includes: the claim and denial details (date of service, claim number, CPT/ICD-10 codes, the CARC reason cited); a direct argument addressing that exact denial reason, citing the payer’s own coverage policy, coding guidelines, or regulation where relevant; and the supporting documentation that backs the argument — clinical notes, operative reports, orders, and anything else that demonstrates medical necessity or corrects the payer’s stated reason for denial.
For a full breakdown of what separates a strong appeal from a weak one, see our post on building an appeal payers take seriously. And for why it’s worth doing this well in the first place, see the real cost of a denied claim — it’s rarely just the billed amount.
Before a claim ever reaches submission: verify eligibility and coverage for this specific date of service (not just at intake); confirm the diagnosis and procedure codes are clinically consistent with each other; check that any required prior authorization is on file; scrub the claim for missing or mismatched fields; and confirm you’re well inside the payer’s timely filing window. Every one of these maps directly to one of the top denial reasons above.
Preventing denials starts upstream of the appeal — see our step-by-step guide to running an internal medical coding audit to catch coding errors before they turn into denials.