Certified Payroll Under Davis-Bacon: Why Worker Classification, Not Underpayment, Is What Gets Contractors Audited

5 days ago

6 min read

A contractor who's never worked a federal or federally-assisted construction contract before often discovers certified payroll requirements for the first time only after winning a bid — and by then, the weekly reporting obligation that comes with any Davis-Bacon-covered contract worth more than $2,000 is already running against the clock. Davis-Bacon applies to federal government construction contracts and, through related acts, to many federally-assisted contracts (infrastructure projects funded partly or fully with federal dollars, certain HUD and transportation projects, and similar federally-backed work) above that $2,000 threshold, requiring contractors and subcontractors to pay laborers and mechanics no less than locally prevailing wages and fringe benefits as determined by the Department of Labor, and to document that compliance weekly on Form WH-347 or an equivalent certified payroll report.

What Certified Payroll Actually Requires Each Week

Certified payroll reporting under Davis-Bacon requires a contractor to submit Form WH-347 (or a state or agency equivalent carrying the same required information) weekly for every week work is performed on a covered contract, listing each laborer and mechanic by name, work classification, hours worked (including any overtime), hourly wage rate, fringe benefits paid or provided, and gross wages earned — accompanied by a signed Statement of Compliance certifying under penalty of perjury that the information is accurate and that wages paid meet or exceed the applicable prevailing wage determination for each classification. This isn't a one-time submission at project start; it's a recurring weekly obligation that continues for the full duration of the contractor's work on the covered project, for every tier of subcontractor performing covered work, not just the prime contractor.

The $2,000 threshold applies to the total contract value, not to any individual worker's pay — a small contract just over that threshold triggers the full certified payroll obligation the same as a multi-million-dollar one.
Prevailing wage determinations are set by classification and geographic area (county-level in most cases) by the Department of Labor, and a worker's actual classification on the job — not their job title — determines which wage rate applies; misclassifying a skilled trade worker under a lower-wage laborer classification is one of the most common and most heavily scrutinized compliance failures.
Apprentices can be paid less than the full journeyman prevailing wage rate, but only if they're enrolled in a bona fide apprenticeship program registered with the Department of Labor or a state apprenticeship agency — an unregistered or informal "apprentice" designation doesn't qualify for the reduced rate and can trigger significant back-wage liability if discovered.
Fringe benefits can be satisfied either by actually providing benefits (health insurance, retirement contributions) or by paying the cash equivalent directly to the worker, but the math has to add up to the full prevailing wage determination either way — a contractor can't average fringe benefit costs across a workforce to claim compliance on workers who individually received less than the required amount.

Why Weekly Submission Deadlines Matter More Than They Seem To

Most Davis-Bacon-covered contracts require certified payroll submission within a set number of days after the end of each payroll week (commonly seven to ten days, though the exact requirement is set by the specific contract and contracting agency), and consistently late or missing submissions are themselves a compliance finding independent of whether the underlying wages paid were actually correct — meaning a contractor can be paying every worker correctly and still face a compliance issue purely from reporting lateness. For a contractor used to running payroll on a normal biweekly or semi-monthly cycle for private work, shifting to a weekly certified payroll submission cadence for federal work specifically requires building a separate administrative process, not just a modified version of the existing one.

Flow-Down Obligations Across Every Tier of Subcontractor

A prime contractor on a Davis-Bacon-covered contract is responsible for ensuring every subcontractor at every tier — not just its own direct subs — complies with certified payroll requirements, and for collecting and reviewing their certified payroll submissions as part of the prime's own compliance obligation to the contracting agency. This flow-down responsibility means a prime contractor's compliance exposure isn't limited to its own payroll practices; a second- or third-tier subcontractor's misclassification or underpayment can become the prime's problem if it isn't caught through adequate oversight, making subcontractor certified payroll review a necessary compliance function on any Davis-Bacon project with multiple layers of subcontracting, which describes most meaningfully sized federal construction work.

The Classification Dispute That Causes the Most Trouble

