What Are Remittance Advice Remark Codes (RARCs)?

Remittance Advice Remark Codes (RARCs) are standardized codes used in healthcare remittance advice to provide additional information about claim adjustments and payment processing. These codes help healthcare providers, medical billers and EDI professionals better understand information communicated by health insurance payers after a medical claim has been adjudicated.

RARCs are commonly reported through an Electronic Remittance Advice (ERA), using the X12 835 Health Care Claim Payment/Advice transaction. They may provide additional explanation for a Claim Adjustment Reason Code (CARC) or communicate other important information about the payer's processing of a claim or service.

In this guide, we'll explain how RARCs work, how they differ from CARCs, where they're reported in the X12 835 version 5010 transaction, and why interpreting the complete remittance information is essential when investigating claim adjustments and denials.

Why Are Remittance Advice Remark Codes Used?

When a healthcare payer adjudicates a claim, the payment decision may involve coverage policies, benefit limitations, submitted claim information, provider agreements and other processing requirements.

Although Claim Adjustment Reason Codes (CARCs) identify reasons for financial adjustments, a CARC may not provide enough information to explain the specific circumstances behind the payer's decision.

RARCs help communicate additional details that may be useful for understanding the adjustment or other aspects of remittance processing.

For medical billers, this information can help identify what needs further investigation. For EDI developers, RARCs provide structured information that should remain associated with the appropriate claim or service line.

However, RARCs do not establish a universal billing correction, reconsideration or appeal procedure. Their significance depends on the remark itself, the surrounding remittance information and the applicable payer requirements.

Supplemental RARCs vs. Informational RARCs

RARCs are generally divided into two categories: supplemental remark codes and informational remark codes, also known as Alerts.

1. Supplemental RARCs

Supplemental RARCs provide additional explanation about a financial adjustment already described by a CARC.

For example, a CARC might indicate that submitted claim information was missing or incorrect. A supplemental RARC may help identify the specific information or documentation involved.

Supplemental remarks can be particularly useful when the CARC provides only a broad description of the adjustment reason.

2. Informational RARCs (Alerts)

Informational RARCs communicate information about remittance processing without identifying an adjustment reason. These codes are identified by the word Alert in their official descriptions.

For example, an Alert may notify the provider that claim information has been forwarded to another insurer or communicate another processing-related notice.

An informational RARC does not necessarily indicate a reduction in payment, a denied service or a problem requiring correction.

Important: RARCs may appear on claims or services that have been paid, partially paid or denied. The presence of a remark code alone does not establish the adjudication outcome.

What Is the Difference Between a CARC and a RARC?

CARCs and RARCs serve different purposes in healthcare remittance advice.

A CARC identifies the reason for a financial adjustment, while a RARC may provide additional explanation or communicate other remittance-processing information.

For example, CARC 16 generally indicates missing or incorrect claim information and requires accompanying remark information under the applicable code usage instructions.

A supplemental RARC may provide additional detail about the information involved. However, the combination must be evaluated alongside the claim or service payment information and applicable payer rules.

Not every RARC is directly associated with a CARC, and not every adjustment requires the same remark information. Informational RARCs may be reported separately from a specific financial adjustment.

Where Are RARCs Located in the X12 835 Version 5010?

In the X12 835 version 5010 transaction, RARCs are reported in different segments depending on whether they apply to the overall claim or an individual service line.

The MIA and MOA segments can contain other adjudication information in addition to remark codes. Their use is based on the applicable adjudication context rather than simply whether the payer is Medicare or a commercial insurer.

For service-level remarks, the LQ segment uses LQ01 to identify the code list and LQ02 to report the remark code. The qualifier HE identifies Claim Payment Remark Codes.

Unlike CARCs, which are reported in the CAS segment with adjustment amounts, RARCs provide explanatory or informational details and do not independently identify a financial adjustment amount.

It is important to retain the reporting level of each remark. A RARC reported for one service line should not automatically be interpreted as applying to every service on the claim.

Example: Reading a RARC in an X12 835 Service-Line Adjustment

Consider an illustrative professional claim containing a service billed at $125. During adjudication, the payer reports a $125 adjustment associated with missing or incorrect claim information and provides an additional remark indicating that an Explanation of Benefits (EOB) related to other insurance information is missing.

The following simplified X12 835 example demonstrates how the CARC and supplemental RARC could be communicated at the service level:

Example: Missing Other-Payer EOB Information

