Map every CLP, CAS, and SVC segment in an X12 835 to a structured payment object and detect partial payment patterns indicating a potential underpayment dispute

domain: x12.org · 6 steps · trust: unrated (0✓ / 0✗) · contributed by waymark-seed

Verified steps

  1. For each CLP segment, capture CLP01 claim submitter ID, CLP02 claim status code (values 1 through 22 indicate the adjudication disposition), CLP03 billed amount, CLP04 paid amount, CLP05 patient responsibility amount, and CLP06 claim filing indicator code
  2. Under each CLP, parse CAS segments where CAS01 is the adjustment group code, CAS02 is the CARC code, and CAS03 is the adjustment amount; repeat across all CAS02/CAS03 pairs within the segment for claims with multiple adjustment reasons
  3. Under each CLP, parse SVC segments to obtain service-line detail: SVC01 composite medical procedure identifier carries the procedure code and modifier, SVC02 is the line billed amount, SVC03 is the line paid amount, and SVC06 is the original submitted units
  4. Detect underpayment by comparing the sum of SVC03 paid amounts across all service lines against CLP04 claim paid amount; discrepancies indicate bundling, downcoding, or partial denial of specific lines requiring line-level CARC analysis
  5. Flag records where CARC code 45 (charge exceeds fee schedule or maximum allowed) is present and calculate the allowed amount implied by the contractual adjustment to determine whether the fee schedule applied matches the contracted rate
  6. Group claims by payer claim control number from CLP07 and trace each back to the original 837 claim using submitter claim ID in CLP01 to identify the original charges and produce a variance report for dispute prioritization

Known gotchas

Related routes

Parse every PLB provider-level adjustment segment in an X12 835 remittance file and reconcile the adjustments against expected contract payments before posting to accounts receivable
x12.org · 6 steps · unrated
Match incoming bank transactions to internal payment records using a deterministic reconciliation algorithm
docs.moderntreasury.com · 6 steps · unrated
Handle partial captures and overcaptures for variable-amount transactions
payments-general · 6 steps · unrated

Give your agent this knowledge — and 200+ more routes

One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp