How to Read an X12 835 ERA: Claim Payments, Adjustments & Denials

An X12 835 Electronic Remittance Advice (ERA) communicates how a healthcare payer processed medical claims, including payments, financial adjustments, patient responsibility and other adjudication information. Understanding this transaction is essential for medical billers, healthcare providers and EDI professionals responsible for payment posting, reconciliation and denial management.

Although individual Claim Adjustment Reason Codes (CARCs) and Remittance Advice Remark Codes (RARCs) can provide valuable information, they represent only part of the remittance. The payer's processing decision must be interpreted in the context of the applicable claim status, submitted charges, payment amounts, financial adjustments, service-line information and other relevant details.

In this guide, we'll explain the major components of the X12 835 version 5010 transaction, show how important segments work together, and walk through a practical example of reading and balancing an electronic remittance advice.

What Is an X12 835 Electronic Remittance Advice?

The X12 835 Health Care Claim Payment/Advice transaction is the standardized electronic format used to communicate healthcare claim payment and adjudication information.

After processing a claim, a payer may generate an ERA containing information about paid claims, partially paid claims, zero-payment claims, financial adjustments and other remittance-processing details.

An 835 can report information about multiple claims within the same transaction. It may also include financial information necessary to reconcile the remittance with a corresponding payment, such as an Electronic Funds Transfer (EFT).

For medical billing operations, an ERA supports electronic payment posting, account reconciliation and investigation of claim adjustments or denials. For EDI developers, it provides structured data that can be translated into billing application records while preserving the payer's original adjudication information.

Although ERAs are used across Medicare, Medicaid and commercial insurance programs, payers may apply different coverage policies, contracts and processing rules. The standardized transaction communicates the results of adjudication but does not establish universal resolution procedures for every claim issue.

Understanding the Structure of an X12 835

The X12 835 organizes remittance information into segments and loops. Each segment contains related data elements separated by delimiters, while loops organize information into logical groups such as payment details, claims and services.

The following table summarizes the major areas that medical billers and EDI professionals commonly review.

Not every segment appears in every remittance. Certain segments are conditional or situational, depending on the information being reported and the X12 implementation guide requirements.

Understanding where information is reported is important because a claim-level adjustment and a service-level adjustment may describe different aspects of the payer's adjudication.

Step 1: Review Payment Information in BPR and TRN

At the transaction level, the BPR and TRN segments provide important payment and reassociation information.

BPR — Financial Information

The BPR segment communicates financial information, including the payment amount and applicable payment method. The amount reported in BPR02 represents the total payment amount for the entire X12 835 transaction. Because an 835 may contain payment information for multiple claims, this amount reflects the overall transaction payment rather than the payment associated with any single claim.

TRN — Reassociation Trace Number

The TRN segment provides a trace number that can be used to help associate the electronic remittance with the corresponding payment information.

This is particularly important when an organization receives its ERA and EFT through different channels or at different times.

For billing teams, reviewing payment information helps establish what the payer transmitted before examining how individual claims contributed to the remittance total.

Step 2: Identify the Claim and Review the CLP Segment

The CLP (Claim Payment Information) segment is located in Loop 2100 and provides important claim-level adjudication details.

The following elements are especially useful when interpreting a claim:

The patient control number and payer claim control number can be useful when researching a claim, but they serve different identification purposes. They should not automatically be treated as interchangeable.

An Important Distinction: Processed Does Not Always Mean Paid

The claim status reported in CLP02 should be interpreted carefully.

For example, a status of 1 indicates that a claim was processed as primary. It does not necessarily mean that the payer issued a positive payment amount.

A claim may be processed as primary with a payment amount of $0, depending on the payer's adjudication. The associated adjustments and remarks help explain why no payment was made.

Additionally, CLP02 status 4 (Denied) has a specific usage requirement in the X12 835 version 5010 implementation guide. This status applies when the patient or subscriber is not recognized and the claim was not forwarded to another payer. It should not be interpreted as a universal status for every denied or zero-payment claim.

Important: A claim receiving no payer payment does not automatically have a CLP02 status of 4. Medical billers should review the reported claim status, payment amount, applicable CARCs and RARCs, and other relevant adjudication information together to understand how the payer processed the claim.

