What Is Certified Payroll in Construction

Certified payroll in construction is a weekly payroll report, submitted on Form WH-347, that proves contractors on federally funded projects are paying workers at or above the prevailing wage. Required under the Davis-Bacon Act for any federal or federally assisted construction contract over $2,000, it’s the government’s primary mechanism for catching wage violations before they become systemic.

A general contractor we work with lost a $4.2 million federal highway contract last year. Not because the work was bad. The work was fine. Their payroll administrator had been submitting certified payroll reports late, sometimes two or three weeks behind schedule, and had misclassified two electricians as general laborers on the WH-347 forms. The Department of Labor flagged the discrepancies during a routine audit, withheld the remaining contract funds, and the bonding company pulled surety within two weeks of the finding. Then the three-year debarment hit. Four months of sloppy paperwork ended a twelve-year relationship with the federal government, and the GC’s owner told us he didn’t even realize the reports were late until the audit letter showed up.

That story isn’t unusual. With $217 billion in annual federal construction spending flowing through more than 12,000 active projects in 2026, the DOL is auditing more aggressively than it has in decades. If your company handles federal or state prevailing wage projects and you’re not confident your construction payroll services can hold up under scrutiny, this is worth reading carefully.

How Certified Payroll Works

Every week, each contractor on a federally funded construction project submits a report documenting every worker’s hours, job classification, wage rate, fringe benefits, and deductions. Attached to that report is a signed Statement of Compliance where someone with authority at the contracting company certifies, under penalty of perjury, that every worker was paid at least the prevailing wage for their specific trade and geographic area.

That last part matters more than people think. The prevailing wage isn’t one number. It shifts by trade, by county, sometimes by project type. An electrician on a highway project in Los Angeles County earns a different prevailing rate than an electrician on a building project twenty miles away in Orange County, even if they hold the same license and do the same caliber of work. Miss that distinction and you’re underpaying people without realizing it. The DOL doesn’t care whether you meant to or not.

Reports go to the contracting agency weekly. Even during weeks when nobody set foot on the job site, you still submit. A “no work” report. Skip a week and it reads like you’re hiding something. Auditors treat it that way.

The Davis-Bacon Act and Why It Still Matters

The Davis-Bacon Act goes back to 1931. Depression-era problem, blunt solution. Federal construction projects kept going to whichever bidder paid workers the least, out-of-state firms were undercutting local contractors by busing in cheaper crews, and wages across entire regions were collapsing under the weight of government contracts that were supposed to be helping those same communities. Two Republican congressmen from New York got tired of watching it happen to their constituents and wrote the bill.

So Congress set a floor. Every federal construction contract over $2,000 had to pay the “prevailing wage” for each trade in the area where the work happens. That $2,000 threshold hasn’t moved in ninety-five years. Tells you something about how often Congress revisits construction labor law. Related acts later extended the same requirement to federally assisted projects, things like the Federal-Aid Highway Act and the Housing and Community Development Act, so the reach is wider than most contractors assume when they first encounter it.

What has changed, and changed significantly, is enforcement. The DOL issued its 2024 final rule, which was the most substantial regulatory update to Davis-Bacon in four decades. It changed the methodology for calculating prevailing wage rates, broadened who counts as a covered worker, added anti-retaliation protections that didn’t exist before, and ratcheted up the penalties for violations in ways that caught a lot of mid-size contractors off guard. Some of them are still adjusting. Some of them are adjusting in front of an auditor, which is a rough place to learn.

Who Has to Submit Certified Payroll

Every contractor and subcontractor performing work on a covered project. Not just the prime.

This trips people up constantly. The general contractor submits their own certified payroll for their direct employees, sure. But they’re also on the hook for collecting certified payroll from every sub on the project and submitting the full package to the contracting agency. The electrical sub. The plumbing sub. The concrete crew. The drywall guys who showed up for three weeks and then moved to another job. Every single one.

