What Is ERA (Electronic Remittance Advice / 835)?
The ERA (X12 835 transaction) is the HIPAA-standard electronic file payers send to providers detailing claim adjudication results — payments, adjustments, denials with CARC/RARC codes — typically paired with EFT funds transfer.
- Auto-post 835 files into the practice-management system and spend the human effort on the exceptions rather than on the volume.
ERA (Electronic Remittance Advice / 835)
Also known as: Electronic Remittance Advice; 835 Transaction; EFT/ERA
The ERA (X12 835 transaction) is the HIPAA-standard electronic file payers send to providers detailing claim adjudication results — payments, adjustments, denials with CARC/RARC codes — typically paired with EFT funds transfer.
Definition
The X12 835 Health Care Claim Payment/Advice transaction is the provider-facing counterpart to the 837 claim submission. Each file carries one or more claim payment records: the paid amount, the adjustments accounting for the difference between billed and paid with their claim adjustment reason codes, any remark codes the payer attached, the split of patient responsibility, and provider-level adjustments in the PLB segment for amounts that do not belong to a single claim — recoupments of earlier overpayments, refunds, capitation, interest and penalties. CMS states that under HIPAA all payers, including Medicare, must use the claim adjustment reason codes and remittance advice remark codes approved by the X12 recognized code set maintainers, and “are not allowed to use their own proprietary codes to explain any adjustment in the claim payment” (CMS payment, remittance advice and EFT). Providers usually enroll for EFT and ERA together, through the payer or through a clearinghouse-mediated enrollment service.
Example
A synthetic 835 — the figures below are illustrative and not taken from a real remittance. The file contains three claims: one paid $98 with a $52 contractual adjustment, one denied on medical necessity, and one paid $85 with $30 applied to the patient deductible. Below the claims sits a PLB segment recouping $140 against an overpayment identified on a claim from two months earlier. The deposit is therefore $140 less than the sum of the three claim payments, which is the normal case rather than an error. Remark codes are a separate matter from payment: a remark code reporting missing or invalid identifying information generally accompanies a claim the payer would not adjudicate, so reading one on a paid line usually means the line has been misread. Look any code up in the current X12 list rather than relying on a remembered meaning.
Common Misconceptions
An 835 is not one payment — a single file typically covers many claims settled in one deposit, and the deposit can be smaller than the claim payments it reports, because provider-level PLB adjustments come out of the same transfer. Reconciling the file to the bank is a specific mechanic, and it is not the BPR segment. CMS states that health plans must place the X12 835 TR3 TRN segment into the addenda record of the CCD+ payment, and that “the TRN Segment in the Addenda Record of the CCD+ should match the TRN Segment in the associated ERA that describes the payment” — a process CMS calls re-association (CMS). A deposit with no matching TRN, or a file with no matching deposit, is an exception to work rather than something to post on faith.
Practical Application
Auto-post 835 files into the practice-management system and spend the human effort on the exceptions rather than on the volume. The exceptions are the design: deposits that do not re-associate to a file by TRN, PLB adjustments that have to be traced back to the original claim before they can be posted, and any adjustment or remark code outside your standard contractual set, which should open a work-queue item instead of posting silently. How much manual effort auto-posting removes depends on your payer mix, how much of it arrives as an 835 at all, and how clean your contract tables are, so measure it on your own remittances rather than against a published savings rate.
Related Terms
EOB (Explanation of Benefits)
An Explanation of Benefits is a payer-issued document sent to the member (and sometimes the provider) after claim adjudication that itemizes the services billed, allowed amount, plan payment, deductible/coinsurance/copay applied, and patient responsibility.
Read definitionCARC
A Claim Adjustment Reason Code is a standardized code maintained by the X12 External Code List committee that explains why a claim line was adjusted (paid less than billed, denied, or transferred to patient responsibility) on a payer's 835 ERA.
Read definitionRARC
A Remittance Advice Remark Code is a code carried on the 835 ERA that either adds explanation to an adjustment already described by a CARC or conveys information about remittance processing. X12 publishes the list as external code list 411 and names CMS as its maintainer.
Read definitionPayment Posting
Payment posting is the revenue cycle step where insurance payments (from 835 ERA or paper EOBs) and patient payments are applied to specific claim lines and patient accounts in the practice management system, including contractual adjustments and denial transfers.
Read definitionX12 (HIPAA EDI)
ASC X12 is the standards body whose X12N subcommittee develops the HIPAA-named electronic data interchange transactions for healthcare administrative data: 837 (claims), 835 (remittance), 270/271 (eligibility), 276/277 (claim status), 278 (prior auth), and 834 (enrollment).
Read definitionWhere This Applies on MedPrecision
Need help with billing?
If this term is showing up in your denials, EOBs, or A/R aging, we can help. Get a free billing audit and we will trace the issue to its root cause.
- No contract
- No setup fees
- Reply within 1 business day