Step 3: Review Service Payment Information in the SVC Segment

The SVC (Service Payment Information) segment appears in Loop 2110 and reports payment information for an individual service line.

Service-level information is especially useful when a claim contains multiple procedures or services that were processed differently.

Important SVC elements include:

The SVC segment identifies what was charged and what the payer paid for the service. If the payer reduced or adjusted the amount, applicable service-level CAS segments explain the financial differences.

For professional claims and other situations requiring service-line adjudication detail, the original service information and adjustment amounts may be essential for accurate payment posting.

Step 4: Understand Financial Adjustments in the CAS Segment

The CAS (Claim Adjustment) segment reports financial adjustments using standardized Claim Adjustment Group Codes and Claim Adjustment Reason Codes (CARCs).

In the X12 835 version 5010 transaction, CAS may appear in Loop 2100 for claim-level adjustments or Loop 2110 for service-line adjustments.

The following table illustrates how a CAS segment reports adjustment group codes, CARCs, associated amounts and optional quantities across multiple adjustment positions:

A single CAS segment can report up to six CARCs, each with its own associated adjustment amount and optional quantity. All adjustments within the same CAS segment share the adjustment group code reported in CAS01. Multiple CAS segments may be reported when additional adjustments or different adjustment groups are applicable.

Common adjustment group codes include:

• CO: Contractual Obligation.
• PR: Patient Responsibility.
• OA: Other Adjustment.
• PI: Payer Initiated Reduction.

These groups help identify how the adjustment is categorized, while the CARC provides its specific standardized reason.

However, a reported PR adjustment should not automatically be interpreted as an amount already collected from the patient or as permission to bill the patient without considering applicable legal, contractual and payer limitations.

Step 5: Review RARCs and Other Adjudication Information

Remittance Advice Remark Codes (RARCs) provide additional information about claim adjustments or communicate informational notices related to remittance processing.

RARCs may be reported at the claim level through MIA or MOA in Loop 2100, or at the service level through LQ in Loop 2110.

A supplemental RARC may provide additional context about an adjustment reported in CAS, while an informational RARC, also known as an Alert, may communicate information unrelated to a particular financial adjustment.

For example, a remark about other insurance processing or an applicable coverage policy may be relevant to understanding the payer's decision, but it does not independently establish the entire payment outcome.

Medical billers should evaluate applicable CARCs, RARCs and other adjudication details together rather than assuming a remark code identifies the complete reason for a claim's payment status.

Example: Reading a Claim With Multiple Service-Line Adjustments

Consider a professional medical claim containing two services with combined submitted charges of $350.

During adjudication, the payer determines the applicable allowed amounts, reports contractual adjustments, applies deductible and coinsurance amounts, and pays the remaining covered amounts.

For this illustrative example, the adjudication results are:

The first service includes a $40 contractual adjustment and $20 deductible. The second includes a $30 contractual adjustment and $20 coinsurance. The payer pays a combined $240.

Illustrative X12 835 Claim and Service Information

Illustrative educational excerpt using fictional claim information. This is not a complete X12 835 interchange. The example does not imply that all payers would adjudicate these services using the same allowances, codes or payment arrangements.

Understanding the CLP Segment

The first segment communicates the overall claim processing information:

The CLP segment identifies the claim as processed primary and reports the submitted charges, payer payment and patient responsibility. However, it does not independently explain how the payer arrived at each financial amount.

To understand the financial adjustments, the reader must review the applicable CAS segments associated with the individual service lines.

Understanding Service 1

The first service reports:

• SVC02 = $150 submitted charge.
• SVC03 = $90 payer payment.
• CAS*CO*45*40~ = $40 contractual adjustment.
• CAS*PR*1*20~ = $20 deductible adjustment.

The $40 contractual adjustment reduces the amount considered payable under the illustrative fee arrangement from $150 to $110. The $20 deductible is then applied to that allowed amount, leaving a $90 payer payment.

Understanding Service 2

The second service reports:

• SVC02 = $200 submitted charge.
• SVC03 = $150 payer payment.
• CAS*CO*45*30~ = $30 contractual adjustment.
• CAS*PR*2*20~ = $20 coinsurance adjustment.

