UI Audit Response Guide · MI
Michigan UI audit response
Michigan UIA reviews move faster when you lead with reconciled wage/payment totals and a clean worker-by-worker proof structure (especially if records are spread across systems).
Michigan “what’s different”
Michigan UIA audits/records reviews tend to get messy when totals are hard to verify across tools. Your best advantage is to make the payment story verifiable and keep documentation organized per worker/vendor, not scattered by file type. Michigan’s employer UI environment has also been in transition (MiWAM → MiUI), so it’s worth double-checking where you pulled reports from and ensuring they match your response period.
What to expect (Michigan)
- A records request tied to a specific period and worker set.
- Requests for wage/payment detail plus supporting documentation (what was paid, why, and under what arrangement).
- Follow-ups if:
- totals don’t reconcile (bank/processor vs internal records), or
- proof isn’t organized per worker/vendor, or
- payee identity is unclear (name mismatches, multiple entities, etc.).
What to pull first (Michigan checklist)
A) Response cover (make it reviewable)
- Audit period dates + deadline.
- One roster of all payees/workers in scope (one row each).
- A short explanation of your categories (what “outside payroll” includes for your business).
B) Totals that reconcile (don’t make them guess)
- Bank/processor exports for the period.
- Internal payment summaries (GL exports if you have them).
- A totals table by payee:
- payee name
- dates paid
- total paid
- purpose label
- links to proof
C) Proof per payee (keep it consistent)
For each payee, attach a proof set that matches the payment trail:
- W-9 (if applicable)
- Invoices
- Scope documentation (work order / SOW / engagement email / proposal acceptance)
- Payment proof (ACH detail, check image, processor transaction detail)
- Work evidence for repeat/higher-dollar payees (deliverables, milestone notes, project updates)
If your purpose labels are simple (“design,” “cleaning,” “consulting”), keep them consistent across the roster, exports, and proof names. Consistency reduces follow-ups.
If you use employer UI portals for exports, make sure the period you export matches the notice period exactly, and note where the export came from (helpful during system transitions).
Sources
Disclaimer
This material has been prepared for informational purposes only, and is not intended to provide, and should not be relied on for, legal or tax advice. If you have any legal or tax questions regarding this content or related issues, then you should consult with your professional legal or tax advisor.