Certified Payroll and Prevailing Wage Requirements for Government Contractors

Certified payroll is a weekly reporting requirement, but its purpose is to make a wage law enforceable rather than simply to generate paperwork. The Davis-Bacon Act applies to federal construction contracts exceeding $2,000, which in practice covers nearly every federal construction project. The act sets a floor on what workers must be paid, but a wage floor without a verification mechanism is only a statement of intent. Certified payroll reports, filed on the federal Form WH-347, require contractors to document worker names, classifications, hours worked each day, wage rates, and fringe benefits, and to sign a statement certifying that this record is accurate. These reports come due every week a covered project is active, including weeks when no work happens on it.

The reporting obligation exists because prevailing wage rates are not uniform. A wage determination for a carpenter in one county can differ substantially from the determination for the same trade one county over, and without a weekly record tied to specific hours and classifications, a contracting agency has no way to see an underpayment happening. Certified payroll turns an abstract wage law into a line-by-line audit trail that regulators can actually check against. Even contractors working in states without their own prevailing wage statutes still carry this reporting duty whenever federal funds are involved, so the system reaches every government contractor.

How prevailing wage rates are set and what contractors must pay

Prevailing wage compliance asks contractors to solve a matching problem before a single paycheck gets written: which wage framework governs this project, and which rate applies to each worker's classification. Davis-Bacon prevailing wages come from the Department of Labor, set separately for each trade classification in each geographic area, reflecting what is actually paid locally rather than a flat national minimum. That local specificity is what makes the system accurate to real labor markets, and also what makes it easy to get wrong.

A separate and lower obligation runs alongside it. The federal contractor minimum wage under Executive Order 13658 stands at $13.65 per hour for non-tipped workers as of May 11, 2026. This figure applies to covered contracts where Davis-Bacon doesn't reach. Where both frameworks touch the same project, the higher number wins: a Davis-Bacon prevailing wage rate for electricians in a given area means the contractor pays that prevailing wage, not the federal contractor minimum, because the prevailing wage figure is what governs. Contractors also have to track which executive order and which wage determination applied at the time the contract was awarded or renewed, since the applicable framework can turn on the award date rather than the date the work is actually performed.

Fringe benefits sit inside this same obligation rather than beside it. The WH-347 form requires itemized documentation of each fringe benefit component, health and welfare, pension, vacation and holiday pay, training, and where each dollar goes, whether to a union trust fund, an employer plan, a direct payment, or an accrual. A contractor who pays the correct hourly wage but treats fringe benefits as a rounding exercise has not met the obligation, because the law treats the benefit dollars as part of the wage itself.

What the WH-347 form requires field by field

The WH-347 form sets a standard precise enough that an incomplete submission creates liability even when every worker on the job was paid correctly. Every weekly report needs worker names, classifications, hours worked each day, wage rates, gross pay, all deductions broken out individually, the fringe benefits provided, and net wages paid. The fringe benefit section has to show itemized components and their destinations rather than a lump sum, and this single field is consistently one of the most common triggers for an audit. Each submission also carries a signed statement of compliance, certifying under the contractor's own signature that prevailing wages and fringe benefits were paid in full.

The form itself changes. The Department of Labor released an updated version of the WH-347 in January 2025, and contractors still submitting older versions risk having those submissions rejected outright. A late report triggers an investigation on its own, and an incomplete one creates liability independent of whether the underlying pay was correct. Responsibility for getting this right doesn't stop at the prime contractor's own payroll. Primes are responsible for ensuring that every subcontractor on the project files on time and files completely, so the compliance burden compounds with each additional subcontractor added to the chain. Many states layer their own forms on top of this federal standard, sometimes required in addition to the WH-347 and sometimes substituted for it entirely on state-funded work.

Where violations occur and what they cost

Violations tend to follow directly from how the system is built rather than from carelessness on a contractor's part. Worker misclassification is the most frequent and costly violation on record: paying a skilled tradesperson at a laborer's rate when the actual work performed triggers a higher wage determination. A related problem occurs when a single worker performs more than one job classification in the same week, say a laborer who operates equipment one day and does carpentry work the next. Overtime for that worker has to be calculated using either a weighted average across all the rates worked or the highest applicable rate, and getting the method wrong creates liability on its own. States with daily overtime rules add another layer on top of this, since California requires overtime for any hours over eight worked in a single day regardless of the weekly total.

Fringe benefit documentation gaps cause trouble even where no money was actually shorted. A contractor who pays the correct wage but fails to document where fringe benefit dollars went, with itemized records matching the union trust or benefit plan statements, can still trip an audit. Multi-state projects compound all of this. A highway project crossing a state line subjects workers to different wage rates, overtime rules, and tax obligations depending on where each day's work actually happened, and tracking location by worker by day isn't optional on a project like that.

The penalties attached to these violations are severe enough to threaten a contractor's ability to keep working for the government. A Davis-Bacon violation can bring back wage assessments, liquidated damages stacked on top of those back wages, civil monetary penalties of $13,508 per violation, contract termination, and debarment from federal contracts for three years.

Overtime calculation under prevailing wage rules

Overtime on a prevailing wage project is a harder calculation than it looks, because construction scheduling routinely produces exactly the scenarios standard payroll software isn't built to handle. The Fair Labor Standards Act requires overtime pay at a premium rate for hours worked over 40 in a week, but on a prevailing wage job, the rate used in that overtime calculation depends on which classifications the worker held during the week in question. Two methods are permitted: a weighted average of all the rates a worker was paid that week, or overtime paid at the single highest rate worked. These two methods produce different dollar figures for the same set of hours, and each carries its own compliance obligations depending on which one a contractor adopts.

