Why Certified Payroll Is
a Manual Nightmare for Small Contractors

The WH-347 Is a Pre-Internet Form, and the DOL Has No Plans to Change It

Let's start with the artifact at the center of this system.

Federal Form WH-347 — the standard certified payroll report for Davis-Bacon and Related Acts compliance — is available on the Department of Labor website as a PDF. You can download it, open it in Adobe Acrobat, type into the fields, print it, and sign Page 2, the Statement of Compliance. The DOL also offers an "online fillable" version, which renders the same grid of boxes in a browser window. What the DOL has never built is an API. There is no machine-readable endpoint that a payroll system can POST certified payroll data to and receive a confirmation receipt. There is no structured data exchange format. There is no digital submission standard that all federal contracting agencies accept. Some agencies have their own portals — LCPtracker, eCOMM, Elation — but each one is a separate system with its own interface, its own login, and its own interpretation of what a complete certified payroll looks like.

The form itself is dense. For each worker on each project for each week, you must report: full name, last four digits of SSN, journeyworker or apprentice status, work classification, hours worked each day Monday through Sunday split between straight time and overtime, total hours, rate of pay (base rate plus fringe benefit rate), gross amount earned, and itemized deductions. The DOL's own estimate, cited by compliance software vendor Points North, is that completing this form manually takes over one hour per employee, per report. That estimate does not include the time spent finding the correct wage determination before you start filling it out, nor the time spent collecting subcontractor reports, nor the time spent fixing errors after you realize you used last quarter's wage determination instead of the one that was updated three weeks ago.

This would be unremarkable if certified payroll were a once-a-year filing. It is not. It is weekly. Every seven days, for every active federal project, you submit a new WH-347. And if the form itself hasn't changed — and it largely hasn't, aside from a 2025 revision that added apprenticeship tracking fields and tightened fringe benefit reporting — the surrounding complexity has multiplied. More Related Acts. More state-level little Davis-Bacon laws. More electronic submission portals, each demanding the same data in a slightly different format.

The WH-347 is not the problem. The problem is that every system built around it — the wage determination databases, the subcontractor reporting formats, the submission portals — treats the WH-347 as a destination form rather than a data standard. And the contractor is the one who has to carry data across all those gaps by hand.

Every Subcontractor Speaks a Different Payroll Language

On a public works project with five subcontractors, the prime contractor's weekly compliance task is not just filling out one WH-347. It is collecting certified payroll reports from five separate companies, each running different payroll software — or no software at all — and each producing reports in a format that makes sense to their own accountant but not to anyone downstream.

One sub uses Sage 300 CRE and exports a certified payroll report that includes the required fields but arranges them in columns the WH-347 doesn't map to. Another uses QuickBooks with a prevailing wage add-on that calculates fringe benefits correctly but outputs a PDF, not a spreadsheet — so the data has to be re-keyed. A third is a two-person electrical shop whose owner fills out the WH-347 by hand, scans it, and emails the scan. A fourth uses Foundation and sends a clean Excel file, but classifies workers under trade names that don't exactly match the wage determination's classification language, so someone has to verify whether "Electrician Journeyman" and "Journeyman Inside Wireman" refer to the same person doing the same work. The fifth subcontractor is late. Again.

The prime contractor's payroll administrator now faces a weekly data assembly operation: open five reports in different formats, verify classifications against the wage determination, check that hours match the daily logs, convert everything into WH-347 column order, compile into a single submission package, and sign the Statement of Compliance certifying that all of it is accurate under penalty of perjury. A single WH-347 with 12 workers already contains roughly 168 discrete data points — name, classification, 7 daily hour columns, rate, fringe, gross, deductions, net. Across five subcontractors, that number easily passes 800 fields per week. Every field is typed by hand, checked by eye, and certified by signature.

The format diversity is not a solvable problem at the subcontractor level. You cannot mandate that every sub you hire run the same payroll software. The subs work for multiple primes across multiple projects. Asking a small electrical contractor to buy Sage 300 CRE so their reports match your format is not reasonable. The government doesn't solve this either. The DOL accepts certified payrolls in any legible format as long as they contain the required information — but the act of assembling that information into a coherent package falls entirely on the prime contractor, with no tooling to bridge formats.

Finding the Right Wage Rate Shouldn't Be a Research Project

Before you can fill out a single WH-347, you need to know what wage rate each worker classification commands. That means looking up the prevailing wage determination for your project's county, construction type (Building, Highway, Heavy, or Residential), and contract award date.

