EDI 835 (electronic remittance)

The EDI 835, formally titled the ASC X12N 835 Health Care Claim Payment/Advice transaction (version 005010X221A1), is the machine-readable file an insurance payer generates and transmits to a healthcare provider—or its billing agent—after processing one or more claims. It travels in response to a previously submitted EDI 837 (the claim transaction) and carries claim-level and service-line-level detail: the amount billed, the amount paid, contractual adjustments, patient responsibility (deductible, co-insurance, co-pay), and coded explanations for any shortfall via Claim Adjustment Reason Codes (CARCs) and Remittance Advice Remark Codes (RARCs). The 835 typically arrives paired with an Electronic Funds Transfer (EFT), linking a specific dollar deposit to the remittance data so the provider's billing system can reconcile money movement with claim-level specifics.

The file is structured as a hierarchy of X12 loops and segments. The outermost envelope (ISA/IEA, GS/GE) wraps one or more ST/SE transaction sets. Inside, Loop 1000 identifies the payer and payee; Loop 2000 organizes claims by header provider; Loop 2100 carries individual claim payment detail; and Loop 2110 carries service-line-level adjustments. A PLB (Provider-Level Balance) segment at the end of each transaction accommodates recoupments, interest, and cross-claim offsetting. Because one 835 may consolidate payments for many 837 submissions—and conversely, a single 837 may spawn multiple 835 responses—orthopedic billing systems must reconcile by claim control number and trace number rather than by assuming a one-to-one match.

For orthopedic practices, the 835 is the primary data source for auto-posting payments into practice management systems, identifying denial patterns (e.g., bundling edits on multi-level spine procedures, modifier disputes on bilateral arthroplasty), and generating the payer analytics needed to negotiate contracts and forecast revenue. Medicare publishes payer-specific Companion Guides—binding documents that extend the base X12 standard with payer rules about CARC/RARC subsets, PLB usage, file batching frequency, and Trading Partner Authentication requirements.

If an orthopedic practice cannot correctly parse and auto-post 835 data, cash posting reverts to manual entry: a process that introduces misapplied payments, inflates days in accounts receivable, and masks denial trends. More critically, CARC and RARC codes embedded in the 835 are the only payer-generated explanation for why a high-value procedure—such as a total knee arthroplasty or a multilevel spinal fusion—was paid at a rate below the fee schedule. Ignoring or misreading those codes means missing the appeal window (often 90–180 days) and permanently writing off recoverable revenue. On the compliance side, failure to reconcile 835 EFT deposits against the actual bank deposit creates unresolved variances that can trigger internal audit findings or, in Medicare contexts, overpayment obligations under the 60-day rule.