Denial Codes Explained: What Your CARC and RARC Codes Are Telling You About Payer Behavior

Ask a revenue cycle leader what CO-16 means and they can tell you. Ask why it is rising for one payer, which services are driving it and what should change upstream, and the answer gets harder. That gap is not a coding problem. Intelligence is the problem, and it is why the same denial codes keep returning after the claims behind them have been corrected.

This guide explains how group codes, Claim Adjustment Reason Codes and Remittance Advice Remark Codes work together, what the most common combinations mean and how to prevent the root causes behind them. The larger opportunity is to read recurring combinations across remittances as evidence of changing payer behavior, then move the lesson to the workflow before the next claim goes out.

Key takeaways

• A complete adjustment message combines a group code, a CARC and often a RARC.
• Most preventable denials trace to missing information, eligibility, authorization, medical necessity, bundling, modifier use, duplicates or timely filing.
• Not every adjustment is a denial. PR-1 and most CO-45 adjustments are expected financial dispositions, not errors to appeal.
• Many denial causes can be addressed at charge review or before claim submission.
• One code explains one adjudication. Movement across codes, payers and services can reveal a change in payer behavior.

What are denial codes?

Denial codes are standardized codes on an electronic remittance advice, or 835, and on explanations of benefits that tell a provider why a payer denied or adjusted all or part of a claim. Teams may see the same denial reason codes in an ERA, an EOB or a practice management system's denial queue.

The phrase denial code is useful shorthand, but it can also distort the analysis. X12 maintains Claim Adjustment Reason Codes to explain why a claim or service line paid differently than billed. That includes full denials, partial reductions, contractual adjustments and patient responsibility. If all four are counted as preventable denials, the metric is wrong before anyone begins working the queue.

Commercial payers and CMS programs use the same code sets, but handling can differ by payer, plan, specialty and service. The CARC alone rarely provides enough direction.

Use the current X12 CARC list and X12 RARC list rather than a saved cheat sheet. X12 publishes code-list updates throughout the year, and definitions, statuses and effective dates can change.

How to read a denial code: group codes, CARCs and RARCs

A denial code is not one code. Read the adjustment line in three parts: the group code assigns financial responsibility, the CARC states why payment changed and the RARC adds the detail needed to interpret or act on that change.

For example, CO-50 with N115 means the payer assigned the adjustment as a contractual obligation, found that the service did not meet medical-necessity requirements and based the decision on a Local Coverage Determination. The full combination points the team toward the applicable LCD, diagnosis support and documentation. CO-50 alone does not.

Group codes: who is responsible

The group code changes the operational response. PR-1 may appropriately move to patient billing, while an unexpected CO-1 combination should be reviewed before posting. That is why the group code and CARC need to be interpreted together.

Claim Adjustment Reason Codes: why the claim was adjusted

Claim Adjustment Reason Codes, or CARC codes, explain why a payer changed the billed amount. CO-16 points to missing information or a submission error. CO-97 points to a service included in payment for another service. Read the group code with the number.

Remittance Advice Remark Codes: the extra detail

Remittance Advice Remark Codes, or RARC codes, add context the CARC cannot carry alone. They generally begin with M, MA or N. A RARC paired with CO-16 can identify the missing diagnosis, procedure, provider identifier or authorization data. Informational RARCs communicate processing information rather than explain an adjustment.

Read the RARC before choosing the work. MA130 says the claim is unprocessable because information is incomplete or invalid and that appeal rights are not available. Sending it to appeals adds time without changing the outcome. Correct it and resubmit it.

Common RARC codes and what to check next

The CARC sets the adjustment category. The RARC often determines the work. Read the two together before correcting, replacing or appealing the claim.

The most common denial codes and how to prevent them

Denial frequency varies by payer, specialty and patient population. Aptarro's medical billing statistics show how widely reported denial benchmarks differ. A single industry average cannot tell you whether a code is concentrated in one payer, one service or one location, or whether it represents a denial at all. The table below connects common codes to the upstream decision that can prevent repeat work.

*X12 specifies CARC 18 with group code OA except where workers' compensation rules require CO.

Missing or invalid information

