MHCP claim denials are a solvable problem, because Minnesota Health Care Programs (MHCP) and the managed care organizations (MCOs) that pay on its behalf tell you exactly why a line did not pay. The answer is on the 835 electronic remittance advice as a claim adjustment reason code and a remark code. Read those two codes, match them to one of about eight recurring causes, and the fix is usually a corrected claim.
For Minnesota home and community-based agencies, the recurring causes are client eligibility gaps, missing or exhausted authorizations, unit and code mismatches, electronic visit verification (EVV) mismatches on PCA and CFSS visits, missing modifiers, provider enrollment or affiliation problems, duplicate submissions, and late filing. Each has a specific correction and a specific pre-claim check that prevents it.
This guide covers the claim flow, reading a remit, the common denial categories and fixes, timely filing and replacement claims, MCO appeals, and denial tracking, as of September 2026.
How an MHCP claim flows from note to payment
Every claim starts with a documented service: a progress note, a visit record, or an attendance record. From there the professional claim (837P) reaches the payer by one of three routes:
| Route | How it works | Typical user |
|---|---|---|
| MN-ITS direct data entry (DDE) | Staff key each claim into the DHS MN-ITS web portal | Small agencies, low volume |
| MN-ITS 837P batch | Software generates an 837P file and uploads it to MN-ITS | Agencies with an EHR or billing system |
| Clearinghouse | Software sends claims to a clearinghouse, which routes them to MHCP and to MCOs | Agencies billing several payers |
Fee-for-service MHCP claims go to DHS. Clients enrolled in a prepaid health plan are billed to that MCO under its own rules, though the codes and most edits mirror MHCP. DHS sends remits and policy notices to the provider's MN-ITS mailbox, so someone should read that mailbox at least weekly.
Reading the 835 remittance advice
The 835 lists each claim and service line with the billed amount, the paid amount, and any adjustment. An adjustment carries a group code, a claim adjustment reason code (CARC), and often one or more remittance advice remark codes (RARC). Both code sets are maintained by X12 and published on the CARC list and the RARC list.
- Group code says who is responsible: CO (contractual obligation, the provider absorbs it), PR (patient responsibility), OA (other adjustment).
- CARC says why the line paid differently than billed. Example: CO-16 "claim/service lacks information or has submission/billing error(s)."
- RARC adds detail. Example: M53 "missing/incomplete/invalid days or units of service," or N30 "patient ineligible for this service."
A CO-16 alone is not actionable; CO-16 with M53 is. Billing software should post the 835 automatically and show both codes on the claim line, not just a paid or denied flag.
The most common MHCP denial reasons and their fixes
The table maps each cause to the codes you will typically see and the correction. Code assignments vary by payer, so treat the codes as examples to look for, not a guarantee.
| Denial cause | Codes you may see | Fix |
|---|---|---|
| Client not eligible on the date of service, or wrong payer (MCO vs fee-for-service) | CO-31, CO-26, CO-27, CO-22, N30 | Recheck eligibility in MN-ITS for the date of service; rebill the correct payer; if coverage was added retroactively, resubmit |
| No authorization, or authorized units exhausted | CO-197, CO-198, CO-119 | Confirm the service agreement number and remaining units; request an amendment from the case manager or MCO; rebill only once units exist |
| Units or code do not match the authorization or the note | CO-151, M53, CO-96 | Correct units to the documented start and stop time; confirm the code matches the authorized service; replace the claim |
| EVV mismatch on a PCA or CFSS visit | Varies by payer; often a units or documentation code with a DHS EVV notice | Correct or verify the visit in the EVV system so the aggregator has it; then submit or replace the claim with matching dates and units |
| Missing or wrong modifier | CO-4 | Add the modifier the MHCP manual requires for the service and provider type; replace the claim |
| Provider not enrolled, affiliation missing, or NPI mismatch | CO-208, CO-16 with a provider RARC | Fix the provider record in the MPSE portal; confirm the rendering provider is affiliated to the billing organization; resubmit |
| Duplicate claim | CO-18 | Do not resubmit; find the original claim and, if it paid wrong, replace it instead |
| Timely filing expired | CO-29 | Usually unrecoverable; appeal only if you can prove timely submission or a payer error |
Eligibility and span problems
Minnesota eligibility changes monthly, and clients move between fee-for-service and MCOs. Check eligibility in MN-ITS for every date of service before billing, not once at intake. For ARMHS and EIDBI, also confirm the program covers the service; the ARMHS billing guide and the EIDBI billing codes guide explain the checks specific to each program.
Authorization and unit problems
Waiver, CFSS, EIDBI, and adult day services are authorized in units for a date span. A claim that exceeds the remaining units, falls outside the span, or uses a different code than the authorization will deny. Track authorized units against billed units in real time so the shortfall shows up before the claim. The CFSS billing guide and the adult day services billing guide cover the authorization mechanics for those programs.
EVV mismatches
Since January 1, 2026, providers must be enrolled in HHAeXchange and submit complete data for all PCA and CFSS visits, including noncompliant ones, and at least 80% of visits billed after July 1, 2026 must be EVV compliant. DHS compares claims to visits, and manually entered or missing visits count as noncompliant. A claim whose date, client, worker, or units do not match a verified visit is a denial or recoupment risk. Details are in the Minnesota EVV requirements guide.
Audit tip: when an EVV-related denial arrives, fix the visit record before touching the claim. Replacing a claim to match a bad visit record creates a documentation conflict that shows up in a DHS review.
Timely filing and how to correct a claim
As of September 2026, the MHCP Provider Manual billing policy chapter requires that MHCP receive a correctly submitted claim no later than 12 months from the date of service. A replacement claim must be submitted within six months of the date of the incorrect payment or 12 months from the date of service, whichever is later. A claim voided after the timely filing window cannot be resubmitted. Confirm these rules in the current manual; MCOs may set different limits in their provider contracts.
Replacement claims (frequency code 7)
Under the Minnesota Uniform Companion Guides and the AUC replacement/void best practice, a replacement claim is used when a claim paid, but paid incorrectly, or a line was denied and needs correction. It carries:
- Bill frequency code 7 in Loop 2300, CLM05-3.
- The payer's claim number for the claim being replaced in Loop 2300, REF02 with REF01 = F8.
- Every line from the original claim, corrected as needed. A replacement replaces the whole claim, not one line.
- The same provider, patient, payer, and subscriber as the original.
Wait until the original claim reaches final adjudication on the remit before replacing it. In MN-ITS DDE, DHS provides a replace function that opens the paid claim for correction.
Void claims (frequency code 8)
A void deletes the claim and takes back the payment. Use it when the identifying information was wrong: wrong provider, wrong patient, wrong payer, or the client did not want the insurer billed. After the void finalizes, submit a new original claim if one is due, and make sure that new claim is still inside the 12-month window.
MCO denials and the 60-day appeal window
Health plan appeals generally must be filed within 60 days of the remit date. Each MCO publishes its own provider appeal procedure. An appeal packet should contain the claim number, the remit page, the CARC and RARC, the authorization, the progress note or EVV visit record, and a one-paragraph explanation of why the denial was incorrect.
Because the MCO clock is shorter than the MHCP timely filing window, work MCO denials first in the weekly denial queue. Log every appeal with its filing date and outcome; an appeal that succeeds usually points to a pre-claim rule you should add.
Preventing denials with a pre-claim check
Most denials are visible before the claim is sent. A pre-claim check is a list of conditions a claim must pass to leave the building:
- Client eligible on the date of service, with the correct payer identified.
- Active authorization covering the code, the date, and enough remaining units.
- Progress note, visit record, or attendance record complete, signed, and co-signed where required.
- Units on the claim equal the units supported by the documented time.
- Procedure code and modifier match the MHCP manual for the service and provider type.
- Rendering provider enrolled, affiliated, and credentialed on the date of service.
- For PCA and CFSS, the EVV visit is verified in the aggregator and matches the claim.
- No prior claim for the same client, service, and date unless this is a replacement.
Run the check as a hard gate in software if you can, or as a checklist before batch submission if you cannot. Either way, route each failure back to the person who created it, not the biller alone. If your current system cannot enforce the gate, the Procentive alternatives guide lists what to require from a replacement before you switch.
Tracking your denial rate
Measure denials as denied lines divided by submitted lines, split by payer and by CARC, and review it monthly. If eligibility and authorization denials dominate, the pre-claim check is missing or bypassed. If unit, code, and modifier denials dominate, the documentation template or code mapping is wrong; fix it once and the category disappears. If any timely filing denials appear, claims are aging unseen; move to a weekly claim cycle and put the unbilled-services report in front of an owner. Also track days from date of service to submission and days from denial to resolution; cash follows those two numbers.
How Trustora helps
Trustora runs the claims lifecycle for ARMHS, 245D, PCA/CFSS, EIDBI, and adult day services in one system: eligibility checks, 837P generation, ERA/835 reconciliation, denial work queues, and appeal packets assembled from the note, the authorization, and the remit. The compliance engine applies a pre-claim gate that checks eligibility, authorization units, note completeness, code and modifier, provider affiliation, and, for PCA and CFSS, the EVV visit status before a claim can be released.
When a denial comes back, the CARC and RARC are posted to the claim line automatically, the correction opens as a replacement claim with the original payer claim number carried forward, and the MCO appeal deadline is tracked from the remit date. Denial rates are reported by payer and reason code so the pattern is visible. See the platform overview for the claims and compliance features.