Sit with that for a minute. You’re liable for the payroll accuracy of companies you didn’t hire, run by people you’ve maybe met twice, employing workers you couldn’t pick out of a lineup. That’s federal construction liability in a nutshell. And it’s why general contractors who don’t have a real system for collecting and reviewing sub payrolls before submission keep ending up in trouble they didn’t create but absolutely own. We had a GC client last year who was doing everything right on their end, pristine payroll records, but a second-tier plumbing sub had been classifying apprentices wrong for months. The GC submitted those reports. The GC got the audit letter.

Quick note on who’s actually covered. The requirement applies to “laborers and mechanics,” which sounds narrow but isn’t. Truck drivers who deliver materials and do manual work at the site? Covered. Flaggers? Covered. The guy who operates the crane and also does rigging? Almost certainly covered for both functions. The 2024 rule pushed the boundary further out, not closer in.

What Goes on the WH-347 Form

Form WH-347 is the standard certified payroll form from the Department of Labor. Using it is technically optional. You could submit your own format. In practice, almost nobody does, because showing up with a non-standard form is an invitation for auditors to spend an extra hour asking you questions about why you needed to do it differently. Not worth the conversation.

The form got updated in 2025 and the changes aren’t cosmetic. Each worker now has to be explicitly identified as either a journeyworker or a registered apprentice, which used to be handled inconsistently from one contractor to the next and which created a whole category of classification disputes that the DOL was tired of litigating. Two pages. Page 1 is the payroll data itself. Page 2 is the Statement of Compliance, broken into separate certifications for proper payment, accurate records, apprenticeship requirements, fringe benefits, and deductions.

Page 1 fields: worker name, last four of Social Security (full SSN on the first report only, mercifully), work classification, hours worked each day of the week, total hours, rate of pay, gross wages earned, each deduction itemized, and net wages paid. Plus the project name, contractor name, payroll number, and week ending date. It’s a lot of fields. Miss one and the form comes back.

Page 2 is where an authorized officer at your company signs under penalty of perjury. That phrase gets thrown around loosely in business contexts, but here it is literal. The statement explicitly warns that willful falsification triggers prosecution under 18 U.S.C. 1001. Fines. Up to five years in federal prison. People sign it every week without reading past the signature line. I’ve watched them do it.

Certified Payroll vs. Regular Payroll

Every construction company runs payroll. Certified payroll is a compliance reporting layer that sits on top of your regular process, and the two serve completely different masters. One pays your people. The other proves to the government that you paid them correctly.

The operational gap is where companies get hurt. Regular payroll runs biweekly or semi-monthly and stays internal. Certified payroll is weekly, always, and it goes to a government agency that will actually read it. Most standard payroll platforms, your QuickBooks and your Paycom and your ADP Run, weren’t built to handle prevailing wage lookups by county and project type, WH-347 formatting, or fringe benefit allocation math where the health plan covers $8.40 of the required $14.25 fringe rate and you need to make up the $5.85 difference in cash on every single paycheck. That gap between what your software does and what certified payroll requires is where compliance failures breed.

Prevailing Wage Rates and How They’re Set

The DOL publishes prevailing wage determinations through SAM.gov, which used to be called wage.gov before somebody decided it needed a rebrand. Each determination specifies the hourly base rate and fringe benefit rate for every covered trade classification in a given geographic area.

Finding the right one is harder than it sounds. You need the correct county. The correct project type, and there are four categories: building, heavy, highway, and residential. And the correct trade classification, which is its own headache because a worker who does carpentry and concrete form work might need dual classification depending on how the hours split. Two carpenters on the same block, one on a highway job and one on a building job, can have completely different prevailing wages for the same physical work. Get the determination wrong at the start of the project and every single payroll you submit after that is wrong by default.

Fringe benefits make it worse. The prevailing wage has two parts: the base hourly rate and the fringe benefit rate. You can satisfy the fringe requirement with actual benefits, health insurance and pension contributions and vacation pay, or you can pay it as cash on top of the base rate. Mix and match works too. But the total has to meet or exceed the combined rate for that trade and county, and a surprising number of contractors who pay perfectly fair base wages still fail compliance because they never calculated whether their benefits package actually hits the required fringe number. It often doesn’t. Fringe shortfalls are one of the most common DOL audit findings precisely because so many contractors don’t track them as a separate line item.