CO-16 generally needs a RARC because the CARC alone does not identify the missing element. CO-252 points to an attachment or other documentation required to adjudicate the claim. Validate required fields, identifiers and documentation rules through claim scrubbing before submission, then confirm attachments reach the payer through the expected channel.

Eligibility and coverage

CO-22, CO-27, CO-109 and CO-204 often begin with front-end coverage information. Verify eligibility before the visit and repeat the check for recurring patients, scheduled procedures and plan-year changes.

Prior authorization

CO-197 indicates that required authorization, notification or pretreatment approval was absent. Requirements vary by payer, plan, service, provider and site. Check them before the service and match the authorization to the billed service, provider, date and units.

Medical necessity and diagnosis mismatch

CO-50, CO-11, CO-167 and CO-151 point toward the relationship among the diagnosis, procedure, documented frequency and coverage policy. RARCs such as N115 and N386 may identify the LCD or NCD behind the decision. Apply diagnosis-procedure and coverage checks during pre-claim charge review while the encounter context is still available.

Bundling and modifier errors

CO-97, CO-4 and CO-236 frequently affect procedure-heavy specialties because bundling, modifier and same-day procedure rules vary by specialty and payer. Prevention requires more than a generic code-set check. It requires current specialty logic, the documented relationship between services and payer-specific handling. RCx applies more than 2,000 payer, clinical and coding checks across 36-plus specialties before the claim is created.

Duplicates and timely filing

OA-18 often begins with a resubmission while the original claim is pending. CO-29 may reflect rejections, corrections or queue delays that consumed the filing window. Check claim status before resubmission and monitor payer acceptance, not only the date the claim left the billing system.

Patient responsibility and contractual adjustments

PR-1, PR-2 and PR-3 represent deductible, coinsurance and copay amounts. CO-45 or PR-45 represents a reduction to a fee schedule, contracted allowance or other maximum. These are usually adjustments, not denials to appeal. Put them in the preventable-denial rate and the organization spends time improving a number that was misclassified from the start. A recurring CO-45 amount that conflicts with the contract, however, may indicate an underpayment worth investigating.

A denial code records the decision, not the change behind it

Working denial codes one claim at a time is reactive by design. Staff correct the claim, appeal it or write it off. The claim may be resolved while the workflow that produced it remains untouched. The same code then returns on the next remit.

Here is the asymmetry. A national payer can see the same procedure, modifier and diagnosis combination across thousands of provider organizations. A physician group or health system only sees its own claims. By the time a change becomes obvious in an internal denial report, the affected revenue is already at risk and the appeal clock is running.

Published policy explains what should happen while claims and remittances reveal what the payer actually did. The first evidence of a new interpretation may be a rising combination of payer, procedure, CARC and RARC, not a policy bulletin. One side of the transaction compounds what it learns. The other fixes one claim at a time.

Volume can also mislead. The most common code may reflect growth or normal contractual adjustments. A smaller combination accelerating within one payer, service or market may carry the greater financial risk. Frequency matters. Movement and concentration matter more.

What recurring denial codes reveal about payer behavior

A spike in CO-197 after an authorization update can expose a workflow that has not caught up. CO-97 appearing on a procedure pair that previously paid may signal a bundling change. CO-50 rising within one specialty and region can reveal a coverage interpretation hidden by a systemwide average. The code names the adjustment; however, the recurring combination reveals what changed.

RemitIntel analyzes payment outcomes and policy signals across a network spanning more than 500 million annual transactions and 130,000 providers, alongside 30,000 policy changes each month. That broader view helps distinguish an isolated denial from a pattern concentrated within a payer, specialty, service combination or market.

One behavioral health pilot analyzed 1.3 million charges and connected approximately 17,500 denials to eight recommendations representing about $1.6 million in denied charges. The strongest signals centered on CPT 96127: bundling with psychotherapy, psychiatric evaluation and E/M services; modifier use intended to bypass edits; repeat screening frequency; and payer-specific nonpayment. Other patterns included H2013 billed without an HA or HB modifier and 90868 appearing without prerequisite 90867.

