Skip to content

The Full Platform

Purpose-built for reimbursement intelligence

RemitIntel, RCx, HCC, and ClaimStaker — each solving a distinct piece of the revenue cycle puzzle.

Explore Prism
AdobeStock_480718916

 

AdobeStock_489535207Featured Case Study

$475.5K est. annual labor savings

2,500-provider group sees 16% denial reduction

RemitIntel connects 17.5K denials to actionable signals across 1.3M charges.

 

 

AdobeStock_589628042

Our Vision

The right care gets paid the right way, the first time

130K+ providers trust Aptarro to turn reimbursement complexity into a competitive advantage.

About Aptarro

Tool

Aptarro ROI Calculator

Model your revenue impact by product in under 5 minutes. No sales call required.

Open the calculator
Blog

What Is an 835 Remittance Advice?

What Is an 835 File in Healthcare? How to Read Your ERA
16:23

A claim can balance and still deserve a second look: one service paid; another was bundled; a contractual adjustment reduced the balance. The accounting is complete, but someone still needs to decide whether the payer got it right.

An 835 remittance advice is the electronic record of how a payer processed your claims: what it paid, adjusted or denied. Most of the attention goes to posting those results, yet 835 files in healthcare also hold evidence of reimbursement problems that can repeat long after the first balance is resolved.

That creates a practical gap. Your team can reconcile the deposit, close the account and send the next claim through with the same condition that caused the last denial. Reading the 835 details helps you account for the payment but reading it alongside the submitted claim and payer policy helps you decide what needs to change.

Key takeaways

  • The 837 submits the claim; the 835 reports adjudication and payment. One 835 can cover multiple claims.
  • An adjustment is not automatically a denied service: contractual reductions, coinsurance and bundled services require different responses.
  • Claim payments and the bank deposit may differ because provider-level adjustments can offset or increase the payment.

What is an 835 file in healthcare?

An 835 is the ASC X12 Health Care Claim Payment/Advice transaction, the standardized electronic format used to communicate a payer’s claim adjudication and payment information to a provider. Its purpose in medical billing is to support accurate payment posting, reconciliation and follow-up on unpaid or adjusted amounts.

CMS identifies X12 version 5010 as the adopted national electronic remittance advice standard. The applicable implementation guide is 005010X221A1.

The file can carry payment information, claim status, service-line payments and explanations for adjustments. It does not move money by itself. An electronic funds transfer, or EFT, handles the transfer. The associated trace information helps match that payment to its remittance, a process CMS calls reassociation. An 835 can also report adjudication without a positive payment.

835 vs. ERA vs. EOB

Electronic remittance advice, or ERA, describes the provider-facing payment explanation. The 835 is its standardized electronic format. An explanation of benefits, or EOB, is generally the member-facing explanation of how insurance processed a claim. It is not simply a printed 835, and an EOB is not a bill.

Term

What it is

Who uses it

835

The structured electronic transaction containing remittance data

Billing systems, clearinghouses and authorized revenue cycle teams

ERA

The electronic explanation of claim adjudication and payment

Providers and billing teams

EOB

The health plan’s explanation of benefits applied to a member’s claim

Patients or plan members

 

In medical billing, ERA and 835 are often used interchangeably. Your practice management system may display the file as a readable report rather than raw EDI. CMS also provides software to view and print Medicare 835 information.

835 vs. 837: What you billed and what the payer decided

The 837 is the claim submitted for payment, while the 835 reports the payer’s adjudication and payment response. The 837 describes the services billed; the 835 explains the financial outcome. Professional claims use the 837P transaction and institutional claims use 837I, as reflected in CMS’s transaction standards.

They do not map neatly by submission batch. One remittance can include claims submitted on different dates, while claims from one batch may be adjudicated on different payment cycles. Reconciliation needs claim identifiers and payment references, not an assumption that the next remit corresponds to the last batch.

An 835 also does not replace a claim acknowledgment. A file or claim rejected before adjudication may require action through acknowledgment reports rather than waiting for a payment response.

Inside an 835 file: The details behind the total

You do not need to read raw EDI to understand an ERA. Knowing the segment names helps when the billing system, clearinghouse and payer use different labels for the same information. The 835 implementation guide organizes claim information in Loop 2100 and service-line information in Loop 2110.

Segment

What it contains

Why it matters

BPR

Payment amount, payment method and payment date information

