Reference·CLP Segment·CLP03
X12 835 Reference

What Is X12 835 CLP03? Total Claim Charge Amount, Explained for Testers

Jul 27, 2026 · 4 min read
← CLP02 CLP04 →

CLP03 is the anchor number every other amount on the claim gets compared against. If it doesn't match what was actually billed on the corresponding 837, your reconciliation dashboards will show variances that have nothing to do with the payer's adjudication.

Quick answer

CLP03 reports the total amount originally billed for the claim, expressed as a decimal dollar figure with no currency symbol or thousands separator. It should mirror the total charge amount reported on the original 837 claim submission (CLM02), and it stays fixed regardless of how much the payer ultimately decides to pay.

What this element contains

Format
Decimal amount — numeric with up to two decimal places, no dollar sign or commas, e.g. 450.00
Relationship
Matches CLM02 — should equal the total charge amount from the originating 837 claim submission
Sign
Always non-negative — unlike CLP04, this value is never reported as negative, even on a reversal

Example

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

The claim was originally billed at $450.00, shown in CLP03 regardless of how it was later adjudicated.

Where this trips people up

When synthetic test files are generated independently for the 837 and the 835, it is easy for the charge amounts to drift apart because each generator invents its own number. Real payers echo the billed amount exactly, so a mismatch between CLM02 on your test 837 and CLP03 on the matching test 835 will make your reconciliation tests fail for a reason that would never occur in production.

X12 835 CLP Segment Guide: Fields, Format, and Testing Gotchas
How to Validate X12 EDI Files Before Payer Submission
How to Test 835 Remittance Reconciliation Before Go-Live
Keep billed and remitted amounts in sync automatically
Synthibase generates matched 837/835 test pairs where charge amounts stay consistent end to end, eliminating false-positive reconciliation failures caused by mismatched synthetic data.
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.