TL;DR
Certified payroll is the weekly report proving that every worker on a federally funded construction project was paid the prevailing wage and fringe benefits for the classification of work they actually performed. It is not a payroll task. It is an evidentiary filing, and payroll can be entirely correct while the filing still fails. The recurring difficulty is that the report is due weekly while its inputs arrive on other cadences.
Key Takeaways: Davis-Bacon applies to federal construction contracts above a low threshold, requiring weekly submission with a signed Statement of Compliance. The WH-347 form itself is optional; the information and the statement wording are not. Misclassification is the most commonly cited violation. The revised form expands fringe benefit reporting considerably. State prevailing wage regimes overlay federal requirements with their own forms and portals.
What is certified payroll?
Certified payroll is a weekly payroll report submitted by contractors and subcontractors on construction projects covered by the Davis-Bacon Act, which applies to federal and federally assisted construction contracts above a low dollar threshold, and by state prevailing wage laws covering public works at state level.
The report documents, for each worker and each week: name and identifier, the labor classification for the work actually performed, daily straight-time and overtime hours, the rate of pay, gross earnings, deductions, net wages, and the treatment of fringe benefits. It is accompanied by a signed Statement of Compliance.
The distinction worth drawing at the outset is that this is not payroll processing. Paying the right amount is one obligation. Proving it, weekly, in a prescribed format, is a separate one, and it is possible to satisfy the first completely while failing the second.
One detail surprises people: the WH-347 form itself is optional. The Department of Labor provides it for convenience, and a contractor may use its own format. What is not optional is submitting the required information weekly with a Statement of Compliance whose wording is identical to the prescribed text.
What changed with the revised WH-347
The Department of Labor revised the form, and reporting indicates the updated version became mandatory from October 1, 2026. Given how recent that is, verify the current requirement with the contracting agency rather than relying on any published summary including this one.
Two changes matter operationally.
Fringe benefit reporting expanded materially. Contributions to bona fide plans are now reported separately from cash paid in lieu of benefits, broken out by benefit type, plan name, hourly credit, and total credit. That is substantially more granular than a single aggregate figure.
Submitting an outdated form is reportedly treated as a missing filing for that pay period, rather than as a correctable formatting issue. The consequences attached to a missing certified payroll are not administrative: wage restitution, withheld contract payments, and agency audit.
That distinction is worth sitting with. A contractor who paid every worker correctly, computed everything accurately, and filed on time on the wrong form is in the same position as one who did not file.
The Statement of Compliance
Each weekly submission carries a signed statement certifying that the payroll is complete and correct, that workers were paid without prohibited rebates or deductions, that classifications and wage rates are correct, and that fringe benefits were provided as stated.
The certification is made subject to federal criminal provisions covering false statements. Falsified reports carry civil penalties per violation, potential criminal exposure, and debarment from future federally funded work.
This is why certified payroll sits differently from most reporting obligations. A named individual attests weekly to the accuracy of data assembled from several systems, and carries personal exposure for it.
Classification: the most common failure
Across guidance from practitioners and compliance specialists, the same error leads the list: incorrect labor classification.
The requirement is that a worker is classified according to the work actually performed, not according to their job title, their usual trade, or how they are set up in the payroll system. A worker who spends part of a week performing one classification and part performing another must be reported with daily hours split accordingly, each at the applicable rate.
That requirement exposes a systems problem rather than a knowledge problem. A readiness question put well by one compliance practitioner: can your timekeeping system produce daily hours split by classification for an employee who worked two classifications in one week?
For many contractors the honest answer is no, or not without someone reconstructing it manually from field records.
The cadence problem
Here is the structural issue underneath most certified payroll difficulty, and it explains why the work is chronically painful rather than occasionally.
The filing is weekly. The inputs are not.
Timekeeping data arrives daily, from the field, often on paper or in a separate system, and requires classification detail the field may not have captured. Payroll runs on its own cycle, weekly or biweekly, and Davis-Bacon separately requires that workers be paid weekly. Fringe benefit administration is frequently handled by a third party reporting on a monthly or quarterly cycle, which means worker-level hourly fringe credits may simply not exist at the moment the weekly report is due.
That last mismatch is the sharpest. Where fringe benefits are administered externally and reported quarterly, the reporting cadence itself becomes the compliance problem, because the weekly form now demands worker-level fringe detail broken out by plan.
So the weekly report requires reconciling three streams running at three different frequencies, every week, for every active covered project, with a personal certification attached.
State overlays
Federal Davis-Bacon frequently coexists with a state prevailing wage law on the same project, and the two do not harmonize. Filing frequencies, forms, submission channels, and record requirements vary. Several states mandate electronic submission through their own portals and will not accept the federal paper form.
A contractor operating across states is therefore maintaining several parallel reporting regimes against one set of underlying payroll data, which multiplies the reconciliation rather than the paperwork.
Where the work actually goes
The operational shape is specific.
Someone collects field time records and establishes which classification applies to which hours. Someone reconciles that against the payroll run. Someone obtains or calculates worker-level fringe credits, which may require apportioning a periodic third-party contribution to individual weeks. Someone maps all of it onto the correct form for the correct jurisdiction, in the correct version. Someone checks the applicable wage determination and revision number for the project. And someone reviews it before a named individual signs the certification.
Then it repeats next week, for every project.
Almost none of this is payroll calculation. It is gathering records from systems on different clocks, reconciling them, and assembling a prescribed submission, at a volume that scales with projects multiplied by weeks.
Where automation fits
Because the constraint is reconciliation and assembly rather than calculation, that is where automation changes the position.
Automation that can read unstructured records and reason across sources addresses it directly: interpreting field time records whatever form they arrive in, reconciling classification detail against payroll data, apportioning periodic fringe contributions to weekly worker-level credits, flagging the mismatches before submission rather than after, and assembling jurisdiction-specific outputs from one reconciled dataset.
The value sits in the checking as much as the assembly. A worker whose reported classification does not match the hours recorded against a task, or whose rate falls below the applicable determination, is detectable before filing. The same error found during an agency audit is wage restitution.
Because a named individual certifies the submission under penalty provisions, every figure needs to be traceable to the record it came from. A certification signed over numbers nobody can substantiate is precisely the exposure the statement is designed to create.
To be clear about scope, Kognitos is not a payroll system or a certified payroll filing platform. It does not run payroll, maintain wage determination libraries, or submit to agency portals, and the specialist platforms that do those things remain the right tools. What it addresses is the reconciliation layer beneath: pulling together records from systems on different cadences into a consistent weekly position with a record of how each figure was derived.
For related processes, see our guides on payroll automation, regulatory reporting, internal controls, quality management systems, and AI for compliance automation. To see how deterministic AI reconciles records across systems with a full audit trail, book a demo or try the platform.
Getting started
Two checks, both answerable this week.
Confirm which form version you filed last week, for every covered project. Given the recency of the revision, this is the single highest-value check available, because an outdated form is reportedly treated as a missing filing rather than a correctable error.
Run the two-classification test. Pick one worker who performed more than one classification in a week and establish how long it takes to produce daily hours split by classification from source records. That duration, multiplied by your covered headcount, is the real cost of your current process, and it is usually absorbed invisibly by someone reconstructing it by hand.
