Rejections vs. denials: two different problems with two different fixes.
Staff use these two words interchangeably all the time, and it costs practices real money when they do, because the correct response to one is nothing like the correct response to the other. Sorting a claim problem into the right bucket is the first decision, before anyone touches a fix.
Key takeaways
- A rejection never entered adjudication. It's a structural refusal, corrected and resubmitted freely, no appeal involved.
- A denial is a decision, not an error message. The payer looked at the claim and decided not to pay, and disputing that runs through a formal appeal.
- CO-16 and CO-18 are common rejection-adjacent codes. Both point at data or workflow problems, not coverage disputes.
- Misrouting one as the other wastes work. Resubmitting a genuine denial unchanged usually just produces the same denial twice.
What makes a rejection a rejection
A rejection means the claim never made it into the payer's adjudication process at all. Either the clearinghouse refused it before it reached the payer, or the payer's own front-end intake system bounced it before any substantive review began. The reason is almost always structural: a missing required field, a malformed identifier, an invalid or outdated code, a date that doesn't reconcile with another date on the same claim.
CARC CO-16 — "claim lacks information or a submission/billing error that prevents correct adjudication" — is the code that shows up on a large share of these. It's a broad code precisely because it covers a broad category: anything that stops the payer's system from being able to process the claim at all, regardless of the specific field or identifier at fault. Because nothing has actually been decided about coverage or payment, there's no dispute to raise. The response to a rejection is simply to identify what's wrong, correct it, and resubmit — usually the same day, with no formal process, no deadline beyond timely filing, and no appeal.
What makes a denial a denial
A denial means the opposite: the payer received the claim, ran it through adjudication, and made a substantive decision not to pay some or all of it. Common reasons include the diagnosis not supporting medical necessity for the procedure under the payer's coverage policy, the service not being covered under the patient's specific plan, the patient's benefits for that service already being exhausted, or the claim being identified as a duplicate of one already paid — CARC CO-18.
The key distinction from a rejection is that a decision was actually made. The payer looked at the substance of the claim and concluded it shouldn't be paid as submitted. If you disagree with that conclusion, the path forward is a formal appeal — which runs on the payer's own timeline, usually requires supporting documentation beyond what was on the original claim, and is a materially bigger undertaking than correcting and resending a rejected claim. Not every denial is worth appealing; some are correct as issued, and the right move there is either to write the balance off according to policy or bill the patient where that's appropriate, not to force an appeal that isn't going to succeed.
| Rejections (pre-adjudication) | Denials (post-adjudication) |
|---|---|
| Missing or invalid NPI/taxonomy | Diagnosis doesn't support medical necessity under payer policy |
| Required field blank or malformed (CO-16) | Service not covered under the patient's specific plan |
| Invalid or deleted procedure/diagnosis code | Patient benefits for the service already exhausted |
| Date inconsistency within the claim | Duplicate of a claim already paid (CO-18) |
| Malformed member or subscriber ID | Required prior authorization missing at time of service |
Why the mix-up is expensive
Treating a denial as though it were a rejection — correcting a field and resubmitting unchanged — usually just produces the identical denial a second time, because nothing about the substantive issue (medical necessity, coverage, benefits) was actually addressed. That's wasted staff time twice over: once on the original claim, once on the pointless resubmission, with the underlying problem still unresolved and now closer to whatever appeal deadline applies.
Treating a rejection as though it required a full appeal is the opposite mistake, and while less costly in dollar terms, it still wastes time: a rejection doesn't need supporting documentation or a formal dispute letter, it needs a data correction. Sorting incoming claim problems correctly at the point staff first see them — rejection or denial, structural or substantive — is a small process change with an outsized effect on how efficiently a billing team actually works.
The scrubbing discipline described throughout our claims scrubbing guide exists specifically to shrink the denial category and grow the "caught before submission" category instead, because a claim caught by your own scrubber never becomes either a rejection or a denial in the first place — it's simply corrected before anyone outside the practice ever sees it.
Not sure your team is routing rejections and denials correctly?
We review a sample of your recent claim problems, confirm they're being worked the right way, and fix the process where they aren't.
Frequently asked questions
What's the single fastest way to tell a rejection from a denial?
Ask whether the claim was ever adjudicated. A rejection never entered the payer's adjudication system at all — it was refused on structural grounds by the clearinghouse or the payer's front end. A denial means the payer received and adjudicated the claim, then decided not to pay some or all of it. If a decision was made about coverage or medical necessity, it's a denial; if the claim never got that far, it's a rejection.
Does a rejection count against timely filing the same way a denial does?
A rejected claim generally still has to be corrected and resubmitted within the original timely filing window in most cases — the rejection itself doesn't usually grant an extension. Because rejections typically surface quickly, this is rarely the bottleneck, but a rejection that sits unworked in a queue for weeks can still burn through a meaningful share of a short commercial filing window.
Do all denials require an appeal?
Only if you disagree with the payer's decision and want to contest it. Some denials are correct as issued — the service genuinely wasn't covered, or was billed with an error that, once identified, is better handled as a corrected claim than an appeal. An appeal is the right tool when the underlying facts support payment and the payer's decision was wrong, not a default response to every denial.
Confirm before you rely on this. Payer edit rules, clearinghouse requirements and timely filing limits change and vary by payer. The process information on this page reflects standard industry practice as of August 2026 and is provided for general education — verify current requirements directly with your clearinghouse and payer mix before relying on it.