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: 65 minutes / Reviewed 2026-07-10
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.
Module frame: act from procedural status, not frustration
Post-adjudication work begins by reconstructing what the payer decided and why. Group codes, CARCs, RARCs, line-level data, payer messages, and the original transmitted claim determine whether the next action is posting, correction, inquiry, reopening, appeal, refund, or write-off.
The same account can contain more than one issue. A data error may need correction while a separate coverage determination requires appeal. Deadlines continue to run while the team investigates, so ownership and calendar control are part of the analysis.
Deep dive
The 835 reports payment and adjustments at claim, service-line, and provider levels. Group codes assign adjustment categories, CARCs state general reasons, RARCs add detail, and PLB segments report provider-level adjustments. The full combination controls posting and follow-up.
- CO and PR do not mean the same responsibility.
- A CARC without its RARC can be misleading.
- A PLB is not automatically attributable to the nearest claim.
Remittance interpretation
| Concept | Meaning | Operational control |
|---|---|---|
| Group code | Adjustment category or responsibility | CO, PR, OA or PI context |
| CARC | General reason | Amount and line relationship |
| RARC | Additional detail | Missing information or policy message |
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.
Worked case
Patient responsibility posted too quickly
Known facts
- The ERA reports PR with a CARC.
- A RARC references a required notice.
- No notice record is present.
Decision question
May the balance be billed automatically?
Analysis
- 1. Read the complete code combination.
- 2. Review notice and contract requirements.
- 3. Hold patient billing until liability is supported.
Resolution: Do not transfer the amount solely because PR appears; validate the underlying liability requirements.
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.
Key terms
- CARC
- Claim Adjustment Reason Code describing a general adjustment reason.
- RARC
- Remittance Advice Remark Code adding explanatory information.
- PLB
- Provider-level adjustment reported outside an individual claim.
Field checklist
- Claim and line totals
- Group code
- CARC
- All RARCs
- PLB
- Liability basis
Independent practice
Chapter assignment: Reading the 835 ERA, CARCs, and RARCs
- 1. Answer the worked-case question: May the balance be billed automatically?
- 2. Complete the field checklist for a fictional or fully de-identified case: Claim and line totals; Group code; CARC; All RARCs; PLB; Liability basis.
- 3. Build a source log that identifies the controlling publication, effective or reviewed date, and the fact it supports.
- 4. Write a one-page finding that separates facts, unresolved evidence, procedural status, owner, deadline, and next action.
Submit or produce
- Reading the 835 ERA, CARCs, and RARCs case analysis
- Completed field checklist
- Source and evidence log
- One-page professional finding
Self-evaluation criteria
- Uses only supplied facts
- Applies the correct distinction and workflow
- Cites primary authority
- Explains the resolution
- Assigns an operational next step
Key takeaways
- 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.
Related in-depth guide
Knowledge check
Which code adds detail to a general claim adjustment reason? Explain why the correct answer is supported and why one alternative fails.
Linked HCPCS records
No HCPCS record is linked to this lesson.