CARC B13 Active

OA-B13: Previously Paid Service

TL;DR

Another payer may have already paid this service. Include the primary payer's remittance with the secondary submission to prove this is a COB claim, not a duplicate.

Action
Review & Decide
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-B13 Mean?

OA-B13 appears in coordination of benefits situations where one payer believes the service was already paid by another payer. The OA designation indicates the financial responsibility needs further investigation. This can occur when the primary payer paid the claim and the secondary payer's duplicate detection flags the submission as previously paid rather than recognizing it as a COB claim.

CARC B13 fires when the payer's system detects a potential duplicate payment — it found a prior remittance that appears to cover the same service for the same patient. The payer is withholding payment on the current claim to prevent double reimbursement. This is a protective measure against overpayment, but it frequently catches legitimate claims that are not actually duplicates.

The most common trigger is an accidental resubmission of a claim that was already paid. Batch processing errors, system glitches, or a billing team member re-dropping a claim they assumed was not submitted can all produce genuine duplicates. However, B13 also misfires when the payer's duplicate detection logic is too aggressive. Services performed on the same date by the same provider but for different encounters, split claims that cover different service lines, and corrected claims that replace prior versions can all be incorrectly flagged as previously paid.

B13 typically pairs with Group Code CO because the payer is asserting a contractual adjustment — the service was already paid and no additional reimbursement is owed. The first action is always to verify the payer's assertion by pulling the prior remittance and comparing it line-by-line with the current claim. If the claims are identical, the denial is correct and the duplicate should be voided. If the claims differ in any material way — different procedures, different dates, different encounters — the denial is a false positive and should be appealed with documentation clearly demonstrating the distinction.

Common Causes

Cause Frequency
Duplicate claim submission The same claim was unintentionally submitted more than once due to human error, batch processing mistakes, or system glitches, and the payer already paid the first submission Most Common
Overlapping services billed twice Same or similar services were billed twice for the same date of service and patient, often due to split billing or multiple encounter entries Most Common
Overpayment on prior claim The provider received more than what was owed on a previous claim, and the payer is flagging the current submission as a potential duplicate or overpayment recovery Common
Incorrect payment allocation Payment received on a prior remittance was allocated to a different claim or patient, making it appear that the current claim was already paid Common
Claim splitting errors A larger claim divided into smaller parts was accidentally resubmitted, creating a duplicate payment scenario Common
Coordination of benefits confusion Multiple insurance policies led to payment from one payer being mistaken for full payment, causing the second payer to flag the claim as previously paid Occasional

How to Resolve

Verify whether the claim was genuinely paid before, and either accept the duplicate denial or appeal with evidence showing the claims are distinct.

  1. Provide the primary payer's remittance Submit the primary payer's ERA showing what was paid and what patient responsibility remains. This proves the claim is a COB submission, not a duplicate.
  2. Resubmit with COB information Resubmit the claim to the secondary payer with the primary remittance attached and the correct COB indicators on the claim form.

Common RARC Pairings

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

RARC Description
MA01 Alert: If you do not agree with what we approved for these services, you may appeal our decision.
N381 Alert: Consult your contractual agreement for restrictions, billing, and payment information.

How to Prevent OA-B13

General Prevention

Also Filed As

The same CARC B13 may appear with different Group Codes:

Related Denial Codes

Sources

  1. https://www.mdclarity.com/denial-code/b13
  2. https://www.healthquestbilling.com/b13-denial-code/
  3. Codes maintained by X12. Visit x12.org for official definitions.