RARC N935: Patient No Longer a Medicaid or Qualified Medicare Beneficiary
Informational alert: the patient's Medicaid or Qualified Medicare Beneficiary (QMB) status has ended as of this claim's processing. Verify current eligibility before making any billing decisions — do not assume prior QMB protections still apply.
What Does RARC N935 Mean?
N935 is an alert-type remark rather than a denial. It appears on the remittance to notify the billing office that the patient no longer shows as an active Medicaid recipient or Qualified Medicare Beneficiary at the time the claim was adjudicated, even if that status was in effect previously. Dual-eligible patients — those enrolled in both Medicare and Medicaid, including under the QMB program — receive protection from being billed for Medicare deductibles, coinsurance, and copayments while that status is active. When Medicaid or QMB coverage lapses, that protection is tied to the coverage period, and this alert exists specifically to flag that the coverage picture has changed.
Dual eligibility is not static. States redetermine Medicaid and QMB eligibility on a recurring basis, and enrollment can start or stop mid-month for reasons unrelated to the patient's ongoing clinical situation — income changes, redetermination paperwork, administrative processing delays, or a gap between when a state updates its eligibility file and when that update reaches Medicare's systems. N935 is the payer's way of telling you that, as of processing, its records no longer reflect active status, without necessarily telling you why or exactly when the change took effect.
Because this is an informational alert rather than a payment adjustment, N935 doesn't by itself change what's owed on the claim. What it does is remove the assumption that this patient's QMB or Medicaid protections are still in force. The billing office needs to treat the patient's cost-sharing status as unconfirmed until it is independently verified, rather than carrying forward whatever status applied on a previous claim.
What to Do
Before making any decision about patient billing, verify the patient's current Medicaid and QMB status directly with the state Medicaid eligibility system or the relevant state's provider portal — do not rely solely on the payer remittance or on the patient's self-reported coverage, since both can lag actual eligibility changes. Check the specific date range the eligibility change applies to, since coverage can lapse and later be reinstated retroactively in some states, which would restore balance-billing protections for the affected period.
If verification confirms QMB or Medicaid coverage has genuinely ended for the service date in question, follow your standard process for coordinating benefits and determining patient responsibility under the now-applicable coverage. If verification shows the patient's status is still active or was reinstated, note this in the account and treat the balance-billing restrictions as still in effect for that service date, since billing a QMB beneficiary for Medicare cost-sharing while their protections apply is a compliance risk independent of what appears on a single remittance.
Common Scenarios
- A patient who was QMB-eligible at the time of a January visit shows N935 on the remittance for a March claim, prompting the billing office to check whether the patient's status genuinely lapsed or the state's file simply hadn't updated.
- A dual-eligible patient completes their annual Medicaid redetermination late, causing a temporary gap in active Medicaid status that generates N935 on claims processed during the gap, before coverage is reinstated retroactively.
- A patient moves to a new state and their prior state's Medicaid/QMB enrollment is closed, but the new state's enrollment hasn't yet taken effect, producing this alert on claims submitted during the transition.
- A billing office sees N935 and, without verifying current status, prepares a patient statement for Medicare cost-sharing before confirming whether the patient's QMB protections were actually still active for that date of service.
Commonly Paired With
No common pairings documented yet.