ProBuildermuse Pro is live — Fire sale: Pro for $1.99/mo.Get Pro
B
Buildermuse
Labor & Wages

Certified Payroll on Government Jobs: The WH-347 Mistakes That Trigger Audits

Sarah Torres·September 23, 2026·14 min read
Certified Payroll on Government Jobs: The WH-347 Mistakes That Trigger Audits

A single false statement on a certified payroll can carry a fine and up to five years in federal prison under 18 USC 1001 — and the person exposed is not an abstract "company," it is the individual owner, officer, or payroll clerk who signed the Statement of Compliance that week. The Department of Labor's Wage and Hour Division recovered $32.9 million in back wages for construction workers in fiscal year 2023, and certified payroll records were the paper trail in nearly every case. For contractors working government jobs, the WH-347 is not administrative housekeeping. It is a sworn weekly statement, and it is the first document an investigator reads.

The obligation reaches further than most contractors realize. Every prime and every subcontractor at every tier on a Davis-Bacon covered job — any federal construction contract over $2,000, plus tens of billions of dollars in federally assisted state and local work — must submit a certified payroll for every week in which any covered work is performed. With roughly 1.2 million workers on Davis-Bacon covered projects at any given time and the 2021 infrastructure law still pushing hundreds of billions of dollars through covered programs, more contractors are filing WH-347s today than at any point in the law's 91-year history. Most of the ones who get in trouble make the same eight or nine mistakes. This article walks through the form, the rule, and the audit triggers.

What 29 CFR 5.5 Actually Requires Every Week

The weekly submission duty

The regulation is 29 CFR 5.5(a)(3)(ii): the contractor shall submit weekly, for each week in which any contract work is performed, a copy of all payrolls to the contracting agency (or, on federally assisted work, to the applicable funding recipient). "Weekly" means weekly — not monthly batches, not end-of-job packages. The payroll is due within seven days after the regular pay date for the pay period. A prime contractor is responsible for the submission of payrolls by all subcontractors, which means a prime that lets a second-tier sub go silent for six weeks owns that gap when the agency asks for the file.

