docs
Claim Rejection vs Denial Explained
Billing-company guide to claim rejection vs denial: where each happens in the EDI flow, the resubmit-vs-appeal workflow, and timely-filing implications.
Claim Rejection vs Denial: How They Differ and How to Work Each
Short answer
A claim rejection happens before adjudication. The 837 claim file reaches the clearinghouse or the payer's front-end edit engine, fails a format or eligibility check, and gets sent back — often through a 999 functional acknowledgment or a 277CA claim acknowledgment — before a human reviewer or adjudication system ever touches it. The payer's internal claim record was never created. The timely-filing clock is still running.
A denial happens after adjudication. The claim entered the payer's system, was processed, and the payer made an explicit decision not to pay — fully or partially. The decision comes back on an 835 Electronic Remittance Advice, tagged with a Claim Adjustment Reason Code (CARC) and usually a Remittance Advice Remark Code (RARC). Because adjudication occurred, the appeal rights that contract law and state prompt-pay statutes provide are now in play. MGMA research consistently puts the average initial denial rate above 10 percent, meaning that a large portion of the work in any billing company is managing post-adjudication outcomes — which requires understanding what a denial actually is before assigning it to a worklist.
Sources: MGMA 2024 Cost and Revenue Report
Where each outcome occurs in the EDI flow
The transaction chain for a submitted claim runs: 837P or 837I claim file to clearinghouse, then clearinghouse to payer. Two checkpoints sit before adjudication, and one sits after.
| Stage | Transaction | What it signals |
|---|---|---|
| Clearinghouse receipt | 999 Functional Acknowledgment | The 837 file was received and syntactically valid (or rejected at the file level) |
| Pre-adjudication check | 277CA Claim Acknowledgment | The claim was accepted into the payer's pipeline or rejected before entry |
| Post-adjudication | 835 Remittance Advice | The payer adjudicated and is paying, partially paying, or denying with coded reason |
A rejection surfaces at the 999 or 277CA stage. A denial surfaces on the 835 — after all that, after days or weeks of adjudication cycle time.
The 999 signals whether the entire transaction set was structurally acceptable to X12 standards. The 277CA is the per-claim response — it reports accepted or rejected status using Claim Status Category Codes and Claim Status Codes in the STC segment, which can point to the specific party and edit that caused the problem. Neither the 999 nor the 277CA carries CARC or RARC codes; those belong to the 835. Mixing up those two layers is the most common source of mislabeled worklist items in billing operations. For a fuller breakdown of 277CA status codes, see the 277CA acknowledgment guide.
Sources: X12.org Transaction Set Directory, Stedi EDI Claim Responses Overview
What a rejection looks like and how to read it
A rejection comes back as a 277CA with a status code in the A7 category (Acknowledgment/Rejected for Missing Information, Please Resubmit) or similar pre-adjudication category. The clearinghouse may also produce its own error report — some present these as portal alerts; others batch them into a nightly file.
Common rejection reasons:
- Member ID does not match payer records
- Missing or invalid NPI for the billing or rendering provider
- Duplicate claim detection based on matching claim control number
- Subscriber date of birth mismatch
- Claim submitted to the wrong payer ID
The fix in every case is correction and resubmission — not an appeal letter, not a reconsideration request. Those tools apply after adjudication. A rejection requires finding the edit that failed, correcting the source data, and re-filing the 837 before the timely-filing window closes.
What a denial looks like and how to read it
A denial arrives on the 835, embedded in the CLP loop (Claim-Level Adjustment) and the SVC loop (Service-Level Adjustment). The key codes are:
- CARC: Claim Adjustment Reason Code — the primary reason for the adjustment, published by the Washington Publishing Company (WPC)
- RARC: Remittance Advice Remark Code — supplemental context, also published by WPC
- Group code (CO, PR, OA, PI): determines who is financially responsible for the adjustment
A CO group code (Contractual Obligation) means the amount falls under a contract write-off. A PR group code (Patient Responsibility) means the patient owes it. An OA (Other Adjustment) usually signals a coordination-of-benefits situation. Understanding the group code before assigning a denied claim to a work queue is mandatory — a CO denial that gets sent to an appeal queue wastes the specialist's time on a claim that was already settled contractually.
For a full treatment of common CARC codes and denial triage, see the denial management workflow guide.
Sources: WPC CARC/RARC Code Lists, CMS ERA/835 Remittance Advice Resources
The workflow difference: resubmit versus appeal
| Scenario | Correct action | Wrong action |
|---|---|---|
| 277CA shows rejected, no payer claim ID | Correct and resubmit | Filing a formal appeal |
| 835 denial with CARC 16 (missing info) | Corrected claim resubmission or appeal — depends on payer contract | Treating it as a simple reject and skipping documentation |
| 835 denial with CARC 4 (service not covered) | Appeal with medical necessity documentation | Resubmitting with no changes |
| 835 denial with CARC 45 (charges exceed fee schedule) | CO write-off per contract | Appealing a contractual adjustment |
The resubmit path does not consume appeal rights. The appeal path requires a formal packet — cover letter, medical records, authorization reference, and often a timely appeal certificate — and the deadline is set by contract and state statute, not the original submission date.
One operational trap: some payers return a soft denial on the 835 with a CARC that implies correction and resubmission rather than a formal appeal. CARC 16 (Claim/service lacks information needed for adjudication) is the classic example. The right action depends on what the RARC says and what the payer's correction-claim policy is. When in doubt, call the payer's provider line before filing anything.
Why mislabeling rejections and denials costs money
When a billing company labels a 277CA rejection as a denial, two things go wrong. First, the claim sits in an appeal queue while the timely-filing window runs. Appeal timelines are measured from original service date or claim date — the payer does not reset the clock because the billing team was working the claim in the wrong worklist. By the time someone routes it correctly, filing may be barred.
Second, incorrect labeling inflates the denial rate metric. A rejection is a pre-entry failure — a quality control failure in claim construction or data entry — not an adjudication outcome. Commingling them obscures where the actual problem is. A billing company with a 14 percent "denial rate" may actually be running a 9 percent denial rate and a 5 percent rejection rate, and the fixes for each are completely different.
The reverse mislabeling also happens: a denied claim gets corrected and resubmitted without formal appeal, which can be appropriate (corrected claim) or a rights-forfeiture (if the payer requires appeal). Knowing which situation you are in requires reading the CARC and checking the payer's provider manual.
Timely-filing implications
Rejections leave the timely-filing clock running. The original service date — or claim date for some payer contracts — is what determines the deadline. A common error is assuming that a clearinghouse response of any kind constitutes proof of timely filing. It does not. The payer's timely-filing limit counts from the date of service (or discharge for inpatient), and a rejected claim that was never assigned a payer claim ID has never met that requirement.
Most commercial payers allow 90 to 180 days from date of service. Medicare's timely filing limit is one year. Medicaid limits vary by state. Some payer contracts are shorter — 60 days is not unusual for large commercial plans.
If a rejection is caught within 30 days of the deadline, the team needs to prioritize correction immediately, not at the next weekly worklist sweep. Late-filed claims are denied with a CARC 29 (Timely Filing) denial, and appeals on timely filing grounds require documented proof of the original attempt — which is exactly what the 277CA rejection provides, if it was saved.
Sources: CMS Medicare Claims Processing Manual, Chapter 1
How Medi handles rejections and denials
Medi surfaces 277CA acknowledgment status at the claim level. When a claim comes back rejected, the reason code from the 277CA is displayed alongside the claim in the work queue — so the team sees it without digging into a raw EDI file. The claim routes to a resubmission queue rather than a denial queue.
Denials from the 835 are parsed per service line. Each line shows the CARC, the RARC, and the group code. Billing specialists work from a denial queue organized by CARC code group and aging bucket — the configuration that lets a three-person team triage 400 denials a day without losing track of appeal deadlines.
For the full acknowledgment workflow, see the 277CA guide. For denial triage and appeal packet management, see the denial management guide. To see the queues in the product, book a demo.
Medi is priced at $20 per client practice per month, with published volume discounts (1-25 at $20, 26-50 at $15, 51+ at $10), plus per-transaction EDI fees. No per-provider fee. No contract. The fee follows client practices, not providers: adding providers inside a practice never changes the fee, while adding practices adds the per-practice rate, which falls as the book grows. Full pricing and migration terms are published at /pricing.
When Medi is not the right fit
Medi is built for billing companies managing multiple client practices — the workflow, the queue structure, and the pricing model all assume that context. Solo in-house billing departments at single-practice providers often need a lighter tool integrated directly into their PM/EHR. If that is the setup, Medi is probably not the right fit.
Medi also does not handle clinical documentation, prior authorization, or automated coding. The platform picks up after the encounter is coded and the claim is ready to build.
Frequently asked questions
Does a clearinghouse rejection reset the timely-filing clock?
No. A rejection means the claim was never assigned a payer claim ID, which means the payer never received it for adjudication purposes. The timely-filing window continues from the original date of service. Some payers accept the 277CA rejection report as proof of a timely attempt during an appeal — but that is an exception policy you have to verify with each payer, not a standard.
Can I appeal a rejected claim?
Formally, no — an appeal is a post-adjudication recourse, and a rejection means adjudication never happened. What you do with a rejection is correct it and resubmit. That said, if the timely-filing window has already closed due to an unreasonably long rejection-correction cycle, some payers accept timely-filing appeals with the original submission attempt documented. Again, that is payer-specific and requires calling the provider line.
What is the difference between a corrected claim and an appeal?
A corrected claim is submitted on a new 837 with a claim frequency code of 7 (replacement) or 8 (void) and the original claim control number referenced. It is used when the original claim had a fixable error — wrong code, missing modifier, incorrect date of service. An appeal is a formal dispute of the payer's adjudication decision. Some post-adjudication denials require appeal; some accept a corrected claim instead. The CARC code and the payer's provider manual tell you which applies.
How do I know if a 277CA means rejected or accepted?
The 277CA uses Claim Status Category Codes in the STC segment. Category A1 indicates acceptance into adjudication. Category A7 indicates rejection with a request to resubmit. Other A-series codes indicate pending status or additional information requests. For a full list of codes and how to read the STC segment, see the 277CA guide.
What CARC code appears on a timely-filing denial?
CARC 29 — the code for "The time limit for filing has expired." When this appears, the next step is a timely-filing appeal with documentation of the original submission attempt. The 999 and 277CA records from the original filing are the primary evidence. Payers set their own appeal deadlines and documentation requirements for timely-filing disputes, so check the provider manual before submitting.
References
These public sources provide background for standards, terminology, or competitor context discussed on this page.
- Stedi healthcare claim responses overviewStedi
- X12 external code listsX12
- MGMA detecting and fixing leaks across the revenue cycleMedical Group Management Association