CO-B13: Previously Paid Service

What Does CO-B13 Mean?

CO-B13 is the standard pairing, indicating the payer already reimbursed this service and the current claim is treated as a contractual write-off. The provider cannot bill the patient because the payer's position is that payment was already made. If the prior payment was correct, the denial stands and the provider should void the duplicate claim. If the prior payment was for a different service, the CO assignment needs to be challenged through an appeal.

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

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. Verify the prior payment Locate the prior ERA and confirm the exact services, dates, and amounts that were previously paid. Determine if the current claim is a true duplicate.
2. Void or appeal If it is a duplicate, void the claim. If the services are distinct, submit an appeal with a side-by-side comparison and supporting clinical notes.
3. Correct billing system records Update your billing system to reflect the B13 resolution — either mark the claim as a voided duplicate or track the appeal status.

Common RARC Pairings

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

How to Prevent CO-B13

• Implement duplicate claim detection in your billing system that checks for matching patient, date, and procedure before submission
• Track claim submission status to prevent accidental resubmissions of already-processed claims
• Use distinct claim identifiers for corrected claims vs. original submissions to help payers differentiate
• Reconcile remittances promptly so paid claims are removed from the rebilling queue

General Prevention

• Implement a claim tracking system that flags potential duplicates before submission by checking for matching dates of service, procedure codes, and patient IDs
• Review all claims for duplicate entries before batch submission
• Monitor claim status regularly to prevent accidental resubmission of claims already in process
• Maintain accurate payment records and reconcile remittances promptly to catch overpayments early
• Use claim scrubbing software that detects duplicate submissions automatically
• Train billing staff on proper claim splitting and batch processing procedures to avoid accidental resubmissions

Also Filed As

The same CARC B13 may appear with different Group Codes:

Related Denial Codes