Certified Payroll and What It Actually Requires of You

Why this matters

Certified payroll is not a report your payroll system produces. It is a sworn statement, signed by someone with authority to bind your company, asserting facts about classification, fringe treatment, apprentice registration and deductions that your payroll system was never asked to hold. That is the whole difficulty. The arithmetic is easy and it is not where shops fail. They fail because the form asks for eight or nine things and payroll only knows five of them. One scope note before any of it: everything below describes the federal scheme on Davis-Bacon and Davis-Bacon Related Act work. State prevailing wage acts run their own form, cadence, portal and retention period, and on a state-only project the federal mechanics here do not apply.

The other half of the trouble is a misread of what submission means. Nobody sends back a letter saying your classifications are correct, because nobody is checking that at submission. Acceptance is a receipt. The review that matters can come a year later, and by then your accepted submissions are the evidence.

How prevailing wage reshapes a technician's day and how hours have to be captured is covered separately and is not repeated here. See related: What Prevailing Wage Changes About a Job You Already Know.

What it is, mechanically

Two things bound together. First, a weekly payroll record covering every laborer and mechanic who worked on the covered contract that week. Second, a statement of compliance signed for that week.

The submission runs weekly, for each week in which any contract work is performed, under the contract provisions at 29 CFR 5.5(a)(3). The weekly statement itself comes from the Copeland Act regulations at 29 CFR Part 3, and 29 CFR 3.4 requires that statement to be delivered within seven days after the regular payment date for the pay period. The Department of Labor's optional Form WH-347 is built to satisfy both at once, which is why most agencies simply ask for it, though a contractor may submit its own format carrying the same information.

Records supporting all of this are preserved for three years after all the work on the contract is completed, under 29 CFR 5.5(a)(3). That clock runs from project completion, not from the pay date, which is a longer hold than most shops apply to ordinary payroll.

What certified payroll is not

This is the useful list, because everything it is has already been described.

It is not a payroll register with a cover sheet. The statement of compliance is an affirmation, and the form's own language warns that willful falsification may expose the signer to civil or criminal prosecution. The general federal false-statements statute at 18 U.S.C. 1001 is the usual hook. This is why the signer matters: it must be a person authorized to make that affirmation for the company, and many agencies expect an owner or officer rather than whoever runs payroll.

It is not approval of your classifications. An agency receiving your payroll is confirming receipt and completeness, not adjudicating whether the work you called one classification was really another. A classification error found later produces back wages for the entire period it ran, and every accepted submission in between is documentation of how long it ran.

It is not a substitute for reading the wage determination. The determination incorporated into the contract is the operative one for that contract. A determination modified later does not generally reach back into a contract already awarded, but contracts with option years or extended periods can pick up a current determination at the renewal, so confirm which applies rather than reusing last year's numbers.

It does not verify your fringe math. Nothing on the form checks whether your benefit contributions were annualized across all hours worked or only across covered hours, and nothing checks whether your overtime premium used the right regular rate. Both are common underpayments and both pass a completeness review cleanly.

It is not the only form you owe. State prevailing wage statutes typically require the state's own form, often on a different cadence and through a different portal. On a project with both federal and state funding, both regimes can apply and the higher applicable rate governs.

It is not waived in a week with no work. Many agencies require a payroll marked no work performed so the sequence of weekly numbers stays unbroken. A gap in the numbering reads as a missing submission whether or not anyone worked.

It does not reach a supplier who only delivers. A material supplier delivering to the site is generally outside coverage. A driver who spends more than a minimal amount of time on the site performing work generally is not, and the line between those two is fact-specific enough that it is worth asking the contracting agency rather than deciding it yourself.

The fields your payroll system does not hold

Walk any submission and these are the ones that came from somewhere else:

• Work classification, per employee, per day. Payroll holds a pay rate. It rarely holds the determination classification that rate corresponds to, and it almost never holds a second classification for part of a day.
• The individual identifying number. Department of Labor guidance directs contractors not to include full Social Security numbers or home addresses on submitted payrolls; the last four digits are what goes on the submission, with the full record held in your own files.
• Fringe treatment. Whether the fringe obligation was discharged in cash on top of the base, through contributions to approved plans, or through a split, and an explanation where it is split. The form carries separate boxes for the two treatments precisely because they are different assertions.
• Apprentice registration. The program name and the individual's registration number, plus the step or percentage he is at. This lives in a training file, not in payroll.
• Deduction detail. Each deduction itemized, and each one either standard or explained. The Copeland Act regulations restrict what may be deducted from a covered worker's wages, with 29 CFR 3.5 listing the deductions permitted without approval and 29 CFR 3.6 the route for anything else, and a deduction that is routine on your private work can be impermissible here.
• Project and contract identification. Which contract these hours belong to, which is a field your service software may treat as a customer name rather than a contract number.

