CARC B11 Active

OA-B11: Claim Transferred to Proper Payer

TL;DR

Claim transferred in a COB scenario but the service is not covered by this payer. Investigate the payer order and redirect the claim to the correct payer.

Action
Verify & Resubmit
Who Pays
Depends
Appeal
Yes
Patient Impact
Indirect
Disclaimer
This content is for informational purposes only and does not constitute professional billing advice. Always verify information against your payer contracts and current coding guidelines. Consult a certified billing specialist for specific claim issues.

What Does OA-B11 Mean?

OA-B11 signals a coordination of benefits issue where the claim was transferred between payers and the receiving payer determined the service is not covered. The OA group code indicates the financial responsibility has not been definitively assigned to either the provider or the patient. This requires further investigation to determine where the claim should be directed next.

CARC B11 indicates a two-part problem: the claim was routed to the correct payer or processor, but that payer determined the service is not a covered benefit. This code often surfaces in coordination of benefits (COB) scenarios where a claim bounces between payers before landing at the one responsible for adjudication. When it arrives, the payer processes it but finds the specific service falls outside the patient's benefit plan.

The most common trigger is outdated or incorrect insurance information. If the patient's coverage changed — new employer, new plan, terminated policy — claims submitted to the old payer get transferred to the current one, which then denies the service as non-covered. B11 also fires when the claim crosses payer boundaries in COB situations and the receiving payer's benefit design excludes the procedure. Out-of-network provider status, plan exclusions, and incorrect payer sequencing all contribute to B11 denials.

B11 can appear with CO, OA, or PR group codes depending on where the financial responsibility falls. Under CO, the provider absorbs the loss because the service is contractually non-covered. Under PR, the patient bears the cost because their plan does not include the benefit. Under OA, the responsibility is unresolved and requires further investigation, typically in multi-payer COB situations. The first step in resolution is always verifying that the patient's insurance information is current and that the claim was submitted to the correct payer in the correct order.

Common Causes

Cause Frequency
Claim submitted to wrong payer initially The claim was originally submitted to an incorrect payer and was transferred to the correct one, which then determined the service is not a covered benefit Most Common
Coordination of benefits routing issue In COB scenarios, the claim was forwarded to the appropriate payer in the payment hierarchy, but that payer does not cover the specific service Most Common
Service not covered under patient's plan The claim reached the correct payer but the specific procedure or service falls outside the patient's benefit plan coverage Common
Out-of-network provider The provider is not in the payer's network, and the service is not eligible for out-of-network coverage Common
Incorrect insurance information on file Outdated or inaccurate patient insurance details caused the claim to be routed incorrectly before reaching the proper payer Common
Duplicate claim submission The same claim was submitted multiple times and one instance was flagged as transferred or already processed Occasional

How to Resolve

Verify the patient's current insurance details and payer order, confirm coverage for the service, and resubmit to the correct payer or appeal the non-coverage determination.

  1. Map the payer chain Identify all payers involved in the patient's coverage and determine the correct primary-secondary order.
  2. Submit to the correct payer Redirect the claim to the primary payer if it was incorrectly sent to a secondary, or to the next payer in the chain if the primary correctly denied.
  3. Provide COB documentation Include the primary payer's remittance with the secondary submission so the next payer can properly adjudicate.

Common RARC Pairings

The RARC code tells you exactly what triggered the OA-B11:

RARC Description
N381 Alert: Consult your contractual agreement for restrictions, billing, and payment information.
N130 Alert: You may need to review plan documents or guidelines for coverage details.

How to Prevent OA-B11

General Prevention

Also Filed As

The same CARC B11 may appear with different Group Codes:

Related Denial Codes

Sources

  1. https://www.mdclarity.com/denial-code/b11
  2. https://x12.org/codes/claim-adjustment-reason-codes
  3. Codes maintained by X12. Visit x12.org for official definitions.