CARC 16 appears on more remittance advices than almost any other Claim Adjustment Reason Code. The official description reads: "Claim/service lacks information which is needed for adjudication. Additional information is supplied using the 835 Healthcare Policy Identification Segment (loop 2110 Service Payment Information REF) if used."
Read that again. The description itself tells you that the additional information — the part that explains what is actually missing — is supplied somewhere else. Specifically, in the RARC: the Remittance Advice Remark Code that accompanies the denial on your 835.
CARC 16 is not a denial code. It is a header. It marks the category of problem. The RARC is the actual content.
The problem is that most billing teams treat CARC 16 like it contains the full answer, guess at what might be missing, try something, and resubmit. Sometimes they guess correctly. Often they don't. The denial comes back again. The cycle repeats. The claim ages. Eventually it either gets written off or someone who knows what to look for finally reads the 835 properly.
How the CARC and RARC System Actually Works
The CARC/RARC system is a two-tier coding structure built into the ANSI X12 835 transaction — the electronic remittance advice that tells you how a claim was processed and why.
The CARC (Claim Adjustment Reason Code) is the category. It tells you the type of adjustment the payer made. CARC 16 says: the claim is missing information. CARC 29 says: it was filed too late. CARC 50 says: the service isn't covered under this plan. The CARC is always present on a denial.
The RARC (Remittance Advice Remark Code) is the specifics. It provides additional context about why the CARC was applied. On a CARC 16 denial, the RARC is the answer to the question the CARC raises: missing information — but what information, exactly?
The RARC is not optional supplemental information. For CARC 16, it is the diagnosis. Without it, you don't have enough information to take a specific corrective action. With it, the fix is usually straightforward and specific.
The Most Common CARC 16 Pairings — and What Each One Actually Means
CARC 16 pairs with dozens of RARCs depending on the payer, the service type, and the specific missing element. The following are the pairings that account for the majority of CARC 16 denials in most practice settings:
| RARC | Combined Meaning | Immediate Action |
|---|---|---|
| MA27 | Missing/invalid Medicare Beneficiary ID (MBI) | Obtain the patient's current Medicare card. Verify the MBI format (11 characters, alphanumeric). Enter in the correct claim field and resubmit as corrected. |
| MA61 | Missing/invalid Social Security Number | Verify whether this payer uses SSN or member ID as the primary identifier. Confirm the correct number in your registration system and resubmit. |
| N290 | Missing/invalid rendering provider identifier | Confirm the rendering provider's NPI is in the correct loop (2310B). Verify the provider is actively enrolled with this payer. Resubmit with the correct identifier. |
| M124 | Missing service circumstances documentation | Most common on DME or home oxygen claims. Attach the required clinical documentation (CMN, testing results) per the payer's LCD requirements. Resubmit with attachment. |
| N479 | Missing/invalid National Provider Identifier | Identify which NPI is flagged (billing, rendering, or ordering). Verify it's active in the CMS NPI Registry. Confirm the correct field placement and resubmit. |
| MA130 | Incomplete/invalid coverage information | Review the coverage information in the claim header. Confirm primary insurance information matches what the payer has on file. May require an eligibility reverification. |
Each of these is a different problem, with a different fix, requiring different documentation. Without the RARC, all six look identical from the CARC alone. With the RARC, each one has a clear, specific action path.
Where to Find the RARC on Your 835
The RARC appears in the 835 transaction in the CLP/CAS/MOA segment structure. Specifically, it shows up in the SVC segment loop (loop 2110) or in the MOA segment — depending on the payer's implementation and the position of the remark code in the remittance.
In practical terms, most billing software surfaces it as a separate field alongside the CARC on the denial detail view. It may be labeled "Remark Code," "Reason Code 2," or simply listed below the CARC code depending on your system's display logic.
If your billing system's denial display doesn't surface the RARC consistently, that's worth raising with your vendor. The information is there — it just may not be visible in your current interface.
The Codes That Always Need Their RARC — and the Ones That Don't
Not every CARC is incomplete without a RARC. Some codes are fully self-explanatory: CARC 29 (timely filing expired), CARC 97 (bundled service), and CARC 27 (coverage terminated) each contain enough information on their own to take immediate action. The RARC, when present, adds context — but the CARC alone is actionable.
CARC 16 is different. It is explicitly incomplete by design. The X12 definition acknowledges this with the reference to the 835 healthcare policy identification segment. The intent was always that the remark code would carry the specifics. Using CARC 16 without reading the RARC is like reading a chapter title without the chapter.
"CARC 16 alone tells you there's a problem with your claim. The RARC tells you what the problem is. Working CARC 16 without the RARC is the single most common source of repeat denials on an otherwise straightforward category."
— From the ROI Denial Management FrameworkThe following CARC codes should always be read with their accompanying RARC:
- CARC 16 — Information missing (RARC identifies what's missing)
- CARC 4 — Modifier inconsistency (RARC identifies which modifier and why)
- CARC 15 — Authorization issue (RARC distinguishes missing vs. invalid vs. non-applicable)
- CARC 96 — Non-covered charge (RARC provides the specific contract or policy reason)
- CARC 18 — Duplicate claim (RARC identifies which prior claim is the conflict)
What This Looks Like as a Process Change
If your team is currently pulling the CARC from the denial queue and working from that alone, the process change is simple and immediate. It requires no new technology — just a standard operating procedure and a reference resource.
Every time CARC 16 appears:
- Pull the 835 or ERA for the denial — not just the billing system's summary view.
- Locate the RARC in the remark code field (or in the raw 835 if your system doesn't surface it).
- Look up the CARC and RARC combination to confirm the specific meaning and action path.
- Take the specific corrective action the RARC indicates — don't guess.
- Document both the CARC and the RARC in your denial tracking log for trend analysis.
The trend analysis piece is worth emphasizing. If CARC 16 + MA27 (missing MBI) appears more than a few times per month, the problem is upstream: registration staff aren't collecting or verifying the Medicare Beneficiary Identifier at check-in. That's a training and workflow fix, not a denial management fix. You won't see it if you're only tracking the CARC.
Root cause tracking — which requires both codes — is how denial management becomes denial prevention.
A Note on the EDI Code Intelligence Lab
The ROI platform's EDI Code Intelligence Lab has been updated to reflect the CARC/RARC relationship directly. When you look up a code that commonly has a RARC pairing — like CARC 16 — the tool now prompts you to enter the RARC from your 835 and shows you the combined story: what the denial actually means given both codes, and the specific action steps for that combination.
The goal was to build the tool the way the codes are actually intended to work — not as a glossary that treats each code in isolation, but as a paired lookup that surfaces the complete picture. If you've been using the lab and only looking up one code at a time, try the combined lookup. It's a different experience.