X12 835 Reference

CLP02 in X12 835: A Field Guide to Claim Status Code

Jul 27, 2026 · 4 min read

A denial and a partial payment can look nearly identical if you only skim the dollar amounts. CLP02 is the field that tells your system which one it is actually looking at, and most test suites only ever exercise the "paid as primary" happy path.

Quick answer

CLP02 is a two-digit numeric code that states how the payer adjudicated the claim. Common values include 1 (processed as primary), 2 (processed as secondary), 3 (processed as tertiary), 4 (denied), 19 (processed as primary, forwarded to additional payer), and 22 (reversal of previous payment). This single field is what tells a posting system whether to apply money, hold for secondary billing, or route the claim to a denial-management workflow.

Valid code values

Processed as Primary — standard adjudication with this payer as the primary insurer

Processed as Secondary — payer adjudicated after a primary payer already applied benefits

Processed as Tertiary — third payer in a coordination-of-benefits chain

Denied — no payment issued — CAS segments underneath should explain why

Processed as Primary, Forwarded to Additional Payer — payment made and claim data forwarded via COB, often via crossover

Reversal of Previous Payment — a prior remittance is being taken back, often paired with a negative payment amount

Example

Synthetic example Generated by Synthibase

CLP*PAT29817*1*450.00*360.00*45.00*12*993820011477*11*1*

Status code 1 shows this synthetic claim was processed as primary.

Where this trips people up

Teams frequently build their entire 835 test suite around status code 1 and never generate a code 4 (denied) or 22 (reversal) file, because those cases feel like edge cases rather than the norm. In production they are common enough that skipping them in testing leaves the denial-management and reversal-handling code paths completely unverified until they fail on a live payment.

→

X12 835 CLP Segment Guide: Fields, Format, and Testing Gotchas

→

EDI Rejection Codes: Complete List and How to Fix Them

→

How to Reduce Claim Denials Through Better Pre-Submission Testing

Test every claim status, not just the happy path

Synthibase can generate synthetic 835 batches that deliberately mix paid, denied, and reversed claims so your posting and denial-management logic gets exercised the way production actually behaves.

Start free trial →

This page is written independently by Synthibase for testing and informational purposes. It is not an official publication of HL7 International or X12/Washington Publishing Company, and is not a substitute for reviewing the official standard or your trading partner's companion guide. See our Terms of Service for full legal terms.