Certified Payroll Mistakes That Trigger Audits

Certified payroll mistakes rarely stay small. A single misclassified worker or an incomplete form doesn't just get quietly corrected; it's often the detail that convinces an auditor to look at everything else on your project, too. Understanding what actually triggers that closer look is the difference between fixing an error internally and explaining your entire payroll history to the Department of Labor.

Time-sensitive update: the WH-347 form has changed

As of October 1, 2026, the previous version of the federal WH-347 form is no longer accepted. If your team hasn't already switched to the current version, you need to handle this immediately. Submitting the outdated form isn't a minor formatting issue; the agency treats it as a missing or invalid report, which is a red flag in itself.

What certified payroll actually certifies

Certified payroll isn't just a payroll report; it's a legal certification, submitted with every WH-347 or state equivalent, that your payroll information is accurate and that every worker was paid according to the applicable wage requirements. That certification is what gives auditors grounds to treat an error as more than a clerical slip. A mistake on a certified document reads differently than a mistake on an internal spreadsheet.

The mistakes that most often trigger a closer look

Worker misclassification. Listing a worker under the wrong trade classification, whether to simplify payroll or by genuine error, is one of the most common issues auditors identify on prevailing wage projects. Different classifications carry different prevailing wage rates, so a misclassification isn't just a paperwork problem; it usually means someone was underpaid relative to their actual work.

Fringe benefit reporting errors. Fringe benefits are one of the most common problem areas in certified payroll audits. Whether fringe is paid in cash, contributed to a bona fide plan, or some combination of both changes how it must be reported, and it’s easy to get this wrong without meaning to.

Incomplete or missing daily hours. The WH-347 requires hours broken out by day, not just a weekly total. Reporting only the weekly sum is a common shortcut that immediately looks incomplete to anyone reviewing the form against actual time records.

Incomplete Statement of Compliance. Page two of the WH-347 is the Statement of Compliance, the actual certification language. A payroll report with all the wage data filled in correctly but a blank or incomplete Statement of Compliance is still a deficient submission.

Late submissions. Certified payroll is typically due weekly, generally within seven days of the end of each pay period. Late submissions are one of the most common audit triggers because they're easy to track; a missing or late report creates a visible gap in the record, regardless of whether the underlying payroll was handled correctly.

Unregistered or improperly supervised apprentices. Apprentices who aren't enrolled in an approved program, or who work without proper journeyworker supervision, show up repeatedly in audit findings. This ties directly into the apprenticeship ratio and registration requirements that run alongside prevailing wage obligations on many of these same projects.

Mathematical errors. These sound minor but compound fast. A miscalculation of even a dime per hour across a full crew over several months can turn into a five-figure back-wage liability once it's caught, and auditors specifically check that certified payroll numbers match actual time and pay records line by line.

Poor recordkeeping and inconsistent records. Auditors compare certified payroll reports against actual time records, and any inconsistency between the two is treated as a discrepancy worth investigating further, even if the certified report itself looks clean in isolation.

What actually invites an audit in the first place

Certified payroll discrepancies are one trigger, but they're not the only one. Worker complaints, tips from competitors, and routine agency review can all prompt a closer look. Once a project is on an agency's radar for any reason, certified payroll becomes one of the first things reviewed. This is part of why a single visible error, a late submission, an obviously incomplete form, matters more than it might seem: it's often the detail that moves a project from routine to flagged.

Non-work weeks still need a submission.

A common point of confusion: if no work was performed during a given week, you still generally need to submit the WH-347 with contractor and project information completed, noting that it was a non-work week, rather than skipping the submission entirely. Treating a non-work week as a week with no reporting obligation creates exactly the kind of gap in the record that looks like a missing report during an audit.

How to catch these before they become a problem

The contractors who avoid repeated audit findings tend to share a few habits: reviewing the applicable wage determination before the first payroll run rather than after, reconciling time tracking weekly instead of waiting until the report is due, training field supervisors on classification accuracy so misclassification doesn't start at the source, and keeping certified payroll records centralized and organized rather than scattered across individual project files.

Self-auditing your own certified payroll periodically costs very little compared to the cost of a finding after the fact. Catching a classification error or a missing daily breakdown internally means a quick correction. Catching the same error during a Department of Labor audit means back wage assessments, potentially withheld payments, and a much longer, more disruptive review process.

Frequently asked questions

What happens if I discover an error on a certified payroll report I already submitted?
Submit a corrected report as soon as possible. Delayed corrections increase audit exposure and agency scrutiny; catching and fixing an error quickly is far better than letting it sit until an audit surfaces it.

Do I need to submit certified payroll for a week when no work happened?
Generally yes. Submit the form with contractor and project information completed, noting it was a non-work week, rather than skipping the submission; an unexplained gap looks like a missing report.

Is using the exact WH-347 form required, or can I use an equivalent?
For state-funded projects, requirements vary; some states require their own form rather than the federal WH-347. What's mandatory is the weekly submission of certified payroll information itself, not necessarily the specific federal form, unless the project is federally funded or federally assisted.

Does a 1099 worker performing covered work need to be included on certified payroll?
Yes. If a 1099 worker performs covered work on the project, they need to be listed on the certified payroll report and paid the applicable prevailing wage, regardless of their contractor classification for tax purposes.

What's the single most common reason certified payroll triggers a deeper audit?
Inconsistency between the certified payroll report and actual time records is one of the most consistent red flags, since it suggests the certification itself may not be accurate, which is a much bigger issue than any single line-item error.

Not sure whether your certified payroll process would hold up under closer scrutiny?

See how we handle certified payroll review as part of our services, or check which rules apply to your project, and we'll walk you through it.