OA-5: Procedure Code Inconsistent with Place of Service
Place-of-service mismatch flagged by a secondary payer. Review the primary ERA, correct the POS if needed, and resubmit to the secondary payer.
What Does OA-5 Mean?
OA-5 is uncommon and typically appears in coordination of benefits or secondary payer situations where the place-of-service mismatch is flagged during cross-payer adjudication. The primary payer may have processed the claim differently, and the secondary payer's edits catch the inconsistency.
CARC 5 flags an inconsistency between the procedure code (or type of bill) and the place of service (POS) on your claim. The payer's front-end edits detected that the billed service cannot be performed in the location indicated, or the billing format does not match the facility type. This is a straightforward data integrity rejection rather than a coverage denial — the payer is not saying the service is uncovered, but that the claim as submitted does not make logical sense.
Common scenarios that trigger CARC 5 include billing an inpatient-only procedure with an outpatient POS code, submitting a facility-only service from a physician office, or using the wrong type of bill on a UB-04 claim. Telehealth billing is another frequent source of CARC 5 denials, particularly when telehealth services are submitted with an in-person POS code instead of POS 02 (Telehealth Provided Other than in Patient's Home) or POS 10 (Telehealth Provided in Patient's Home).
Because this is a coding-level error, CARC 5 almost always appears with Group Code CO, meaning the provider absorbs the denial and cannot bill the patient. The fix is typically straightforward: identify the mismatch, correct the POS code or procedure code, and resubmit as a corrected claim. There is no need to appeal unless the original coding was actually correct and the payer's edit logic is wrong — in which case you would contact the payer directly to request override or reprocessing.
How to Resolve
Identify the procedure-to-place-of-service mismatch, correct the claim, and resubmit.
- Review the primary payer's adjudication Check how the primary payer processed the claim and what POS code they accepted. The secondary payer may have different POS edit rules.
- Correct the POS code if needed Align the secondary claim's POS code with the correct service location and resubmit to the secondary payer.
- Contact the secondary payer if the coding is correct If the POS is accurate, provide the primary ERA showing the claim was processed correctly and request the secondary payer to override their edit.
Common RARC Pairings
The RARC code tells you exactly what triggered the OA-5:
| RARC | Description |
|---|---|
| M77 | Missing or incomplete place of service information. |
| N517 | Alert: Payment based on an alternate procedure code or place of service. |
How to Prevent OA-5
- Ensure POS codes are consistent across primary and secondary claim submissions
- Review secondary payer POS edit requirements, which may differ from primary payer rules
General Prevention
- Maintain an up-to-date reference of valid procedure code and place of service code combinations for each payer
- Configure claims scrubbing software to flag procedure-to-POS mismatches before submission
- Train billing staff on current POS code requirements, especially for telehealth, ASC, and facility vs. professional billing scenarios
- Conduct regular coding audits to identify recurring POS-related denials and update workflows accordingly
- Stay current with CMS and payer-specific updates to POS code requirements, particularly around telehealth waivers and facility billing rules
- Implement pre-submission claim validation that cross-references procedure codes against the place of service
Also Filed As
The same CARC 5 may appear with different Group Codes:
Related Denial Codes
Sources
- https://www.mdclarity.com/denial-code/5
- https://ambci.org/medical-billing-and-coding-certification-blog/guide-to-claim-adjustment-reason-codes-carcs
- https://etactics.com/blog/denial-codes-in-medical-billing
- Codes maintained by X12. Visit x12.org for official definitions.