The $30 contractual adjustment reduces the illustrative allowed amount to $170. The payer applies $20 coinsurance, resulting in a $150 payer payment.

Although both services have contractual adjustments, they also have different types of patient responsibility. This is one reason service-level information is important when posting payments and determining the appropriate patient account balance.

How to Balance the X12 835 Service and Claim Amounts

Financial balancing is an important part of validating and interpreting electronic remittance information.

For a typical service line, the submitted service charge minus the applicable monetary adjustment amounts should equal the reported service payment amount.

Service 1 Balancing

Submitted charge: $150

Adjustments: $40 contractual adjustment + $20 deductible

Payer payment: $90

$150 - $40 - $20 = $90

Service 2 Balancing

Submitted charge: $200

Adjustments: $30 contractual adjustment + $20 coinsurance

Payer payment: $150

$200 - $30 - $20 = $150

Claim-Level Balancing

For this example, both service-line charges and their adjustments contribute to the overall claim totals:

$350 - $70 - $40 = $240

The calculated payment matches CLP04, confirming that the illustrative claim balances using the applicable reported adjustment amounts.

The patient responsibility amount reported in CLP05 is $40, which also matches the combined PR adjustments of $20 deductible and $20 coinsurance in this example.

Important: The claim payment amount is not necessarily the same as the overall transaction payment amount. An 835 can contain multiple claims and provider-level adjustments, which must be considered separately when reconciling the payment reported in BPR02.

How to Identify Denials and Zero-Payment Claims in an 835

A claim or service receiving no payer payment may require further review, but a zero-payment amount does not independently explain the adjudication outcome.

For example, a zero-payment service may involve a reported denial, a contractual or benefit-related adjustment, patient cost sharing, prior payment considerations or other payer-specific circumstances.

When investigating a potential denial, medical billers should review:

• The claim processing status in CLP02.
• The claim payment amount in CLP04.
• The applicable service payment amounts in SVC03.
• The adjustment groups, CARCs and financial amounts reported in CAS.
• Any supplemental or informational RARCs reported through the appropriate segments.
• The original claim information and relevant payer coverage or processing requirements.

This distinction is especially important for billing systems that attempt to classify claims as denied based only on a $0 payment amount or a single adjustment code.

A claim may have been processed successfully under the payer's rules even when it produces no payment. Conversely, one service on a partially paid claim may have been denied or adjusted for a reason that differs from the other services.

Key Point: An 835 should be interpreted through the combined claim status, payment information, financial adjustments, remarks and relevant payer details rather than by treating one field as a universal denial indicator.

Understanding Provider-Level Adjustments in the PLB Segment

The PLB (Provider Adjustment) segment reports applicable provider-level adjustments that may affect the overall payment associated with an 835 transaction.

These adjustments are distinct from claim-level and service-level CAS adjustments. They may relate to payment recovery, financial reconciliation or other permitted provider-level activity.

For example, a payer may use the PLB segment to recover an overpayment associated with a claim or service processed in a previous transaction. The original claim may not appear anywhere in the current 835, even though the adjustment affects the overall payment being issued to the provider.

The PLB segment is reported after the claim and service payment information. Although it may appear immediately after the last claim, this does not mean the adjustment belongs to that claim or any other claim reported in the current transaction.

When reconciling an ERA, medical billers and payment posting systems must consider applicable provider-level adjustments in addition to individual claim payment amounts.

However, a PLB adjustment should not automatically be interpreted as an additional denial or adjustment against every claim appearing in the transaction.

For EDI developers, this distinction matters when designing payment posting and reconciliation logic. Claim-related adjustments and provider-level adjustments may require different accounting treatment.

Common Mistakes When Interpreting an X12 835 ERA

Misinterpreting remittance information can lead to inaccurate payment posting, unnecessary claim follow-up or incorrect denial classification.

How Medical Billers Should Review an ERA

The following workflow provides a general approach for reviewing an X12 835 and determining whether any follow-up is needed.

Step 1: Identify the Remittance and Payment

