RARC M39: Missing or Invalid Date of Service or Admission Date

What Does RARC M39 Mean?

M39 tells you that the payer found a problem with the date of service (on professional claims) or the admission or discharge date (on institutional claims). This is a fundamental data element — without a valid date, the payer cannot determine benefit eligibility, timely filing compliance, fee schedule applicability, or coordination with other claims for the same patient. Even a single-digit error in a date field can prevent adjudication.

Common triggers for M39 include a completely blank date field, a date in an unrecognized format, a date that falls in the future, or a date range where the "from" date is after the "to" date. On institutional claims, inconsistencies between the admission date, discharge date, and statement covers period can also produce this remark. Less obviously, some payers flag dates that fall on impossible calendar dates (such as February 30) or dates that predate the patient's coverage effective date.

M39 typically pairs with CARC 16 (missing information) or CARC 252 (additional information required). While it may seem like a simple data entry fix, recurring M39 denials across multiple claims often point to a systemic issue — such as a billing system integration that drops or reformats dates during electronic claim generation.

What to Do

Check the date fields on the claim — date of service for professional claims, or admission date, discharge date, and statement covers period for institutional claims. Compare them against the patient's medical record to confirm the correct dates. Fix any blank fields, formatting errors, or logical inconsistencies (such as a discharge date before the admission date). Resubmit the corrected claim.

If M39 is appearing across a batch of claims, investigate the data pipeline from your scheduling or registration system through to claim generation. Date formatting mismatches between systems — such as MM/DD/YYYY versus YYYY-MM-DD — can cause widespread issues that look like random errors on individual claims but have a single root cause. Testing a small batch of claims through your clearinghouse after any system update can catch these problems early.

Common Scenarios

• A professional claim is submitted with the date of service left blank because the encounter was entered into the EHR but the date did not carry over to the billing system due to an interface error.
• An inpatient claim lists an admission date of 03/15/2026 but a discharge date of 03/12/2026, creating a logical impossibility that the payer rejects with M39.
• A batch of claims generated after a billing system update has dates formatted as DDMMYYYY instead of MMDDYYYY, causing the payer to interpret them as invalid dates.

Commonly Paired With

No common pairings documented yet.