UI Audit Guide

Indiana DWD Audit Response: A Former Auditor's Guide (2026)

A former Indiana DWD auditor walks through what an audit actually looks like, which records auditors want in what order, and how to respond in the first 72 hours.

Receiving an Indiana Department of Workforce Development (DWD) audit notice changes the question you have been avoiding into a deadline. This guide walks through what an audit actually looks like from the state's seat, what records the auditor will ask for and in what order, and how to respond in the first 72 hours so the review closes cleanly. It is written by someone who conducted these audits inside the agency — not from templates or summaries. The material here is administrative guidance for organizing a response; it is not legal advice. If the dollar exposure is large or the auditor signals an intent to issue a reclassification finding, consult qualified counsel before your final response goes to the state.

What an Indiana DWD audit actually looks like

An Indiana DWD audit begins with a notice. The notice arrives by mail on state letterhead, names a specific auditor, states the audit period (typically the three most recent calendar years), and lists the records being requested. The language is procedural, not accusatory. The auditor's job at this stage is to collect the documents needed to answer a single question: during the audit period, were any of the workers you paid as contractors actually performing work that, under the Indiana 123 Test, requires employee treatment for unemployment insurance (UI) tax purposes?

The sequence is consistent. First, the notice and initial records request. Second, the employer produces records by the deadline — or requests an extension. Third, the auditor reviews what came in and issues follow-up questions. The follow-ups are where audits either close cleanly or unravel. An auditor who has everything they need and can tie each payment to a payee and to classification evidence will generally close the file without a finding. An auditor who has to chase documents, reconcile totals, or piece together the nature of a relationship from fragments will keep asking questions, and each question is an opportunity for the evidence to look weaker than it is.

What the auditor is actually doing during the review is pattern-matching. They have seen hundreds of employer files. They know what a well-documented contractor engagement looks like — signed agreement predating the first payment, current W-9, invoices tied to deliverables, independence proof like a business license or Certificate of Insurance, and payment records that show irregular amounts consistent with project work. They also know what a thinly documented engagement looks like — verbal agreement, missing or recently collected W-9, regular weekly payments of identical amounts, no invoices, and no independence documentation. The visible pattern drives the finding more than any single document.

After the review closes, the auditor issues one of three outcomes: no finding and the classifications stand, a request for additional information on specific relationships, or a reclassification finding with an assessment of back UI taxes, interest, and penalties. A reclassification finding can be appealed through the DWD's administrative process, but the burden at appeal is on the employer to present evidence that should have been in the original response.

The 123 Test in practice

Indiana's 123 Test is an ABC-style test with the employer bearing the burden of proof on all three prongs. A worker is presumed to be an employee for UI purposes unless the employer can affirmatively demonstrate that the worker is free from direction and control in performing the work (Prong A), that the service is performed outside the usual course of the employer's business or outside all of the employer's places of business (Prong B), and that the worker is customarily engaged in an independently established trade or business of the same nature (Prong C). All three must be satisfied. Failing any one is sufficient for the auditor to find an employment relationship for UI purposes.

What the statute says and what an auditor pattern-matches against in the field are not the same thing. For Prong A, the auditor is looking at practice, not contract language. A contract that says "the contractor controls their own methods" does not override an email thread showing the employer setting hours, assigning specific tasks, and directing how work should be performed. For Prong B, the auditor is asking whether the work the contractor did is the same work direct employees of the business perform. A construction company paying a subcontractor to frame walls — the same work framers on payroll perform — has a Prong B problem that no amount of paperwork can fix. For Prong C, the auditor is looking for evidence the worker has a real, separate business: a business entity, an employer identification number (EIN), Certificates of Insurance, invoices that show other clients, a website, Secretary of State registration. A worker who works exclusively for one employer with no independent business identity fails Prong C regardless of how the contract reads.

The practical result: classification is rarely a single-document question. It is a pattern across contract, practice, payment, and independence evidence. For the deep mechanics of each prong and how to document each one, the dedicated guide covers it — see the full breakdown of the 123 Test and how auditors apply it.

The four document categories an Indiana auditor will ask for

