What Is ERA (Electronic Remittance Advice)?

Electronic Remittance Advice, or ERA, is the digital file a payer sends after processing a claim, showing exactly what was paid, denied, or adjusted and why. It replaces the paper Explanation of Benefits with a standardized electronic format that billing software can read and post automatically.

The Standard Behind Every ERA File

ERA is not a loose term insurers use however they like. It follows a federally mandated format called ASC X12 835, officially titled the Health Care Claim Payment and Remittance Advice transaction. HIPAA requires any covered entity, meaning health plans, clearinghouses, and providers, to use this exact format whenever remittance data moves electronically. The CMS Medicare Claims Processing Manual documents the full requirement for Medicare specifically, and the standard applies the same way across commercial payers.

Enrollment to receive ERA files is typically its own setup step with a payer or clearinghouse, separate from claim submission enrollment. A large share of payers also follow CAQH CORE operating rules, which standardize how ERA and its matching EFT payment connect to each other.

How ERA Moves Through The Billing Cycle

1. Claim submission. The provider sends the claim electronically, usually through the 837 transaction format, often through a clearinghouse that validates and routes it to the right payer.
2. Claim adjudication. The payer reviews coverage, coding, and allowed amounts, then decides whether to pay, partially pay, or deny.
3. ERA generation. The payer builds the 835 file listing every claim, payment amount, and adjustment or denial reason.
4. Posting. The ERA reaches the provider's practice management or EHR system, where payments post automatically if auto-posting is enabled.

ERA is usually paired with EFT, the electronic transfer of the actual payment. Both share a trace number, specifically the TRN segment in the 835 file, which lets billing software match the deposit to the remittance details without manual cross-referencing.

What An ERA File Actually Contains?

An 835 file is dense, but four elements carry the bulk of the daily workload:

• Claim Adjustment Reason Codes (CARC) explain why a payment was adjusted, such as a non-covered service or missing information.
• Remittance Advice Remark Codes (RARC) add detail to a CARC, often specifying what needs correcting for reprocessing.
• Group Codes identify who is responsible for an adjustment: PR (patient responsibility), CO (contractual adjustment), OA (other adjustment), and PI (payer-initiated change).
• Service line detail breaks payment down by CPT code, showing billed, allowed, and paid amounts for each line.

A few common codes show up constantly in practice. CO-45 marks a contractual adjustment, meaning the charge exceeded the contracted rate and gets written off. PR-1 marks a patient's deductible responsibility. CO-97 means the service is bundled into payment for another procedure already billed.

ERA Compared To EOB And EDI

ERA gets confused with two related terms, and the distinction matters for anyone new to payment posting. A closer look at what an EOB actually is makes the comparison clearer.

EDI is the broader category, and ERA sits inside it as one specific transaction type. EDI covers everything from claim submission (837) to eligibility checks (270/271) to remittance (835). ERA is the result that arrives after a claim has already been adjudicated. In short, EDI is the system that moves the data, and ERA is one particular file that system produces.

Where ERA Creates Real Problems?

Automation does not remove every friction point. A few issues come up often enough to plan around:

• Inconsistent formatting across payers. HIPAA sets the 835 standard, but individual payers still vary in which optional fields they populate, which can interrupt auto-posting.
• Missing trace numbers. Without a matching TRN, a payment and its remittance detail have to be reconciled by hand.
• Legacy system gaps. Older practice management systems sometimes cannot fully import 835 files, forcing manual workarounds that defeat the purpose of automation.
• Staff unfamiliarity with codes. A CARC or RARC means nothing if the person reading it does not know what action it calls for, which slows denial management regardless of how fast the file arrived.

Keeping ERA Running Smoothly

• Confirm ERA enrollment is active with each payer and that the clearinghouse is receiving files without duplication.
• Match every ERA to its EFT using the trace number before considering a payment fully reconciled.
• Post ERA files daily rather than letting them accumulate into a backlog.
• Keep a searchable archive of ERA files for audit and appeal purposes.
• Train staff specifically on reading CARC, RARC, and Group Codes, since the file's speed does not help if the codes inside it are misread.

Getting More Value From ERA

ERA does more than replace paper. Done well, it turns payment posting into something that happens automatically instead of something a staff member has to type in line by line. The parts that still cause friction, mismatched trace numbers, inconsistent payer formatting, and codes nobody has time to interpret, are operational problems, not limitations of the format itself. Fixing those is usually a matter of daily reconciliation habits and staff training, and a payment posting team that handles this daily tends to catch mismatches before they turn into a backlog.