Review the payer information, payment details, reassociation trace number and applicable transaction identifiers. Determine which claims and payment records are associated with the remittance.

Step 2: Match the Remittance to the Original Claim

Use the reported claim identifiers to locate the corresponding submitted claim. Review the original charges, services, provider information and other relevant billing details.

Step 3: Review Claim and Service Adjudication

Examine the CLP and applicable SVC segments to understand the claim's status, submitted charges, payer payment amounts and service-line processing.

Step 4: Interpret Adjustments and Remarks

Review the applicable CAS adjustments and any reported RARCs. Evaluate the codes in relation to the associated financial amounts and other adjudication details rather than interpreting them individually.

Step 5: Verify Financial Reconciliation

Check applicable service and claim balancing relationships. Reconcile transaction payment totals with reported claim payments and provider-level adjustments, as appropriate.

Step 6: Determine Whether Follow-Up Is Necessary

Compare the adjudication with the original claim, applicable coverage policies and payer requirements. Determine whether payment posting, additional investigation, documentation, a permitted claim correction, reconsideration or appeal is appropriate.

Important: These steps provide a general review framework. They do not establish payer-specific billing procedures or replace the applicable X12 implementation guide.

Medicare, Medicaid and Commercial Payer Considerations

The X12 835 provides a standardized structure for communicating healthcare remittance information. However, the underlying coverage requirements, payment policies and available follow-up procedures may differ between payer programs.

Medicare

Original Medicare uses standardized remittance advice to communicate adjudication outcomes through Medicare Administrative Contractors (MACs). Medicare coverage determinations, billing instructions and applicable processing rules may provide additional context when interpreting adjustments and remarks.

Medicare Advantage plans may have different coverage requirements, operational processes and appeal procedures. An adjustment reported by a Medicare Advantage plan should not automatically be interpreted using every Original Medicare procedure.

Medicaid

Medicaid fee-for-service programs and Medicaid managed care organizations may have different reimbursement methodologies, documentation requirements and claim correction or appeal procedures.

When reviewing Medicaid remittances, applicable state Medicaid guidance and managed care plan requirements should be considered alongside the information reported in the 835.

Commercial Payers

Commercial health insurers, including Blue Cross Blue Shield plans and other insurance carriers, use standardized remittance transactions while applying their own benefit structures, provider contracts, medical policies and payment requirements.

The same standardized adjustment code may appear across multiple insurers, but the underlying circumstances and appropriate follow-up actions may differ.

Clearinghouses and Billing Applications

Clearinghouses and payment services, including platforms such as Availity and Office Ally, may provide access to electronic remittance files, reports or other supported payment information.

Billing systems may transform the original 835 data into readable payment posting screens or denial work queues. When possible, the original codes, amounts, loop associations and other relevant remittance details should remain available for investigation.

Frequently Asked Questions About the X12 835 ERA

Key Takeaway

The X12 835 Electronic Remittance Advice provides structured information about healthcare claim processing, payments, patient responsibility, financial adjustments and other adjudication details.

Understanding an ERA requires more than reading an individual CARC or RARC. Medical billers and EDI professionals should examine the applicable CLP, SVC, CAS, MIA, MOA, LQ and other relevant remittance segments to understand how the payer processed the claim.

Financial balancing can help confirm that the reported charges, adjustments and payment amounts are consistent, while provider-level adjustments and payment information may be necessary for overall remittance reconciliation.

Most importantly, an individual code, status or payment amount does not tell the complete story of a payer's adjudication. The complete applicable 835 information, original claim and payer-specific requirements must be considered before determining whether additional investigation or claim follow-up is needed.

Related Eclaims Articles and Resources

• What Are Claim Adjustment Reason Codes (CARCs)?
• What Are Remittance Advice Remark Codes (RARCs)?
• Medical Claim Denials: Common Reasons Claims Are Denied
• Duplicate Medical Claim Denials

Disclaimer: This article provides general educational information about electronic healthcare remittance advice, payment posting, claim adjustments and X12 transactions. It does not replace official X12 implementation guides, payer instructions, provider agreements or applicable laws and regulations. Transaction requirements, code definitions and payer policies may change. Always verify current requirements with the applicable payer and official standards organization.