MN-ITS is the free, web-based portal that Minnesota Health Care Programs (MHCP) providers use to verify eligibility, submit claims, check claim status, and retrieve remittance advices from the Minnesota Department of Human Services (DHS). It is also a mailbox. DHS delivers remittances, service authorization letters, and official enrollment notices there, and it does not send most of them anywhere else.
That second role is why MN-ITS matters to an owner and not just to a biller. The Revalidate 2026 notices, the electronic visit verification (EVV) corrective action letters described in the EVV compliance checklist, and cost-report selection memos all land in the PRVLTR folder of the MN-ITS mailbox. An agency that does not read the mailbox can be in corrective action, or disenrolled, without knowing it.
This guide covers what MN-ITS does, how the mailbox is organized, direct data entry versus batch 837 files, eligibility and claim status transactions, the 835 remittance advice and its schedule, user administration, common access problems, and a weekly routine. It reflects DHS guidance as of September 2026.
What MN-ITS is and who needs it
MN-ITS (Minnesota Information Transfer System) is the DHS transaction system for MHCP fee-for-service business. Under the MHCP Provider Manual billing policy chapter, an enrolled provider uses it to:
| Function | Transaction | What you get back |
|---|---|---|
| Verify member eligibility | 270 request, 271 response | Program or prepaid health plan, eligibility spans, other insurance |
| Submit professional claims | 837P by direct data entry (DDE) or batch upload | A claim response and, for batch, a 999 acknowledgment |
| Check claim status | 276 request, 277 response | Current status and the remittance date if paid or denied |
| Receive payment detail | 835 (batch) or PDF remittance advice (DDE) | Paid, denied, and adjusted lines with reason codes |
| Receive DHS notices | Mailbox folders | Authorization letters, enrollment letters, provider news |
Every pay-to provider needs its own MN-ITS access, even one that bills through a clearinghouse. DHS does not accept direct data entry from a clearinghouse, and HIPAA does not allow a clearinghouse to run 270 eligibility or 276 claim status inquiries on a provider's behalf.
The MN-ITS mailbox and why notices land there
The MN-ITS Mailbox User Guide describes four areas: Links, Archive, Transaction Responses, and Miscellaneous Received. Retention differs by area, and that is the first thing to understand.
| Area or folder | What it holds | Available for |
|---|---|---|
| Links | Provider updates and provider news | 30 days |
| Archive | Older files you requested from DHS | 30 days |
| Transaction Responses: 271, 277, 999, TA1 | Eligibility, claim status, and batch acknowledgment files | 90 days |
| Transaction Responses: 835_PDF and 835_X12 | Remittance advices (PDF for DDE users, X12 835 for batch users) | 12 months |
| Miscellaneous Received: PRVLTR | Affiliation letters, category-of-service changes, and enrollment status changes from DHS | 90 days |
| Miscellaneous Received: SAL | Waiver and home care service authorization letters | 90 days |
| Miscellaneous Received: PAL | Medical, medical supply, and dental authorization letters | 90 days |
A file type such as PRVLTR or SAL does not appear in the folder list until the first file of that type arrives, and an administrator can restrict which folders a user sees. If the person who reads the mailbox cannot see PRVLTR, nobody is reading it.
Compliance note: DHS delivers revalidation notices, disenrollment notices, EVV corrective action notices, and CFSS cost report memos to the PRVLTR folder. The clocks on those notices run from the date printed on the letter, not the date someone opens it. Assign one named person to open Miscellaneous Received at least weekly and log every letter with its due date.
Direct data entry versus batch 837 uploads
MN-ITS accepts professional claims two ways. Direct data entry (DDE) means a user keys each claim into the MN-ITS 837P screens, following the MHCP MN-ITS 837P user guide for the service. Batch means the agency's software produces an X12 837P file and uploads it under Submit Transactions, or sends it by SFTP.
DDE needs no software and shows the claim in the 276 claim status inquiry the same day, but every field is typed by hand. Batch lets the claim be built from the progress note or visit record, but the file must pass MHCP's front-end checks. MHCP rejects a batch at the interchange level with a TA1 if the file structure is invalid, and at the transaction level with a 999 if the file does not meet the X12 5010 implementation guide and the Minnesota Uniform Companion Guide. The 837P claim guide walks through the segments that fail those checks.
For batch users, the 999 is the receipt. The DHS MN-ITS troubleshooting guide says that if you have not received a 999 within four hours of a batch submission, contact the MHCP Provider Resource Center and report your submitter ID and the date and time of the submission. Do not resubmit the file until you know whether the first one was accepted, or you will create duplicates.
Eligibility requests: 270 and 271
The MN-ITS eligibility request (270) lets a provider check one member or up to 50 at a time, for dates of service up to one year before the date of inquiry. The 271 response shows the member's program or prepaid health plan, the eligibility span, and other insurance. MHCP requires providers to verify eligibility before rendering services and before submitting claims.
Because eligibility changes monthly and members move between fee-for-service and managed care, run the check for the date of service before the first visit of each month and again before each claim batch. The MHCP eligibility verification guide explains how to read spans, managed care enrollment, and spenddowns on the 271.
Claim status: 276 and 277
The MN-ITS request claim status (276) returns a 277 response with the claim's current status and, if the claim has been paid or denied, the remittance advice date. Claims submitted by DDE are visible the same day. From the 277 a user can open the claim to copy it, replace it, or void it.
Use the 276 to confirm a claim arrived, to find a claim that never appeared on a remittance, and to locate the payer claim number for a replacement. The claim retrieval process does not return every data field, so check a copied or replaced claim before resubmitting it.
The 835 remittance advice and its schedule
MHCP pays on a set cycle. The DHS Payment and Claim Cut-off Calendars (DHS-3947K) list a claim cut-off at 11:59 pm, an electronic funds transfer date, and a remittance date for each cycle. MHCP places remittance advices in PDF format and X12 835 files in the MN-ITS mailbox by the end of the business day every other Friday. The calendar's own advice is to bill early and bill often rather than waiting for the cut-off day.
Which file you get depends on how you bill. DDE users find a readable PDF remittance advice in the 835_PDF folder. Batch users find a downloadable X12 835 in the 835_X12 folder, which billing software can post automatically. Suspended claims are listed in the Provider Supplemental Data section of the PDF remittance. The remittance starts the denial work and the appeal clocks; the MHCP claim denials guide explains how to read the reason and remark codes on each line.
Download and store every remittance in your own system; an audit or appeal two years later will need it.
User administration and the primary administrator
Access to MN-ITS is controlled by the provider, not by MHCP. When an organization enrolls with MHCP it names an MN-ITS primary administrator (PA). Registration runs through LoginMN, the state identity service, which gives each person an individual account protected by multifactor authentication; the user ID is the email address entered at registration. Completing LoginMN and MN-ITS registration creates the organization's MN-ITS administration account.
The PA, or a secondary administrator the PA appoints, can create users, update and disable accounts, assign MN-ITS roles, assign SFTP access for batch files, manage service agent roles in the Minnesota Provider Screening and Enrollment (MPSE) portal, and restrict which mailbox folders a user sees. Treat those roles as HIPAA access controls: disable accounts the day someone leaves and review the user list quarterly. The HIPAA guide for home care agencies covers the access review that auditors expect.
Common login and access problems
| Problem | Cause | Fix |
|---|---|---|
| Locked out | Five failed login attempts | The PA or secondary administrator resets the password; MHCP will not |
| Cannot find the LoginMN registration email | Sent to an address nobody monitors | DHS instructs providers to email the MHCP provider help desk with the subject "LoginMN" and the address to use |
| Mailbox folder missing | No file of that type has arrived yet, or the administrator restricted the role | Check the user's role; a folder appears after the first file |
| No 999 after a batch upload | File never reached MHCP or failed at the interchange level | Wait four hours, then contact the Provider Resource Center with the submitter ID and submission time |
| Eligibility inquiry blocked from the clearinghouse | Clearinghouses cannot run 270 or 276 for a provider | Run the inquiry from the provider's own MN-ITS account |
| The only administrator has left the agency | Access was tied to one person | Contact MHCP provider enrollment to reassign the primary administrator; name a secondary administrator going forward |
Two administrators is the minimum; an agency whose only PA has left cannot add a biller or unlock an account.
A weekly MN-ITS routine
- Monday: eligibility. Run 270 inquiries for every member scheduled that week and for every claim in the outgoing batch.
- Tuesday: submit. Upload the batch or complete DDE entry; confirm the 999 arrived and shows the transaction set was accepted.
- Wednesday: mailbox. Open Miscellaneous Received. Read every PRVLTR, SAL, and PAL file and log each one with its due date.
- Friday, on remittance weeks: download the 835 or PDF remittance, post it, and open a denial work queue from every adjusted line.
- Every week: aging. Run the 276 on any claim two cycles old with no remittance, and check the unbilled services list against the 12-month window in the MHCP timely filing guide.
How Trustora helps
Trustora generates 837P batch files for MHCP and managed care organizations from the documented service, posts the X12 835 remittance automatically, and reconciles every line to the claim so that denials open as work items with the reason and remark codes attached. Eligibility checks are run against the date of service before a claim is released, and the compliance engine's pre-claim gate holds any claim that fails eligibility, authorization, or documentation checks.
The platform covers ARMHS, 245D, PCA/CFSS, EIDBI, and adult day services in one system, with role-based, field-level access so that the person who reads the MN-ITS mailbox and the person who posts remittances can have exactly the permissions they need. See the claims and compliance features for the full lifecycle.