Illustrative example only. This is a partial X12 835 transaction using fictional billing information. It does not represent a complete interchange or establish that a particular payer will use this combination of codes for a specific claim scenario.

Understanding the Example

In this example, the payer reports a $125 adjustment and $0 payment for the service. CARC 16 identifies a general claim-information issue, while RARC N479 provides additional context concerning missing other-payer EOB information.

The RARC helps explain what may need to be investigated, but it does not establish whether the original claim was billed incorrectly or whether a corrected claim, additional documentation, inquiry or other payer-specific action is required.

The billing office should review the original claim, other insurance information, the applicable payer's coordination-of-benefits requirements and the remaining relevant remittance details before determining the appropriate follow-up.

Important: The LQ segment reports the remark code, not the financial adjustment amount. The adjustment group, reason code and amount are reported in the CAS segment.

Common Remittance Advice Remark Code Examples

RARCs cover a wide variety of situations involving claim information, coverage policies, documentation requirements, provider information and payer processing notices.

The following examples illustrate different types of remarks that billing professionals may encounter. They are not a statistical ranking of commonly reported RARCs and do not represent the complete official code list.

These descriptions are simplified educational summaries. Each RARC has an official definition and may have applicable usage instructions or code status information.

For the complete, current list and official definitions, refer to X12 Remittance Advice Remark Codes.

When reviewing a RARC, medical billers should not assume that the remark describes every reason for the payer's determination. The complete remittance advice, original claim and applicable payer policies may contain additional information necessary to understand the processing outcome.

Can a RARC Be Reported Without a CARC?

Yes. A RARC may be reported without a direct association to a specific CARC when the payer is communicating applicable remittance information.

Informational RARCs, or Alerts, are specifically intended to communicate processing information rather than explain a particular financial adjustment.

For example, RARC MA18 is an informational Alert concerning claim information being forwarded to the patient's supplemental insurer.

The following simplified claim-level example shows how such an Alert could appear in an outpatient adjudication:

Example: Claim-Level Informational RARC

In this example, MA18 is reported in MOA03, a claim-level remark code position. The empty MOA01 and MOA02 elements are preserved by the asterisk delimiters.

The excerpt does not report a financial adjustment or establish the claim's payment status. Those details must be determined from other applicable information in the 835 transaction.

This illustrates an important distinction: the presence of a RARC does not necessarily mean that a claim or service was denied.

Claim-Level RARCs vs. Service-Level RARCs

RARCs may apply to an entire claim or to an individual service line, and their placement within the 835 is important when interpreting their meaning.

A medical claim may contain multiple services with different payment outcomes and applicable remarks. A service-level remark should be evaluated in relation to the specific service with which it is reported.

Similarly, a claim-level remark should not automatically be treated as a separate adjustment against each service line.

For EDI developers, preserving the original loop and segment association is important when translating remark codes into billing application messages or denial management records.

Why RARCs Cannot Be Interpreted by Themselves

Although RARCs can provide valuable details, they represent only part of the information available in an X12 835 transaction.

A complete understanding of a payer's adjudication may require reviewing:

• Claim status and payment information: The CLP segment identifies claim-level adjudication information, including applicable claim status and payment amounts.
• Service payment information: The SVC segment reports service-level charges and payment information.
• Financial adjustments: The CAS segment identifies adjustment group codes, CARCs and associated adjustment amounts.
• Additional remarks: Applicable MIA, MOA and LQ segments provide claim-level or service-level remittance information.
• Other remittance details: Additional applicable segments may provide information about claim identifiers, coverage policies, payment processing or other adjudication circumstances.
• Payment reconciliation: Provider-level adjustments and other payment information may also need to be considered when reconciling the overall remittance.

Medical billers and EDI professionals should review the RARC in the context of the complete applicable remittance information rather than relying solely on the remark description displayed by a billing system.

For example, a remark about a coverage policy does not by itself establish whether the payer denied the entire claim, reduced payment for one service or communicated additional information about a processed service.

The payer's adjudication details, applicable coverage requirements and original claim information must be considered before determining whether further action is necessary.

How Medical Billers Should Interpret a RARC

The following steps provide a general approach to reviewing RARCs and determining whether additional investigation may be needed.

Step 1: Identify the RARC and Its Reporting Level

Identify the remark code and determine whether it applies to the entire claim or a specific service line. Review the appropriate MIA, MOA or LQ segment when the X12 835 is available.

Step 2: Review the Associated Adjustment Information

