What Is a Remittance Advice (ERA/EOB) and How Should RCM Teams Use It

Every claim your practice submits eventually comes back with an answer. That answer arrives in the form of a remittance advice — and how well your revenue cycle management (RCM) team reads, interprets, and acts on it determines how much money you actually collect.

Yet remittance advice is one of the most underutilized documents in healthcare billing. Many teams treat it as a receipt rather than a roadmap. That's a costly mistake.

This guide breaks down what remittance advice is, the difference between ERAs and EOBs, how to decode the key fields, and — most importantly — how RCM teams can use it to drive faster collections, fewer denials, and smarter workflows.

What Is Remittance Advice?

Remittance advice is the explanation a payer sends after processing a claim. It tells you what was paid, what was denied, what was adjusted, and why. Think of it as the payer's accounting of your claim — line by line, code by code.

Remittance advice comes in two forms:

• ERA (Electronic Remittance Advice): The electronic version, delivered in the HIPAA-standard 835 transaction file format directly to your practice management or billing system.
• EOB (Explanation of Benefits): The paper or PDF version, typically mailed to the provider and sometimes the patient. EOBs contain the same core information as ERAs but in a human-readable format rather than a machine-readable file.

In modern RCM, ERAs are the norm. Most commercial payers and Medicare/Medicaid transmit ERAs automatically when you enroll. But EOBs still surface — especially from smaller payers, in disputes, or when a patient brings one in and asks why their balance looks different from what the insurer says.

‍

Anatomy of a Remittance Advice: Key Fields to Know

Whether you're looking at an ERA translated by your billing system or a paper EOB, the same core data points appear. Here's what each one means and why it matters.

Claim-Level Information

Claim Status Code The payer's summary disposition of the claim: paid, denied, adjusted, or pended. If you're triaging a remittance, this is where you start.

Check/EFT Number and Date Identifies the specific payment transaction. Essential for matching payments to deposits and reconciling your bank account.

Payer Claim Control Number (ICN/DCN) The payer's internal identifier for the claim. Always include this number when calling a payer about a specific claim — it's their primary lookup key.

Patient Control Number Your internal claim or account number. How the ERA links back to the right patient account in your system.

Service Line Information

Date of Service The specific date(s) the procedure was performed. Mismatches between what you submitted and what the payer shows here are a common source of denial.

Procedure Code (CPT/HCPCS) The billed service. Verify this matches what was submitted — occasionally payers recode claims on their end, which can affect your reimbursement.

Billed Amount What your practice charged. The starting point for all subsequent calculations.

Allowed Amount What the payer has determined is the maximum payable amount under the contract. This is determined by your fee schedule or network agreement — not what you billed.

Contractual Adjustment (CO-45) The difference between your billed amount and the allowed amount. This is the write-off your practice is contractually obligated to take as a network provider. It's not a denial.

Paid Amount What the payer is actually sending you. This equals the allowed amount minus the patient responsibility (deductible, copay, coinsurance).

Patient Responsibility The portion owed by the patient — deductible, copay, or coinsurance as determined by their benefit plan. This is what should flow to a patient statement.

Adjustment Reason Codes and Remark Codes: The Real Story

Here's where most of the diagnostic value lives — and where many teams stop reading carefully.

Claim Adjustment Reason Codes (CARCs)

CARCs explain why a claim or line item was adjusted. They're standardized across payers (maintained by X12), so CO-45 means the same thing regardless of whether it's UnitedHealthcare or a regional Blues plan.

Common CARCs every RCM team should know:

CO-4: Service requires prior authorization

Appeal if auth was obtained; prevent with pre-auth verification

‍

CO-11: Diagnosis inconsistent with procedure

Correct and resubmit or appeal with clinical documentation

‍

CO-16: Claim lacks information for adjudication

Find missing data; resubmit

‍

CO-22: Coordination of Benefits — other payer responsible

Bill primary payer first

‍

CO-45: Charges exceed fee schedule

Write off; no action needed

‍

CO-97: Benefit included in allowance for another service

May indicate bundling issue

‍

PR-1: Deductible

Bill patient

‍

PR-2: Coinsurance

Bill patient

‍

PR-3: Copay

Bill patient

‍

CARCs starting with CO (Contractual Obligation) are write-offs. CARCs starting with PR (Patient Responsibility) go to the patient. CARCs starting with OA (Other Adjustment) require investigation.

‍

Remittance Advice Remark Codes (RARCs)

RARCs provide additional explanation beyond the CARC — often the specific policy reason for a denial or adjustment. A claim might come back with CO-16 (missing information) + N290 (missing authorization number). The CARC tells you the category; the RARC tells you exactly what to fix.

Key RARCs to know:

• MA01 — Appeals rights attached; this claim is eligible for appeal
• MA04 — Secondary payment cannot be considered without remittance from primary payer
• N30 — Patient cannot be identified as our insured
• N115 — This decision is based on a Local Coverage Determination (LCD)
• N290 — Missing prior authorization number

When a denial arrives, read the CARC and RARC together before deciding on next steps. The pair almost always tells you what to do.

‍

How RCM Teams Should Work Remittance Advice

