Reading Remittance Details and Understanding Payment Decisions
An Explanation of Benefits (EOB) or Electronic Remittance Advice (ERA) tells a healthcare organization how a payer processed a claim. The document may show what was billed, what the payer allowed, what it paid, what was adjusted, and what may remain as patient responsibility. Reading those figures correctly is an important part of payment posting, account reconciliation, and follow-up.
The challenge is that a remittance is more than a payment amount. A single ERA may contain many claims, multiple service lines, reversals, informational messages, and adjustments affecting the provider's total payment. A line that appears unpaid does not automatically become a patient bill, and an ERA with claim payments totaling more than the bank deposit is not automatically incorrect.
The right reading moves between the payer's overall payment, the claim decisions, and the service-line details. Codes and amounts only become meaningful when they're reconciled to the actual account and to one another.
What a Remittance Tells You
An Explanation of Benefits (EOB) commonly refers to a readable explanation of how an insurer processed a claim. Patients may receive a member EOB, while providers receive remittance information in a payer portal, paper document, or another format. A member EOB isn't itself a bill and may not contain all of the operational details available on a provider remittance.
A Remittance Advice (RA) is the payer's explanation of its claim-payment decisions, including payments and adjustments. A Standard Paper Remittance (SPR) is the paper version used in Medicare workflows. An Electronic Remittance Advice (ERA) uses the standardized HIPAA X12 835 electronic transaction and can be imported into a billing or patient accounting system for electronic posting.
Electronic Funds Transfer (EFT) is the movement of money, often through the ACH network. It's separate from the ERA, which explains the payment. A remittance may also be associated with a paper check or another permitted payment arrangement. The organization must associate the remittance to the correct payment before balancing and posting.
The payer's terminology and display can vary. An integrated billing platform might label its ERA screen an EOB, even though the underlying data came from an 835. Readers should identify the underlying document and transaction rather than relying on a screen label alone.
Where Remittance Interpretation Fits in the Revenue Cycle
A remittance is produced after a payer has adjudicated a claim or made another reportable payment decision. The healthcare organization then needs to record the outcome accurately, connect the remittance with funds received, and direct unresolved balances or exceptions to the appropriate workflow.
The teams involved may include payment posting, cash applications, accounts receivable, denial management, patient financial services, refund specialists, revenue integrity, and treasury or accounting. Smaller organizations may combine these functions. Each team uses the same information for a different purpose.
- Payment posting records payer payments, adjustments, and properly supported patient responsibility.
- Cash or bank reconciliation verifies the deposit and its relationship to the corresponding remittance or remittances.
- Accounts receivable and denials investigate unpaid or reduced claims, coding issues, requests for information, and follow-up opportunities.
- Patient financial services validates remaining patient responsibility before statements or collections.
- Accounting and revenue integrity may analyze unapplied money, recoupments, unexplained adjustments, and repeated variance patterns.
An ERA can arrive before the associated deposit is visible or after funds have reached the bank. That timing difference is a matching problem to resolve, not permission to invent a deposit or force the remittance to balance. In the HIPAA EFT/ERA workflow, the trace number helps reassociate a payment with the appropriate ERA.
How to Read a Remittance from the Top Down
Before examining individual adjustments, establish which payer, payment, and claims are represented. A useful review proceeds through three levels: payment or provider, claim, then service line.
Payment and provider-level information
Look for the payer name, payee or billing provider identifiers, payment date, payment or check amount, payment method, trace/check reference, and any provider-level adjustments. In an 835, the BPR information describes payment, and the TRN segment supports reassociation. Provider-level adjustment information is reported in PLB segments.
Claim-level information
Identify the patient or account, payer claim control number when available, claim status, billed amount, claim payment, and claim-level adjustments. An 835 includes claim payment information in the CLP segment. Never assume an account number shown by a payer is identical to an internal encounter number without checking identifiers.
Service-line information
A claim may contain several CPT/HCPCS or revenue-code lines. Depending on the remittance, line details can include billed charges, paid amount, allowed amount when reported, service date, units, and adjustments. The payment on one line can't always be inferred by dividing the claim total evenly or by copying a value from an unrelated line.
A claim-level adjustment should not be posted again at the line level merely because the same amount appears in a system summary. Some screens redistribute or display claim information differently from the native 835. Use the underlying transaction and approved posting rules to avoid double-counting.
Understanding Charges, Allowed Amounts, Payments, and Adjustments
Billed charge is the amount submitted for the service. Allowed amount generally represents the amount recognized under the applicable payer methodology or contract, when that concept applies. Paid amount is what the payer reports paying on the claim or line. Patient responsibility is the portion the payer identifies as the patient's responsibility, subject to applicable contractual, coordination-of-benefits, legal, and account-validation requirements.
A simple clean example can help, but not every claim follows one formula. Secondary processing, capitation or other payment arrangements, interest, recoupments, reversals, and provider-level adjustments may require additional analysis.
Worked example: A single service line
Assume a fictional primary payer remittance reports the following for one service:
The line balances: $300.00 − $100.00 − $40.00 − $32.00 = $128.00. The implied allowed amount in this simplified example is $200.00, consisting of $128.00 payer payment and $72.00 reported patient responsibility.
That result isn't a universal authorization to bill $72.00. Check other coverage, prepayments, contractual limitations, account history, and applicable protections before transferring or billing a balance. For a secondary payer, the primary adjudication may already have allocated responsibility that the secondary payer subsequently changes.
Don't confuse adjustment with cash
A contractual adjustment generally reduces a receivable. A deductible or coinsurance amount can identify patient responsibility. Neither is the same as cash received. Posting a PR amount as payer payment, or converting CO to PR solely to make a batch balance, misstates the account and may create an improper patient balance.
Group Codes, CARCs, and RARCs
Most 835 payment adjustments are communicated through a Claim Adjustment Group Code (CAGC) and a Claim Adjustment Reason Code (CARC). A Remittance Advice Remark Code (RARC) may add explanatory information. The codes should be read together rather than interpreting the reason number alone. X12 maintains the CARC and RARC lists, and code validity can change over time.
Examples of commonly encountered adjustment combinations include PR-1 for deductible, PR-2 for coinsurance, PR-3 for copayment, and CO-45 for an applicable charge reduction. Not every CARC can be freely combined with every group code, and payer reporting can contain errors. Consult the current X12 definition, the accompanying remarks, and applicable contractual or program guidance.
A RARC may clarify why documentation was insufficient, provide a specific billing message, or convey informational processing guidance. Some RARCs are informational alerts rather than amounts. A remark code does not independently change the dollar amount of an adjustment.
An important secondary-payer example: OA-23
CARC 23 describes the impact of prior payer adjudication, including payments and/or adjustments. A secondary payer may report OA-23 as part of its coordination-of-benefits calculation. OA-23 should not automatically become patient responsibility, and it should not be added to a cash payment.
Suppose a fictional primary remittance reports $90 paid on a $150 allowed amount with $60 remaining in reported patient responsibility. The secondary payer subsequently pays $35. The analyst must review the secondary adjudication and remaining patient responsibility to determine whether anything is still owed, instead of assuming that the $60 from the primary remittance remains payable by the patient. If the secondary remittance reports OA-23, its amount may reflect prior adjudication information rather than a new amount the patient owes.
Coordination of benefits deserves its own detailed posting guide. Here, the core interpretive skill is to keep prior-payer information, current-payer payment, and actual patient liability distinct.
Reading the 835: Essential Data Elements
The X12 835 has a structured format that software converts into readable posting screens. Analysts do not necessarily need to read raw EDI every day, but understanding where the information originates makes unexpected screens easier to investigate.
The exact fields and situational rules are governed by the applicable 835 implementation guide. A billing system may simplify these elements, combine them in a display, or present separate views for reversals and corrections. When a visible summary conflicts with the electronic source, compare the native file and system import mapping through the approved support process.
A Complete Remittance Review and Posting Workflow
Step 1: Identify the correct remittance and payment
Confirm payer, payee, payment date, payment method, remittance identifier, and trace or check number. Review whether the file is an original, replacement, reversal, or another type of processing entry. Prevent the same ERA or deposit from being processed twice.
Step 2: Review payment-level totals
Find the payment amount reported in the ERA and compare it with the bank EFT or check. Note any provider-level adjustments or other differences requiring investigation. For a single associated deposit, the actual bank receipt is the hard cash target, not a sum chosen from a displayed screen to force a match.
Step 3: Match claims to patient accounts
Verify identifying information against the patient-account and encounter records. Resolve unknown claims, unmatched identifiers, duplicates, and prior postings before making new entries.
Step 4: Analyze the claim and service lines
Read the billed and paid amounts, status, adjustment groups, CARCs, RARCs, and allowed amounts when supplied. Separate contractual reductions, reported patient responsibility, denial-related balances, and amounts that require follow-up.
Step 5: Address exceptions without guessing
A zero-pay line may involve deductible, denial, bundling, previous payment, another payer, or processing information. Trace the actual reason and supporting records. A mismatched line display should be investigated rather than reallocated to PR or CO merely to make arithmetic work.
Step 6: Post only supported transactions
Follow authorized posting rules for payer payment, adjustments, patient responsibility, reversals, and recoveries. Don't treat an informational batch, a payment reversal, or a PLB adjustment as ordinary claim payment without reviewing its purpose.
Step 7: Balance and verify
Reconcile the remittance, payment, posting batch, and unresolved exceptions. Where claim payments and payment-level adjustments both occur, balance each level independently and establish how they roll up to the bank receipt.
Step 8: Document and route unresolved items
Record what was reviewed, the discrepancy, supporting documents, and who owns the next action. Escalate payer reporting errors, interface mapping problems, unexplained retractions, or suspected automation mispostings according to approved procedures.
Worked Example: Claim Payments Do Not Equal the EFT
Consider a fictional ERA that reports two claim payments and one provider-level recovery adjustment.
Here, $180.00 + $95.00 − $40.00 = $235.00. The remittance and EFT can both be correct, even though the total claim payments exceed the bank deposit by $40.00.
The posting team should validate the PLB reason and its related account or prior transaction where applicable. The $40 reduction must not simply be assigned as a new patient balance or subtracted arbitrarily from either of the two new claim payments. A provider-level recovery may require a separate recoupment workflow with its own audit history. A dedicated PLB, Recoupments & Retractions guide will explain those mechanics in depth.
Important sign convention: Internal reporting and software may display a recovery as a positive PLB adjustment, a negative amount, or a net payment reduction. The table uses a minus sign to illustrate its effect on this deposit, not to prescribe every system's PLB storage convention.
Common Interpretation Errors and How to Resolve Them
Scenario: A zero-dollar ERA isn't a missing deposit
A payer sends a remittance for a fully denied claim with $0.00 payment and detailed adjustments. It may provide necessary posting and follow-up information even though there's no EFT to match. The correct workflow is to interpret the adjudication and route the appropriate account activity, not to manufacture a payment or disregard the file solely because its cash total is zero.
Scenario: A reversal followed by reprocessing
A payer reverses a previous $120 payment, then processes a corrected claim for $110. Depending on how the payer transmits the transactions and funds, the remittance may contain reversal and new-payment activity together or across separate remittances. Review the original posted claim, reversal records, claim control references, and actual EFT impact before updating the account. Reposting only the $110 while ignoring an existing $120 payment can overstate cash or leave a false credit.
Scenario: A recurring automation discrepancy
A posting interface begins placing informational-only amounts into cash posting batches. The difference may appear repeatedly but only for one batch type. Rather than correcting every patient account with a manual write-off, an analyst can collect redacted transaction identifiers, compare source ERA records with the posting output, document the exact transformation, and escalate it to the interface owner. Changes to automation logic and historical corrections need controlled authorization and testing.
Operational Controls and Downstream Impact
Correct remittance interpretation affects account balances, denial workqueues, patient statements, refund identification, underpayment reviews, cash reconciliation, and financial reporting. One incorrectly categorized adjustment can move from a posting batch into a patient bill or conceal a payer balance that should be investigated.
Reliable controls can include unique ERA identifiers, trace-number matching, duplicate-file checks, line- and claim-level balancing, separate PLB review, account-level audit trails, and exception reports. A report showing a recurring variance is a starting point; analysts still need evidence to establish whether the problem originates in payer adjudication, the import mapping, posting automation, or the organization's own workflow.
Payment posting staff should understand enough about secondary billing, payer contracts, refunds, and denials to recognize where a transaction belongs. Deep training in every one of those specialties is not necessary for this guide, but the distinction between recognizing an issue and having authority to change the account or system remains essential.
Practical EOB and ERA Interpretation Checklist
Before considering a remittance fully reviewed, confirm the applicable points:
- ☐Identify the payer, payee, payment date, method, and trace/check information.
- ☐Confirm whether the transaction is original, corrected, reversed, or informational.
- ☐Match the remittance to the correct EFT or check where money was issued.
- ☐Compare the payment-level total with claim payments and any PLB activity.
- ☐Match claims and service lines to the correct accounts without duplicate postings.
- ☐Read adjustment group codes and reason codes together; inspect RARCs as needed.
- ☐Separate payer cash, contractual adjustments, patient responsibility, and other adjustments.
- ☐Review secondary adjudication before transferring remaining balances to the patient.
- ☐Investigate zero-pay claims, unexpected reversals, and line-summary discrepancies.
- ☐Apply only supported, authorized corrections and document unresolved items.
- ☐Verify batch balancing, deposit reconciliation, and exception ownership.
A remittance is a record of payer decisions, not a shortcut around account validation. The practical skill is to determine which amounts belong to cash, which amounts change receivables, and which entries require additional review before anyone changes a balance.
References and Further Learning
These resources support the technical concepts described in this guide. Requirements and implementation details vary by payer and program; verify current guidance before operational use.
References
Additional Learning
Educational Disclaimer
Revenue Cycle Uncovered is an independent educational resource. Content is provided for general informational purposes and does not represent the policies, practices, or positions of any employer or organization. Workflows, payer requirements, regulations, and operational practices may vary. Information should be independently verified when applied to specific situations.
Continue Exploring Revenue Cycle Uncovered
Return to this category or explore the complete educational library.