Certified Payroll Reporting: The Weekly Process and Common Errors

The Weekly Reporting Cycle, Start to Finish

Certified payroll reporting runs on the same weekly cadence as the underlying payroll it documents. Each week, a contractor collects the hours worked by classification for every covered employee, applies the correct base rate and fringe benefit rate from the project's wage determination, calculates gross wages including any overtime, reconciles the fringe benefit obligation against how those benefits were actually paid, and itemizes deductions to arrive at net wages.

That data is transferred onto a WH-347 form or the state's required format, one row per worker, and the contractor's authorized signatory signs the Statement of Compliance for that specific week before submission. The cycle repeats for the full duration of the project - including weeks where the contractor performed no covered work at all, which still require a payroll marked "no work performed" so the agency's record has no unexplained gap.

Larger contractors with several crews on the same project often run this cycle per subcontractor rather than per company, since each contractor and subcontractor on a job certifies its own workers independently - a general contractor typically compiles and forwards its subcontractors' certified payrolls but does not merge them into a single report.

The recurring nature of the cycle is what makes certified payroll reporting fundamentally different from a one-time compliance filing: it has to run correctly every single week of a project that can last months or years, with the same wage determination applied consistently to the same classifications throughout, unless the agency issues an updated determination partway through the job.

Who Submits, and to Whom

On federal Davis-Bacon contracts, the certified payroll is usually submitted to the contracting agency administering the project, often routed through the prime contractor, who is responsible for making sure every subcontractor's payroll reaches the agency on schedule even though each subcontractor certifies its own numbers.

On state-funded prevailing-wage projects, submission frequently goes through a dedicated state portal instead of a mailed or emailed form. California's Department of Industrial Relations requires electronic certified payroll reports (eCPR) through its own system; New York's Department of Labor runs its own electronic certified payroll process; Illinois requires submission through its Certified Transcript of Payroll system. A contractor working jobs in several states, or a mix of federal and state-funded jobs, has to track which format and portal each specific contract requires rather than assuming one process covers everything.

It's common for a mid-size contractor to be filing WH-347-style PDFs to one federal agency, uploading to California's eCPR portal for a different job, and mailing a state-specific form for a third - all in the same week, for different crews. Building a single internal process that can output whichever format each project needs, rather than treating certified payroll as one uniform task, avoids the scramble of reformatting data under a filing deadline.

Error 1: Misclassifying a Worker's Trade

The wage determination attached to a project sets a different prevailing wage and fringe rate for each classification - carpenter, laborer, electrician, and so on - and paying someone at the wrong classification's rate is consistently the most cited type of certified payroll violation. It happens most often with workers who perform mixed duties, or with a classification that doesn't map cleanly onto the wage determination's listed trades, and it is worth resolving with the contracting agency before the work starts rather than after payroll has already been submitted at the wrong rate.

A worker classified as a laborer when the actual work performed matches a higher-paid trade like carpenter results in underpayment even though the hours and pay rate on the form look internally consistent - the error only shows up when someone compares the classification against the actual scope of work performed, which is exactly what a compliance audit does.

Error 2: Fringe Benefits Left Out of the Rate

The prevailing wage obligation is base rate plus fringe benefits combined, and a contractor that pays only the base cash rate without also covering the fringe portion - either into bona fide plans or as additional cash in lieu, disclosed on the Statement of Compliance - has underpaid the worker even if the cash hourly rate looks correct on its own. This error is easy to miss because fringe is tracked in a separate part of the WH-347 form (box 6B) from gross and net wages, so a contractor reviewing only the wage columns can overlook that the fringe obligation was never actually funded.

Fringe is also owed on overtime hours, not just straight-time hours - a payroll that calculates fringe only against the 40 straight-time hours in a week and skips the overtime hours has still underfunded the fringe obligation for that week, even if the base wage overtime calculation itself is correct.

Error 3: Missing Weeks Instead of "No Work Performed" Payrolls

A gap in the weekly submission record - a week where no payroll was filed at all because no covered work happened - reads to an auditor as a missing record, not as a week off. The correct practice is to submit a payroll for that week explicitly marked "no work performed," which keeps the compliance record continuous for the life of the project instead of leaving an unexplained hole that has to be reconstructed or explained later.

This matters most on projects with seasonal gaps or weather delays, where a contractor might genuinely have zero covered hours for several weeks in a row - each of those weeks still needs its own "no work performed" submission rather than a silent pause in filing.

Error 4: An Unsigned or Late Statement of Compliance

Each week's Statement of Compliance is a distinct, sworn document - not a one-time signature covering the whole project - and it has to be signed for that specific week's report before submission. A payroll with the wage table filled in correctly but no signed statement, or a statement dated for the wrong week, is treated as incomplete, and falsifying it knowingly is a federal crime under 18 U.S.C. Section 1001, separate from any wage-restitution exposure from the underlying pay error itself.

The statement also requires the signatory to be someone with actual authority to certify payroll on the contractor's behalf, and to check the correct box disclosing whether fringe was paid into plans or in cash - an inconsistency between that disclosure and what the wage columns show is one of the easier mismatches for a reviewer to catch.

Error 5: Overtime Split Incorrectly

Overtime for hours beyond 40 in a week on covered federal contracts is generally required at 1.5 times the base rate under the Contract Work Hours and Safety Standards Act, calculated on the cash base rate rather than the base-plus-fringe combined rate. A common mistake is applying the 1.5x multiplier to the wrong base number, or failing to separate straight-time and overtime hours by day on the form, both of which produce a gross wage figure that won't reconcile against the hours actually reported.

A related version of this error shows up on multi-employer weeks: a worker who splits 40 regular hours across two different covered projects in the same week may still owe overtime once combined hours for that employer cross 40, depending on how the projects are structured - a detail that a per-project view of hours alone can miss.

Tools That Help

Our free multi-week certified payroll template (tabletemplates.com/free/certified-payroll-template-excel/) gives a small contractor a working register to log hours and rates across a project. LeaveSheet's Certified Payroll add-on ($19/month or $190/year per organization, 14-day trial) tracks workers and their fringe plans, takes weekly straight-time and overtime entries, reconciles the fringe math in a WH-347-style table, and exports a PDF plus Excel copy - it does not submit to state portals like eCPR or DIR, which still have to be filed directly with the state.