Processing remittance advice isn't just about posting payments. Done well, it's a systematic workflow that drives collections, surfaces denial trends, and prevents future revenue leakage.

1. Automate ERA Enrollment Wherever Possible

Manual EOB posting is slow and error-prone. If you haven't enrolled for ERAs with every payer where it's available, do it now. Most clearinghouses make enrollment straightforward, and auto-posting reduces the time between claim adjudication and a clean AR balance.

Where to start: Medicare, Medicaid, and major commercial payers (UHC, Aetna, BCBS, Cigna) all support ERAs. Smaller or regional payers may require direct enrollment or still rely on paper.

2. Don't Auto-Post Everything Blindly

Auto-posting is efficient — but it should never be set-and-forget. Configure your system to flag exceptions: claims where the paid amount is significantly below expected, where a new CARC code appears, or where the patient responsibility calculation seems off.

A common trap: auto-posting a CO-45 write-off on a claim that was actually underpaid due to a fee schedule error. Without a secondary review workflow, that difference disappears quietly.

3. Work Denials the Day They Post

Timely filing limits don't just apply to initial claims — appeal deadlines are often 30 to 180 days from the remittance date. A denial worked the day it posts has far better recovery odds than one that sits for 60 days.

Triage by CARC on the day remittance posts:

• Clinical/documentation denials → to coding or clinical staff
• Authorization denials → to auth/prior auth team with appeal queue
• Eligibility/COB denials → to eligibility verification team
• Contractual adjustments (CO-45) → write off and close

4. Track Denial Patterns, Not Just Individual Denials

Every denial is a data point. Over time, patterns tell you something is broken upstream — in scheduling, eligibility verification, coding, or authorization workflows.

Build a simple denial tracking log (even a spreadsheet works to start) that captures: payer, CARC, RARC, procedure code, denial date, and resolution. Review it monthly. You'll quickly see whether your CO-4 (auth) denials are concentrated with one payer, or whether your CO-11 (diagnosis/procedure mismatch) denials cluster around a specific CPT code or provider.

5. Reconcile Payments Against Deposits Daily

The ERA posts a payment. The bank receives a deposit. These two events must match — and they often don't perfectly, especially if multiple ERAs are bundled into a single EFT.

Daily reconciliation catches underpayments, misapplied credits, and system posting errors before they compound. Many billing systems have a payment reconciliation module; use it, and investigate any variance before month close.

6. Use Remittance Data to Renegotiate Contracts

Allowed amounts on remittance are the ground truth of what payers are actually paying you — not what your contract says they should pay. If you're systematically seeing allowed amounts below your contracted rates, you have a documentation problem (the payer may be applying the wrong fee schedule) or a contract enforcement issue.

Pull allowed amounts by payer and CPT code quarterly. Compare to your contracted rates. Discrepancies are worth a call to your payer rep — and they're leverage at renewal time.

‍

Common Remittance Advice Mistakes RCM Teams Make

Writing off CO-22 denials without billing primary first. CO-22 means COB — another payer is primary. This is not a final denial; it's a redirect. Bill the correct primary payer.

Ignoring MA01 remarks. MA01 means the denial is eligible for appeal. Many teams see a denial and move on without noting they have appeal rights explicitly granted. Every MA01 denial should enter an appeal workflow.

Treating all write-offs the same. CO-45 (contractual) is appropriate to write off. CO-97 (bundling) may be appropriate to write off or may indicate a coding issue worth reviewing. OA codes almost always require investigation. Not all adjustments are equal.

Misrouting patient responsibility. PR codes mean the patient owes the money — not that the claim was denied. Incorrect routing of PR balances as write-offs is a direct revenue leak.

Failing to capture secondary payer information. When primary remittance posts, it often contains the COB data needed to bill the secondary. If your team doesn't capture and forward that information immediately, secondary billing gets delayed — or missed entirely.

‍

Putting It Together: A Remittance Workflow Built for Performance

A high-performing RCM remittance workflow looks something like this:

1. ERA arrives via clearinghouse → auto-posts to practice management system
2. Exception queue flags non-standard CARCs, underpayments, and pended claims
3. Denials route to appropriate work queues by denial type, same day
4. Patient responsibility flows to statement or patient portal immediately
5. COB claims trigger secondary billing within 24–48 hours
6. Reconciliation runs daily against bank deposits
7. Denial trend report reviewed weekly or monthly by billing leadership
8. Contract performance analyzed quarterly using allowed amount data

The teams that do this well don't just process remittance faster — they use it as a feedback loop that makes every part of the revenue cycle smarter over time.

‍

The Bottom Line

Remittance advice is the most data-rich document in the revenue cycle. It tells you not just what you were paid, but why — and implicitly, what to do next. RCM teams that treat ERAs and EOBs as simple payment confirmations leave money on the table. Teams that read the codes, work the denials, and mine the patterns close the loop on revenue that would otherwise slip through.

If your team is spending time chasing payers for information that's already sitting in your remittance data, that's worth fixing — and the fix starts with knowing how to read what payers are already sending you.

‍

SuperDial helps RCM teams eliminate hours of manual payer calls by automating the most time-consuming parts of revenue cycle follow-up. Learn how we can help your team work smarter on what the remittance tells you needs attention.

‍