Denial Knowledge Center

CO-5 — Place-of-Service Inconsistent or Invalid

The two-digit Place of Service (POS) code on the claim doesn't match the type of service billed, or the payer considers that setting invalid/inappropriate for this specific service.

D17
Resolves: Billing/Follow-Up
Prevents: Registration/Scheduling — accurate encounter-location capture; Charge Capture — POS-to-service validation before claim submission.
Primary CARCCO-5CO-58
Common RARCsM77

Denial Identifier

  • Primary CARCs: CO-5 — "The procedure code/type of bill is inconsistent with the place of service." CO-58 — "Treatment was deemed by the payer to have been rendered in an inappropriate or invalid place of service." (X12)
  • Common RARC: M77 — "Missing/incomplete/invalid/inappropriate place of service."

Plain-Language Meaning

  • The two-digit Place of Service (POS) code on the claim doesn't match the type of service billed, or the payer considers that setting invalid/inappropriate for this specific service.

Why the Claim Was Denied

  • Claim construction: wrong POS code entered (e.g., POS 11-Office billed for a service actually performed in a facility setting, or vice versa)
  • Charge capture: scheduling/registration recorded the wrong encounter location
  • Coding: service has specific POS restrictions (e.g., incident-to billing requires POS 11/non- facility settings; certain telehealth codes require POS 02/10)

Information the Biller Must Review

  • POS code billed, actual encounter location per registration/scheduling record, CMS POS code set definitions, payer-specific POS-to-service restrictions (e.g., incident-to requires a non- institutional, office setting).

What Needs to Be Corrected

  • Claim correction: If the POS code was simply mis-keyed relative to the actual encounter location, correct and resubmit.
  • Upstream correction: If registration/scheduling consistently mis-records encounter location for a given service line or provider, that workflow needs correction.

Resolution Workflow

  • Confirm the actual location where the service was rendered from scheduling/registration records.
  • Compare to the POS code billed.
  • If mismatched due to data entry, correct the POS code and resubmit.
  • If the service has a POS-specific restriction (e.g., incident-to requiring POS 11), confirm all conditions for that billing method were actually met before resubmitting under that POS.
  • Document the POS verification outcome.
  • Escalate to Registration/Scheduling if a specific location is consistently mis-coded.

Corrected Claim vs Appeal vs Other Action

  • Corrected claim — for POS data-entry errors.
  • Compliance escalation — if there's a suggestion to bill a facility-based service as office- based (or vice versa) merely to obtain a more favorable payment rate without matching the actual encounter location.

Do Not Do This

  • Do not misrepresent the place of service to obtain a higher (e.g., non-facility) payment rate.
  • Do not bill incident-to under POS 11 if the service was actually rendered in a hospital or SNF setting.

Department Most Likely Responsible

  • Resolves current claim: Billing/Follow-Up. Prevents recurrence: Registration/Scheduling — accurate encounter-location capture; Charge Capture — POS-to-service validation before claim submission.

Prevention Control

  • Claim-scrubber POS-to-CPT compatibility edits; scheduling-system location field tied directly to POS code generation; periodic audit of POS billing patterns by service line.

Escalation Trigger

  • Pattern suggesting POS is being selected for payment-rate advantage rather than actual encounter location (compliance issue).

Sample Scenario

  • Scenario: Claim denied CO-5/M77.
  • Finding: Service was performed in the hospital outpatient department (POS 22) but billed as POS 11 (office) due to a scheduling-template default.
  • Action: Corrected claim submitted with POS 22; scheduling template default corrected for that department.

Resolution path at a glance

IdentifyAssign ownerCorrectResubmit / AppealPrevent

AI Search Terms / Synonyms

  • CO5; CO-5; CO58; place of service denial; POS mismatch; invalid place of service; M77.

AI Answer Guardrail

  • Confirm the actual physical location where the service was rendered before recommending any POS code change — never suggest a POS change made only to increase reimbursement.

Sources

  • X12 CARC list; X12 RARC list; CMS Place of Service Code Set

Validated ClaimetryX Source — Denial Management Knowledge Base, 2026 Research Edition

Research date August 18, 2026. CARC/RARC combinations and payer processes vary. Always check the specific remittance advice and the payer's current requirements before acting on any denial.

Work this denial faster

Denial trackers, corrected-claim checklists, and appeal templates.

Get denial trackers & appeal templates