That specificity changed the decision. The team could correct deterministic, payer-aligned findings, route documentation-dependent cases for review and audit existing logic when denials suggested it was not firing. Some expected denials could remain in the billing flow to support payer and contract discussions. Financial estimates from the pilot were projections, not realized results.

An ophthalmology pilot with Vision Innovation Partners surfaced denials rooted in policy rather than missing documentation. Refraction and contact-lens services such as 92015, 92310 and 92311 were not payable under medical policy; more documentation would not change the outcome. Diagnostic tests including 76514, 92133 and 92250 showed bundling and frequency constraints. For some exam-and-testing combinations, modifier 25 did not override same-day payment policy. The useful action was to suppress, reroute or review the charge before submission, not appeal it again.

Clinical, coding and reimbursement specialists validate each finding before it becomes a recommendation. The customer decides whether to approve it, monitor it or reject it. Vision Innovation Partners reduced preventable denials from 2.9% to 1.5% after approved patterns were carried into earlier decisions.

A six-step playbook for denial prevention

The tool can be a dashboard, a spreadsheet or a reimbursement intelligence platform. The operating discipline is the same:

1. Track the complete combination. Capture the group code, CARC, RARC, payer, plan, procedure, provider, location, specialty, adjustment amount and claim or line level.
2. Separate denials from expected adjustments. Remove PR deductible, coinsurance and copay amounts and expected contractual reductions from preventable-denial reporting.
3. Prioritize by dollars and movement. Identify the few root causes driving the most reimbursement risk, then look for combinations that are new, accelerating or concentrated.
4. Trace the remit back upstream. Compare the outcome with the submitted 837, encounter documentation, authorization, payer policy and contract.
5. Change the earlier decision. Put the validated correction into charge review or claim creation rather than leaving the lesson in the denial queue.
6. Measure the next remits. Confirm whether the change reduced the code combination, improved payment and removed staff work without creating false positives.

Step five is the economic test. RCx can apply approved logic before a claim exists, while ClaimStaker applies it to completed claims before submission. If the lesson never changes an earlier decision, the organization has better reporting. It does not yet have denial prevention.

Denial codes FAQ

What are denial codes?

Denial codes are standardized codes on an EOB or electronic remittance advice that explain why a payer denied or adjusted a claim or service line. The full message may include a group code assigning responsibility, a CARC explaining the adjustment and a RARC adding detail.

How do I find the denial code on an EOB or ERA?

Look near the adjusted claim or service line for a two-letter group code followed by a numeric CARC, such as CO-97 or PR-1. A separate M, MA or N code may appear as the RARC. In an 835 file, the adjustment appears in CAS segments with related remarks in the remittance detail.

What is a 252 denial code?

CARC 252 means the payer needs an attachment or other documentation. Read the accompanying RARC to identify what is missing, then confirm the record reached the payer in the required format before correcting the claim.

What is the difference between a CARC and a RARC?

A CARC gives the broad reason payment changed. A RARC adds the detail needed to interpret the adjustment or communicates separate remittance information. CO-16 identifies missing information or a billing error; the paired RARC should identify the specific field, code or identifier involved.

Is CO-45 a denial?

Usually not. CARC 45 means the charge exceeded a fee schedule, contracted allowance or other maximum, and the adjustment cannot equal the full charge. Compare the amount with the contract. Investigate when the reduction is inconsistent, but do not automatically count every CO-45 as a preventable denial.

How often are CARC and RARC codes updated?

X12 publishes code-list updates throughout the year. Individual codes can be added, revised, deactivated or assigned new effective dates. Use the current X12 lists and record a review date for internal references rather than relying on an undated spreadsheet or payer cheat sheet.

Move the lesson upstream

Knowing what a denial code means can fix one claim. Knowing why it is rising, where it is concentrated and which earlier decision should change can prevent the next hundred. RemitIntel connects recurring codes across more than 500 million annual transactions to the payer behavior behind them, so the lesson reaches the workflow before the next remit.

See RemitIntel in action

Editorial sources

• X12 Claim Adjustment Reason Codes
• X12 Remittance Advice Remark Codes
• X12 Code Updates
• CMS Health Care Payment and Remittance Advice
• Aptarro Medical Billing Statistics
• Aptarro RemitIntel