Common drivers: Missing or invalid data element (NPI, taxonomy, demographics, POS code, procedure or diagnosis code, dates) or a format error; almost always reflects a correctable submission defect.
- Missing or invalid data element (NPI, taxonomy, demographics, POS code, procedure or diagnosis code, dates) or a format error; almost always reflects a correctable submission defect.
- Obtain the drug name, strength, and dosage from the MAR/order
- Populate the drug detail and NDC (loop 2410)
- Resubmit the corrected claim.
- Appeal with the MAR/pharmacy record documenting the drug
- Cite the NDC/drug reporting policy
- Attach the order and administration record.
- If a corrected claim is required:
- Submit a corrected claim, making sure that the claim frequency code is updated ("7", in most cases) to prevent being denied as a duplicate, and the payer's original claim number is included
- For ALL reworked claims (appealed/corrected/resubmitted):
- Your standard workflow process should include a 24 hour follow up to check in with the clearinghouse to validate that all corrected claims show "accepted" and that they have not been rejected as a duplicate
- Set a follow up date and track the claim to ensure timely payment
- Implement front-end claim edits in the clearinghouse and PM system validating all required data elements before transmission.
- Monitor clearinghouse acknowledgment reports on every batch; claims with no acknowledgment must be investigated and resubmitted within 24 hours.
- Conduct quarterly audits of CARC 16 denials by element type and address recurring deficiencies with system fixes or staff training.
What CARC 16 Actually Means
Claim Adjustment Reason Code (CARC) 16 is one of the most common denial codes payers use, but it is also one of the easiest to fix if you understand the full story. CARC 16 denials are administrative denials that happen when claims do not pass verification checks through the payer's automated validation system. This means that the claim is missing required information, contains incomplete data, or has a submission error. The payer is not saying the service isn't covered. They're saying they can't process the claim as submitted.
The RARC Completes the Story
CARC 16 is incomplete by design. It is intended to be used as a catch-all for multiple errors that fail automated administrative checks. RARCs are required to carry the heavy lifting for these denials. ANSI X12 standards require that CARC 16 is always paired with a RARC. Attempting to appeal CARC 16 without reading the RARC is like reading a chapter title without the chapter, and it is the single most common source of repeat denials on an otherwise straightforward category.
Always read the RARC alongside CARC 16. The CARC only tells you PART of the story. The RARC gives the back story that makes it come alive and gives you the details you need to file an effective appeal.
The Most Common CARC 16 + RARC Pairings
CARC 16 pairs with dozens of RARCs depending on the payer, service type, and the specific missing element. These pairings account for the majority of CARC 16 denials in most practice settings. Each is a different problem with a different fix, all of which look identical from the CARC alone.
| RARC | Combined Meaning | Immediate Action |
|---|---|---|
| MA27 | Missing/incomplete/invalid entitlement number or name shown on the claim | Obtain the patient's current Medicare card. Verify the MBI (11 characters, alphanumeric) and confirm the patient's name exactly matches the card. Correct the claim field and resubmit. |
| MA61 | Missing/incomplete/invalid Social Security Number | Confirm the correct SSN in your practice management system and resubmit. Note: Medicare no longer uses MA61 for patient ID issues; an invalid HICN/MBI will return N382 instead. MA61 now appears only for actual SSN problems. |
| N290 | Missing/incomplete/invalid rendering provider primary identifier | Confirm the rendering provider's NPI is in the correct loop (2310B / Item 24J). Verify the NPI is active AND linked to the billing group in the payer's enrollment records. An active NPI not associated with the group still triggers N290. Resubmit a corrected claim. |
| M124 | Missing indication of whether the patient owns the equipment that requires the part or supply | Common on DME part/supply claims. Confirm whether the patient owns the base equipment, add the ownership indication to the claim narrative (NTE segment / Item 19), and resubmit. |
| N479 | Missing Explanation of Benefits (Coordination of Benefits or Medicare Secondary Payer) | Obtain the primary payer's EOB or adjudication detail and submit it with the claim or complete the COB/MSP fields in the 837. Confirm the payer's COB records are current; the patient may need to update their coordination of benefits. |
| MA130 | Claim contains incomplete/invalid information and is unprocessable; no appeal rights | Do not appeal. Unprocessable claims carry no appeal rights. MA130 never identifies the error by itself. Find the accompanying remark code(s) that specify what's wrong, correct it, and submit a NEW claim (not a corrected claim or appeal). |
| N382 | Missing/incomplete/invalid patient identifier | This is what Medicare now returns for HICN/MBI problems (replaced MA61 for identifier issues). Obtain the current Medicare card, verify the MBI, and resubmit. |
| N257 | Missing/incomplete/invalid billing provider/supplier primary identifier | Verify the billing NPI is active in the CMS NPI Registry and matches the payer's enrollment file. Confirm correct placement (Loop 2010AA / Item 33a) and resubmit. |
Where to Find the RARC on Your 835
The RARC can be found in the 835 at the claim level in the MOA segment for professional claims, or MIA segment for institutional claims. At the service level, the RARC will be in the LQ segment with qualifier "HE" in loop 2110 following the SVC segment. A RARC is REQUIRED with CARC 16. Most billing software will show the RARC as a separate field labeled as "Remark Code." The two codes together should look something like: CO-16/MA27, for example. If your billing software shows only CARC 16 without a RARC you should investigate to see why it is suppressing the remark code.
The location of these codes varies depending on what EHR or PM system you are using. Look for a section called "Remark Code(s)" or "Remark." If you only see the CARC and no remark code, your system might be suppressing the remark code. This is something you will need to investigate. The raw 835 will always contain both the CARC and RARC.
Most Common Root Causes
- Missing NPI. Referring provider, rendering provider, or facility NPI is absent or doesn't match payer records.
- Incomplete claim data. Required fields left blank, date of service, units, place of service, diagnosis pointer.
- Invalid data format. Date formatted incorrectly, ICD-10 code with the wrong number of characters, or an NPI that doesn't pass the formatting review.
- Missing required attachments. The payer requires documentation (prior auth, referral, clinical notes) that wasn't submitted with the claim.
How to Fix It
- Pull the 835 and locate the CARC and RARC details.
- Identify the data element that the RARC code refers to.
- Correct the missing or incorrect data on the claim.
- Update the claim frequency code and enter the original claim number in the appropriate data field and submit a corrected claim (not a new claim) or use the payer portal to update the information, if that is the payer's preferred process.
- If an attachment is required, submit it with the corrected claim and note the attachment control number.
How to Appeal
If you believe the original claim contained the required information and the denial was a payer processing error, appeal with a copy of the original claim, a copy of the 835 remittance, and a letter identifying the specific field the payer flagged and demonstrating it was populated correctly.
In most cases, CARC 16 denials should be corrected rather than appealed, because there is genuinely an error on the claim that needs to be fixed. The appeals process should be reserved for situations where the data was submitted correctly and the payer's system failed to read it.
How to Prevent It
CARC 16 denials are process failures, not payer issues. Every CARC 16 you receive is a claim that made it through your internal review with missing data. Prevention requires you implement the following:
- A pre-submission claim scrubber with required field validation turned on for every payer; no exceptions.
- Payer-specific edit rules for attachment requirements. These vary by payer and procedure type.
- An NPI crosswalk audit to ensure every rendering and referring provider in your system has a valid NPI on file, and that the NPI numbers are correctly recorded and documented in your PM system.
- Front-end training so intake staff understand which fields create downstream billing problems when left blank.
Run a 90-day lookback on your CARC 16 denials and group them by RARC. You will almost always find two or three RARCs accounting for 80% of the volume, and those are your training and workflow priorities.
Search the full CARC/RARC database
Every denial code includes what it means, why it happens, how to fix it, how to appeal it, and how to prevent it from coming back.
Search the EDI Lab