EDI 835 adjustment and remark code mapping is not a single lookup table. It is a layered process in which claim adjustment reason codes (CARCs) explain why payment differs from the billed amount, while remittance advice remark codes (RARCs) add supplemental explanation or convey processing information [2][3]. The mapping question matters because a payer's internal adjudication codes often do not match the standardized codes that appear in an 835 transaction. CMS documentation states that in most cases, reason and remark codes reported in remittance advice transactions are mapped to alternate codes used by a shared system, and those shared system codes may exceed the number of reason and remark codes approved for reporting in a remittance advice transaction [1]. A particular ASC X12 835 reason or remark code might map to one or more shared system codes, or vice versa, which can make it difficult for a Medicare administrative contractor to determine each of the internal codes that may be impacted by remark or reason code modification, retirement, or addition [1]. Software teams therefore need to separate code ownership, placement rules, and payer-specific mapping behavior rather than treating the 835 as a universal dictionary.
Code Ownership and the Mapping Boundary
The two code sets have different stewards and different jobs. X12 describes claim adjustment reason codes as codes that describe why a claim or service line was paid differently than it was billed [7]. The X12 code list page describes remittance advice remark codes as codes that provide additional explanation for an adjustment already described by a CARC or convey information about remittance processing [2]. CMS documentation states that remark codes are maintained by CMS but may be used by any health plan when they apply [1]. This split matters for mapping because a payer may maintain internal reason codes that are richer than the standardized set, then translate them into CARCs and RARCs at the point of 835 generation.
The mapping boundary is therefore between an internal adjudication system and the outward-facing transaction. CMS states that in most cases, reason and remark codes reported in remittance advice transactions are mapped to alternate codes used by a shared system [1]. The documentation does not describe the mechanics of that mapping in detail, but it does establish that a particular ASC X12 835 reason or remark code might map to one or more shared system codes, or vice versa [1]. For a software team, this means a mapping engine should expect non-bijective relationships and should not assume that a single internal code always produces a single standardized code, or that a single CARC always traces back to one internal adjudication reason.
Placement Rules Across Claim and Service Levels
Where a code appears in the 835 depends on the scope of the adjustment and the type of claim. CMS documentation states that reason codes may be used at the service or claim level, as appropriate, and that current ASC X12 835 structures only allow one reason code to explain any one specific adjustment amount [1]. Remark codes that apply to an entire claim must be reported in either an MIA segment for inpatient claims or an MOA segment for non-inpatient claims [1]. This placement distinction is a practical constraint for parsers: a claim-level remark code will not appear in the same location as a service-level remark code.
Commercial and state payer guides reinforce these placement rules with specific segment references. Cigna's companion guide states that remark codes in the LQ segment are required when claim adjustment reason code 16, 17, 96, 125, 148, 226, 227, or A1 is used in the 2110 CAS segment [6]. Nevada Medicaid's companion guide identifies MIA05 and MIA20 as reference identification fields for HIPAA remark codes on inpatient and institutional regular and crossover claims, and MOA03 and MOA04 for outpatient adjudication information [5]. These examples show that mapping logic must be segment-aware, not just code-aware.
What to Capture in a Mapping Record
A mapping record should capture more than the source and target codes. Based on the documented distinctions, useful fields include the internal adjudication code, the standardized CARC, the optional supplemental RARC, the segment where the RARC appears (MIA, MOA, or LQ), the claim or service level, and whether the RARC is supplemental or informational [1][2]. The record should also note the TR3 version and any payer-specific companion guide constraints, since Medicare and Nevada Medicaid both document version 005010X221A1 but apply different qualifier and code restrictions [4][5]. Because CMS documentation states that shared system codes may exceed the number of reason and remark codes approved for reporting in a remittance advice transaction and that a particular ASC X12 835 reason or remark code might map to one or more shared system codes, or vice versa [1], the record should not assume a one-to-one relationship. Teams that store mappings as a flat CARC-to-RARC table will lose the segment and type information needed to reconstruct a valid 835.
Supplemental and Informational RARCs
RARCs are not a single category. X12 documentation distinguishes supplemental RARCs, which provide additional explanation for an adjustment already described by a CARC, from informational RARCs, which are prefaced with 'Alert:' and are never related to a specific adjustment or CARC [2]. CMS documentation describes the same split, noting that informational remark codes start with the word 'Alert' and can be reported without a group and claim adjustment reason code [1]. This distinction affects mapping because an informational RARC should not be attached to a CARC in the same way a supplemental RARC is.
The practical consequence is that a mapping table keyed only on CARC-to-RARC pairs will miss informational codes entirely. A software system that expects every RARC to have a corresponding CARC may misclassify an Alert code as an adjustment explanation. CMS documentation states that MACs must report appropriate remark codes that apply [1], but it does not provide a universal rule for when an informational code should be used. Teams should therefore model supplemental and informational RARCs as separate record types rather than forcing them into one relationship.
Payer-Specific Mapping Lists and Version Boundaries
MassHealth publishes CARC and RARC lists that match its explanation of benefits codes to corresponding standardized codes. The Mass.gov page states that the lists match MassHealth EOB codes to a corresponding Healthcare Claim Adjustment Reason Code, and when appropriate, a Remittance Advice Remark Code that appears on 835 transactions [3]. It also notes that the lists should only be referenced when reconciling denied claims [3]. MassHealth aligns relevant EOBs with CAQH CORE Code Combinations, which are updated quarterly [3]. This is a documented example of a payer maintaining a mapping artifact that is narrower than the full X12 code set.
Version boundaries also shape mapping work. The Novitas Solutions companion guide is based on ASC X12N TR3 version 005010X221A1 and identifies specific qualifier codes Medicare does not use in various loops [4]. Nevada Medicaid's companion guide is also based on 005010X221A1 and lists adjustment reason codes documented within the TR3 guides for PLB segments [5]. These version-specific boundaries mean a mapping implementation built for one TR3 version may not be valid for another. The documentation does not state that all payers use the same subset of codes, and teams should treat each companion guide as a constraint layer on top of the standard.
A Hypothetical Validation Scenario
A software team could validate its mapping logic by constructing a synthetic 835 that exercises the documented placement and type distinctions. The scenario would include a claim-level adjustment with a CARC and a supplemental RARC in the MOA segment, a service-level adjustment with a CARC and an LQ segment RARC, and an informational Alert RARC with no associated CARC. The parser would then be checked against three assertions: the claim-level RARC is read from MOA, the service-level RARC is read from LQ, and the Alert code is not incorrectly linked to any CARC.
This scenario is a suggestion for internal testing, not a claim about any vendor's behavior. It draws on documented rules: CMS states that claim-level remark codes belong in MIA or MOA [1], Cigna states that LQ remark codes are required for certain CARCs in the 2110 CAS segment [6], and X12 states that Alerts are never related to a specific adjustment or CARC [2]. A team could also add a MassHealth-style EOB mapping check by confirming that an internal denial code resolves to the expected CARC and optional RARC pair from the payer's published list [3]. The value of the scenario is that it separates mapping correctness from parsing correctness.
Sources & references
- Medicare Claims Processing Manual, chapter 22 · www.cms.gov
- Remittance Advice Remark Codes | X12 · x12.org
- 835 Payment Advice and EOB/CARC & RARC Lists | Mass.gov · www.mass.gov
- [PDF] 835 Standard Companion Guide-JH-2026 - Novitas Solutions · www.novitas-solutions.com
- Health Care Payment/Advice (835) - Nevada Medicaid · www.medicaid.nv.gov
- Companion guide · www.cigna.com
- Claim Adjustment Reason Codes | X12 · x12.org