Audit document requests vary by auditor and by case, but the underlying ask is almost always the same four categories. Organizing your response around these categories — rather than by document type or by date — is what makes the difference between a clean review and a messy one.

Period and reconciliation

This is the foundational layer. The auditor needs to know, with certainty, what the total contractor spend was during the audit period and how that number ties to the records you are producing. A one-page period summary that states the audit dates and the total contractor payments, followed by a reconciliation note showing how bank or processor totals map to your internal records, closes off an entire class of follow-up questions before they start. Without this, the auditor has to build the total themselves and will ask clarifying questions every time a number doesn't tie.

Payment trail

Bank statements or processor exports covering the full audit period. Check images or automated clearing house (ACH) detail if you used either method. A payee register — date, payee, amount, and a purpose label for each payment — that matches the bank and processor records. If you used multiple payment methods (checks plus ACH plus card), a single consolidated payee total per person so the auditor doesn't have to stitch the payment methods together. The payment trail is the skeleton that every other document hangs off of.

Per-payee proof

For each person or entity that received payment during the audit period, a per-payee packet containing: a current W-9, a signed contractor agreement that predates the first payment, the invoices submitted by the contractor, scope documentation such as the engagement email, the statement of work (SOW), the accepted proposal, or the work order, any approvals used for changes in scope, and work evidence for repeat relationships — deliverables completed, project milestones reached, the output of the engagement. Organizing per payee rather than per document type is important: an auditor reviewing twenty contractors can move through them quickly when each one has its own packet, and they form stronger impressions of the employer's record-keeping when the organization is clean.

Classification basis

This is the independence evidence that supports Prong C of the 123 Test. For each contractor: business license or entity registration, EIN documentation, Certificate of Insurance, evidence the contractor has other clients, a website or public business presence, and Secretary of State registration if applicable. Classification basis documentation should ideally have been collected at engagement time — before the first payment — and should predate the audit notice. Documentation collected after the notice arrives is treated with less credibility than documentation that was always in the file. The earlier the paper trail, the stronger the defense.

The most common Indiana audit findings — and how to avoid them

Patterns repeat across Indiana DWD audits because the pressure points are the same across employers. The most common findings are predictable once you have sat on the state's side of enough reviews.

The single most common finding is a Prong B problem in construction, staffing, trucking, and home services. An employer pays subcontractors to perform the same work the employer's direct employees perform. No contract language can fix that — the only way to be safe is to either bring those workers onto payroll or restructure the engagements so the work performed is genuinely outside the usual course of business. The second most common pattern is missing or post-hoc W-9s. An employer paid a contractor $50,000 over two years, the auditor asks for the W-9 and a signed agreement, and the employer produces documents with recent dates — sometimes the same week the notice arrived. The discovery that documents were assembled under deadline rather than before engagement is one of the most damaging signals in an audit.

The third pattern is payment records that look like payroll: regular weekly or biweekly payments of identical amounts with no corresponding invoices. This reads as employee treatment even when the paperwork says contractor. The fourth is contractors who work exclusively for one employer with no independent business identity — no EIN, no website, no other clients. These are Prong C findings and they are difficult to defend even when Prongs A and B are clean. The fifth is industry clustering: construction, staffing, and transportation attract more audit attention than other sectors, so employers in those sectors face a higher baseline and need stronger-than-average documentation.

The observable truth across all of these: audits where the classification gap was addressed years before the notice — complete files, independence documentation collected at engagement, invoices tied to deliverables, payment records that don't look like payroll — close without findings the vast majority of the time. Audits where the gap was addressed only after the notice arrived close without findings far less often. The difference is documentation practice, not audit strategy.

What to do in the first 72 hours after receiving a notice

The notice arrived yesterday. The response deadline is three weeks out. What to do right now matters more than what to do in week three.

Read the notice carefully and write down the key facts. Audit period, response deadline, specific records requested, auditor name and contact information, and the reference number for the case. Everything else you do is organized around these facts.

Notify the right internal people and no one else. Your accounting lead, your owner or CEO, and whoever manages contractor payments and onboarding. Do not discuss the audit with the contractors themselves unless you have a specific reason — your characterization of the relationship will show up in any communications they have with the auditor.

