AGAR Guide
CARC170ReferenceCurrentVerified Aug 15, 2026

CARC 170

AR Guide workflow

Step-by-step: Provider & Credentialing

✓ 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. Provider enrollment / credentialing status with the payer

    2. NPI and taxonomy on file

    3. Rendering vs. billing provider on the claim

    4. Network status for the date of service

    5. Facility certification for the specific service

    6. CARC 170 / 208 / 242 and the accompanying remark code

    7. Confirm the provider's enrollment and credentialing status with the payer

    8. Verify the NPI against the provider's enrollment records

    9. Check the rendering vs. billing provider on the claim

    10. Confirm the facility's certification for the specific service

    11. Check the provider's network status for the date of service

  2. ActSteps 12–15

    1. Complete provider enrollment or credentialing, then resubmit

    2. Correct the provider information (NPI, taxonomy) and resubmit

    3. Have the appropriate provider type bill the service if scope rules apply

    4. If the arrangement is correct, appeal with provider credentials or certification documentation

  3. Document & QASteps 16–22

    1. Provider enrollment and credentialing confirmation

    2. NPI and taxonomy records

    3. Facility certification documentation

    4. Network status verification for the date of service

    5. Verify provider enrollment before billing a new payer

    6. Track credentialing renewals and NPI updates

    7. Confirm the rendering provider matches the service billed

Sort it: data mismatch (correct) vs. benefit dispute (appeal): Note

Coverage denials split into two very different fixes: if the member data was wrong, correct and resubmit; if coverage existed but the payer misapplied it, appeal with the benefit document and eligibility confirmation.

If you take the wrong path: Appealing a data error burns the window; resubmitting a genuine benefit dispute gets denied again. Either way you lose weeks.

AR Guide explanation

What it means

Payment is denied when the service is performed or billed by this type of provider.

AR Guide knowledge

Common denial category

Provider & Credentialing — The provider type, enrollment, credentialing, network status, or facility certification does not support payment for the service billed.

AR Guide knowledge

Most common causes

  • Provider type not recognized for the service
  • Provider not credentialed for the service type

AR Guide knowledge

Action in your PM/EMR system

In your PM system: re-verify eligibility for the exact date of service first. If the member data was wrong, correct it and resubmit. If coverage is confirmed, attach the verification reference and appeal.

Illustrative scenario

Real-world example

A service was denied with CARC 204 as not covered, but the patient's rider covered it. The appeal attached the benefit document and the denial was reversed.

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

AR Guide knowledge

What AR should verify

  1. Confirm the provider type can bill the service
  2. Check the rendering vs. billing provider on the claim

AR Guide knowledge

Recommended action

  1. Correct the provider information and resubmit
  2. If the arrangement is correct, appeal with provider credentials

Appeal template

No code-specific template yet

No downloadable template targets CARC 170 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 170 on the ERA/EOB. Select the one on your line to focus the workflow, or use the list as a lookup.

  • RARCN130Consult plan benefit documents/guidelines for information about restrictions for this service.Pull the specific plan benefit document and quote the exact restriction in your appeal — a general appeal without the plan language rarely succeeds here.

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

Enrollment, credentialing and network requirements are payer-specific and change over time. Confirm the provider's status with the payer for the exact date of service before appealing or resubmitting.

Medicaid

Enrollment, credentialing and network requirements are payer-specific and change over time. Confirm the provider's status with the payer for the exact date of service before appealing or resubmitting.

UnitedHealthcare

Enrollment, credentialing and network requirements are payer-specific and change over time. Confirm the provider's status with the payer for the exact date of service before appealing or resubmitting.

Aetna

Enrollment, credentialing and network requirements are payer-specific and change over time. Confirm the provider's status with the payer for the exact date of service before appealing or resubmitting.

Cigna

Enrollment, credentialing and network requirements are payer-specific and change over time. Confirm the provider's status with the payer for the exact date of service before appealing or resubmitting.

Anthem (BCBS)

Enrollment, credentialing and network requirements are payer-specific and change over time. Confirm the provider's status with the payer for the exact date of service before appealing or resubmitting.

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.