Remittance Advice Remark Codes Explained

Remittance advice remark codes, explained simply, are short notes a payer adds to a remittance to give detail a reason code cannot. A supplemental remark code clarifies one adjustment, such as which piece of a claim was missing. An alert remark code, which starts with "Alert:", carries general processing information and is not tied to any adjustment.

RARC vs CARC: what a remittance remark code adds

A remittance advice remark code (RARC) adds detail to an adjustment that a claim adjustment reason code (CARC) has already explained in general terms. The CARC says why the amount changed, such as missing information. The RARC says what exactly was missing, such as a procedure code or a rendering provider identifier.

The X12 Remittance Advice Remark Codes list states the job directly: RARCs "provide additional explanation for an adjustment already described by a Claim Adjustment Reason Code (CARC)." The two lists are maintained separately. Chapter 22 of the Medicare Claims Processing Manual on remittance advice says "Remark codes are maintained by CMS, but may be used by any health plan when they apply."

Both codes appear because some reason codes are too broad to act on alone. CARC 16 means "Claim/service lacks information or has submission/billing error(s)." That tells a poster the line was not paid. It does not tell them what to fix. Chapter 22 says some CARCs "are so generic that the reason for adjustment cannot be communicated clearly without at least one remark code," and that Medicare contractors must add a remark code when they use one of those.

The meaning of each group code and the most common reason codes have their own post. For that background, read the guide to the CARCs billing teams see most often.

Eight CARC and RARC pairs, and what each tells the poster

The pairs below use code text from the X12 lists. They are examples of how a pair reads, not a list of combinations a payer must use. The claim details in the last column are fictional.

Read each pair left to right. The group code says who carries the amount, the CARC says why, and the RARC says what to do about it.

Alert RARCs vs supplemental RARCs: which kind is on your remittance?

Alert RARCs and supplemental RARCs differ in what they attach to. A supplemental RARC explains one specific adjustment and sits next to its CARC. An alert RARC starts with the word "Alert:" and shares general processing information, such as appeal rights. The X12 list says alerts are "never related to a specific adjustment or CARC."

The X12 page names the two types. It says "There are two types of RARCs, supplemental and informational," and that the informational ones "are all prefaced with Alert: and are often referred to as Alerts." So the first word of the code's text tells you which kind you are reading.

Three alert examples from the X12 list show the pattern:

• MA01: "Alert: If you do not agree with what we approved for these services, you may appeal our decision."
• N211: "Alert: You may not appeal this decision."
• N381: "Alert: Consult our contractual agreement for restrictions/billing/payment information related to these charges."

None of these changes a dollar amount. They tell the provider about rights or rules that apply to the claim. A poster records them but does not post an adjustment for them.

Supplemental codes do change what the poster does next. M51, N290 and M127 each name a specific gap in the claim. Each one only makes sense beside the CARC it explains, usually CO-16. If a supplemental code appears and you cannot tell which adjustment it belongs to, treat that as a reading problem to fix, not a code to ignore.

A quick sorting rule works for most remittances. If the text starts with "Alert:", log it at claim level and move on. If it does not, find the adjustment it explains and post the two together.

Where do remark codes appear on paper EOBs and 835s?

Remark codes appear in two places on an 835 and in printed form on paper. In the electronic 835, line-level remark codes go in the LQ segment, and claim-level codes go in the MOA segment for outpatient claims or the MIA segment for inpatient claims. Paper EOBs print the code beside the line or claim with a glossary.

Chapter 22 of the Medicare manual sets out the electronic rule: "Remark codes at the service line level must be reported in the ASC X12 835 LQ segment." It adds that remark codes for an entire claim go in "either an ASC X12 835 MIA (inpatient) or MOA (non-inpatient) segment." The manual notes the implementation guide allows up to 5 codes in the MOA or MIA segment and up to 99 in the LQ segment, though a payer's system may report fewer.

Paper remittances carry the same codes in a different form. The Medicare Standard Paper Remittance reports the standard codes and, according to the CMS remittance advice page, "provides the code text as well." Commercial paper EOBs vary. Some print the remark code in a column on the line. Others print a footnote marker on the line and the code with its text at the bottom of the page or on the last page.

Footnote layouts are where remark codes get lost. The line shows a marker such as a letter or a number, and the actual code sits a page later. A poster, or a program, that reads only the service line misses the code. When you capture EOB data, record each remark code at the level it was printed: line or claim.

