Reference·CLP Segment·CLP01
X12 835 Reference

X12 835 CLP01 (Patient Control Number): Format, Values, and Testing Notes

Jul 27, 2026 · 4 min read
CLP02 →

If your auto-posting job can't match a remittance line back to the claim it billed, nothing downstream matters. CLP01 is that match key, and it is entirely provider-defined — which means your test data generator has to invent it, not look it up in a code table.

Quick answer

CLP01 is a free-form alphanumeric value, up to 38 characters, that repeats the patient account or claim control number the provider assigned when the original 837 claim was submitted. The payer does not generate or validate this value; it simply reflects it back so the billing system can reconcile the payment against the claim it billed.

What this element contains

Format
Alphanumeric — up to 38 characters, no fixed structure — defined entirely by the submitting provider's system
Source
Round-trip value — copied from CLM01 on the original 837 claim submission, not generated by the payer
Uniqueness
Practice-managed — should be unique within the provider's billing system so no two claims collide during posting

Example

Synthetic example Generated by Synthibase
CLP*PAT29817*1*450.00*360.00*45.00*12*993820011477*11*1*

PAT29817 is a synthetic patient control number a billing system might have assigned when the claim was first submitted.

Where this trips people up

Test data generators sometimes reuse the same patient control number across multiple synthetic claims to save effort, then wonder why the reconciliation engine under test merges unrelated payments into one record. Real billing systems rarely reuse this value within a reporting period, so your synthetic files should generate genuinely unique identifiers per claim to catch collision bugs before production does.

X12 835 CLP Segment Guide: Fields, Format, and Testing Gotchas
How to Test 835 Remittance Reconciliation Before Go-Live
EDI 835 Remittance Advice: Complete Guide for Healthcare IT
Stop hand-crafting patient control numbers
Synthibase generates internally consistent 837/835 pairs where CLP01 always matches the originating claim, so your reconciliation tests exercise real matching logic instead of guesswork.
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.