Establishes the transaction’s payment context

TRN

Reassociation trace information

Helps connect the remit with the corresponding payment

N1

Payer and payee identification

Confirms which organizations the transaction concerns

CLP

Claim identifier, processing status, charges, payment and patient responsibility

Shows the claim-level financial result

SVC

Procedure or service information and line-level charges and payment

Identifies which service was paid differently

CAS

Adjustment group, reason code and amount at claim or service level

Explains the adjustment and responsibility classification

LQ

Service-level remark codes when applicable

Supplies additional context for a line’s outcome

MOA / MIA

Outpatient or inpatient adjudication information, including applicable claim-level remarks

Adds claim-level detail beyond payment totals

PLB

Provider-level adjustment references, reasons and amounts

Explains offsets or additions outside the current claim totals

 

CAS carries the adjustment group code, Claim Adjustment Reason Codes, and adjusted amount. Remittance Advice Remark Codes, or RARCs, add detail at the claim or service-line level. Read them together. See the full guide to CARC and RARC codes for interpretation beyond the file structure.

Pay particular attention to PLB. A recoupment of an earlier overpayment can reduce today’s deposit even when today’s claims paid as expected. Searching current claim lines for the difference will not resolve that offset.

How to read an 835 remittance advice

Start with the transaction, move to the claim and then inspect the service lines. Finishing at the claim total can hide a zero-paid line inside an otherwise paid claim.

A paid claim with an unpaid service

The following amounts are fictional and illustrate remittance interpretation.

Item

Service A

Service B

Claim total

Billed charge

$200

$50

$250

Contractual adjustment CO-45

$50

—

$50

Coinsurance PR-2

$30

—

$30

Bundled-service adjustment CO-97

—

$50

$50

Payer payment

$120

$0

$120

 

For Service A, assume an allowed amount of $150: $200 billed less the $50 contractual adjustment. The $150 consists of $120 paid by the payer and $30 assigned to coinsurance. Service B received no separate payment because the payer reported it as included in another service’s allowance.

The claim balances: $120 payment + $30 patient responsibility + $100 in provider-side adjustments = $250 billed. That arithmetic accounts for the money. It does not establish that the payer’s adjudication was correct.

1. Confirm the payment and trace information

Check the payer, payee, payment amount and date. Match the remittance’s trace information to the associated EFT information.

2. Find the claim and check its status

Locate the claim identifier in CLP and compare it with the billing record. Check processing status, billed charges, payer payment and patient responsibility. In this example, the claim has a payment even though one service received none; the claim-level result is not the full story.

3. Review each service line

Use SVC detail to identify Service A’s $120 payment and Service B’s $0 payment. Compare the adjudicated service with what was submitted. Where an allowed amount is reported or derived, reconcile it with the applicable adjustments rather than treating billed charges as expected reimbursement.

4. Read the adjustments and remarks

X12’s CARC definitions distinguish reason 45 for charges above the applicable allowance, reason 2 for coinsurance and reason 97 for a benefit included in another service’s payment. The group code classifies responsibility; the reason and remarks explain the adjustment.

CO-45 in this example is the portion of the charge above the applicable allowance or contractual amount. PR-2 is coinsurance, subject to applicable benefit and billing requirements. CO-97 indicates that the payer considered the service included in the payment of allowance for another adjudicated service. That warrants review of the code combination, documentation and payer policy, not an automatic appeal or modifier change.

5. Check provider-level adjustments

Suppose this is the only claim on the remittance and a $30 recovery of an earlier overpayment reduces the payment. The claim still reports $120 paid, but the net payment is $90. Reconcile the PLB entry and its reference to the earlier balance rather than changing Service A’s payment to force a match.

CMS’s remittance guidance identifies prior-overpayment deductions and interest additions as examples of provider-level adjustments. Preserve that distinction in the ledger and in follow-up work.

How 835 data moves through the revenue cycle

A typical path runs from the payer through a clearinghouse or other authorized connection into the practice management or billing system. The system matches claims, posts payments and adjustments, then routes exceptions for review. Bank reconciliation separately confirms that the associated funds arrived.

At each handoff, identifiers need to remain intact. A billing company may receive remittances for many client entities; the right payment posted to the wrong account is still a posting error. A health system may need to reconcile across facilities and billing platforms before the enterprise total makes sense.