Medicare remittances have their own field names for the claim-level codes. The post on Medicare remittance fields, ICN, MOA codes and reason codes walks through that layout. Reading the codes off a scan raises its own problems, covered in what EOB OCR reads and where it slips.

Remark codes that ask the provider to act

Remark codes that ask the provider to act usually start with M or N and name something missing, invalid or billed the wrong way. Their text often begins "Missing/incomplete/invalid", which means the claim needs a correction or an attachment. These codes turn a zero-pay line into a task, not a write-off.

The X12 list uses a consistent phrase for these requests. Some examples, quoted from the list:

• M20: "Missing/incomplete/invalid HCPCS."
• M51: "Missing/incomplete/invalid procedure code(s)."
• N290: "Missing/incomplete/invalid rendering provider primary identifier."
• N4: "Missing/Incomplete/Invalid prior Insurance Carrier(s) EOB."
• M127: "Missing patient medical record for this service."
• MA04: "Secondary payment cannot be considered without the identity of or payment information from the primary payer."
• N657: "This should be billed with the appropriate code for these services."

Each one points to a different fix. M20 and M51 send the claim back to coding. N290 sends it to whoever maintains provider enrollment data. N4, N479 and MA04 mean a secondary claim went out without the primary payer's payment details. M127 asks for documentation.

One code changes the route rather than the content. MA130 reads "Your claim contains incomplete and/or invalid information, and no appeal rights are afforded." The text says the claim has no appeal rights, so the path forward is a corrected claim rather than an appeal.

A worklist built from these codes saves time. Group open lines by remark code instead of by payer, and the same fix applies to every line in the group. Follow-up work on denials and corrected claims sits in the revenue cycle automation category.

Keeping a RARC lookup list current

A RARC lookup list stays current only if you refresh it from the X12 site on a schedule. Codes are added, reworded and retired. Chapter 22 of the Medicare manual says the remark code list "is updated three times a year," at the same time as the reason code list, "on or around March 1, July 1, and November 1."

Each code on the X12 list carries its own dates. The page shows a start date, a last modified date and, for retired codes, a stop date. A local table that stores only the code and its text cannot tell you whether a code was valid on the date of service. Store the dates too.

A short routine keeps a team's list honest:

1. After each update, download the current list from the X12 page.
2. Compare it with your table and flag new, changed and stopped codes.
3. Update any posting rules or worklists that depend on a changed code.
4. Keep old wording for codes that stopped, because older remittances still carry them.

Medicare contractors must also follow combinations of CARCs and RARCs. Chapter 22 says CAQH CORE operating rules "require the usage of a standardized CARC and RARC combinations" and that the list is "updated three times a year by CAQH CORE." A pair that looks odd may be on that list, so check before you call it an error.

Schema Care reads remark codes from EOBs along with service lines and amounts. Every value comes back with a confidence score, and the document types Schema Care reads are listed on the homepage. Your lookup table still supplies the meaning.

RARCs printed without a CARC: an edge case to flag

A RARC printed without a CARC is normal for an alert and suspicious for anything else. Chapter 22 of the Medicare manual says informational remark codes "can be reported without Group and Claim Adjustment Reason Code." A supplemental code standing alone has nothing to explain, so the missing CARC is likely a reading or layout problem.

Start by checking the first word of the code's text. If it begins "Alert:", post nothing and record the note at claim level. MA01 printed alone at the bottom of a claim is a typical example. It tells the provider about appeal rights and needs no adjustment.

If the code is supplemental, look for its CARC in three places. First, the claim level: some payers print the CARC on the claim line and the remark code on each service line. Second, the footnote area, where a marker may connect the two. Third, the next page, when a claim breaks across pages. Most lone supplemental codes turn up their partner in one of these spots.

Here is a fictional example. A paper EOB for patient Lee Navarro, member ID QRT992004 (made up), shows a service line with a $0.00 payment and the remark code N290, but no group or reason code. The line's billed amount is $140.00. A $140.00 gap with no CARC cannot be posted, because nothing says who carries it. The poster finds CO-16 printed once at claim level, above the lines. With that pair, the line becomes a correction task: add the rendering provider identifier and resubmit.

If no CARC turns up, do not guess one. Hold the line, note the remark code, and ask the payer which adjustment it explains. Field-level extraction should treat the same case as a failed check. The post on the EOB fields worth capturing and how to check them covers balancing rules that catch an adjustment amount with no code.