A Minnesota DHS audit is not one event. The Minnesota Department of Human Services (DHS) reviews care agencies through several doors: licensing reviews, program integrity audits by the Surveillance and Integrity Review Section (SIRS), pre-payment claim review, managed care organization (MCO) audits, and the unannounced site visits that came with Minnesota Revalidate 2026. Each one asks for a slightly different stack of records, but they all test the same thing: can you prove, from the file, that a billed service was authorized, delivered by a qualified person, and documented on time.
The legal footing is short. Minn. R. 9505.2175, subp. 1 says program funds paid for a service not documented in the client's record "shall be recovered by the department." Minn. Stat. § 256B.064 gives DHS the power to withhold payments, fine, suspend, terminate, and recover money. Everything below is about making sure the record exists before anyone asks for it.
This checklist applies as of September 2026 and covers Adult Rehabilitative Mental Health Services (ARMHS), 245D home and community-based services, personal care assistance (PCA) and Community First Services and Supports (CFSS), Early Intensive Developmental and Behavioral Intervention (EIDBI), and adult day services.
What kinds of DHS reviews are there?
| Review type | Who runs it | What it tests |
|---|---|---|
| Licensing review or recertification | DHS Licensing (245D, 245A adult day), DHS behavioral health (ARMHS certification) | Policies, staff qualifications and training, client records against the licensing statute |
| SIRS program integrity audit | DHS Office of Inspector General, Surveillance and Integrity Review Section | Paid claims against the health service record; results in overpayment notices, fines, or sanctions under § 256B.064 |
| Pre-payment review | DHS with a third-party contractor | Claims for 14 high-risk services are reviewed for documentation and billing anomalies before payment; payments can be paused for up to 90 days |
| MCO audit | The managed care organization that paid the claim | Contract compliance, medical necessity, EVV, and documentation for the plan's members |
| Revalidation site visit | DHS Office of Inspector General | Unannounced verification that the business location, owners, staff, and credentials in the enrollment record are real |
Pre-payment review began after the governor's October 29, 2025 directive. The 14 services are the 13 in the January 2026 enrollment freeze plus housing stabilization services, which DHS has since ended. If you bill any of these, assume every claim is read by a reviewer.
What triggers a review?
Some reviews are scheduled: 245D and adult day licensing renewals, ARMHS recertification at least every three years, and the standard MHCP revalidation cycle. Others are data-driven. Under Minn. R. 9505.2200, DHS may investigate when it has reason to believe fraud, theft, abuse, or error has occurred, and its analytics flag units per client far above peers, services billed while a client was hospitalized, overlapping times for one staff person, or staff without a background study clearance.
Complaints and maltreatment reports are the other big source. A report to the Minnesota Adult Abuse Reporting Center, a client grievance to an MCO, or a former employee's tip can open a file, and a review that starts as a complaint often widens to a claims audit.
What auditors request, and how fast
A SIRS records request names clients and a date range and asks you to produce, usually electronically:
- Client records. Assessments, care plans or treatment plans, service agreements and authorizations, progress notes, timesheets or activity records, and signatures.
- Staff files. Qualifications, licenses, training records, background study determinations, and dates of hire.
- Schedules and supervision. Who was scheduled, who worked, supervisor visits, and co-signatures.
- EVV data. Clock-in and clock-out times, GPS location, and any manual edits for services that require electronic visit verification.
- Claims. The 837P claims and 835 remittances for the period.
- Policies and procedures. The versions in force on the dates of service.
The rule on access is Minn. R. 9505.2185, subp. 2: a vendor "shall grant the department access during the department's normal business hours" to health service and financial records related to a billed service, at the vendor's place of business, with at least 24 hours' notice. A written request carries its own due date. Refusing access is a ground for sanction under § 256B.064, subd. 1a.
Retention is set by Minn. R. 9505.2190: keep all health service and financial records for at least five years after the initial date of billing, even after you withdraw or are terminated, and for the full length of any contested case.
Audit tip: produce records in the order the reviewer will read them. For each client, put the authorization first, then the plan, then the notes, then the EVV log, then the claim.
How claims are sampled and reviewed
SIRS selects clients and dates from paid claims, requests the records for those claims, and compares each claim line to the record. The published Office of Administrative Hearings decisions in SIRS appeals show the pattern: care plans missing required elements, unsigned timesheets, services outside the authorization, and staff without a current background study. Each failed claim becomes an overpayment, and repeated failures can support a fine.
Minnesota's statute and rules do not prescribe a sampling formula, and the published decisions generally list the specific claims reviewed. Federal Medicaid integrity audits can project a sample's error rate onto all claims in a period. Prepare as if that is possible: an error in 10 percent of sampled notes is an error in your template, not in ten notes.
Recovery follows § 256B.064, subd. 1c, which allows DHS to recover money paid as a result of fraud, theft, abuse, or error, including plain error, and to debit future payments. Under subd. 2, DHS must withhold payments when it determines there is a credible allegation of fraud under investigation.
Self-audit checklist by program
Run this quarterly on a random sample of clients and staff, reviewed by someone other than the author of the notes.
ARMHS
Diagnostic assessment current; functional assessment with a narrative in every domain; level of care documented; treatment plan signed by the client and approved by a supervisor within ten business days; every H2017 unit backed by a note with start and stop times and an ITP goal; MHRW notes co-signed. See the ARMHS documentation checklist.
245D
Coordinated service and support plan addendum on time (preliminary within 15 days, full within 60 days for intensive services); progress reviews on the schedule in the plan; incident reports within 24 hours; staff orientation within 60 days and annual training on the required topics; service recipient rights signed. See the 245D documentation checklist.
PCA and CFSS
Service authorization matches units billed; care plan or CFSS service delivery plan with start and end dates; worker competency visits within 30 days of hire and every 90 days; EVV compliance at or above the 80 percent threshold in force since July 1, 2026; no manual visits without a documented reason; surety bond, liability, fidelity, and workers' compensation current on the provider record.
EIDBI
Comprehensive multi-disciplinary evaluation current; individual treatment plan with measurable goals; session notes per code (97153, 97155, 97156); 97155 units proportional to intervention time and justified in the ITP; all qualified supervising professionals on payroll as employees. See EIDBI documentation: ITP and session notes.
Adult day services
Attendance records with arrival and departure times that support S5102 full days or S5100 units; transportation logs for T2003 UC; license capacity and staff ratios met daily; participant plans reviewed on schedule.
Across all programs, check the claim side too; the MHCP claim denials guide lists the errors reviewers find first.
How to respond to a findings letter
A notice of overpayment or sanction states the amount, the claims, the grounds, and your appeal rights. Read it the day it arrives.
- Calendar the deadline. Under § 256B.064, subd. 2, a written appeal must be filed no later than 30 days after the date the notice was mailed. For a revalidation disenrollment notice the window is 60 days from the notice date.
- Rebuild each disputed claim. Match every claim line to the record; some findings are misfiled documents, not missing ones.
- Write the appeal the way Minn. R. 9505.2245 requires. For each disputed item: the reason, your dollar estimate, your own computation, and the statute or rule you rely on, plus a contact person.
- Fix the pattern now. Correct the template or workflow that produced the finding and document the corrective action; it matters if a fine is on the table.
- Decide what to repay. Voluntary repayment, lump sum or installments with interest, is a recovery method under Minn. R. 9505.2215. Do not repay an amount you intend to dispute without saying so in writing.
Never delete, backdate, or "complete" records after a request. Altered records turn an overpayment case into a fraud referral.
Appeal rights at the Office of Administrative Hearings
A vendor appeal of a SIRS action is a contested case under Minn. Stat. §§ 14.57 to 14.62, heard by an administrative law judge at the Office of Administrative Hearings (OAH). DHS has the burden of proving the overpayment, and the judge's report goes to the commissioner for the final decision. Before the hearing, the commissioner may suspend or reduce payments to protect the program (Minn. R. 9505.2245, subp. 1, item C), so a pending appeal does not by itself restore cash flow.
The Minnesota Revalidate guide covers the separate 60-day appeal process for revalidation disenrollments.
Build an always-ready audit binder
An audit binder is a standing export, not a project. For any client and date range you should be able to produce:
| Section | Contents |
|---|---|
| Enrollment | MHCP enrollment record, license or certification, insurance and bond certificates, owner and controlling individual list |
| Policies | Current policies and procedures with version dates and staff acknowledgment |
| Staff | Qualification proof, background study determinations, training log, supervision log |
| Client | Authorization, assessment, plan, notes or timesheets, signatures, incident reports |
| Visits | EVV export with clock times, GPS, and edit history |
| Claims | 837P claims, 835 remittances, denial and appeal history |
| Access log | Who viewed or edited each record and when |
The last row is where HIPAA and program integrity meet: reviewers ask who had access to a record and whether entries changed after billing. The HIPAA compliance guide explains what an access log has to capture.
How Trustora helps
Trustora's compliance engine runs the self-audit continuously instead of quarterly. A pre-claim gate blocks a claim when the note, authorization, EVV record, or staff qualification behind it is missing or expired, and gap-day alerts flag clients with authorized units and no documented service. Required fields are enforced on assessments, plans, progress notes, and attendance records for ARMHS, 245D, PCA/CFSS, EIDBI, and adult day services in one platform.
When a request arrives, the one-click DHS audit binder assembles the client records, staff files, schedules, EVV export, claims, and remittances for any client list and date range. Every record carries an append-only, SHA-256-chained audit log with seven-year retention, so a reviewer can see when each entry was created and by whom. See the platform overview for the full compliance feature list.