AGAR Guide
CARC236ReferenceCurrentVerified Aug 15, 2026

CARC 236

AR Guide workflow

Step-by-step: Coding & Modifiers

✓ Workflow verified Aug 15, 2026 · Verified via review of official sources and AR Guide practice testing — not payer policy. View the full guide

  1. VerifySteps 1–11

    1. Submitted code vs. the clinical documentation

    2. Modifier validity for the procedure

    3. NCCI / mutually exclusive edits for the combination

    4. Diagnosis specificity

    5. Revenue code mapping (institutional)

    6. CARC 4 / 11 / 199 / 236 and the accompanying remark code

    7. Compare the submitted code against the clinical documentation

    8. Check modifier usage against coding guidance for the procedure

    9. Review the payer's coding edits (NCCI and similar) for the combination

    10. Confirm the diagnosis is the most specific code for the condition

    11. Check the revenue code mapping for institutional claims

  2. ActSteps 12–15

    1. If the code was wrong, correct and resubmit

    2. If the code was correct, appeal with documentation and the applicable coding guidance

    3. If services were distinct but bundled, appeal with documentation and appropriate modifiers

    4. Run coding edits before submission to catch issues early

  3. Document & QASteps 16–21

    1. Clinical documentation supporting the code

    2. Coding guidance or edit references

    3. The original claim and the corrected version if applicable

    4. Run modifier and coding edits before submission

    5. Match diagnosis specificity to documentation

    6. Track payer-specific modifier requirements in the AR reference notes

AR Guide explanation

What it means

This procedure or procedure/modifier combination is not compatible with another procedure or modifier combination provided on the same day.

AR Guide knowledge

Common denial category

Coding & Modifiers — The payer identified a coding issue — a mismatched or missing modifier, an inconsistent diagnosis, a revenue-code mismatch, or an unbundled service.

AR Guide knowledge

Most common causes

  • Mutually exclusive procedures billed same day
  • Unbundled services
  • Modifier combination conflict

AR Guide knowledge

Action in your PM/EMR system

In your PM system: review the code/modifier/diagnosis against the documentation, correct it, run your edits, and resubmit with frequency code 7 (Replace). Only appeal when the code was correct as billed.

Illustrative scenario

Real-world example

A claim was denied with CARC 4 because a required modifier was missing. Adding the correct modifier and resubmitting with frequency code 7 resulted in payment.

Example — not a claim about any specific payer or account.

AR Guide knowledge

What AR should verify

  1. Review all procedures billed for the same date
  2. Check the NCCI/mutually exclusive edits

AR Guide knowledge

Recommended action

  1. Correct the coding combination and resubmit
  2. If services were distinct, appeal with documentation and appropriate modifiers

Appeal template

No code-specific template yet

No downloadable template targets CARC 236 specifically. Browse all appeal letter templates — or follow the recommended workflow above.

About this guidance: Note

AR Guide knowledge is general reference content written by our team — it is not payer-specific policy and never replaces the payer’s documentation or your contract. Always confirm specifics with the payer.

Priority 2

Commonly paired RARCs

RARCs commonly accompany CARC 236 on the ERA/EOB. Select the one on your line to focus the workflow, or use the list as a lookup.

  • RARCN519Invalid combination of HCPCS modifiers.
  • RARCN431Not covered with this procedure.
  • RARCN20Service not payable with other service rendered on the same date.Identify which same-date service the payer treated as mutually exclusive and confirm it was paid. If the rule was applied incorrectly (the services are separately billable), appeal with the coding guidance; otherwise no action.
  • RARCM78Missing/incomplete/invalid HCPCS modifier.
  • RARCN122Add-on code cannot be billed by itself.Bill the add-on code with its required primary procedure code, or appeal if the primary was separately processed.
  • RARCN38Missing/incomplete/invalid place of service.Correct the place of service code and resubmit.

Priority 3

Payer-specific nuance

How major payers handle this denial — what AR Guide has verified, and what you must confirm with the payer. We never publish payer handling we have not verified.

Medicare

Coding edits, modifier requirements and bundling rules vary by payer. Confirm the payer's specific edit before resubmitting, and keep the documentation that supports the code as billed.

Medicaid

Coding edits, modifier requirements and bundling rules vary by payer. Confirm the payer's specific edit before resubmitting, and keep the documentation that supports the code as billed.

UnitedHealthcare

Coding edits, modifier requirements and bundling rules vary by payer. Confirm the payer's specific edit before resubmitting, and keep the documentation that supports the code as billed.

Aetna

Coding edits, modifier requirements and bundling rules vary by payer. Confirm the payer's specific edit before resubmitting, and keep the documentation that supports the code as billed.

Cigna

Coding edits, modifier requirements and bundling rules vary by payer. Confirm the payer's specific edit before resubmitting, and keep the documentation that supports the code as billed.

Anthem (BCBS)

Coding edits, modifier requirements and bundling rules vary by payer. Confirm the payer's specific edit before resubmitting, and keep the documentation that supports the code as billed.

Did this resolve your denial?

Help us keep this accurate

Report an error in this code’s guidance

Spotted something outdated or incorrect in the AR Guide guidance or the official description? Flag it — the report becomes a review item for our team and never changes the published page directly.

Do not include patient/member information or PHI — no patient names, member IDs, claim numbers, dates of birth or clinical information. This tool never stores PHI, and the server rejects it.