One more wrinkle. Wage determinations can change mid-project. The one that was current when the contract was awarded is usually locked in, but modifications and new classifications get published regularly, and keeping track of which determination applies to which workers on which project across multiple jobs running simultaneously is genuinely a full-time compliance function. For a 20-person contractor running three federal projects in two counties, it’s already more than one person can reliably manage in a spreadsheet.

What Happens When You Get It Wrong

Penalties stack faster than contractors expect, and the consequences aren’t symmetrical. Small violations get expensive. Big violations end companies.

Debarment is the one that kills. Not a fine. Not a slap. A three-year ban from all federal work, and it cascades in ways the statute doesn’t mention. Every GC bidding federal projects stops calling you as a sub. Your surety company recalculates your risk profile and your bonding capacity drops, sometimes to zero. The debarment listing goes up on SAM.gov where every contracting officer and every prime contractor in the country can search it. Three years is a long time to survive on private work alone, especially if federal projects were 40 or 50 percent of your revenue.

Back wages hit harder than people expect too. If an electrician was classified as a laborer for six months, you owe the wage differential for every hour worked during that period, and when you multiply that across a crew of eight or ten people who were all misclassified the same way across twenty-six pay periods, the number reaches six figures before anyone in the room stops being surprised. The 2024 rule added liquidated damages that can double the back wage amount. That was new. A lot of contractors still don’t realize it’s on the table.

Criminal prosecution is rare. Genuinely rare. Reserved for people who knowingly falsified records, not for honest mistakes. But when you’ve been signing a Statement of Compliance every week for six months swearing that you personally verified those wage records were accurate, the honest-mistake argument gets hard to sell to a federal prosecutor who can see that you signed forty-two separate certifications without catching a classification error that shows up on line three of every single form.

How Construction Companies Handle Certified Payroll

Three approaches, and we’ve seen all three work and all three fail depending on who’s actually doing the work.

In-house with general payroll software. Most small contractors start here. QuickBooks handles the regular payroll run, and somebody on the team, usually the office manager or the owner’s spouse or a bookkeeper who also handles AP and AR, manually prepares the WH-347 from that data. It works for a while. The prevailing wage lookups are manual, the fringe calculations live in a spreadsheet that hasn’t been audited since it was created, and the person responsible has five other jobs that feel more urgent on any given Friday afternoon. We’ve seen this setup produce clean certified payrolls for years. We’ve also seen it produce the kind of errors that trigger debarment. The difference is entirely about whether the person doing it actually understands what they’re certifying when they sign Page 2.

Specialized construction payroll software. Platforms like Foundation, Sage 300 CRE, or hh2 that were built for prevailing wage work. They pull wage determinations automatically, generate WH-347s, track fringe allocations by trade, and flag mismatches before you submit. Good option for mid-size contractors running multiple federal projects who have outgrown the spreadsheet approach. The catch is that the software can’t fix what you put into it. If someone enters a journeyworker as a laborer in the system, the software will faithfully generate a perfect-looking WH-347 with the wrong classification on it. You still need a person who understands the compliance requirements reviewing the output before it goes out the door.

Outsourced to a payroll provider. You hand the whole thing, prevailing wage calculation, WH-347 prep, fringe tracking, submission, to a company whose entire business model depends on getting it right. Compliance becomes their problem instead of your side project. And the liability shifts in a meaningful way. A reputable provider accepts responsibility for errors on their end, which is a very different risk profile than absorbing all the downside yourself while also trying to pour concrete and manage subs and bid new work.

For contractors who are growing into federal work or running their first prevailing wage project, outsourcing almost always makes more sense than trying to build internal expertise from scratch, because the learning curve on certified payroll compliance is steep enough that the cost of mistakes during the learning period routinely exceeds the cost of payroll outsourcing for the entire project duration. Companies that handle accounting and finance functions for construction firms see this pattern on repeat.

Common Mistakes That Trigger Audits