ERA and EFT enrollment also deserve separate attention. Receiving funds electronically does not prove that the remittance reaches the correct system or that the team retains access to the underlying 835.

Successful auto-posting may complete an accounting task, but the same data can still contain a recurring reimbursement problem that no individual exception queue is designed to investigate.

Why most remittance data goes unused

Each remittance advice records how a payer processed the claims it covers: what paid, what was adjusted and what was denied. But most teams encounter that information one account at a time, with a balance to resolve and another claim waiting.

The broader review often happens in a spreadsheet. Someone exports denial data, groups the results and prepares a monthly report. By the time a recurring condition becomes visible, weeks of additional claims may have passed through the same workflow.

Volume creates another limitation. One revenue cycle team may see too few comparable claims to distinguish an isolated adjustment from an emerging payer pattern. The evidence accumulates slowly., and the financial exposure can accumulate with it.

That leaves much of the value of 835 files in healthcare untapped. The payment gets posted and the exception gets assigned, while the lesson that could prevent another denial stays buried in the remittance or work queue. Revenue cycle intelligence puts those connections to work before another claim repeats the problem.

Turning 835 data into denial prevention 

Suppose the same service starts receiving CO-97 adjustments from one payer across several locations. Adding a modifier across the board would be a premature response. The team needs to establish which code combinations are affected, whether the services were distinct and what the payer's policy supports.

That investigation should lead to a specific decision: correct the claim when the documentation supports it, challenge the payer's determination or change the review logic for future claims. A denial count cannot make that decision for you.

RemitIntel, the remittance learning layer within Aptarro's Prism platform, connects submitted claims and payment outcomes with policy signals and broader network learnings to develop evidence-backed recommendations. Your team can examine the supporting evidence and approve, monitor or reject the recommendation.

When you approve a change, Aptarro implements the logic in the appropriate workflow. That can mean identifying the condition during pre-claim charge review through RCx or claim scrubbing through ClaimStaker. Your coding specialists retain the judgment; the workflow carries the approved logic forward.

For a 2,500-provider behavioral health network, that review connected approximately 17,500 denials to actionable signals across 1.3 million charges, replacing monthly spreadsheet review and rework for $475,500 in estimated annual labor savings.

For a billing company, a recurring condition may affect several authorized client accounts. For a health system, it may span facilities using different billing platforms. The response still needs to reflect the payer, service and organization involved. Intelligence earns its place when it makes that decision more specific.

835 remittance advice FAQ

What does 835 mean in healthcare?

835 identifies the X12 Health Care Claim Payment/Advice transaction. It is the electronic remittance format that reports claim adjudication, payment and adjustment information. The number identifies a transaction type, not a claim status. A single 835 can explain several claims and may report outcomes without a positive payment.

Is an 835 the same as an EOB?

No. An 835 is a structured electronic transaction used for provider remittance processing. An EOB generally explains a health plan’s handling of a claim to the member. They may describe related financial outcomes, but their audiences and formats differ. A printed provider remittance is not automatically a patient EOB.

How do I get 835 files from a payer?

Enroll for electronic remittance advice with the payer, commonly through your clearinghouse or billing-system connection. Confirm the receiving entity, identifiers and delivery route, then verify that files arrive and reconcile correctly. EFT enrollment may be separate. Ask whether your system provides access to the original 835 as well as its readable report.

How long does it take to receive an 835 after payment?

The 835 may arrive before or after the corresponding EFT. CAQH CORE operating rules coordinate the timing of the ERA and EFT and generally require the transactions to be delivered close enough together to support reassociation. Actual availability in your billing system can depend on the payer, clearinghouse, bank and system processing

Can an 835 include payments for multiple claims?

Yes. One 835 can contain adjudication information for multiple claims and service lines. The associated payment must also account for applicable provider-level adjustments. Reconcile the transaction using its payment and trace information, then retain claim-level and service-level detail for posting, follow-up and analysis across payment cycles.

Give the next claim the benefit of what the network learned

Once your team has identified why a service keeps receiving no separate payment, that finding should reach charge review while it can still change a submission. RemitIntel helps turn 835s and submitted claims into recommendations your team can evaluate and approve.

See RemitIntel in action

Keep reading

Related articles

See how Aptarro catches errors before they cost you.

Book a live demo and watch Aptarro review and correct real claims in your specialty.

Book a demo

Avg. 2–4 weeks to first claims processed · No long-term contracts required