Understanding Payment Information in an X12 835 ERA

An X12 835 Electronic Remittance Advice (ERA) communicates healthcare claim payment and adjustment information from a payer to a provider. In addition to reporting how individual claims were processed, the transaction identifies the overall payment amount, payment method, and information used to associate the remittance with its payment.

Understanding how these different amounts relate is useful when reviewing remittance files, developing healthcare EDI integrations, or reconciling claim payment information.

In this article, we'll examine a simplified X12 835 example containing one paid claim with three service lines. Our focus is on how the BPR, TRN, CLP, and SVC segments work together to describe a single payment.

How Payment Information Is Organized in an X12 835

An 835 contains information at different levels. Some segments describe the payment associated with the transaction, while others provide information about individual claims and services.

For this example, we'll concentrate on five segments:

These segments provide different views of the same payment activity. The overall payment reported in the 835 is not the same thing as the charges submitted on a claim, and claim-level payment information may represent the combined payment amounts from multiple services.

X12 835 Example: A $180 Check Payment

The following example demonstrates a payer issuing a $180 check for a single processed claim. The claim contains three services, with a portion of each service amount reported as patient coinsurance.

This excerpt is not a complete X12 835 transaction. The individual sections are labeled for readability, and segments unrelated to the payment example have been omitted.

Understanding the BPR Segment: Overall Payment Information

The BPR segment provides payment information for the remittance. In our example, it indicates that the payer has reported a $180 payment by check.

Rather than examining every possible BPR element, we can identify the values relevant to this payment:

The most important value for our example is the $180 payment amount. This represents the overall payment reported for the remittance, rather than the total charges submitted by the provider.

Other payment methods can also appear in an 835. For example, an electronic funds transfer may be identified using ACH rather than CHK. Our example uses a check to keep the payment information straightforward.

Understanding the TRN Segment: Payment Identification

The TRN segment provides trace information associated with the remittance and payment. This information is useful when matching an ERA with its corresponding payment record.

In this fictional example, 202611030001 represents the payment trace identifier, and 1234567890 is a fictional originating company identifier.

Because the payment method is check, the trace identifier may represent the check number associated with the payment. For an electronic funds transfer, the corresponding trace information can help associate the ERA with the EFT.

The key distinction is that BPR describes the payment, while TRN helps identify that payment. The trace identifier is not itself a payment amount.

We'll explore payment trace numbers and EFT/ERA association in more detail in our next article.

Understanding the CLP Segment: Claim Payment Information

After the payment-level information, an 835 reports claim-level information. The CLP segment identifies an individual claim and provides financial amounts associated with its processing.

Our fictional claim reports the following values:

Notice that the claim was submitted for $200, but the payer payment is $180. The remaining $20 is reported as patient responsibility.

The claim payment amount is the value we're most interested in for this article. Because this example contains only one paid claim and no provider-level adjustments, the $180 claim payment matches the $180 overall payment reported in the BPR segment.

Understanding the SVC Segments: Service-Level Payments

Our example includes three services. Each SVC segment reports a submitted service charge and the corresponding payer payment.

The associated CAS segments identify coinsurance adjustments using the Patient Responsibility group code PR and Claim Adjustment Reason Code 2.

Each service contains a positive payer payment. Together, the three service payments total $180, which matches the payment reported for the claim.

Although the CAS adjustments help explain the financial difference, this article is not intended to provide a complete discussion of adjustment reason codes. For additional information about these codes, see our What Are Claim Adjustment Reason Codes (CARCs)? article.

How the Payment Amounts Relate to Each Other

One of the most useful aspects of this example is that we can follow the payment from the individual services to the claim and finally to the overall remittance payment.

The financial relationship can also be expressed as:

Because the example contains only one claim, the sum of the service payments equals the claim payment, and the claim payment equals the overall amount reported in BPR.

In a larger ERA, the overall payment may reflect several claims. Provider-level adjustments can also affect the payment total without changing the payment amount reported on an individual claim. We'll examine those scenarios in later articles in this series.

Does BPR Always Match a Single CLP Payment?

No. The amounts match in our example because the remittance contains only one paid claim and no provider-level adjustments.

An ERA may contain multiple claims with different payment amounts. In that situation, the overall payment generally reflects the combined claim payments, taking any applicable provider-level adjustments into account.

For example, if a remittance reports two claim payments of $180 and $120, with no provider-level adjustments, the overall payment would be $300.

However, when provider-level adjustments are reported, the overall payment can differ from the sum of individual claim payments. Those adjustments are commonly reported using the PLB segment.

Our current example intentionally avoids PLB adjustments so we can concentrate on the basic relationship between payment-level and claim-level information.

What This Example Does Not Include

A production X12 835 contains more information than the selected segments shown in this article. Depending on the transaction, additional information can include:

• Payer and payee identification
• Claim and service reference identifiers
• Service dates and other date information
• Supplemental monetary amounts
• Additional claims and service lines
• Provider-level adjustments
• Transaction envelopes and control segments

These details have been excluded from the displayed example because they are not needed to demonstrate the basic payment relationship. The excerpt should not be used as a complete transaction template or implementation reference.

Frequently Asked Questions

Key Takeaway

An X12 835 ERA communicates payment information at more than one level. The BPR segment identifies the overall payment, the TRN segment provides payment trace information, and the CLP and SVC segments report the payment amounts associated with individual claims and services.

In our simplified example, three services totaling $200 in submitted charges contain $20 in coinsurance adjustments. The remaining $180 is reported as the claim payment and also as the overall check payment in the remittance.

Understanding these relationships provides a useful starting point for reviewing more complex X12 835 payment examples.

Related Eclaims Articles

• How to Read an X12 835 ERA: Claim Payments, Adjustments & Denials
• What Are Claim Adjustment Reason Codes (CARCs)?
• What Are Claim Adjustment Group Codes (CO, PR, OA & PI)?

This article is provided for educational purposes and uses fictionalized X12 835 transaction excerpts. It is not a substitute for the official X12 implementation guide, payer-specific requirements, or applicable billing and payment policies.