BCBS denial code guide

BCBS CO-170 Denial Code — Payment denied when performed or billed by provider type

What BCBS CO-170 means, why it happens, corrected claim vs appeal steps, evidence checklist, and RARC clues for providers.

Fast answer: CO-170 is commonly used when the payer indicates payment denied when performed or billed by provider type. For BCBS-related claims, read the paired RARC and plan-specific EOB text before choosing corrected claim, appeal, COB update, or payment dispute.

What CO-170 usually means on a BCBS denial

CO-170 is the search phrase many billers use, but the CARC number, group code, RARC, and EOB wording all matter. The same CARC can point to different next actions depending on whether the line is contractual obligation, patient responsibility, other adjustment, or a payer-requested correction.

For BCBS claims, also identify whether this is a local Blue plan claim, an out-of-area BlueCard claim, a carved-out benefit, a secondary claim, or a plan-specific medical policy issue. That context prevents wrong-channel appeals and duplicate resubmissions.

Recommended first action

Provider-data correction or enrollment escalation before appeal.

Common causes

  • NPI is missing, invalid, or not matched to the payer record.
  • Provider type, specialty, taxonomy, service facility, or network status does not support the billed service.
  • Ordering/referring provider is not eligible or not recognized by the plan.
  • The provider contract or negotiated rate is expired, missing, or attached to the wrong product.

Step-by-step fix workflow

  1. Compare the 837 provider loops to payer enrollment, roster, taxonomy, location, and network/product records.
  2. Correct NPI/taxonomy/location fields if the claim is wrong.
  3. Open provider enrollment or credentialing escalation if the payer record is wrong.
  4. Attach roster effective dates, contract proof, and portal screenshots when disputing.
  5. Prevent recurrence by syncing PMS provider tables with the payer’s current provider file.

Evidence checklist

  • Provider enrollment record
  • NPI registry/taxonomy data
  • Payer roster or contract proof
  • Claim provider loops
  • Portal screenshots
  • Corrected claim notes

What not to do

  • Do not change provider fields without confirming who rendered/ordered the service.
  • Do not appeal before checking enrollment effective dates.
  • Do not ignore service facility and taxonomy loops.

Appeal or corrected claim wording

Use a short, evidence-led narrative:

We are requesting review of claim [claim number], DOS [date], denied with CO-170. The attached documentation shows [specific fact]. Based on the plan rule and records, the service should be reprocessed because [one-sentence reason]. Please reprocess the line or provide the exact policy basis for maintaining the denial.

Related codes and RARCs

FAQ

Is BCBS CO-170 always an appeal?

No. Match billing, rendering, ordering, referring, supervising, attending, and service-facility data to the payer’s provider record. The correct action depends on the group code, RARC, EOB text, plan rule, and whether the claim data was originally correct.

What should I check first for CO-170?

Start with the line-level ERA/EOB details: group code, CARC, RARC, claim number, service line, CPT/HCPCS, modifier, date of service, provider identifiers, and payer note.

Can I resubmit the same claim after CO-170?

Only when the plan specifically asks for resubmission. Most repeat denials happen when the second claim does not change the exact field, document, or evidence that triggered the first denial.

What evidence helps overturn CO-170?

The strongest packet usually includes Provider enrollment record, NPI registry/taxonomy data, Payer roster or contract proof, Claim provider loops, plus a short explanation tied to the denial reason.