Overview
The 835 — formally, the ASC X12 Health Care Claim Payment/Advice Transaction Set — is the HIPAA-standard electronic file payers send to providers to explain how each submitted claim was adjudicated. It contains, at the claim and service-line level, the billed amount, the allowed amount, the paid amount, any contractual adjustment, any denial with its associated Claim Adjustment Reason Code (CARC), any Remittance Advice Remark Code (RARC) providing additional context, and the patient-responsibility amount split into copay, coinsurance, and deductible. Paired with an EFT (Electronic Funds Transfer) identified by a trace number, the 835 is the mechanism that posts cash and adjustments to the practice management system.
The 835 replaced paper Explanation of Benefits (EOB) statements for the majority of US healthcare transactions and is now the backbone of auto-posting workflows. A well-structured 835 ingestion pipeline auto-posts payments, contractual adjustments, and patient-responsibility balances for 90 percent or more of adjudicated claims without manual touch. The remaining 10 percent — denials, partial payments, and claims requiring clinical interpretation — flow into the denial-management work queue for biller review.
The file structure is hierarchical. At the top sits the ISA/GS envelope identifying sender, receiver, and transaction control numbers. Below that is the BPR segment with the total payment amount and the EFT trace number. The CLP loop opens for each claim, with CAS segments reporting claim-level adjustments. The SVC loop opens within each claim for each service line, with its own CAS segments and adjudication detail. The LQ segment carries RARCs. Parsing the hierarchy correctly is non-trivial because CAS segments appear at both claim and service-line levels and their adjustments must be summed correctly to balance the payment.
Reconciliation is the most common friction point. The 835 sum of paid amounts must match the actual EFT received from the payer's bank, and the sum of claim-level activity must balance to the total payment in the BPR segment. Mismatches — often caused by payer corrections applied mid-batch, multiple EFTs within one 835, or 835s split across multiple EFTs — require biller intervention to resolve. CARC 85 (Claim Adjustment — Prior Period Adjustment) and BPR reversal flags are common sources of reconciliation complexity.
Providers typically enroll for 835 delivery through each payer's EDI enrollment process or through their clearinghouse. CMS's CAQH CORE operating rules require payers to support the 835 with specific response times and content, and the CORE v5010 payment-related rules standardize how certain CARCs must be reported. Practices that have not enrolled for 835 from all active payers are foregoing material posting productivity; paper EOB posting commonly requires 3–5 minutes per claim compared to seconds for an 835 auto-posted line.
Industry benchmark
HIPAA and CAQH CORE operating rules require payers to support the 835 electronic remittance with standardized content and timing. Mature revenue cycle teams auto-post 90%+ of 835 lines; the remaining lines — denials, unmatched payments, and partial-pay exceptions — fall through to manual work queues. Time saved versus paper EOB posting is typically 80–90%.
Worked example
A provider receives an 835 from Aetna containing 120 CLP loops. 102 loops auto-post at the full contracted allowed amount with standard contractual adjustments (CARC 45). 12 contain denial CARCs (CARC 197 authorization absent, CARC 16 missing information) and route to the denial-management queue. 4 are partial payments routing to an underpayment review. 2 are duplicate-claim reversals posting as negative payments. The $42,300 BPR total reconciles exactly to the Aetna EFT.
Frequently asked questions — Electronic Remittance Advice (835)
What is the difference between ERA and EOB?
They contain the same information — payer adjudication of a claim. An EOB is the paper or PDF version sent to patients and sometimes to providers. An ERA is the structured X12 835 file sent electronically to providers for auto-posting. The 835 is machine-readable; the EOB is not.
Is the 835 the same as the EFT?
No, but they are paired. The 835 is the remittance advice file explaining how each claim was adjudicated. The EFT is the electronic funds transfer that delivers the cash. They connect via an EFT trace number in the 835 BPR segment.
Why does our 835 not reconcile to the EFT?
Common causes include multiple EFTs covered by one 835, one EFT covering multiple 835s, mid-batch payer reversals, takebacks from prior-period adjustments, or manual check-payment batches sent outside the EDI stream. Each mismatch should be investigated and resolved in the posting work queue.
How do we enroll for 835 from a payer?
Each payer has an EDI enrollment workflow, typically accessible through the payer's provider portal or through your clearinghouse (Availity, Change Healthcare, Waystar). Enrollment requires the practice's NPI, tax ID, and the clearinghouse trading-partner ID. Most enrollments activate within 5–15 business days.
Disclaimer
This glossary entry is operational reference for revenue-cycle and medical-billing professionals. It is not legal, clinical, or contractual advice. Industry benchmarks cite named public sources where available; always verify against the current guidance from the authority body before relying on a number in a contract, policy, or compliance filing.