Start assembling the four document categories in parallel, not in sequence. Period summary and reconciliation. Payment trail. Per-payee proof packets. Classification basis documentation. Different people should be working on each category at the same time — waiting for the payment trail to be complete before starting per-payee packets wastes days you need.

Identify your gaps early. Know which contractors have complete files and which have missing pieces before you respond. If a W-9 is missing, request it now. If an independence document is missing, see what you can still collect that is real — do not fabricate. Missing documents handled proactively are manageable; missing documents discovered by the auditor are damaging.

Request an extension if you need one — before the deadline, not after. A proactive extension request is almost always granted. A missed deadline is always remembered.

Do not send the response piecemeal. Assemble the full response, review it for completeness and consistency, and send it as a single production. A partial response with a promise to follow up is an invitation to more questions and a longer audit. When the dollar amounts are meaningful, the exposure is real, or the auditor has already signaled a classification concern, bring in a compliance partner before the response goes out — the Classifi audit response service is designed for exactly this situation and is led by a former Indiana DWD auditor.

Frequently asked questions

How long do I have to respond to an Indiana DWD audit notice?

The notice itself will specify the response deadline — typically 14 to 30 days from the date the notice was issued. The deadline applies to the document production, not to a final decision, so you have time to organize your records as long as you confirm receipt and stay in contact with the auditor.

Can I ask for an extension on an Indiana DWD audit response?

Yes. Extensions are commonly granted when you request them before the original deadline and explain why you need the time. The worst thing you can do is miss the deadline without contacting the auditor. A proactive request signals good faith; a missed deadline signals the opposite.

Do I need a lawyer for an Indiana DWD audit?

Not for the initial records response. A DWD records request is a compliance matter, not a legal proceeding. Legal counsel becomes valuable if the auditor issues a reclassification finding you intend to contest, or if the exposure is large enough that a settlement negotiation would benefit from counsel. For the document production itself, organized records and clear communication matter more than legal representation.

What happens if I ignore an Indiana DWD audit notice?

Ignoring the notice does not make it go away. The DWD can issue an assessment based on the information it has — which is typically the worst possible outcome for the employer, because the agency will estimate the liability on assumptions the employer never had a chance to rebut. You lose the ability to present independence documentation and end up owing more than you would have with a complete response.

How far back can an Indiana DWD audit go?

The standard audit period is the three most recent calendar years. In cases involving willful misclassification or fraud, the look-back window can extend further. For most employers responding to a routine audit, the three-year window is what to plan for.

Will an Indiana DWD audit share findings with the IRS?

Indiana DWD and the IRS run separate programs with different classification tests, but information-sharing agreements exist. A reclassification finding at the state level can trigger federal interest, particularly when the dollar amounts are significant. Treating a state audit as purely a state matter is a mistake.

What's the difference between an Indiana UI audit and a contractor classification audit?

They overlap. Most Indiana DWD audits are framed as unemployment insurance (UI) tax audits, but the central question is almost always whether workers paid as contractors should have been treated as employees for UI purposes. The classification determination drives the UI tax liability. In practice, "UI audit" and "contractor classification audit" describe the same review from different angles.

What's the most common reason Indiana audits end badly for employers?

Missing or reconstructed documentation. When the auditor asks for signed contractor agreements, W-9s, and independence proof and the employer produces documents that were created after the notice arrived, credibility drops. Audits where the documentation clearly predates the engagements almost always go better than audits where the paper trail is assembled under deadline.

Related Indiana guides

• What to expect step-by-step in a DWD contractor audit →
  A walk-through of the full Indiana DWD contractor audit process, from notice to resolution, with the specific records the auditor will request at each stage.
• Full breakdown of the 123 Test and how auditors apply it →
  How Indiana's three-part classification test actually works, what each prong requires, and how to document contractor relationships so each prong is defensible.
• Indiana 1099 filing requirements and how they tie to classification →
  Federal 1099-NEC rules, Indiana-specific filing requirements, and why a correct 1099 filing does not protect you from a DWD reclassification finding.

Sources

• Indiana DWD — Employer Handbook (PDF)

Administrative guidance only — not legal advice.