Remittance Advice (ERA / 835)

What remittance advice is

Remittance advice is the payer's accounting of a claim. In behavioral health and across healthcare, it is the document that connects what you billed to what actually got paid and why.

Electronically, remittance advice is the HIPAA 835 transaction. Most payers send ERAs through a clearinghouse or directly to your practice management system. Paper versions are often called EOBs, although technically the explanation of benefits is for the member and the 835/RA is for the provider.

Each ERA includes claim‑level information and service‑line details. At a minimum you see billed charges, payer allowed amounts, payment amounts, patient responsibility, and adjustments with claim adjustment reason codes (CARCs) and remittance remark codes (RARCs).

Why remittance advice matters operationally

Cash posting and revenue reporting depend on accurate interpretation of remittance advice. If posting rules ignore CARCs and RARCs, your A/R looks inflated, your write‑offs are wrong, and net collection rate is misleading.

ERAs are also where most underpayments hide. A claim can show as "paid" in a portal, yet the payer may have priced a H‑code, S‑code, or per‑diem rate below contract. The only place to consistently catch that is in the allowed amount fields and the associated adjustment codes on the 835.

For audits and appeals, remittance advice is the official record of the payer's position. Incorrect posting or losing access to historical ERAs makes it much harder to argue pattern underpayments, dispute recoupments, or prove timely filing on corrected claims. That shows up as days in A/R, unworked denials, and real cash left on the table.

How remittance advice is read and used

Operationally, ERAs drive several core workflows:

• Cash posting to patient and insurance balances
• Identifying denials and underpayments
• Applying contractual write‑offs
• Feeding denial and payment variance reporting
• Reconciling deposits to expected payments

Reading an 835 means tying together a few key fields:

• Claim control number and patient info to match back to your PM/EHR claim
• Billed charge versus allowed amount for each CPT/HCPCS, H‑code, or revenue code
• Payment amount and patient responsibility (deductible, coinsurance, copay)
• CARCs and RARCs that explain any reduction or denial
• Group codes (PR, CO, OA, PI) that identify who owes what and whether an amount is contractual

The CARCs and RARCs on each adjusted line should map directly into your denial‑code reporting. Codes like CO‑45 (contractual obligation) help you separate true denials from contractual adjustments. Codes like CO‑16 or CO‑97 signal fixable issues that belong in your denial work queues, not in permanent write‑offs.

A clean behavioral health revenue cycle builds posting rules around the ERA. The team or system should auto‑post standard contractual adjustments, route non‑contractual CO adjustments and PR shifts for review, and flag any allowed amount below contracted rate for a given service or level of care.

• Treating every CO‑45 adjustment on the ERA as automatically correct, so underpayments on H0010 or residential per‑diem codes post as contractual instead of being checked against your actual fee schedule.
• Ignoring line‑level allowed amounts and only looking at total payment per claim, which hides situations where a payer underprices one CPT or H‑code but slightly overpays another so the claim total looks plausible.
• Not mapping CARCs and RARCs from the 835 into your denial categories, which forces staff to hunt denials in portals instead of working a clear CO‑16, CO‑97, or PR‑related queue generated directly from the ERA.
• Letting the system auto‑post patient responsibility from the ERA without comparing to the benefit plan, which creates patient statements that do not match what members see on their EOBs and drives complaints and refunds.
• Failing to monitor PLB segments and negative adjustments on ERAs, so payer recoupments quietly offset future payments and you never work the original overpayment or appeal if the take‑back is wrong.

Behavioral health underpayments often sit inside "paid" ERAs, not in obvious denials. Managed Medicaid, MCOs, and carve‑out vendors frequently price H‑codes, S‑codes, and ASAM levels of care at the wrong contract rate or use outdated fee schedules that were never updated in their system.

The only reliable way to catch those misses is to compare the allowed amount on each service line in the ERA to your contracted rate by payer and level of care. For example, if H2034 per 15 minutes of ACT is contracted at one rate and the ERA consistently shows a lower allowed amount with CO‑45, you have a pattern underpayment issue, not a normal contractual adjustment.

Behavioral health also sees long episodes and per‑diem billing for residential, PHP, and IOP. Payers may partially approve days, downgrade levels of care mid‑stay, or apply concurrent authorization limits. Those changes appear as adjustments across multiple ERAs, with CARCs and RARCs that explain why some days price differently. If nobody reads and codes those remits correctly, you lose days of payment with no clean denial to appeal.

For carved‑out behavioral benefits, the RA from the carve‑out vendor is often the only clear record of how a global authorization was consumed across multiple levels of care. Consistent review of 835s against authorizations, clinical documentation, and contracts is what turns vague "they never pay us correctly" complaints into specific, appealable dollar variances.

AI can help with remittance advice by reading every 835 line, tying it back to claim data, and classifying CARCs and RARCs into clear work queues. An agent can compare allowed amounts to your contracted rates, detect when a payer underprices a specific H‑code or residential per‑diem, and flag those variances for review instead of letting them post as silent CO‑45 write‑offs.

Supabill's remittance and denials agent can ingest ERAs from all payers, normalize the adjustment codes, and feed them into denial and underpayment reporting that operators actually trust. Humans still own contract interpretation, escalation with payers, and judgment calls about when to appeal or write off, but the agent takes on the grunt work of reading every 835, so your team is not buried in raw remits and spreadsheets.

What is the difference between an ERA (835) and an EOB?

An ERA is the electronic remittance advice sent in the HIPAA 835 format from payer to provider. It is designed for systems to read and load into billing or practice management software. An explanation of benefits, or EOB, is the member‑facing document that explains how the plan processed a claim. Content often overlaps, but only the ERA reliably carries all the fields needed for posting, denial classification, and payment variance analysis. Source

Why do some payers still send paper remittance advice instead of ERAs?

Some payers, especially smaller regional plans or state programs, are slower to adopt full ERA capability, or they require separate enrollment for 835s. In other cases the provider or billing system has not completed ERA enrollment or connectivity through a clearinghouse. Until the enrollment and testing steps are finished, payers typically default to paper or portal‑only remits, which increases manual posting work and makes denial analytics much harder. Source

How should CARCs and RARCs from the 835 be used in denial management?

CARCs and RARCs on the ERA should be mapped into standardized denial categories in your billing or analytics system. For example, CO‑16 can feed an "information missing or invalid" queue, CO‑97 can feed a "billing / frequency / bundling" queue, and PR codes should guide patient balance follow‑up. Using the 835 as the single source of denial reasons avoids double‑counting and lets you measure denial rate by payer, location, and service line in a consistent way. Source

Can remittance advice be used as documentation for appeals in behavioral health?

Yes. The ERA is often the cleanest summary of the payer's rationale for reducing or denying a service, especially when paired with the contract and the authorization history. For behavioral health, pulling specific CARCs and RARCs from the 835, along with evidence that the allowed amount does not match contracted rates for the relevant H‑codes or levels of care, creates a focused appeal packet that is much stronger than a generic "please reconsider" letter.

How long should ERAs and paper remittance advice be kept for compliance and audit purposes?

Retention requirements vary by state law, payer contract, and program rules such as Medicare or Medicaid. Many organizations keep ERAs and related posting records for at least as long as clinical and financial records are required, so audits and payer disputes can be supported with original payment data. Check state regulations and major payer contracts for specific retention language before setting your policy. Source

• CMS — Electronic billing & EDI transactions
• X12 — Remittance Advice Remark Codes