MHCP timely filing has one core rule: Minnesota Health Care Programs (MHCP) must receive a correctly submitted claim no later than 12 months from the date of service. The MHCP Provider Manual billing policy chapter states it, and Minn. R. 9505.0450, subp. 2 sets the same limit in rule. Medicare crossover claims and third party liability (TPL) claims are inside the rule, not outside it.
Around that rule sit a replacement window, a short list of exceptions, and one trap. Replacement claims get six months from the incorrect payment or 12 months from the date of service, whichever is greater. The exceptions in Minn. R. 9505.0450, subp. 4 each carry their own six-month clock. And a claim voided after the timely filing window cannot be resubmitted, which turns a careless void into a permanent write-off.
This guide covers the 12-month rule, the replacement window, the exceptions you can cite, how managed care limits differ, how to prove timely submission, the void and replacement mechanics, and an unbilled services routine. It reflects the manual and rule as of September 2026.
The 12-month rule from the date of service
The measure is receipt by MHCP, not the date you sent the claim. The Department of Human Services (DHS) publishes Payment and Claim Cut-off Calendars (DHS-3947K) with a cut-off at 11:59 pm for each payment cycle, and its own advice is to bill early and bill often. A claim that arrives at MHCP on day 366 after the date of service is late regardless of when it left your system.
"Correctly submitted" matters as much as the date. A batch that MHCP rejects on a TA1 or 999, or a claim rejected on a 277CA, never entered adjudication and was not received for timely filing purposes. The 837P claim guide explains those front-end rejections. A claim that is received and then denied on the remittance advice was received, and the 12-month clock for correcting it keeps running from the date of service.
| Situation | Deadline | Source |
|---|---|---|
| Original claim, including Medicare crossover and TPL claims | Received within 12 months of the date of service | MHCP billing policy; Minn. R. 9505.0450, subp. 2 |
| Replacement claim after an incorrect payment | Within 6 months of the incorrect payment or 12 months from the date of service, whichever is greater | MHCP billing policy |
| Medicare crossover that did not cross automatically | Within 6 months of the Medicare determination or adjudication date, or 12 months from the date of service, whichever is greater | MHCP billing policy |
| Claim MHCP denied in error (system error or incorrect county information) | Within 12 months of the date of service or 6 months from the county correction, whichever is greater | MHCP billing policy |
| Claim over one year old | Submit with appropriate dated documentation; MHCP reviews but does not guarantee payment | MHCP billing policy |
| Claim voided after the timely filing window | Cannot be resubmitted | MHCP billing policy |
The replacement claim window
A replacement claim corrects a claim that paid, but paid incorrectly, or that had a line denied. It must be received within six months of the date of the incorrect payment or within 12 months from the date of service, whichever is greater. The six-month rule extends the window only when the incorrect payment itself came late in the year.
The replacement is a whole-claim transaction. Under the Minnesota Uniform Companion Guide and the AUC replacement and void best practice, it carries claim frequency code 7 in CLM05-3, the original payer claim number in REF*F8, and every line from the original, corrected as needed. Wait for the original to reach final adjudication on the remittance before sending it. The MHCP claim denials guide maps the denial codes that most often lead to a replacement.
The exceptions you can actually cite
Minn. R. 9505.0450, subp. 4 lists four situations in which a claim may be submitted more than 12 months after the date of service. Each has a six-month window.
| Exception | Window | What you must show |
|---|---|---|
| A Medicare claim was filed first | Within 6 months of the Medicare determination | The Medicare remittance and its date |
| Payment was ordered by a court | Within 6 months of the court order | The order |
| The department had erroneous or incomplete information about the recipient's eligibility | Within 6 months of the erroneous determination | The eligibility notice or county correction |
| The department erroneously rejected the claim | Within 6 months of receipt of the rejection notice | Documentation proving the original claim was submitted on time |
Subpart 3 separately allows a provider to bill when a recipient is retroactively eligible for medical assistance and notifies the provider. Keep the eligibility notice with its date, because that notice is what establishes the clock.
Third party liability delay is not on the list. The billing policy applies the 12-month rule to TPL claims, and when probable liability is not established or benefits are not available at the time of the claim, MHCP pays the allowable amount and recovers from the third party itself. If you believe a denial was a DHS error, the MHCP appeals guide explains how to document it.
Compliance note: the exceptions require you to prove the original submission was timely. That proof is the 999 and 277CA acknowledgment, or the MN-ITS claim response, from the original batch. Store acknowledgments with the batch for at least as long as the claim record itself.
Managed care timely filing is different
The 12-month rule is MHCP fee-for-service policy. Members enrolled in a prepaid health plan are billed to that managed care organization (MCO), and each MCO sets its own timely filing limit and corrected-claim window in its provider manual and contract. Those limits can be shorter than MHCP's, and they differ from plan to plan, so this guide does not state a number for any of them. Check the current manual for each plan you bill and record the limit next to the payer in your billing system.
The appeal clock is also separate. Health plan appeals generally must be filed within 60 days of the remittance date, so MCO denials should be worked before MHCP denials in the weekly queue. The MHCP eligibility verification guide explains how to tell from the 271 whether a member is fee-for-service or enrolled in a plan on the date of service.
How to prove timely submission
Every route into MHCP produces an acknowledgment, and the acknowledgment is the evidence.
- Batch 837P to MN-ITS. MHCP returns a 999 for the transaction set; a 999 that shows acceptance proves the file was received and passed format checks. The DHS MN-ITS troubleshooting guide says to contact the MHCP Provider Resource Center if no 999 arrives within four hours. A 277CA, where issued, shows which claims entered adjudication.
- MN-ITS direct data entry. The claim response on screen and the 276/277 claim status, which shows the claim the same day, record the received date.
- Clearinghouse. Keep both the clearinghouse acceptance report and the payer's 999 and 277CA; the clearinghouse accepting a claim is not the payer receiving it.
A rejected transaction is not a received claim; if a rejection sits unread for eleven months, the 12-month clock has run on every claim in it. The MN-ITS guide describes where those files land in the mailbox and how long they stay there.
Void and replacement mechanics
Use the right transaction for the problem, because they do different things.
| Transaction | Frequency code | Use when | Effect |
|---|---|---|---|
| Replacement | 7 in CLM05-3, with REF*F8 | The claim paid incorrectly or a line was denied and the data needs correcting | The original payment is taken back and replaced by the corrected claim; history is preserved |
| Void | 8 in CLM05-3, with REF*F8 | The claim was submitted in error: wrong provider, wrong patient, wrong payer, wrong subscriber, or the client did not want the payer billed | The claim is reversed and the payment recouped; a new original claim is needed if one is due |
In MN-ITS direct data entry, DHS provides copy, replace, and void functions from the claim response or the 276/277 claim status. The claim retrieval process does not return every field, so check a copied or replaced claim before submitting it. In an 837P batch, the frequency code and REF*F8 do the same job.
Order matters with a void. Submit the void, wait for it to finalize on the remittance, then submit the new original claim, and confirm that the new claim will still be received within 12 months of the date of service. If it will not, do not void; correct the claim with a replacement instead, because a claim voided after the timely filing window cannot be resubmitted.
An unbilled services routine
Timely filing denials are the only denial category that is entirely self-inflicted, and they are prevented by one report run on a schedule.
- Weekly unbilled services report. List every documented service with no accepted claim, aged from the date of service. Sort oldest first. Anything over 60 days gets a named owner.
- Weekly acknowledgment check. Confirm every batch from the prior week has a 999 showing acceptance and no unresolved 277CA rejections.
- Every remittance cycle. Post the 835, and add every denied line to a denial queue with its own age from the date of service. MCO denials first, because of the 60-day appeal window.
- Monthly aging review. An owner reviews every unbilled or denied service older than 180 days, while eligibility fixes, authorization amendments, and replacement claims can still be completed.
- Hard stop at 11 months. Any service approaching 12 months from the date of service is either submitted that week or written off with a documented reason. Nothing should be discovered at month 13.
How Trustora helps
Trustora tracks every documented service from the date of service to an accepted claim, and the unbilled services report is built in: services with no accepted claim are aged automatically, flagged at configurable thresholds, and assigned to a person. Batch acknowledgments (999 and 277CA) and MN-ITS claim responses are stored with each batch, so proof of timely submission is attached to the claim rather than kept in a mailbox folder that expires.
Corrections open as replacement claims with frequency code 7 and the original payer claim number carried forward, and the system warns before a void when the new claim would fall outside the 12-month window. Timely filing and appeal deadlines are tracked per payer, so MCO limits can be recorded separately from the MHCP rule. See the claims lifecycle features for eligibility, 837P, remittance reconciliation, and denials in one system.