Understanding 835 Remittance Advice: Reconciling Provider Payments
In healthcare revenue cycle management, getting paid is only half the story. The other half is understanding why you were paid what you were paid. This is where the EDI 835 transaction, also known as the Electronic Remittance Advice (ERA), earns its keep.
The 835 explains how a payer processed a claim and how the payment was applied. It translates dollars into logic.
At its core, the 835 remittance advice links payments to claims submitted via the 837. Each 835 file contains details about the total payment, individual claim payments, adjustments, and denial reasons. For providers, it’s the authoritative source for reconciling expected vs. actual reimbursement.
The real power of the 835 lies in its adjustment data. Each claim line may include Claim Adjustment Reason Codes (CARCs) and Remittance Advice Remark Codes (RARCs). CARCs explain why a payment was reduced or denied — contractual obligation, patient responsibility, non-covered service. RARCs add context, often clarifying documentation issues, policy limits, or payer rules. Together, they form the payer’s explanation of benefits in machine-readable form.
Payment reconciliation typically follows a predictable flow. First, the payment amount in the 835 is matched to the EFT (Electronic Funds Transfer) deposit. Next, claim-level details are reconciled against the original 837 submission. Adjustments are then posted to patient accounts or written off according to contractual rules. Finally, denied or underpaid claims are flagged for follow-up or resubmission.
Despite its structure, the 835 is a frequent source of confusion. Common issues include mismatched claim identifiers, inconsistent use of adjustment codes across payers, missing or delayed 835 files, and difficulty mapping codes correctly in billing systems. These gaps often result in manual work, delayed posting, or missed revenue opportunities.
Effective 835 processing depends on accurate payer enrollment, consistent companion guide interpretation, and well-maintained code mapping tables. Regular audits of adjustment trends can also reveal systemic issues, such as recurring denials tied to eligibility, authorization, or coding errors.
Understanding the 835 is not just an accounting exercise. It’s a feedback loop. When analyzed properly, remittance data highlights revenue leakage, payer behavior, and operational weak spots, turning payment data into strategic insight. In healthcare EDI, clarity equals cash flow. And the 835 is where clarity begins.
To learn more about EDI and become a CEDIAP® (Certified EDI Academy Professional), please visit our course schedule page.