Skip to main content
The 835 is the X12 electronic remittance advice: the payer’s line-by-line explanation of what it did with your claims and why. Every dollar of difference between what you billed and what you received is accounted for in it. Reading one fluently is the most valuable skill in healthcare revenue operations.

The mental model

An 835 has three levels:

The key segments

The adjustment grammar

The core concept. Every dollar not paid is explained by a triple: Group code + CARC (+ optional RARC)

Group codes, who bears the cost

Group codes drive your patient ledger. Posting a PR amount as CO means you never bill a patient who owes you money, pure revenue loss. Posting a CO amount as PR means you bill a patient for something your contract says they don’t owe, which is a balance-billing problem, not just an error.

CARCs, why

Claim Adjustment Reason Codes are maintained by X12. The ones you’ll see constantly: The full working set: CARC codes.

RARCs, the detail

Remittance Advice Remark Codes qualify a CARC when it alone is ambiguous. A CARC 16 with a RARC telling you which information is missing is actionable; a bare CARC 16 is a scavenger hunt. See RARC codes.

Reading a claim

Reading it: billed − contractual = allowed; allowed − patient responsibility = paid. The allowed amount is the real number. Your billed charge is a chargemaster rate no contracted payer pays; the contractual adjustment is the arithmetic difference. New operators fixate on the write-off column, which is the least informative number on the page.

PLB, the segment that breaks reconciliation

Provider-level adjustments sit outside the claim detail and adjust the total payment. They carry:
PLB takebacks are recoupments, and they’re how a payer recovers an overpayment without asking. The dollars vanish from a deposit with no corresponding claim-level entry. If your posting process ignores PLB, your books overstate revenue and your reconciliation never ties. See Handle recoupments and takebacks.

One 835 is not one bank deposit

The single most important operational fact about remittances.
  • One deposit can cover multiple 835s
  • One 835 can be split across multiple deposits
  • The PLB shifts the total away from the sum of the claims
  • Paper checks and virtual credit cards arrive on entirely different timelines than the 835
The mechanism for matching them is the TRN reassociation trace number, carried in the 835 and referenced in the ACH addenda record of the corresponding EFT.
Reconcile by TRN, never by hunting for matching dollar amounts. Amount-matching works until you have two payers sending similar amounts on the same day, then it produces silently wrong postings. See Reconcile payments daily.

Claim status codes (CLP02)

Status 4 sends the line to the denial queue. Status 22 is a reversal, and it means a claim you already posted as paid is being unwound.

Paper EOBs

An explanation of benefits is the paper equivalent. Same information, unstructured, requiring manual posting. Every paper EOB is a payer you should push to ERA, both for the labor saving and because manual posting is where group-code errors happen.

Why 835s are PHI

An 835 contains patient names, member IDs, dates of service, diagnosis and procedure information, and amounts. It is protected health information in every sense. Treat it accordingly: encrypted in transit and at rest, access-controlled, covered by BAAs wherever it lands, including any analytics warehouse you build. And never put PHI in a bank memo field when reconciling. See HIPAA for MSO-PC operators.