UI Audit Response Guide · DC
District of Columbia UI audit response
DC UI tax reviews move faster when you keep a clean wage/payment trail and deliver proof organized by payee and period.
District of Columbia “what’s different”
In DC, the fastest path is an audit-ready submission where every total is traceable and every payee’s records are grouped cleanly. Think “reviewer checklist,” not “document archive.”
What to expect (District of Columbia)
- A deadline-driven request tied to a period and specific record types.
- Requests centered on wage/payment detail and supporting source documentation.
- Follow-ups if the reviewer can’t verify totals from your payment exports.
What to pull first (DC checklist)
A) Period summary + roster
- Audit period dates and a totals summary.
- Payee roster: payee, dates paid, totals, purpose label.
B) Payment trail
- Bank statements and/or processor exports.
- ACH/check detail if used.
- Payee register: date, payee, amount, purpose.
C) Reporting tie-out
- The reporting summaries you relied on for wage/tax reporting.
- Internal exports used to compile totals.
D) Proof per payee (organized and readable)
- W-9 (if applicable)
- Invoices
- Scope/engagement documentation (work order, SOW, proposal acceptance, engagement emails)
- Approvals (if used)
- Work evidence for repeat/higher-dollar payees (deliverables, milestones, email threads)
If your payee list includes multiple entities with similar names, add a one-line identifier note (LLC vs individual) so the reviewer doesn’t mismatch records.
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.