Worked example: one rejected week, four defects

Payroll number 7 for a public elementary school renovation. Three workers: two journeyworker pipefitters at 44 and 38 hours, one apprentice at 40 hours, 122 hours total for the week.

Defect one: 44 hours with no overtime line. On contracts above the CWHSSA dollar threshold, the overtime obligation runs under the Contract Work Hours and Safety Standards Act, 40 U.S.C. chapter 37, at time and a half over 40 in the workweek. Confirm the clause is actually in your contract; below the threshold the FLSA governs instead and the workweek is still the unit. The upstream cause is not a calculation error. This technician's 44 hours were split 22 and 22 across two covered contracts, and the shop's payroll was configured to compute overtime per job rather than per workweek, so neither job reached 40 and the system reported no overtime at all. The workweek is the unit, not the contract.

Defect two: the apprentice line has no registration number and no program name. The reviewer cannot confirm he is registered, so the apprentice rate cannot stand, and the default position is the full journeyworker rate for the classification of work he performed, for all 40 hours. Note what was fine here: the ratio on site that week was one apprentice to two journeyworkers, within what the program permits, so the ratio was not the problem. The number that would have proven it was sitting in a folder in the office.

Defect three: a deduction on the second pipefitter for a tool purchase. This shop routinely lets technicians buy tools through payroll deduction, and nobody reviewed that practice against covered work. The deduction is not among those permitted without approval, and on this week it pulled his effective rate below the determination.

Defect four: the statement of compliance was signed by the bookkeeper, who has no written authorization to sign for the company. Nobody had ever designated a signer.

Read what those four have in common. Only defect one is anything a payroll clerk would recognize as a payroll problem, and even it is a configuration choice rather than a mistake in arithmetic. Defect two is a fact that never entered payroll. Defect three is a company policy nobody reviewed. Defect four is a governance gap. Three of the four were fixed in an afternoon and none of the three involved payroll at all.

Then the part that hurts. The overtime configuration had been running since payroll number one. Across seven weeks this technician averaged 43 hours, so roughly 3 overtime hours a week went unpaid at the premium, about 21 hours in total, and the same configuration touched every other technician who crossed 40 across two contracts in any week. One rejected submission became a recomputation of seven, plus corrected payrolls for each. Under the contract provisions at 29 CFR 5.5(a)(2) the agency may withhold from contract payments enough to cover the underpayments, so the shop's progress payment sat while the correction ran. Where an investigation concludes there was disregard of obligations to employees, debarment from future covered contracts is available under 29 CFR 5.12, though the standard and the debarment period differ between the Davis-Bacon Act and the Related Acts and have been amended in recent rulemaking, so read the current text rather than a summary, which is the reason a shop should treat a small finding as a signal rather than a nuisance.

The failure mode. A shop reads its first rejection as a form problem, fixes the form, and resubmits. The form was never the problem. Every one of these four defects had a source outside the submission, and a fix applied at the form corrects one week while the source keeps producing the same defect. The tell is a shop on its fourth week of corrections for the same reason.

Where the burden sits when you are a sub

A general contractor generally collects your submissions and forwards them with its own, and it will chase you when yours is late because its own payment depends on the package being complete. What it does not do is sign your statement of compliance or take responsibility for your classifications. Subs consistently expect the burden to shift more than it does, and the practical consequence is a sub that never builds its own review step because it assumes someone upstream has one.

How to verify you got this right

Take one submitted line and ask, field by field, where each value came from. Classification, identifying number, fringe treatment, apprentice registration, deductions, contract number. Any field whose answer is "the person filling in the form knew it" is a field with no source, and it will be wrong the first week that person is on vacation.

Then run one policy check that has nothing to do with payroll: list every deduction your shop takes from any technician's pay for any reason, and confirm each is permissible on covered work. That list is short, it takes twenty minutes, and it is the defect most likely to be running quietly across every submission you have already filed.

References

• 29 CFR Part 3 (Copeland Act regulations), including 29 CFR 3.4 on submission of the weekly statement of compliance
• 29 CFR 5.5, contract provisions including payroll submission and retention at (a)(3), withholding at (a)(2), and apprentice provisions at (a)(4); 29 CFR 5.12 on debarment
• Contract Work Hours and Safety Standards Act, 40 U.S.C. chapter 37, overtime on covered contracts
• U.S. Department of Labor Form WH-347 and its instructions, the optional format for weekly certified payroll
• See related: What Prevailing Wage Changes About a Job You Already Know, How to Decide Whether to Take Prevailing Wage Work