The single most common source of Davis-Bacon enforcement actions isn't underpayment of a correctly classified worker — it's misclassification itself, particularly workers whose actual job duties span multiple trade classifications with different prevailing wage rates. An equipment operator who also performs some laborer-level tasks during a shift, for instance, should generally be paid at the higher applicable rate for any hours performing higher-skilled work, and a contractor that defaults to classifying mixed-duty workers at the lower rate across all their hours — intentionally or simply out of administrative convenience — is exactly the pattern Department of Labor Wage and Hour Division investigations most commonly find and pursue, often resulting in substantial back-wage liability calculated across the full duration of the misclassification.

State Prevailing Wage Laws Can Add a Parallel Requirement

Beyond federal Davis-Bacon, many states maintain their own "little Davis-Bacon" prevailing wage laws applying to state-funded public construction, and contractors working purely state-funded public projects (with no federal funding involved) need to check that state's specific requirements separately, since state prevailing wage rates, reporting formats, and certified payroll deadlines don't always mirror federal requirements exactly even when they're conceptually similar. A contractor who's built a certified payroll process around federal WH-347 requirements for federal work shouldn't assume that same process automatically satisfies a different state's prevailing wage reporting format for a state-only funded project — the two systems can and do diverge in specific procedural details even where their underlying intent is similar.

A Worked Example: The Audit That Started With One Classification Question

Illustrative example, not an actual case: a site-work contractor working a federally-assisted road project classifies several workers as "laborers" throughout the contract, even though those workers regularly operate skid steers and compact excavators as part of their daily duties — work that falls under a higher-paying operator classification in the area's wage determination. A routine Department of Labor compliance review, triggered by a worker complaint on an unrelated issue, asks to see equipment logs alongside certified payroll records and discovers the mismatch between the actual duties performed and the lower classification used throughout the contract. The resulting back-wage calculation, covering the full period those workers operated equipment while classified as laborers, runs into real money — and because certified payroll records are the Department's primary audit trail, the contractor's own weekly submissions become the evidence used to calculate exactly how much is owed.

Building a Compliance Process That Survives an Audit

A defensible certified payroll process starts with classifying every worker correctly based on actual duties performed, not job title or administrative convenience, cross-checked against the specific prevailing wage determination issued for that contract and locality. It continues with disciplined weekly recordkeeping that tracks hours by classification when a worker's duties genuinely span more than one, consistent and timely weekly submission rather than batching several weeks together when things get busy, and active review of every subcontractor's certified payroll submissions rather than simply collecting and filing them. Many contractors handling meaningful federal work volume invest in dedicated certified payroll software specifically because the recordkeeping discipline required is genuinely different from standard payroll, not a minor variation on it.

How This Connects to Equipment Financing

A contractor pursuing federally-funded infrastructure work — the kind of project that increasingly requires excavators, dozers, and haul trucks at scale — needs both the equipment capacity to perform the work and the payroll compliance infrastructure to document it correctly, and underestimating either one can derail a contract that looked straightforward at the bidding stage. BFC finances the equipment contractors need to take on larger infrastructure and public-works contracts, including the kind of Davis-Bacon-covered work this certified payroll obligation applies to. Our piece on

the workers' comp premium audit and uninsured subcontractor exposure covers a related payroll documentation discipline that matters on both private and public work. Our piece on the federal overtime threshold and working foreman classification covers a closely related classification challenge that compounds with Davis-Bacon on federal work.

The Bottom Line

Certified payroll under Davis-Bacon is a weekly, recurring compliance obligation triggered by any covered federal or federally-assisted contract over $2,000, and the most common and costly enforcement issue isn't underpayment of a correctly classified worker — it's misclassifying mixed-duty workers at a lower prevailing wage rate than their actual work requires. Contractors who classify by actual duties performed, submit weekly reports on time without exception, and actively review subcontractor submissions at every tier are the ones positioned to take on federal infrastructure work without discovering a six-figure back-wage liability on their first audit.