Skip to main content

835/837 EDI in Behavioral Health: A Practitioner's Guide

Jeremy Bloom, Co-founder · · Updated

An 837 is the claim a provider sends. An 835 is the remittance the payer sends back. Behavioral health billing depends on both, and the codes inside them are defined by X12 and by the payer’s companion guide. This post uses those definitions. It does not estimate how much money the transactions move.

What an 837 professional claim carries

The professional 837 (837P) is the usual transaction for outpatient behavioral health. Each claim can include subscriber and patient identifiers, billing and rendering provider identifiers, service lines, diagnosis codes, and prior-authorization numbers when the payer requires them.

Service lines are where behavioral health claims usually break. A line needs the procedure code, any modifiers the payer requires, units, dates, a place of service, and diagnosis pointers. Timed psychotherapy codes are different procedure codes, not a unit count the biller invents after the fact. Place of service 02 is telehealth provided somewhere other than the patient’s home, and place of service 10 is telehealth provided in the patient’s home [6]. Which telehealth modifier a payer wants is a payer rule. That discussion is in Telehealth Billing Pitfalls in Behavioral Health.

HCPCS modifiers such as HE and HF are payer instructions. This post does not state an order between them. If a payer requires one before the other, that requirement is in the payer’s policy, not in the 837 format itself.

What CLP02 on the 835 actually means

The CLP segment is claim-level payment information. CLP02 is the claim status code. It does not mean “paid” when the value is 1, and it does not mean “denied” when the value is 2.

X12 has said that CLP02 value 1 means processed as primary, and that value 19 means processed as primary and forwarded to additional payers [1]. Using 1 when the payer forwarded the claim is not the correct representation of that action [1]. A CMS instruction, in a reversal and correction, treats a CLP02 value of 22 as identifying the claim to be a corrected claim [2]. A published remittance guide lists value 2 as processed as secondary, and values 20 and 21 as the forwarded-to-another-payer forms of secondary and tertiary processing [3]. The same guide says CLP02 value 4 should be used only when the payer has no record of ever providing coverage to the patient or subscriber and did not forward the claim, and that 4 should no longer be used as an indicator that a claim was denied [3]. Medicare’s 835 companion guide also notes that claim status code 25, predetermination pricing only with no payment, does not apply to Medicare [4].

The CAS segment carries the adjustment. The code in that segment is a claim adjustment reason code (CARC), which is a different list from CLP02. On the X12 list opened for this review [5]:

  • CARC 16: the claim or service lacks information or has a submission or billing error. At least one remark code is required [5]. X12 says not to use 16 for claim attachments or other documentation.
  • CARC 22: this care may be covered by another payer under coordination of benefits.
  • CARC 50: these are non-covered services because this is not deemed a medical necessity by the payer.
  • CARC 96: non-covered charges, and at least one remark code is required [5].
  • CARC 197: precertification, authorization, notification, or pre-treatment is absent.

A missing authorization is CARC 197. A medical-necessity decision is CARC 50. A claim or service that lacks information or has a submission or billing error is CARC 16, and at least one remark code is required. X12 says not to use 16 for claim attachments or other documentation [5]. Those are different work queues.

Failures that show up on the 835

A taxonomy or NPI that does not match the payer’s enrollment file comes back as a billing error, often CARC 16 or a related procedure-and-provider code, not as a clinical denial. An authorization that lapsed before the date of service is the situation CARC 197 describes [5]. A commercial plan that should have been billed before Medicaid, with the coordination-of-benefits loops empty, is the situation CARC 22 describes [5].

The 837 will send the modifiers and place of service you put on the claim. The 835 will explain the adjustment. It will not repair an expired authorization or a stale enrollment record.

What posting can and cannot do

Posting an 835 means matching the payment and the adjustment codes to the open claim. A payment that matches the expected allowed amount can close the line. An adjustment with CARC 197, 16, or 22 can be routed to the queue for that code. A CLP02 value of 22, in that instruction, identifies the corrected claim in a reversal and correction. It is not a new denial category [2].

This post does not claim a posting speed, and it does not claim that software never misreads a CARC. Encore OS scrubs claims against organization and payer edit rules before submission. It takes in remittances and checks claim status through a clearinghouse connection. Remittance reconciliation that flags underpaid claims is on the roadmap. Those are the billing functions in the product’s capability list. They do not replace reading the CARC.

Sources

  1. RFI 2025: 835/837 payer crossover process, X12. Accessed September 28, 2026.
  2. CMS Manual System, transmittal R1862CP (CLP02 value 22), CMS. Accessed September 28, 2026.
  3. Processing and Reporting Remittance Information, OneHealthPort. Accessed September 28, 2026.
  4. Medicare Fee-for-Service 835 companion guide, 005010X221A1, CMS. Accessed September 28, 2026.
  5. Claim Adjustment Reason Codes, X12. Accessed September 28, 2026.
  6. Place of Service Code Set, CMS. Accessed September 28, 2026.

Encore OS posts billing and finance to one ledger with a fund structure for nonprofit reporting, and reports each grant’s budget against actual spending.

Finance on Encore OS