What Is Certified Payroll?

What certified payroll is, who has to file it, what the WH-347 certifies, and where the reporting most commonly goes wrong.

·By Dan Agarwal

Certified payroll is a signed weekly report showing what each worker on a covered public construction project was paid, submitted to prove that the required wage rates were actually applied. The word that matters is "certified": the report carries a signed statement of compliance, and that signature is what makes it more than a payroll summary.

It is a familiar obligation to anyone in construction payroll and a genuine surprise to organizations taking on public work for the first time, because it turns payroll from something you do into something you have to prove, every week, per project.

Who is required to file it?

Contractors and subcontractors working on covered public projects.

At the federal level, the requirement attaches to construction contracts above a threshold value that are funded or assisted by the federal government, under the Davis-Bacon Act and related legislation. Many states have their own prevailing wage laws with their own certified payroll requirements, which can apply to state and local public projects that carry no federal funding at all.

The practical consequence is that coverage is determined by the project, not by the company. The same contractor can have one crew on a covered job and another on private work in the same week, with reporting obligations attaching only to the first. Subcontractors generally file their own reports rather than being covered by the general contractor's, which means a single project can generate a stack of submissions from different companies every week.

What does the WH-347 actually certify?

The federal form, WH-347, has two parts, and the second is the one that carries the weight.

The first part is the payroll data: each worker, their classification, hours worked by day, rate of pay, gross earnings, deductions, and net pay for the project during that week.

The second part is a signed statement of compliance. In signing, an authorized representative attests that the payroll is correct and complete, that each worker was paid at least the applicable prevailing wage rate for their classification, that no unauthorized deductions were made, and that fringe benefit obligations were satisfied either in cash or through contributions to a bona fide plan.

That signature is the reason certified payroll is not simply reporting. It is a weekly assertion of compliance, made by a named person, on the record.

What has to be reported for each worker, each week?

Enough to demonstrate that the right rate was paid for the right work.

The report identifies the worker and their work classification, since prevailing wage rates are set by classification rather than by person. It shows hours worked on the covered project, day by day, separated from any other work. It shows the rate paid and the gross amount earned on that project. It shows deductions and net pay. And it accounts for fringe benefits, indicating whether they were paid in cash or contributed to a plan.

Two details cause disproportionate trouble. Workers who perform more than one classification in a week need their hours split accordingly, at the correct rate for each. And apprentices must be reported with their program and step, because their rate is a percentage of the journeyman rate and their presence on site is usually subject to ratio requirements.

The wider set of moving parts in construction payroll is worth reading alongside this, because certified payroll is rarely the only obligation running at once.

How do state systems differ from the federal requirement?

In form, in frequency, and in how the report is submitted.

Some states accept the federal WH-347. Others require their own form with additional fields. Several operate electronic submission systems where reports are uploaded to a state portal rather than sent to the contracting agency, each with its own file format and validation rules. California's electronic certified payroll reporting system is the most widely known example, but it is not unusual.

Thresholds differ too. A project may fall below the federal threshold and above a state one, or be covered by a local ordinance with requirements of its own. For contractors working across state lines, the practical effect is that the same weekly payroll data has to be shaped into several different outputs, on several different schedules, for several different recipients.

Where does certified payroll reporting most commonly go wrong?

Not usually in the intent. In the assembly.

Classification errors are common, particularly where a worker performs multiple classifications in a week and the hours are not split correctly. Fringe benefit accounting is another frequent source of problems, because the choice between paying cash in lieu and contributing to a bona fide plan changes both the calculation and how it must be reported, and the two are easy to conflate.

Apprentice reporting causes trouble where the program, step, or ratio is not tracked as carefully as the rate. Multi-site weeks generate errors when hours are attributed to the wrong project. And late submission is its own category of failure, entirely procedural, arising when the reporting calendar is tracked by memory across a growing number of active jobs.

Underneath most of these is a single structural issue: the data needed for certified payroll is assembled from the same sources as the payroll itself, but shaped differently and to a different deadline. Where that assembly is manual, it competes for time with the pay run, and it happens weekly, per project, indefinitely. That is why it tends to be the first thing to strain as a contractor takes on more public work, and it is a good example of complexity that scales with moving parts rather than headcount.

This article is general information about payroll operations and reporting practice. It is not legal advice, and it does not replace the specific requirements of a contract, an agency, or a jurisdiction.

Frequently asked questions

Is certified payroll required on every public project? No. It applies to covered projects, which is determined by the funding source, the contract value against the applicable threshold, and the governing federal, state, or local law. Some public projects carry no certified payroll obligation at all, and coverage should be confirmed per contract rather than assumed.

What is the difference between certified payroll and prevailing wage? Prevailing wage is the obligation: the minimum rate and fringe amount that must be paid for a given classification in a given locality. Certified payroll is the proof: the weekly signed report demonstrating that the obligation was met. One is what you must do, the other is how you show you did it.

How often must certified payroll be submitted? Weekly, for each week in which covered work is performed, for each covered project. The submission deadline and destination depend on the governing law and the contracting agency, and electronic systems in some states impose their own timing.

What happens if a certified payroll report is filed late or incorrectly? Consequences vary by jurisdiction and contract, and can include withheld payments, required corrections and back payment, and in serious or repeated cases, penalties or debarment from future public work. Because the report carries a signed statement of compliance, errors are treated more seriously than an ordinary reporting mistake.

Do subcontractors file their own certified payroll? Generally yes. Each contractor and subcontractor performing covered work is responsible for reporting its own workers, though the general contractor often has a collection and oversight role and may be responsible for ensuring submissions are complete before passing them to the agency.

See it on your own payroll data.

The pilot runs the pipeline against your live payroll data, in your environment.