EOB, ERA, RA, CARC, and RARC Reading

A billing specialist must be able to read payer remittance information because payment posting, denial management, patient billing, appeals, and aging follow-up all depend on it. The explanation of benefits, or EOB, is commonly sent to the patient or available through the patient's insurance portal. It explains, in patient-friendly terms, what was billed, what the payer allowed, what was paid, what was denied, and what the patient may owe. The remittance advice, or RA, is sent to the provider and is designed for business office use.

Key Concepts

It contains the payment and adjustment details needed to post payer payments, contractual allowances, denials, recoupments, and patient responsibility. An electronic remittance advice, or ERA, is commonly the HIPAA 835 transaction. The 835 can be imported into a practice management or billing system for automated or semi-automated posting, but human review remains important when there are denials, unusual adjustments, credit balances, unmatched claims, secondary billing issues, or payment variances.

The RA usually includes payer information, payee information, check number or electronic funds transfer trace number, payment date, payment amount, claim identifiers, patient account numbers, dates of service, billed charges, allowed amounts, payments, adjustments, and remark codes. Before posting is complete, the payment poster should reconcile the RA or ERA to the actual deposit. The electronic funds transfer amount should match the total paid on the remittance batch, except when the payer reports offsets, recoupments, withholding, or other balancing items.

A mismatch should be investigated before balances are closed or transferred to patients. Remittance advice uses standardized and payer-specific data to explain outcomes. Claim adjustment group codes identify the general category of adjustment. Common group concepts include patient responsibility, contractual obligation, payer-initiated reductions, and other adjustments. Claim adjustment reason codes, or CARCs, explain why an amount was adjusted.

A CARC might indicate deductible, coinsurance, copayment, noncovered service, duplicate claim, missing information, timely filing, bundling, benefit maximum, medical necessity, authorization, or provider credentialing issues. Remittance advice remark codes, or RARCs, provide additional explanation when the CARC alone is not enough. A RARC may tell the provider that medical records are needed, the payer needs another payer's EOB, the service requires prior authorization, the claim was processed according to a specific policy, or appeal rights are available.

Workflow and Documentation

For exam purposes, think of CARCs as the adjustment reason and RARCs as extra processing detail. Neither should be read in isolation. The same CARC can require different next steps depending on the group code, payer, benefit plan, and RARC. For example, a noncovered service with patient responsibility may lead to patient billing if notice and consent rules were met. A noncovered service with contractual obligation may require a provider writeoff. A missing information denial may require records submission, claim correction, or a payer portal upload.

A duplicate claim denial may be correct if a prior claim already paid, but it may require follow-up if the payer duplicated the wrong claim or failed to process a corrected claim. A remittance also helps distinguish denial, reduction, and patient responsibility. If the payer allowed the service but applied the allowed amount to deductible, the payer did not deny payment because the service was invalid; the plan assigned payment responsibility to the patient.

If the payer denied because the patient was not eligible on the date of service, follow-up should begin with coverage verification and possible alternate insurance.

If the payer paid less than expected, the next step is contract review rather than automatic appeal. If the payer offset the payment because of a prior overpayment, the posting team must record both the current payment and the recoupment accurately so accounts receivable and cash balancing remain correct. Manual and electronic remittance reading also supports secondary billing. Secondary claims often require the primary payer's allowed amount, payment, adjustment, and patient responsibility data.

Exam Application

The 835 or EOB may feed the secondary claim automatically, but the biller should verify that the primary adjudication information is complete and correctly mapped. Incorrect primary data can cause secondary rejection, denial, or overpayment. Medicare crossover, commercial coordination of benefits, workers' compensation, and liability claims each have their own timing and documentation expectations. For CBCS study, practice tracing a line from charge to allowed amount to payment to adjustment to remaining balance.

Ask: who is responsible, why was the amount adjusted, is the adjustment contractual or patient responsibility, does the remittance request more information, does the payer payment match expected reimbursement, and what note should be entered for follow-up? Accurate RA reading prevents wrong patient bills, missed appeals, duplicate work, and hidden underpayments.

High-Yield Checkpoints

• An explanation of benefits is patient-facing, while a remittance advice is provider-facing and supports payment posting and denial follow-up.
• An electronic remittance advice is usually transmitted as an 835 transaction and should be reconciled to deposits before posting is finalized.
• CARCs explain why a payment was adjusted, denied, reduced, or assigned to patient responsibility.
• RARCs add supplemental detail, such as documentation needed, appeal rights, or payer-specific processing information.
• Reading group codes, CARCs, RARCs, allowed amounts, payment amounts, and remark text together prevents incorrect writeoffs and missed appeals.