UI Audit Response Guide · MN
Minnesota UI audit response
Minnesota reviews run smoother when you provide a clean roster and reconciliation, then organize payee proof in a consistent folder structure.
Minnesota “what’s different”
Minnesota requests are easier when you keep your response systematic: totals first, then payee-by-payee documentation. Reviewers typically want to verify your numbers quickly before deep-diving.
What to expect (Minnesota)
- A records request tied to a defined period and deadline.
- Requests for wage/payment detail and supporting source records.
- Follow-ups if totals don’t reconcile or proof is not clearly organized per payee.
What to pull first (Minnesota checklist)
A) Period summary
- Audit period dates + one-page totals summary.
- Reporting summaries/confirmations (if available).
B) Payment trail
- Bank/processor exports for the audit period.
- Payee register: date, payee, amount, purpose label.
C) Proof per payee
- W-9 (if applicable)
- Invoices
- Scope documentation (work order / SOW / engagement emails / proposal acceptance)
- Approvals (if used)
- Work evidence for repeat/high-dollar payees
If you have seasonal help, add a short explanation of the seasonality (why the help was needed and how long it lasted). This reduces “ongoing relationship” assumptions.
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.