States that require daily overtime add a second calculation on top of the weekly one. Alaska requires daily overtime for any hours over eight in a single day, and California applies the same eight-hour threshold regardless of what the worker's total hours for the week come to. A worker who logs nine hours on a Monday in California owes an hour of overtime for that day alone, regardless of total weekly hours. Workers who move between states within a single week push this further still: the contractor has to track which state's rules governed each day's hours separately, a genuinely difficult data problem once a system is tracking it by hand rather than automatically. That tracking burden, multiplied across workers, classifications, and states, is the same structural problem that drives the compliance risk described in the next section.

State prevailing wage laws layered on federal requirements: New York and Virginia

State prevailing wage statutes don't just restate the federal Davis-Bacon framework with local paperwork attached. They extend coverage to workers and activities the federal law never reached, and they change on a faster schedule than federal rules do. When a single project draws on both federal and state funding, the contractor has to satisfy both frameworks at once, paying whichever wage rate is higher and meeting whichever jurisdiction's administrative requirements are more demanding.

New York made four significant changes effective in 2026. Electronic certified payroll filing became mandatory as of December 31, 2025, and paper filing is no longer accepted at all; every submission now runs through the NYS DOL's MPWR portal. A prevailing wage expansion for trucking took effect January 1, 2026, covering truckers who haul concrete and asphalt in a set of designated downstate counties: these workers must now be paid prevailing wages for travel time, loading and unloading, and detention time in addition to the hours spent actively hauling. Minimum wage rates rose the same date, to $17.00 an hour in the downstate region, with a lower rate for the rest of the state and higher exempt salary thresholds alongside it. A fourth change, amendments to Labor Law § 220(3)(f) extending coverage to custom-fabricated materials built off-site for specific New York public works projects, remains suspended by federal court order, and the state Department of Labor is not currently enforcing it. Contractors evaluating these changes should treat the fabrication rule as paused rather than active, and budget for real cost increases tied specifically to the trucking expansion where it applies.

Virginia moved in the same direction from a different angle. Governor Spanberger signed legislation in April 2026 that strengthens the state's prevailing wage program, shifting toward Virginia-specific rate-setting and expanding wage theft enforcement under HB 238, which gives the state civil remedies and enforcement authority over wage, overtime, misclassification, and prevailing wage claims. New York's shift to mandatory electronic filing is itself an instance of a wider pattern, as more states move toward portal-based submission systems that weren't necessarily designed with existing construction payroll software in mind.

Electronic filing mandates and compliance risk for legacy payroll systems

New York's electronic filing mandate exposes a mismatch that has nothing to do with whether a contractor intends to comply. The state's portal accepts certified payroll data only as XML file uploads, and producing a properly formatted XML file takes technical knowledge that most payroll teams simply don't have sitting in-house. Common construction payroll platforms, including Sage/Timberline, don't offer a clear import or export path built for the NYS portal, which leaves contractors re-entering the same data by hand for every weekly submission across every active project.

The weekly workflow compounds the risk. Timesheets get collected on Friday, payroll gets processed against the applicable prevailing wage rates, an internal compliance review happens, and the submission goes in, all inside a tight window. Manual re-entry errors introduced at any point in that chain typically appear only in post-submission audits, after the submission has already gone to the state. No automated reconciliation exists between a contractor's internal payroll records and what actually got submitted through the portal, so a discrepancy introduced in week one can persist for several weeks before an audit catches it.

The penalties attached to non-compliance with New York's electronic filing rule are not minor administrative fines. They include payment holds placed directly on project contracts, work stoppages on active projects, debarment from future public works projects, civil penalties, and back wage liability. A contractor whose internal systems can produce a correct paper report but can't generate a properly formatted XML file is, under this rule, no more compliant than one that filed nothing at all. As more states adopt their own portal-based filing systems, each with its own data format and its own technical requirements, the gap between what a contractor's payroll system can output and what the state demands only grows wider with every new jurisdiction added to a contractor's project list.

Building a certified payroll compliance process for multi-state and multi-subcontractor conditions

Every element described above, wage determinations that vary by county and classification, a federal form with specific fields and a signature requirement, overtime rules that stack federal and state calculations on top of each other, and state portals with their own data formats, points toward the same operational conclusion. Certified payroll compliance cannot be managed project by project or state by state as separate problems, because the underlying data, which worker performed which classification of work on which day in which jurisdiction, is the same data every one of these requirements draws from. A process built to track that data accurately at the point of entry, rather than reconstructing it after the fact to satisfy a specific form, is what holds up when a contractor is running projects in multiple states with multiple tiers of subcontractors at once.

The practical requirement is tracking hours, classifications, locations, and rates at the level of the individual worker and the individual day, below the weekly aggregate most payroll systems default to. Subcontractor oversight has to work the same way: a prime contractor responsible for every subcontractor's timely and complete filing needs visibility into those filings before the weekly deadline, not confirmation after a late submission has already triggered an inquiry. And as more states move toward mandatory electronic portals with their own file formats, the contractors least exposed to compliance risk will be the ones whose underlying payroll data was structured correctly from the start, built to be reshaped into whatever a state portal demands next, rather than retrofitted to each new mandate as it arrives.