Electronic Remittance Advice (ERA / EDI 835): ASC X12N 835 Segments, ERA vs. EOB, EFT Reassociation, and Clinical Trial Billing

An Electronic Remittance Advice (ERA)—commonly referred to by its HIPAA transaction standard, the EDI 835 or ASC X12N 835 (005010X221A1) file—is a machine-readable electronic transaction sent by a health plan (payer) to a healthcare provider, hospital, or medical claims clearinghouse that explains exactly how a submitted health care claim (EDI 837P or 837I) was adjudicated and paid. Mandated nationwide under the HIPAA Administrative Simplification rules at 45 CFR § 162.1602, the 835 ERA enables automated payment posting, contractual adjustment reconciliation, denial management, and clinical trial billing reconciliation.

What Is Electronic Remittance Advice (ERA) and What Is an EDI 835 File?

When a clinic or hospital submits an electronic claim using the ASC X12N 837 format, the health plan’s adjudication engine evaluates the billed CPT/HCPCS procedures, modifiers, and ICD-10-CM diagnosis codes against coverage policies and contracted fee schedules. Once adjudication completes, the payer generates two linked outputs (CMS EFT and ERA Standard):

1. Electronic Funds Transfer (EFT): The actual movement of funds from the payer’s bank account to the provider’s bank account over the Automated Clearing House (ACH) network using the NACHA Corporate Credit or Debit Entry with Addenda (CCD+) standard.
2. Electronic Remittance Advice (ERA / EDI 835): The structured X12 data file transmitted to the provider’s practice management (PM) or revenue cycle management (RCM) system itemizing billed charges, allowed amounts, contractual write-offs, deductible/coinsurance patient responsibility, and line-item denial reasons.

ERA vs. EOB vs. Paper SPR: What Is the Difference?

Dimension	Electronic Remittance Advice (ERA / EDI 835)	Explanation of Benefits (EOB)	Standard Paper Remittance (SPR)
Primary Recipient	Healthcare Provider, Hospital, or Clearinghouse	Patient / Health Plan Member (Beneficiary)	Healthcare Provider (legacy paper format)
Technical Format	Machine-readable ASC X12N 835 (005010X221A1) EDI file	Human-readable paper statement or patient portal PDF	Printed paper table mailed with a paper check
Adjustment Coding	Standardized Group Codes (CO, PR, OA, PI) + CARC and RARC codes	Plain-language consumer summary of plan payment and out-of-pocket balance	Printed CARC/RARC codes requiring manual data entry
RCM Workflow Role	Auto-posts payments, contractual write-offs, and secondary crossover triggers in the EHR/PM ledger	Informs the patient of their deductible, copay, or coinsurance before the provider sends a patient statement	Manual posting; high clerical error rate and delayed denial appeals

Inside an EDI 835 File: Core Segments (`BPR`, `TRN`, `CLP`, `SVC`, `CAS`, and `PLB`)

Under the ASC X12N 835 (005010X221A1) Technical Report Type 3 (TR3) implementation specification, an ERA file is organized into a header, claim/service loops (Loops 2000, 2100, and 2110), and a provider summary trailer:

• BPR (Beginning Segment for Payment Order/Remittance Advice): Reports the total net payment amount, the payment method code (e.g., ACH for EFT deposit, CHK for paper check, or NON for a zero-dollar remittance advice), the payment issue/effective date, and originating/receiving bank ABA routing numbers.
• TRN (Reassociation Trace Number): Contains the unique check or EFT trace number (`TRN02`) and the payer’s originating company identifier (`TRN03`). Under federal CAQH CORE EFT & ERA Operating Rules (45 CFR § 162.1603), the exact same trace number must appear in the NACHA CCD+ Addenda record of the bank EFT deposit so RCM software can automatically reconcile bank deposits against 835 remittance files within ±3 business days.
• CLP (Claim Payment Information — Loop 2100): Initiates each individual patient claim within the batch. It records the provider’s Patient Control Number (`CLP01`), the Claim Status Code (`CLP02`)—such as 1 (Processed as Primary), 2 (Processed as Secondary), 3 (Processed as Tertiary), 4 (Denied), or 22 (Reversal of Previous Payment)—total submitted charges (`CLP03`), total claim payment amount (`CLP04`), total patient responsibility (`CLP05`), and the payer’s internal Claim Control Number (ICN/DCN, `CLP07`).
• SVC (Service Payment Information — Loop 2110): Breaks the claim down to each individual CPT or HCPCS procedure line (including modifiers), reporting the line-item billed charge, line-item paid amount, and adjudicated unit count.
• CAS (Claim Adjustment Segment) & LQ (Remark Codes): Explains every dollar difference between the billed charge and the paid amount using a two-letter Claim Adjustment Group Code paired with a numeric Claim Adjustment Reason Code (CARC):
  • CO (Contractual Obligation): Amounts the in-network provider must write off and may not bill to the patient (for example, CO-45: charge exceeds fee schedule/maximum allowable).
  • PR (Patient Responsibility): Amounts transferred to the patient’s ledger balance (PR-1 Deductible, PR-2 Coinsurance, PR-3 Copayment).
  • OA (Other Adjustments) and PI (Payer-Initiated Reductions): Non-contractual regulatory or bundling adjustments.

  Supplementary Remittance Advice Remark Codes (RARCs) in the LQ (Line level) or MIA/MOA (Claim level) segments provide granular reason details (such as which clinical document or prior authorization number was missing).

• PLB (Provider-Level Adjustment): Located at the bottom of the 835 transaction outside individual patient claims, the PLB segment records bulk financial adjustments applied to the provider’s overall check/EFT—such as Medicare 2% sequestration reductions, prior-claim overpayment recoupments (offsets), periodic interim payments, or late-payment interest. Because PLB adjustments alter the net EFT deposit (`BPR02`) without changing individual `CLP04` claim payments, automated RCM parsers must post `PLB` suspense entries so the bank reconciliation balances to the penny.

How Is Electronic Remittance Advice Used in Clinical Research and Trial Billing Compliance?

In academic medical centers and oncology research sites, automated parsing of 835 ERA files is a primary internal control against research billing noncompliance and False Claims Act liability in clinical trial billing:

1. Auditing Routine Care vs. Sponsor-Paid Research Services: During clinical trial charge capture and billing reconciliation, research revenue integrity teams cross-match inbound 835 `CLP` and `SVC` segments against the study’s Medicare Coverage Analysis (MCA) and clinical trial claim coding (such as ICD-10-CM code Z00.6, Condition Code 30, and HCPCS modifiers Q0 and Q1).
2. Preventing Double Billing and Improper Patient Balance Billing: If an 835 ERA returns a `PR` (Patient Responsibility) deductible or coinsurance balance on a service that the clinical trial informed consent form or sponsor Clinical Trial Agreement (CTA) promised to cover at no cost to the participant, automated ERA scrubbing rules intercept the `PR` balance and route it to the research sponsor ledger rather than generating a prohibited bill to the trial participant.
3. Tracking Prior Authorization and Medical Necessity Denials: Automated monitoring of CARC 197 (Precertification/authorization/notification absent) and CARC 50 (Non-covered services: not deemed a medical necessity) in 835 feeds alerts clinical research coordinators when payer policies reject standard-of-care procedures performed alongside an investigational protocol.