Notes on payer behavior
Remark codes (RARCs), decoded: what each one means, what it pairs with, and the fix
A remark code (RARC) is the second code on a remittance line. The reason code (CARC) says what the payer did. The remark code says why, or what to fix. Find the remark code in the table below, read the reason code it's paired with, and you know whether the line needs a corrected claim, a record, or a payment dispute.
Billers usually meet a remark code the same way. A line comes back short or denied, the reason code is something generic like CO-16 or CO-96, and the only specific clue is a string like "N290" or "M80" sitting next to it. So you paste it into a search bar. This page is the answer we'd want to find: what the code means in plain terms, what it usually travels with, and what actually fixes it.
How remark codes pair with reason codes
Every adjusted line on an electronic remittance (the 835) carries three things. A group code (CO, PR, OA, PI) says who the amount belongs to. A reason code (CARC) says what happened to it. A remark code (RARC), when present, explains the reason code. Think of the reason code as the envelope and the remark code as the letter inside.
Some reason codes are close to empty without a remark. CARC 16 ("claim lacks information or has submission or billing errors") is the clearest case: the X12 code list requires at least one remark code that isn't an alert to go with it. CARC 96 (non-covered) and 97 (bundled) behave the same way in practice. The remark carries the real reason, which is why a CO-16 can't be worked without reading it.
Three more things worth knowing:
- Where they sit. Line-level remarks ride in the LQ segment of the service-line loop. Claim-level remarks sit in the MOA segment on professional claims and MIA on institutional ones. Many practice management systems post the reason code and drop the remark. What each 835 field holds.
- "Alert" codes are informational. A remark that begins with "Alert" tells you something; it doesn't adjust anything. The money moves on the reason code.
- Who maintains them. CMS maintains the remark code list and X12 publishes it with the reason codes, updated several times a year. Commercial payers use the same list, though some apply codes more loosely than Medicare contractors do.
The remark codes specialty practices see most
Short forms below are plain-language summaries of the official descriptions. Pairings are the common ones, not the only ones. Payers vary, so read the exact text on your remit.
| RARC | What it says, in plain terms | Usually pairs with | The fix |
|---|---|---|---|
| N130 | Consult the plan's benefit documents or guidelines for restrictions on this service | CO-96, CO/PR-204, CO-50 | Find the plan policy behind it. If the service met the criteria, appeal with the record. If it's a true exclusion, check the group code before billing the patient. |
| N381 | Alert: consult your contract for restrictions, billing, or payment information on these charges | CO-45, CO-97 and others | It points at the contract. Recompute the allowed amount against your fee schedule. If it's short, dispute it and cite the section. |
| N350 | Missing, incomplete, or invalid description of service for a not-otherwise-classified (NOC) code or unlisted procedure | CO-16 | Add the narrative (drug name, dose, route; or what the unlisted procedure was) in the line note, then send a corrected claim. |
| M15 | Separately billed services were bundled as components of the same procedure; no separate payment | CO-97, CO-234 | Check the NCCI pair and its modifier indicator. If the services were truly distinct and the indicator allows it, correct with the right modifier and documentation. If not, the bundle stands. |
| M80 | Not covered when performed in the same session or on the same date as a service already processed | CO-97 | Same-day bundling. Often an E/M with a procedure that needed modifier 25, or two distinct procedures that needed 59 or an X modifier. |
| N19 | Procedure code is incidental to the primary procedure | CO-97 | Confirm against the payer's incidental-procedure policy and NCCI. Reverses only if the service was separate and separately documented. |
| M144 / N525 | Pre- or post-operative care is included in the surgery payment / not covered inside another service's global period | CO-97 | Date math first, then modifiers 24, 25, 57, 58, 78 or 79 if the visit or procedure was unrelated. The global-period play. |
| N290 | Missing, incomplete, or invalid rendering provider primary identifier | CO-16 | Check the rendering NPI on the claim and that it's linked to the group with this payer. Corrected claim; Medicare treats it as unprocessable, not appealable. |
| N382 | Missing, incomplete, or invalid patient identifier | CO-16 | Match name and member ID (or MBI for Medicare) to the current card. Resubmit; a front-end rejection goes back as a new claim. |
| MA130 | Claim has incomplete or invalid information and is unprocessable, so no appeal rights; submit a new claim | CO-16 plus a second remark | Read the second remark to find the field. Send a new claim, not a redetermination, and watch the filing clock. |
| M51 | Missing, incomplete, or invalid procedure code(s) | CO-16 | Correct the code or modifier for the date of service. Corrected claim. |
| N657 | This should be billed with the appropriate code for these services | CO-16, CO-4 | The payer wants a different code or convention (units vs. bilateral modifier, a HCPCS code instead of CPT). Find its coding policy, then send a corrected claim. |
| N479 | Missing explanation of benefits (coordination of benefits or Medicare secondary payer) | CO-16, CO-22 | Send the primary payer's adjudication with the secondary claim, either in the electronic COB loops or as an attachment. |
| MA04 | Secondary payment can't be considered without the primary payer's identity or payment information | CO-16, CO-22 | Fix the primary payer data and payer order on the claim. Resubmit with the primary's payment and adjustments. Secondary claim math. |
| M127 | Missing patient medical record for this service | CO-50 (Medicare), CO-252 | A records request went unanswered or arrived late. Send exactly what was asked through the payer's records channel; on Medicare, request redetermination with the records. |
| N362 | The number of days or units of service exceeds the acceptable maximum | CO-151 | Usually a medically unlikely edit. Check the units for typos first. Documented units can be appealed unless the edit is a date-of-service absolute limit. |
| M86 | Denied because payment was already made for the same or a similar procedure within a set time frame | CO-119, CO-18 | Check who was paid and when. Another provider's claim, or a period that already reset, is a winnable appeal. |
| N115 / N386 | The decision was based on a Local (N115) or National (N386) Coverage Determination | CO-50, CO-96, CO-151 | Read the LCD or NCD and its article. Missing diagnosis codes and frequency rules are the usual culprits. Correct the claim, or appeal with records that meet the criteria. |
| N95 | This provider type or specialty may not bill this service | CO-170 | A specialty or enrollment mismatch. Check how the provider is enrolled with this payer before anything else. |
| N781 | Patient is a Qualified Medicare Beneficiary; review cost-sharing amounts | Patient-responsibility lines | Federal rules bar collecting Medicare cost sharing from QMB patients. Don't send a statement. Who actually owes. |
| N211 | Alert: you may not appeal this decision | CO-29 and others | Believe it, but check the route. On Medicare, timely-filing denials go to a reopening or a good-cause request, not an appeal. The Medicare levels. |
Three kinds of remark code, three different jobs
Once you've read a few hundred, remark codes sort into three piles. The pile decides the work.
- Fix and resubmit. N290, N382, N350, M51, MA130, N479, MA04, N657. Something on the claim was wrong or missing. Nobody needs to be persuaded. A corrected claim (replacement, frequency code 7) for anything that was adjudicated; a new original for anything rejected at the front end. A letter here just burns days.
- Send the record. M127, N115, N386, and many N130s. The payer wants proof that the service met a written policy. The appeal is the chart, organized around the policy's own criteria.
- Dispute the payment. N381, M15, M80, N19, M144, N525, M86. These are payer rules applied to a clean claim. Some are right. A good share aren't: the wrong bundle, a modifier the edit ignored, a global window counted wrong, a contract rate that wasn't loaded. These are where payment disputes are won.
Pile one is fast and cheap. Pile three is where the money is, because it's where a payer rule fires the same way on hundreds of lines.
Read the remark, then count it
One N381 on one line is a curiosity. Two hundred N381s from the same payer on the same visit code, all allowed at the same short amount, is a contract-loading problem. One fix stops it for every future claim, and the past lines go back in one dispute. The same goes for M80 on every E/M billed with a minor procedure. Same with M15 on one recurring code pair.
So the most useful report a billing team can run is a count: remark code by payer by month, with dollars. Most practice systems can't produce it, because the remark was never stored. The raw 835 files still have it. That's usually where we start.
What it means for your practice
Route every denial by its remark code, not just its reason code. It tells you whether the line needs a corrected claim, a record, or an argument, and choosing wrong costs weeks against a filing clock. Then look for remark codes that repeat. Repetition means a rule. A rule that's wrong is one dispute, not a thousand. That's the work our team does in Clearia's diagnostic, across underpayments, administrative denials and downcoding.
Sources
X12, Remittance Advice Remark Codes and Claim Adjustment Reason Codes (official code lists; CARC 16 usage note) · Noridian Medicare denial-resolution pages for N290, M127, M80 and N362 / MUE · CGS Medicare, claim submission errors and MA130 · First Coast Service Options, claims returned as unprocessable and CO-97 tips · CMS transmittal R663PI (CARC 50 with M127 for undelivered documentation) · Noridian, CO-16 with N382. Descriptions summarized October 2026; check the current list for exact wording.
Questions people ask about remark codes
What is a remark code on a remittance?
A remittance advice remark code (RARC) is a short code that adds detail to a claim adjustment reason code (CARC). The CARC says what the payer did to the line; the RARC says why, or what is missing. CMS maintains the RARC list, and X12 publishes it alongside the reason codes.
What is the difference between a CARC and a RARC?
The CARC is the adjustment itself, like 16 (missing information) or 97 (bundled). The RARC is the explanation that rides with it, like N290 (rendering provider identifier missing or invalid). A CARC can stand alone. Most RARCs can't; they always travel with a CARC.
What does remark code N130 mean?
N130 tells you to consult the plan's benefit documents or guidelines for restrictions on the service. It points to a plan policy without naming it. Pull the policy, check whether the service met its criteria, and appeal with the record if it did.
What does MA130 mean on a Medicare remittance?
MA130 means the claim was returned as unprocessable because information was missing or invalid, so there are no appeal rights. Read the companion remark code to find the field, then submit a new, corrected claim inside the timely filing limit. Don't file a redetermination.
Can I appeal a denial based only on the remark code?
The remark code tells you which door to use. Data-error remarks like N290, N382 and MA130 call for a corrected or new claim, not an appeal. Policy and payment remarks like N130, N115 and N381 can support an appeal or a payment dispute when the record or the contract is on your side.