Federal wage determinations live on SAM.gov. The database is public and searchable, but the search interface was built for contracting officers, not for payroll administrators. You need to know either the wage determination number (a string like PA20230002) or navigate by state, county, and construction type to find the correct document. Once you find it, the wage determination itself is not a table you can copy into Excel. It is a text document listing each labor classification — sometimes dozens of them — alongside a base hourly rate and a fringe benefit rate. The classifications use DOL's naming conventions, which may or may not match what your subcontractors call their workers. "Carpenter" might appear, or "Carpenter (Drywall Hanging Only)," or "Carpenter (Formwork)," each with a different rate.

That is the federal level. Twenty-eight states have their own prevailing wage laws — so-called "Little Davis-Bacon" acts — each with its own wage determination database hosted on a different state website. California's Department of Industrial Relations, New York's Department of Labor, New Jersey, Pennsylvania, Illinois — each maintains its own system. A contractor working on a project with mixed federal and state funding may need wage determinations from both SAM.gov and a state portal, and the rates need to be reconciled. If you use the wrong determination, even by one modification number, the worker classification rates will be wrong, and every certified payroll report built on those rates will contain errors that compound across every week of the project.

For small contractors, the wage determination lookup is a task that gets done once at the start of a project — if it gets done at all. The KORE1 article on certified payroll compliance described the small-contractor reality bluntly: "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." When a wage determination is updated mid-project — as happens when DOL publishes a new modification — the contractor may not notice for weeks, and those weeks of certified payrolls are all noncompliant.

Seven Days. No Buffer. No Do-Overs Without a Paper Trail.

The Davis-Bacon regulations at 29 CFR 5.5(a)(3)(ii) require certified payroll reports to be submitted within seven days of the end of each pay period. This deadline is not a suggestion. Contracting agencies can — and do — withhold contract payments for late or missing certified payrolls. For a small contractor operating on thin margins and relying on progress payments to cover payroll, materials, and equipment, having a payment withheld because a certified payroll is two days late is not a compliance problem. It is a cash flow crisis.

The seven-day window also leaves virtually no room for error correction before the next report is due. If you discover on Thursday that last week's WH-347 misclassified two electricians as general laborers, you need to submit a corrected report. You also need to prepare this week's report before the weekend. The correction and the new report share the same deadline. The result, in practice, is that errors are either corrected late — which itself is a compliance flag — or not caught at all, and they sit in the project file until an audit surfaces them months or years later.

Certified payroll corrections are legally permitted and, in the eyes of an auditor, far better than undiscovered errors. But the correction itself creates another data point that has to be tracked. The corrected report must reference the original payroll number and week ending date, clearly identify what changed, and include a new signed Statement of Compliance. In a manual system, that is another form to fill out, sign, and file. In a busy payroll office where next week's report is already overdue, the correction gets deprioritized. And the liability accumulates.

611 Investigators, 120 Million Workers: The Enforcement Lottery

The staffing figure from the Workplace Justice Lab report deserves to sit alone for a moment: 611 investigators for 120 million workers. That is not a ratio designed for systematic enforcement. It is a ratio designed for random deterrence. The theory is that if every contractor knows an audit could happen, that threat is enough to produce compliance. The reality is that most contractors will complete an entire three-year federal project without ever seeing a DOL investigator. They might complete five. And then, on the sixth project, a worker complaint about a shorted paycheck triggers an audit that opens every certified payroll report from the last three years.

The liability window extends backward. Davis-Bacon regulations require contractors to retain payroll records for at least three years after project completion. An audit initiated in 2026 can examine certified payrolls from a project completed in 2023. If errors are found — underpaid wages, misclassified workers, missing fringe benefits — the contractor owes back wages with interest, and the interest compounds daily under 26 U.S.C. § 6621. The math gets worse quickly. On a project where 15 workers were underpaid by an average of $2 per hour over 40 hours per week for 20 weeks, the back wage liability alone is $24,000. Add CWHSSA liquidated damages for overtime violations and civil penalties, and a single audit can produce a liability figure that exceeds the profit margin on the project that triggered it.

The Department of Labor recovered $259 million in back wages in fiscal year 2025 — the highest since 2019, averaging $1,465 per affected worker. Since 1985, Davis-Bacon enforcement has resulted in over 119,000 violations and more than $197 million in back wages. The quantities are large, but the denominator is enormous: an estimated 1.2 million construction workers are covered by Davis-Bacon each year, working on $217 billion in federal and federally assisted construction. Most of those workers are paid correctly most of the time. The risk is not that enforcement is frequent. The risk is that when it happens, it is severe, and retroactive, and unforgiving.

You Are Legally Responsible for Everyone Else's Mistakes

This is the structural feature of Davis-Bacon compliance that most surprises contractors entering the federal market for the first time: prime contractor strict liability.

