Remittance Denials and Appeals

Reading the 835 ERA, CARCs, and RARCs

Translate the full remittance into financial responsibility, root cause, and next action.

Estimated time: 45 minutes / Reviewed 2026-07-10

Lesson progress0%

Learning objectives

Explain reading the 835 era, carcs, and rarcs using current claim facts and official sources.
Apply the 5-step workflow to a de-identified reimbursement case.
Distinguish administrative, coding, coverage, documentation, and procedural-status questions.
Document a bounded conclusion, unresolved facts, and the next supported action.

Core instruction

The group code assigns the adjustment category, the CARC gives the general reason, and RARCs add detail. Read the full combination at claim and line level before deciding who owns the balance or what to do next.

Translate an 835 remittance into financial responsibility, root cause, and the next operational action.

CO generally signals contractual obligation and PR patient responsibility under the remittance rules.
A CARC may be too broad without its associated RARC.
PLB adjustments are provider-level, not automatically tied to one claim.
Never bill a beneficiary merely because a payer did not pay.

How this affects the revenue cycle

This lesson is part of Medical Billing and Medicare Reimbursement Professional Program. Apply it to the payer, plan, jurisdiction, service date, provider or supplier, item or service, and evidence actually under review.

An accurate code or accepted transaction does not independently prove eligibility, coverage, medical necessity, authorization, documentation sufficiency, or payment. Each control answers a different question and must remain traceable to its source.

Intake owns accurate patient, payer, plan, and service facts.
Clinical and coding teams must work from authenticated records and current code sets.
Billing owns transaction accuracy, submission evidence, and reconciliation.
Denial teams must preserve procedural rights while correcting the actual root cause.

Professional standard of work

A professional billing record should be reproducible by another trained reviewer. Record the source consulted, effective date, claim or line affected, evidence reviewed, missing facts, conclusion, owner, and next deadline.

Do not alter clinical meaning, manufacture support, append a modifier solely to bypass an edit, or promise payment. Escalate conflicts involving clinical judgment, legal interpretation, payer contracts, suspected overpayments, or potential fraud to the appropriate qualified role.

Decision workflow

01
Reconcile payment and adjustment amounts at line and claim level.
Complete workflow control 1, retain the supporting evidence, and resolve exceptions before moving to the next claim decision.
02
Read group code, CARC, every RARC, and payer message.
Complete workflow control 2, retain the supporting evidence, and resolve exceptions before moving to the next claim decision.
03
Classify as rejection, denial, reduction, patient responsibility, or provider-level adjustment.
Complete workflow control 3, retain the supporting evidence, and resolve exceptions before moving to the next claim decision.
04
Route to correction, payer inquiry, reopening, appeal, refund, or contractual posting.
Complete workflow control 4, retain the supporting evidence, and resolve exceptions before moving to the next claim decision.
05
Track the final root cause instead of only the code number.
Complete workflow control 5, retain the supporting evidence, and resolve exceptions before moving to the next claim decision.

Common failure patterns

Reading only the CARC.

Why it fails: The conclusion is no longer reliably tied to the controlling facts, source, or procedural status and may produce rejection, denial, incorrect liability, or audit exposure.

Prevention: Reperform the relevant workflow step, identify the accountable owner, and preserve the supporting record or source citation.

Posting every PR amount without checking notices and contract rules.

Why it fails: The conclusion is no longer reliably tied to the controlling facts, source, or procedural status and may produce rejection, denial, incorrect liability, or audit exposure.

Prevention: Reperform the relevant workflow step, identify the accountable owner, and preserve the supporting record or source citation.

Treating an adjustment as a denial requiring an appeal.

Why it fails: The conclusion is no longer reliably tied to the controlling facts, source, or procedural status and may produce rejection, denial, incorrect liability, or audit exposure.

Prevention: Reperform the relevant workflow step, identify the accountable owner, and preserve the supporting record or source citation.