Denials & Appeals
Why Claims Deny After a Clean Submission
A claim can pass every front-end check and still come back denied. What happens after submission — and why rejection and denial are different problems.

A claim that passes your practice management system's scrubber and is accepted by the clearinghouse has cleared one hurdle: it is formatted correctly and contains the data elements a payer needs to process it. It has not been approved. The payer still has to decide whether the patient was covered, whether the service was authorized, whether the codes are consistent with its policies, and whether anything else should pay first.
That distinction explains a frustrating pattern many billing teams see: a low rejection rate alongside a stubborn denial rate. This article looks at what happens after submission and why a "clean" claim can still come back unpaid.
Rejection vs. denial: two different problems
The terms are often used interchangeably, but they describe different events and call for different responses.
| Rejection | Denial | |
|---|---|---|
| When it happens | Before adjudication — at the clearinghouse or the payer's front-end edits | After the payer has processed (adjudicated) the claim |
| What it means | The claim was not accepted into the payer's system, usually for missing or invalid data | The claim was processed and payment was refused in whole or in part |
| How it's fixed | Correct the data and resubmit — the claim was never "received" | Correct and resubmit, request a reopening, or appeal, depending on the reason and the payer |
| Where it shows up | Clearinghouse reports, payer acknowledgment files | Remittance advice (ERA/835) with adjustment reason codes |
Medicare, for example, returns certain incomplete or invalid claims as "unprocessable"; these carry no appeal rights and must be corrected and submitted again (Medicare Claims Processing Manual, Chapter 1). A clean submission eliminates most rejections. It does very little about denials.
Where clean claims deny
1. Eligibility and coverage changed — or were never fully checked
A claim can be perfectly coded for a patient whose coverage terminated last month, whose plan changed at the start of the year, or who has another plan that should pay first. Front-end checks often confirm that a member ID is valid; they do not always confirm active coverage on the date of service, the correct plan product, or coordination of benefits. Eligibility timing is covered in more depth in What Practice Owners Should Know About Eligibility Verification.
2. Authorization was missing, expired, or didn't match
Prior authorization is tied to specific services, dates, units, and sometimes a specific rendering provider or location. A claim can be accepted by the clearinghouse and still deny because the authorization on file covered a different CPT code, ran out of approved visits, or expired before the date of service. See Prior Authorization: Where the Workflow Breaks Down.
3. Coding was valid but not specific or consistent enough
Scrubbers check that codes exist and are formatted correctly. Payers go further: they check whether the diagnosis supports the procedure under their coverage policy, whether code pairs are bundled, and whether units exceed what the payer considers medically likely. Medicare's National Correct Coding Initiative (NCCI), for example, applies procedure-to-procedure edits and medically unlikely edits that are updated quarterly (CMS NCCI). Many commercial payers apply their own edit sets on top.
4. Payer-specific rules applied after submission
Each payer maintains its own medical and reimbursement policies — frequency limits, modifier requirements, place-of-service rules, site-of-care restrictions. For Medicare, local coverage determinations can vary by Medicare Administrative Contractor. None of this is visible to a generic claim scrubber unless someone has built the rule into it. When a payer updates a policy, a claim that paid last quarter can deny this quarter; see Staying Current With Payer Policy Changes.
5. Documentation or supporting information was requested
Some claims pay only after the payer reviews records. A request for additional documentation that goes unanswered — because it was mailed to an old address, routed to the wrong inbox, or simply missed — becomes a denial by default.
6. Timing and administrative rules
A claim can be correct in every clinical and coding respect and still deny because it arrived after the payer's filing limit, duplicated a claim already in process, or listed a provider who was not yet enrolled with that payer. Filing limits vary by payer; see Timely Filing Limits.
Reading the reason codes
Denials arrive on the remittance advice with Claim Adjustment Reason Codes (CARCs), often paired with Remittance Advice Remark Codes (RARCs) that add detail. Both code sets are maintained by X12 and updated several times a year (X12 CARC list; X12 RARC list). A group code in front of the CARC tells you who carries the adjustment — for example, CO (contractual obligation) versus PR (patient responsibility).
A few commonly seen examples, for orientation only — always check the current X12 list and the payer's own explanation:
| Example CARC | General meaning | Likely origin |
|---|---|---|
| 27 | Expenses incurred after coverage terminated | Eligibility |
| 197 | Precertification/authorization/notification absent | Authorization |
| 16 | Claim/service lacks information or has submission/billing errors | Data or documentation |
| 97 | Benefit included in the payment for another service already adjudicated | Bundling / coding edits |
| 29 | The time limit for filing has expired | Timely filing |
The reason code tells you what the payer decided. It usually does not tell you where in your workflow the problem started. That is the job of a denial management process.
What this means for practice leaders
- Don't treat a low rejection rate as proof the front end is working. Rejections measure formatting; denials measure whether the claim was payable.
- Group denials by origin, not just by code. Eligibility, authorization, coding, payer policy, documentation, and timing each point to a different owner.
- Expect payer rules to move. A denial pattern that appears suddenly across one payer is often a policy change, not a staff error.
Knowing why claims deny is the diagnostic step. Building the process that works those denials and prevents their return is covered in A Practical Guide to Denial Management.
How this scales to larger organizations
Hospitals and health systems see the same categories, with more places for them to hide: institutional claims carry revenue codes and condition codes that add their own edits, and payer contracts often include organization-specific policies. Larger organizations typically separate front-end edit management (charge integrity, claim scrubber rules) from back-end denial work — which makes it more important that denial data flows back to whoever owns the edits.
Key Takeaways
- A clean submission prevents rejections, which are formatting and data problems; it does not guarantee the payer will pay.
- Clean claims most often deny for eligibility, authorization, coding specificity, payer-specific policy, missing documentation, or timing.
- Reason codes describe the payer's decision; grouping denials by where they originated shows which workflow step needs attention.
Sources & References
Regulations, program rules, and payer policies change. Educational content only — confirm current requirements with the payer, program, or your advisors before acting.
Related Renvara Solution
Revenue Cycle ManagementWant to discuss how this applies to your practice?
Book a Practice Assessment to talk through this operational area with Renvara.