Under 29 CFR 5.5(a)(3)(ii), the prime contractor is responsible for the compliance of every subcontractor on the project, including lower-tier subcontractors that the prime may never have directly hired. If a second-tier sub misclassifies a worker, the prime is on the hook. If a subcontractor goes out of business and cannot pay the back wages owed to its workers, the prime contractor pays. Contract funds can be withheld from the prime to satisfy a subcontractor's wage liability. In enforcement actions, the DOL has debarred prime contractors not because they committed violations themselves, but because they failed to adequately monitor their subcontractors' compliance.

This is strict liability in the legal sense: the prime does not need to have known about the violation to be held responsible for it. The only defense is to have caught and corrected it before the DOL did. But catching subcontractor errors requires reviewing every certified payroll every subcontractor submits every week — the same assembly task that already consumes the prime's payroll administrator, now with an adversarial lens. You are not just verifying that the sub sent something. You are verifying that the worker classifications match the work actually performed on site, that the wage rates match the current wage determination, that the hours match the daily logs, that the fringe benefit calculations are correct, and that the Statement of Compliance is signed. For five subcontractors, this is a part-time job nobody has time for. But the liability says it is your job whether you do it or not.

General contractors have lost contracts worth millions for subcontractor paperwork failures they didn't know about. KORE1 documented a GC that lost a $4.2 million federal highway contract because the payroll administrator had been submitting reports late and the DOL flagged misclassifications during a routine audit. The owner "didn't even realize the reports were late until the audit letter showed up." The bonding company pulled surety within two weeks of the finding. A twelve-year relationship with the federal government ended over payroll paperwork.

The Small Contractor's Impossible Equation

There is a structural trap built into the certified payroll system that hits small contractors harder than anyone else. It works like this:

A large general contractor with 200 employees and a dedicated compliance department can absorb the cost of certified payroll. They run specialized construction payroll software like Foundation or Sage 300 CRE with prevailing wage modules. They have a payroll administrator whose only job is certified compliance. They have internal audit processes. They can afford to get it right.

A small contractor with 15 employees cannot. The owner's spouse or the office manager handles payroll, along with AP, AR, bidding, and everything else. There is no budget for specialized software, no time for internal audits, and no room to hire a compliance specialist. The economics of a $400,000 public works contract for a small electrical firm do not support a $15,000 annual investment in compliance infrastructure. So the compliance task is done manually, in the gaps between everything else, by someone who may understand the Davis-Bacon requirements at a surface level but has never read 29 CFR Part 5.

The trap is that the penalty structure does not scale with company size. A $28,619 civil penalty hurts a 200-employee GC. It destroys a 15-employee electrical contractor. A three-year debarment from federal contracts is survivable for a diversified company with private-sector work. For a small contractor who has built a reputation in public works, debarment means the business is effectively over. The same violation — misclassifying two workers, missing a wage determination update, signing a Statement of Compliance on a report you didn't fully verify — produces the same legal consequences whether you have five employees or five hundred. But the ability to prevent that violation is radically different.

Small contractors are not less careful than large ones. They are less resourced. And the certified payroll system, by design, treats them identically.

What Would Actually Fix This

This article has deliberately avoided discussing solutions until now because the structural problems of certified payroll compliance deserve to be understood on their own terms. There is no single tool that makes the enforcement lottery disappear or eliminates prime contractor strict liability. But three changes in how data moves through the compliance pipeline would meaningfully reduce the burden on small contractors:

A single data standard for certified payroll submissions. If the DOL published a machine-readable schema — the way the IRS publishes e-file specifications for tax returns — every payroll software vendor could export to it, and every agency portal could import from it. The subcontractor format problem would not disappear, but it would become a one-time mapping exercise instead of a weekly re-keying exercise.

A unified wage determination API. SAM.gov already hosts the data. Making it queryable by county, construction type, and effective date through a simple API would let payroll systems pull the correct rates automatically instead of requiring a human to find the right PDF and manually transcribe rates into a spreadsheet.

Automated subcontractor report validation. The prime contractor needs to review every sub's certified payroll. But the review doesn't have to be manual. Checking that worker classifications match the wage determination, that hours add up, and that rates are correct is pattern matching — exactly the kind of task AI-based extraction can handle. Tools that can read certified payroll reports from any format and map the data into a standard structure close the gap between what the prime contractor is legally required to verify and what a small office can actually verify on a weekly basis.

The goal is not to make certified payroll compliance effortless. Davis-Bacon exists for a purpose: ensuring that workers on taxpayer-funded projects are paid fair wages. The compliance obligation is legitimate. But the tools available to meet that obligation have not kept pace with the complexity of the obligation itself. When the WH-347 is still a fillable PDF, the wage determination database is still a text-search portal, and every subcontractor delivers data in a different format, the system is asking small contractors to bridge gaps that technology closed in every other industry a decade ago.

Frequently Asked Questions

Can a small contractor get debarred for an honest mistake on certified payroll?

