Key Points
- The ERA carries the payer's decision in a form software can read, which is what allows payments to post against claims automatically rather than by hand.
- It holds the same adjudication detail a member sees on the explanation of benefits, line by line, with standardized reason and remark codes on each adjustment.
- Because the reasons arrive as data, denials can be counted and sorted by cause - which turns a queue of individual problems into a shortlist worth fixing upstream.
Electronic Remittance Advice (ERA) Explained
When a payer finishes processing a batch of claims, it reports the outcome back through the clearinghouse as an ERA. The money travels separately, usually as an electronic funds transfer, and the two are tied together by a trace number that appears in both - which is what lets a practice match a deposit in the bank to the claims it actually paid for.
The file is detailed in a way a summary is not. For each claim, and then for each line within it, the ERA reports what was billed, what the contract allowed, what the plan paid, what falls to the member, and every adjustment in between with a standardized reason or remark code attached. Nothing is rounded off or summarized away, which is exactly what makes it usable by software.
Payment posting is where most of the value lands. A billing system reads the file, matches each payment to the claim it belongs to, writes off the contractual adjustment, and moves the patient balance where it belongs, without anyone keying figures off paper. What does not post cleanly is supposed to fall out for a person to look at - partial payments, lines paid at an unexpected rate, claims the system cannot match - and that exception queue, not the automated portion, is where the attention should go.
Reconciliation is the other half. The deposit and the remittance have to agree, and when they do not, the usual explanation is a recoupment: the payer clawing back an earlier overpayment by netting it out of today's payment. Those offsets appear in the file rather than in the bank, so a deposit that looks short is often fully explained by an ERA nobody has opened yet.
Read in aggregate, the reason codes become a diagnostic. One denial is a task; the same code across thirty claims is a process telling you something - an authorization that lapsed, a clinician whose enrollment was never finished, a modifier applied under the wrong payer's rules. Because ERAs arrive as data, that grouping is a report rather than a research project, and the correction and appeal clocks running from the remittance date make working it promptly a deadline as well as a preference.
The ERA and the explanation of benefits are one adjudication in two renditions: the member receives the readable version, the practice works the machine-readable one. Delivery has to be enrolled per payer, which is worth finishing early - until it is, remittances arrive on paper, posting stays manual, and every advantage above stays theoretical.