The payroll must show, for each covered worker: name, an individually identifying number (the last four digits of the Social Security number — full SSNs and home addresses were removed from the submitted copy by DOL's 2008 rule change, though contractors must keep them on file), work classification, daily and weekly hours, rate of pay including fringe, gross wages, deductions itemized, and net wages paid. Since the 2023 Davis-Bacon final rule took effect on October 23, 2023, contractors must also maintain each worker's phone number and email address in their records — not on the submitted payroll, but available to WHD on request.

The WH-347 form itself

DOL publishes optional form WH-347 for this purpose. Its use is optional; its content is not. A contractor may submit payroll from its own software in any format that contains all the required data elements, which is why electronic systems can generate compliant equivalents. The form is one page of columns — worker, classification, day-by-day hours split between straight time and overtime, rate, gross, deductions, net — plus the reverse side, which is where the legal weight sits.

The current WH-347 (OMB control number 1235-0008) estimates 55 minutes of burden per submission. A contractor running a 20-week job files 20 of them. A prime with six subs on that job is responsible for the existence and review of roughly 140 weekly payrolls. That volume is exactly why sloppy patterns develop, and sloppy patterns are what auditors are trained to see.

The Statement of Compliance is a sworn document

Page two of the WH-347 is the Statement of Compliance required by 29 CFR 5.5(a)(3)(ii)(B) and 29 CFR Part 3 (the Copeland Anti-Kickback regulations, rooted in 40 USC 3145). The signer — who must be the contractor, or a person who supervises the payment of wages — certifies three things: that the payroll is correct and complete, that each worker was paid the full weekly wage with no impermissible deductions or kickbacks, and that each worker was paid not less than the applicable wage determination rate for the classification of work performed. Item 4 of the statement requires the signer to check a box declaring how fringe benefits were handled: paid into approved plans, funds, or programs (4(a)), paid in cash (4(b)), or a split explained in the exceptions section (4(c)).

That signature is what converts a bookkeeping error into potential criminal exposure. The form itself says so, in print, directly above the signature line: falsification may subject the contractor or subcontractor to civil or criminal prosecution under 18 USC 1001 (false statements — fines and up to 5 years) and 31 USC 3729 (the False Claims Act — civil penalties currently over $13,000 per false claim, plus treble damages). Federal prosecutors use both. Prevailing wage fraud cases routinely charge each falsified weekly payroll as a separate count.

The Classification and Rate Errors That Fill Audit Files

Matching workers to wage determination line items

Every worker on the payroll must carry a classification that appears on the contract's wage determination, and the classification must match the work the person actually performed that week — not their title, their license, or their rate in the contractor's accounting system. If the determination lists "Laborer: Common" at $19.10 plus $6.22 fringe and "Cement Mason" at $28.40 plus $9.15, a laborer who spends Tuesday finishing concrete must be paid the cement mason rate for those hours. Split classifications are legal and common: the payroll shows the worker on two lines, with hours and rates for each classification, supported by daily time records. What is not legal is paying the blended cheap rate and calling everyone "laborer." Misclassification is the single largest source of Davis-Bacon back wages, and it is visible on the face of the payroll: an "electrical" scope with twelve workers all classified as laborers is an audit that writes itself.

Work not listed on the determination requires a conformance request under 29 CFR 5.5(a)(1)(iii) through the contracting agency before the classification is used — a contractor cannot invent "low-voltage tech, $22.00" and certify it 30 weeks in a row. Contractors pricing federal construction bids should read the wage determination against their actual crew plan before bid day, because every classification gap becomes a weekly certification problem after award.

Apprentices, ratios, and the full-journeyman trap

Apprentices may be paid less than the journeyman rate only if they are individually registered in an apprenticeship program registered with DOL's Office of Apprenticeship or a state apprenticeship agency, and only up to the ratio of apprentices to journeymen the registered program allows. A program permitting one apprentice per three journeymen means the fourth "apprentice" on site that day is not an apprentice for Davis-Bacon purposes — that worker is owed the full journeyman rate for every hour, retroactively. The 2023 final rule tightened this further: where the program's standards specify ratios and wage progressions for the locality of the project, those apply. The certified payroll must show the apprentice's registration and rate step, and WHD investigators routinely subpoena program registration records to test what the payroll claims. The math on a violation is brutal: one unregistered "apprentice" paid $18 against a $45.80 total journeyman obligation, 40 hours a week for 30 weeks, is $33,360 in back wages from a single worker — before any penalties.

Fringe benefits, deductions, and the exceptions section

Item 4 errors are endemic. Contractors check 4(a) — fringe paid to plans — while actually paying part of the fringe in cash, or check 4(b) while claiming credit for the employer's share of FICA (7.65 percent), workers' compensation, or unemployment insurance, none of which count as fringe credit because they are payments required by law. Deductions are governed by 29 CFR Part 3: standard deductions (taxes, court-ordered garnishments, bona fide benefit contributions the worker authorized) are permissible; anything else generally requires the Secretary of Labor's approval. A recurring $50 weekly "tool rental" or "transportation" deduction that drives net pay below the determination rate is a Copeland Act kickback, and it appears in the deductions column of the very form the contractor signed.

Audit Triggers, Recordkeeping, and Flow-Down

The patterns investigators look for first

WHD and agency labor compliance officers review certified payrolls against each other and against the physical job. The classic triggers, in rough order of frequency:

  • Too few workers for the work in place. Daily reports and inspection logs show 14 workers; the payroll shows 6. The missing 8 are off the books or on someone else's.
  • No overtime, ever. A 30-week payroll run with every worker at exactly 40.0 hours every week on a schedule-driven job. Under the Contract Work Hours and Safety Standards Act (40 USC 3701), overtime over 40 hours is due at time and a half on the base rate, with liquidated damages of $31 per worker per day for violations.
  • Uniform round hours and identical crews. Every worker, 8.0 hours, Monday through Friday, no variation for weather, absences, or phase changes — a pattern real jobs almost never produce.
  • Classification mix that contradicts the scope. Structural steel erection certified entirely by "laborers," or a payroll with zero operators on an earthwork phase.
  • Worker interviews that contradict the payroll. Investigators interview workers on site under 29 CFR 5.6; a worker who says "I get $20 cash, no stub" against a payroll showing $31.20 plus benefits ends the document review and starts the investigation.
  • Late, missing, or perfectly retroactive payrolls. Six weeks of silence followed by six tidy back-dated submissions in one day, all signed the same afternoon.

A contractor who discovers an error should file a corrected payroll promptly and pay restitution — corrections happen and are not themselves violations. A contractor who quietly re-certifies known-false numbers converts a wage debt into a fraud case.

Recordkeeping: three years after completion, not three years from today

Under 29 CFR 5.5(a)(3)(i), payrolls and basic records — time cards, classification records, fringe benefit plan documents, apprenticeship registrations, and since 2023 the worker contact information described above — must be maintained for three years after the completion of all the work on the prime contract. On a two-year project, that is a five-year retention clock from the first week's records. The 2023 rule made the stakes concrete: where a contractor fails to keep required records, WHD may compute back wages based on worker statements and reasonable inferences, and the missing records cut against the contractor. GAO reporting on Davis-Bacon enforcement has repeatedly flagged recordkeeping failures as the factor that turns small disputes into large assessments, because the contractor with no records cannot rebut anything.

Electronic systems and subcontractor flow-down

Many agencies and state DOTs now require electronic certified payroll through platforms such as LCPtracker, eMars, eComply, or Trimble construction payroll modules; California's DIR runs its own state portal for public works, and the FAR-based clause structure permits electronic signatures and submissions. These systems validate classifications against loaded wage determinations and flag rate shortfalls before submission, which reduces arithmetic errors — but the legal duty is unchanged. The certifier who clicks "sign" on a false electronic payroll faces the same 18 USC 1001 exposure as one who signs in ink, and system-generated compliance is only as good as the time data entered into it.

Flow-down is the prime's problem by regulation. 29 CFR 5.5(a)(6) requires the prime to insert the Davis-Bacon clauses in all subcontracts, and the prime is responsible for compliance by any subcontractor or lower-tier subcontractor. In practice that means the prime collects, reviews, and transmits every sub's weekly payroll — and when a sub underpays, the contracting agency withholds from the prime's payments under 29 CFR 5.9. AGC's contract-administration guidance tells primes to review sub payrolls before submission, not just forward them, and the case files support that advice: primes have paid six-figure restitution for second-tier subs they never audited. Contractors building a federal pipeline — and prevailing wage coverage keeps expanding at the state level — should treat payroll review capacity as a hard cost of growth, priced into every bid the same way bonding is. For contractors deciding whether the compliance overhead is worth it, the volume argues yes: Buildermuse's board of open federal construction solicitations typically lists around 1,900 active opportunities, and certified payroll competence is a barrier that keeps undisciplined competitors out. Learning how to bid federal construction contracts properly means budgeting for the back office, not just the field.

Frequently Asked Questions

Does a subcontractor with only one worker on site still file weekly certified payroll? Yes. Every subcontractor at every tier performing covered laborer or mechanic work files for every week that work occurs, regardless of crew size or subcontract value. A one-person caulking sub on site for a single Wednesday files a certified payroll for that week showing that day's hours. The prime is responsible for collecting it.

What is a "no work" payroll and when is it required? When a contractor performs no covered work in a given week mid-project, the agency needs to know the gap is real rather than a missing submission. The accepted practice is either a "no work performed" payroll for that week or a statement on the next payroll covering the gap; many agencies and electronic systems require the no-work filing explicitly. Numbering payrolls sequentially — 1, 2, 3, with the final one marked "final" — is how agencies confirm the record is complete.

Can the office manager sign the Statement of Compliance? The regulation permits signature by the contractor or "the person who supervises the payment" of the workers. An office manager or payroll administrator with actual knowledge of and authority over wage payment can sign. What the signature cannot be is ceremonial: the signer certifies personal knowledge that the payroll is correct, and prosecutors have charged signers who certified numbers they never checked. Whoever signs should be reviewing time records, not just the printout.

Are owners and supervisors listed on the certified payroll? Working owners and foremen who perform laborer or mechanic work are listed for the hours they spend on covered manual work. Bona fide executive, administrative, and professional employees exempt under 29 CFR Part 541, and supervisors who spend 20 percent or less of the week on manual work, are not covered for those duties. Many contractors list working owners with their hours and note their status; what matters is that all covered manual hours by anyone appear somewhere.

How long does the contractor have to fix an underpayment found on its own payroll? Immediately, as a practical matter. Restitution is computed as the difference between the required rate and the amount paid, for all affected hours. The contractor pays the workers, files a corrected certified payroll showing the supplemental payment, and documents it. Voluntary, prompt correction is the strongest mitigation available; under 29 CFR 5.12, it is aggravated or willful violations — not corrected errors — that support debarment for up to three years.

Do certified payroll requirements apply on state-funded jobs with no federal money? Not the federal WH-347 duty, but roughly 26 states operate their own prevailing wage laws, and most of the active ones — California, New York, Illinois, Washington, New Jersey among them — impose their own certified payroll requirements, some stricter than federal. California requires electronic submission to the DIR for essentially all public works over $1,000. On mixed-funding jobs, both regimes can apply simultaneously, and the contractor follows the more demanding requirement element by element.

Your Action Item for This Week

Pull the last four certified payrolls from your current government job — or your most recent completed one — and audit them yourself against three questions. One: does every classification on the payroll appear on the contract's wage determination, and does it match what each worker actually did those weeks? Two: does the fringe math work — box 4 checked correctly, cash-plus-plan contributions equal to or above the determination's fringe amount, no FICA or workers' comp counted as credit? Three: do the hours reconcile against daily reports, and is any week over 40 hours showing overtime at time and a half on the base rate? Budget 90 minutes. If you find one error, file the corrected payroll and pay the difference this week — a self-corrected $400 shortfall is a footnote, and the same $400 found by a WHD investigator eighteen months from now is an investigation. Then put a 30-minute weekly review of every subcontractor payroll on your calendar before you submit the next batch.

ST

Sarah Torres

Licensed Electrician & Safety Consultant

More from Sarah Torres→
trending_up

Get monthly construction wage & labor alerts

BLS wage data, workforce gap reports, and labor market shifts — delivered when they move.

Get wage alerts