Misclassifying workers. Most frequent violation. Most expensive to fix. Calling a journeyworker electrician a “helper” to pay a lower prevailing rate is the textbook version, but the subtler ones are just as dangerous. Carpenter who also does form work? Might need dual classification. Worker who splits time between covered and non-covered tasks? Hours have to be allocated correctly or the whole payroll is wrong. The 2024 rule expanded who counts as a covered worker, which means some classifications that were perfectly defensible three years ago won’t survive a current audit.

Fringe shortfalls. Paying the right base rate but coming up short on fringes. Happens constantly when contractors offer a health plan that covers $9 of a $15 fringe requirement and never do the math on the gap. Also shows up when apprentice fringes get calculated off the journeyworker rate instead of the apprentice schedule. Both are underpayments, and neither is obvious until someone audits the numbers line by line.

Late submissions. Certified payroll is due weekly. Not when the project manager remembers. Not at month-end when accounting batches everything together. Weekly. Consistently late submissions tell an auditor that your internal controls are weak, and that invites deeper scrutiny into everything else on the project.

Incomplete records. Gaps between the sign-in sheet and the certified payroll are red flags that practically glow. If your site log shows 14 workers on Tuesday and your WH-347 shows 11, the auditor’s next question is going to be about the other three, and “I’m not sure” is not a good answer.

Apprentice ratio violations. Federal projects cap the ratio of apprentices to journeyworkers. Exceeding that cap while paying apprentice-level prevailing rates to workers who should have been classified as journeyworkers is a wage violation even if those apprentices are legitimately enrolled in a program. Using “apprentice” as a classification for someone who isn’t in a DOL-approved program? That’s straight misclassification.

What Contractors Ask Us

Does certified payroll apply to state projects too, or just federal?

Both, usually. Thirty-two states plus DC have their own prevailing wage laws, sometimes called “little Davis-Bacon” acts, and each one has its own thresholds, its own forms, and its own enforcement quirks that don’t necessarily match the federal version. California’s requirements are notoriously detailed and the penalties are steep. Texas went the other direction entirely and repealed its state prevailing wage law back in 1993. The state that matters is where the project sits, not where your company is headquartered, and that catches multi-state contractors off guard more often than you’d think.

We’re a sub, not the GC. Whose problem is certified payroll really?

Yours and theirs. You prepare accurate certified payrolls for your own workers. The GC collects them and submits the package. If your reports are wrong, you face the back wage liability and potential debarment. The GC also faces consequences for submitting inaccurate sub payrolls they should have caught. Nobody walks away clean when certified payroll goes sideways on a project.

What if we use staffing agencies or temp workers on a prevailing wage job?

The staffing provider is the employer of record for those workers, so they’re the ones who have to submit certified payroll, pay prevailing wages and fringes, and sign the Statement of Compliance. That said, you should absolutely be verifying that it’s happening. If the staffing company cuts corners and the DOL comes looking, they don’t knock on the staffing company’s door first. They knock on the prime contractor’s.

How far back can the DOL go in an audit?

Three years from project completion is the standard window, and that’s also the minimum record retention period under federal rules. Fraud suspicion blows the window open, no statutory limit. Keep your records for at least three years. Four if you want to be safe. Digital copies are fine as long as they’re complete, organized, and producible on demand, which is a higher bar than “we have them somewhere on a shared drive.”

Can we fix a certified payroll after it’s been submitted?

Corrected payrolls are not only allowed, they’re expected when you find an error. Submit a corrected WH-347 clearly marked as a correction, reference the original payroll number and week ending date, and flag what changed. The difference between a contractor who self-corrects and one who gets caught is enormous in the eyes of an auditor. One demonstrates good faith. The other demonstrates something the auditor is going to write up.

Certified payroll compliance isn’t conceptually complicated. Weekly reports. Correct classifications. Prevailing wages. Signed certifications. Where it falls apart is in execution, particularly when you’re juggling three projects across two counties with different wage determinations, twelve subs rotating crews in and out, and a payroll administrator who’s also running AP and answering the phone. If that sounds like your operation, it’s worth having a conversation about how to fix it before the DOL has one with you. Talk to our payroll team about how we handle certified payroll for construction contractors.