Yes. Debarment under the Davis-Bacon Act requires "disregard of obligations," which includes negligent errors, not just intentional fraud. The DOL has debarred contractors for patterns of misclassification, late submissions, and uncorrected errors — none of which require proof of intent. For Davis-Bacon Related Acts, the standard is higher (willful or aggravated violations), but the DBA itself sets a lower bar. Even if debarment is ultimately avoided, the investigation process itself can consume months of legal costs and management attention that a small contractor cannot easily absorb.

Does every prime contractor really face strict liability for subcontractor mistakes?

Yes, and the DOL's own training materials for contracting agencies are explicit about this. The obligation is joint and several: if a subcontractor owes back wages and cannot or will not pay, the prime contractor is financially responsible. Contract funds can be withheld from the prime regardless of which tier of subcontractor caused the violation. This is not a theoretical risk. The Jackson Lewis law firm, which represents construction employers, notes that "the DOL has debarred prime contractors that have failed to properly monitor their subcontractors with respect to the DBRAs' requirements."

Why doesn't the DOL just create a digital submission system?

The DOL's position is that the WH-347 is optional in form (you can submit certified payroll data in any format) and that contracting agencies, not the DOL, are responsible for collecting and reviewing certified payrolls. In practice, this has led to a patchwork: some agencies use LCPtracker, others use eCOMM, others still accept paper. The DOL published an updated WH-347 in 2025 that added apprenticeship and fringe benefit fields, but the form remains a PDF. There is no publicly announced plan for an API or structured data exchange standard.

How much does manual certified payroll processing actually cost a small contractor?

The DOL estimates that manual WH-347 preparation takes over one hour per employee per report. For a 15-worker crew on a single project, that is 15+ hours per week just for the report itself. At a $25/hour effective rate for a payroll administrator, that is $375/week or $19,500/year for one project. Add the time for wage determination lookups, subcontractor report collection and review, error correction, and recordkeeping, and the annual cost of manual certified payroll compliance for a small contractor with two active projects can exceed $40,000 in labor alone — without accounting for the cost of errors. A deeper cost framework is available in our analysis of manual certified payroll processing costs.

What triggers a certified payroll audit?

Worker complaints are the most common trigger. A single employee who believes they were underpaid can file a complaint with the WHD, which may open an investigation that examines all payroll records for the entire project. Other triggers include agency-initiated reviews during contract closeout, discrepancies flagged during routine certified payroll reviews by contracting agencies, and complaints from competing contractors. Audits can also be random. The WHD conducts industry-targeted investigations in "low wage, high violation" sectors, of which construction is one.

Can AI actually help with certified payroll data extraction?

It depends on the approach. Traditional template-based OCR — the kind that requires you to draw boxes around each field on a form — is poorly suited to certified payroll because every subcontractor's report has a different layout. A tool that reads documents by understanding what each column means rather than where it sits (semantic extraction, as opposed to coordinate-based extraction) can handle format diversity across subcontractor reports. This is the mechanism behind ImageToTable.ai's Custom Column Extraction: you specify the column names you want — "Worker Name," "Classification," "Base Rate," "Fringe Rate," etc. — and the AI locates the corresponding values wherever they appear on each subcontractor's report, regardless of layout. For a deeper technical walkthrough, see our guide on extracting certified payroll reports to Excel.

Are there alternatives to doing certified payroll by hand?

Three paths exist: specialized construction payroll software (Foundation, Sage 300 CRE, hh2) with prevailing wage modules that generate WH-347 reports directly from time entry data; outsourced payroll providers that handle prevailing wage calculation and certified payroll preparation as a service; and extraction tools that read subcontractor payroll reports in any format and map the data into your submission structure. The right approach depends on how many projects you run, how many subcontractors you manage, and whether you can afford software that costs thousands annually. For a construction company new to federal work, our beginner's guide to certified payroll covers the fundamentals.

The Compliance Gap Doesn't Close Itself

Certified payroll compliance is not going to get simpler. The 2023 Davis-Bacon final rule expanded coverage, tightened enforcement standards, and introduced more granular reporting requirements. The WH-347 revision taking effect in September 2026 adds fields. Infrastructure spending under the Bipartisan Infrastructure Law is still ramping up, bringing more contractors into the Davis-Bacon system for the first time. The investigator headcount is not likely to increase dramatically regardless of administration. The enforcement dynamic — rare but devastating — will persist.

The question for a small construction contractor is not whether the system is fair. It is whether you can afford to keep bridging the gap between what the law requires and what your current tools enable. If you are assembling certified payroll reports by manually copying data from PDFs into WH-347 fields every week, the gap is wider than you think. And it doesn't close by itself.

Start with the data you already have. Upload a subcontractor's certified payroll report. Enter the column names you need extracted. See whether the 15 hours you spent last week assembling reports becomes 15 minutes.

Test on Your Own Payroll Reports