Determine whether the RARC provides supplemental information about an adjustment or communicates other remittance-processing information.

When applicable, review the associated adjustment group code, CARC and adjustment amount reported in the CAS segment. A RARC should not be treated as an independent financial adjustment.

Step 3: Review the Complete Relevant 835 Details

Examine the claim and service payment information, other applicable remarks and additional remittance details needed to understand the payer's adjudication.

Do not assume that a RARC alone identifies the complete payment decision or explains every adjustment reported for the claim.

Step 4: Compare the Remittance Against the Original Claim

Review the original 837 claim or the information submitted through the payer's portal or paper claim form. Compare the submitted information with the payer's adjustment and remark details.

Depending on the situation, this may involve reviewing coverage, coding, provider information, authorization, supporting documentation or coordination-of-benefits information.

Step 5: Verify Payer Requirements and Determine Follow-Up

Determine whether the payer's adjudication requires any follow-up. An informational remark may not require action, while a supplemental remark may identify information that warrants investigation.

Depending on the payer and circumstances, possible actions may include a claim inquiry, permitted correction, submission of documentation, reconsideration or appeal.

Important: The same RARC may appear in different payer environments, but coverage policies, documentation requirements, correction procedures and appeal rights may differ. Always verify the payer's applicable instructions before taking action.

Medicare, Medicaid and Commercial Payer Considerations

RARCs are standardized across healthcare remittance transactions, but the circumstances behind a remark and the applicable claim resolution procedures can vary among payers.

Medicare

Original Medicare contractors use standardized remittance advice codes to communicate claim adjudication and processing information. Applicable Medicare coverage determinations, billing requirements and Medicare Administrative Contractor (MAC) guidance may provide additional context for certain remarks.

Medicare Advantage plans may use different coverage policies and operational or appeal procedures from Original Medicare. A remark reported by one program should not automatically be interpreted according to another program's requirements.

Medicaid

Medicaid fee-for-service programs and Medicaid managed care plans may apply different coverage, authorization, documentation and payment policies. State-specific requirements and the applicable managed care plan's guidance should be considered when investigating remittance remarks.

Commercial Payers

Commercial payers, including Blue Cross Blue Shield plans and other health insurers, report standardized remittance information while applying their own benefit designs, medical policies, provider contracts and payment requirements.

A RARC may identify additional information relevant to an adjustment, but the payer's applicable policy or provider agreement may be needed to understand the determination and whether follow-up is appropriate.

Clearinghouses and Billing Systems

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

Billing applications may translate RARCs into descriptive messages or combine multiple adjustment and remark codes into simplified explanations.

For accurate interpretation and troubleshooting, the original remark code, reporting level, associated adjustment information and other relevant remittance details should be preserved whenever possible.

Why RARCs Are Important for Payment Posting and Denial Management

RARCs can be valuable for understanding claim adjustments, investigating payment discrepancies and supporting denial management activities.

For example, supplemental remarks may help billing teams identify missing information or coverage requirements that need further review. Informational remarks may communicate processing details that should be retained with the claim record.

When evaluating denial patterns, organizations may analyze CARCs and applicable RARCs together to better understand recurring adjudication issues.

However, automated denial classification should not rely on a RARC alone. The same remark may appear in different claim circumstances, and some RARCs do not describe a denial or financial adjustment.

For EDI developers, maintaining the relationship between remark codes, claim or service identifiers, adjustment details and payer information can improve payment posting accuracy and support later investigation of disputed claims.

Preserving the original remittance data is especially useful when a billing system's translated description does not fully reflect the information reported by the payer.

Frequently Asked Questions About RARCs

Key Takeaway

Remittance Advice Remark Codes (RARCs) provide supplemental explanations for healthcare claim adjustments or communicate other information about remittance processing. They may appear on paid, partially paid or denied claims and should not automatically be treated as denial codes.

In the X12 835 version 5010 transaction, claim-level RARCs are reported in Loop 2100 using the MIA or MOA segments, while service-level RARCs are reported in Loop 2110 using the LQ segment.

For medical billers and EDI professionals, accurate interpretation requires reviewing the remark in the context of the applicable adjustment group codes, CARCs, financial amounts, claim and service payment information, and other relevant remittance details. Payer coverage policies and resolution requirements must also be considered before determining whether additional action is necessary.

A RARC can help explain part of the payer's adjudication, but it should never be treated as a substitute for understanding the complete applicable remittance information.

Related Eclaims Articles and Resources

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

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