Official Definition
The official X12 definition of Claim Adjustment Reason Code 16 is "Claim/service lacks information or has submission/billing error(s). Usage: Do not use this code for claims attachment(s)/other documentation. At least one Remark Code must be provided (may be comprised of either the NCPDP Reject Reason Code, or Remittance Advice Remark Code that is not an ALERT.) Refer to the 835 Healthcare Policy Identification Segment (loop 2110 Service Payment Information REF), if present."
In plain language:
Claim Adjustment Reason Code 16 is vague on purpose. It is designed as a catch-all for administrative denials and occurs before the claim even reaches the adjudication stage. These denials happen when a payer's automated claims validation engine flags a formatting or data entry error. These are considered "soft" denials. They are almost always preventable and most are completely recoverable as long as they are addressed immediately.
CARC 16 requires a Remittance Advice Remark Code (RARC) to fully understand the denial. If you do not see the RARC, sometimes listed as a "Remark Code" or just "Remark", your EHR might be suppressing it or it might be difficult to find. The location in your EHR depends on your system. If you are not able to find remark codes with CARC 16 please make sure to reach out to your EHR provider for help locating that field or making sure it is available if the system is suppressing it. You can also find this information in the MOA (for outpatient claims), MIA (for inpatient claims) or LQ segment on your raw 835 file.
Audits and Frameworks
CARC 16 denials can be prevented by auditing denials to identify trends. Start with pulling a report with all CARC 16 denials and sort by RARC to identify categories. The RARC tells you the exact error that needs to be corrected. In most cases, you should be able to create front end audits to check for these errors and flag claims that fail the front-end audit so they can be corrected before they go out the door.
Creating a framework that checks for issues BEFORE the claim is billed means less time spent correcting errors after claims are denied.
Example Pairing and Strategy: CARC 16 + RARC M123
X12 Official Definition of RARC M123: Missing/incomplete/invalid name, strength, or dosage of the drug furnished.
What this CARC+RARC pair actually means: CARC 16 with RARC M123 means that the submitted claim was either missing the name, strength or dosage of a drug that was provided, or the name, strength, or dosage was invalid or incomplete.
Targeted Action Plan:
- Review the medication order(s) and documentation to obtain the correct information about the name, strength, or dosage of the drug.
- Populate the correct drug detail and NDC in the correct location in the claim (loop 2410).
- Resubmit the corrected claim.
Appeal Tips:
- In most cases an appeal is not required. Instead, review the information on the claim and compare it to the documentation and the medication information.
- Validate the correct drug name, dosage, or strength and correct the data on the claim.
- 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.
Prevention Strategy:
- Implement front-end claim edits for all outgoing claims to validate 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 categorizing by RARC and element type.
- Address recurring deficiencies with process updates, staff training, and updated front end edits and claims scrubbers.
✓ Verified 2026-06-16 · Source: ASC X12
- 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.
- 100% Preventable with the correct claims scrubbing process and claim audits.
- Review the RARC for full denial details.
- Some EHRs suppress the RARC or the RARC is in a field that is not readily apparent. If the RARC is suppressed, work with your EHR provider to ensure the RARC is visible and verify the field that it appears in. It is critical for these denials.
- Rarely Requires an appeal
- Review RARC and make required corrections
- Submit corrected claim (do not forget to enter the claim number and update the claim frequency code so the claim is not denied as a duplicate).
- 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.
- 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.
- Review the medication order(s) and documentation to obtain the correct information about the name, strength, or dosage of the drug.
- Populate the correct drug detail and NDC in the correct location in the claim (loop 2410)
- Resubmit the corrected claim.
- In most cases an appeal is not required. Instead, review the information on the claim, and compare it to the documentation, and the medication information
- Validate the correct drug name, dosage or strength and correct the data on the claim
- 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
CARC 16 is vague on purpose. It is designed as a catch-all for administrative denials before the claim reaches the adjudication stage. These denials happen when a payer's automated claims validation engine flags a formatting or data entry error. These are preventable denials, and completely recoverable, but require a RARC to fully understand the error.
Complete the Story. Find and Understand the RARC
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 address CARC 16 without reading the RARC is trying to understand a book by reading just the title.
The Most Common CARC 16 + RARC Pairings
While CARC 16 can be paired with any number of RARCs, some of the RARCs most often seen with CARC 16 are shown in the table below. The fix is shown in the last column.
| 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. |
Final Thoughts
Don't forget to run a 90-day look-back at your CARC 16 denials and group them by RARC. You will likely find two or three RARCs that account for 80% of the volume. Use those to create workflow strategies and training 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