Certified Payroll for Subcontractors: The Complete Guide

Certified payroll is the price of admission to public construction work, and it's the reason a lot of subcontractors leave that work on the table. The jobs pay well, the pipelines are steady, and the margins can be strong, but every week of every covered project comes with a payroll report that has to be formatted correctly, calculated correctly, and signed under penalty of perjury.

Get it wrong and the general contractor holds your payment. Get it wrong repeatedly and you're looking at back wage assessments or, in serious cases, debarment from public work entirely.

This guide covers what certified payroll actually is, when it applies, how the calculations work including the fringe and overtime rules that cause most of the trouble, why payrolls get rejected, and what a process that doesn't eat your week looks like. It's written from the perspective of a firm that produces certified payrolls weekly on active public projects, not from a compliance textbook.

What certified payroll is

Certified payroll is a weekly report of every worker on a covered project: their classification, hours by day, pay rate, fringe benefits, gross wages, deductions, and net pay, accompanied by a signed statement of compliance certifying under penalty of perjury that the information is accurate and workers were paid the required rates.

On federally funded projects, the requirement comes from the Davis-Bacon Act, which applies to federal construction contracts over $2,000, and the standard reporting form is the WH-347. The form itself is technically optional, but the information and the weekly signed statement of compliance are not, so in practice nearly everyone uses it or a format matching it. On state and municipally funded projects, most states run their own prevailing wage systems with their own forms, thresholds, and quirks. The mechanics rhyme with the federal system, but the details differ by state, and the details are where payrolls get rejected.

The reports flow up the chain: you submit to your GC or the awarding body, the GC's compliance reviewer checks them before releasing payment, and the records become auditable documents that can be examined years later. That's the structural reality that makes certified payroll different from ordinary payroll paperwork. It sits between you and getting paid.

When prevailing wage applies

The trigger is public money. Federal funds bring Davis-Bacon requirements, and state or local funds bring the state's prevailing wage law where one exists, each with its own contract threshold. Schools, municipal buildings, public infrastructure, and increasingly projects with public financing components are covered. Every covered project has a wage determination: the schedule of minimum hourly rates, split into base wage and fringe, for each labor classification on the job.

Two things about wage determinations catch subs off guard. First, the determination attached to your contract governs, and rates can change mid-project when new determinations are issued, so the rate you bid may not be the rate you're paying in month eight.

Second, classifications matter enormously: an electrician doing electrical work at the electrician rate is simple, but workers who move between classifications, apprentices who need registered ratios, and foremen who work with the tools part-time all create classification questions that reviewers check closely.

Base, fringe, and how the math actually works

Every prevailing wage rate has two parts: the base hourly rate and the fringe benefit rate. The total is what each worker must receive for every covered hour, but how you deliver the fringe portion is where the flexibility, and the complexity, lives.

You can pay the fringe as cash on the paycheck, in which case the worker simply receives base plus fringe as wages. Or you can take credit for bona fide benefits you actually provide: health insurance, retirement contributions, and certain other benefit plans, valued at your actual cost, converted to an hourly equivalent. If your benefits cover part of the fringe obligation, the remainder gets paid as cash. The credit has to reflect real costs for real benefits, and reviewers can and do ask for backup.

Overtime is where the most expensive mistakes happen, and the rule surprises almost everyone: the overtime premium is calculated on the base rate, not on base plus fringe. A worker at a $30 base and $10 fringe who works overtime is owed time and a half on the $30, plus the $10 fringe at straight rate for every hour including the overtime hours. The fringe does not get multiplied by 1.5.

Subs who multiply the full package by 1.5 overpay on every OT hour, and subs who forget fringe applies to OT hours at all underpay, which is the direction that produces back wage findings. Workers who earn different rates in the same week add another layer, because the overtime calculation then has to handle multiple rates, and the method needs to match what your state or contract requires.

None of this is exotic once your system handles it correctly, but it has to be built once, carefully, per project, against the actual wage determination.

Why payrolls get rejected

Having produced these weekly under GC review, the rejection patterns are consistent. Classification mismatches lead the list: a worker reported under a classification that doesn't match the work or doesn't appear on the wage determination.

Math errors are second: fringe calculated wrong, overtime handled wrong, or hours that don't tie across the form.

Missing weeks are third, because covered projects require a report every week including weeks with no work, which is its own form most offices don't know exists until a reviewer asks for it.

Stale wage rates after a mid-project determination change, missing or incorrect statements of compliance, and unregistered apprentices round out the usual suspects.

The consequence of rejection isn't a fine in most cases. It's slower: your payment application sits until compliance clears. For a sub floating labor and materials on a public job, weeks of held payment because of a payroll formatting issue is a genuine cash flow problem, which is why the offices that handle this well treat certified payroll as a production process rather than an afterthought.

What a working process looks like

The subs who don't struggle with certified payroll all run some version of the same weekly rhythm. Time comes in from the field daily, tagged by worker, project, and classification, through a digital timekeeping tool rather than texted photos of paper cards. Rates live in a maintained table per project, updated when determinations change, with fringe methodology settled once per project rather than recalculated ad hoc. The weekly report gets produced from that data, reviewed against the prior week for consistency, and submitted on schedule with the statement of compliance.

Amendments, when needed, get filed promptly with a clear explanation, because a clean amendment beats a subsequently discovered error every time.

The failure mode is the opposite: hours arriving late from the field, rates in someone's memory, the form assembled Thursday night by whoever's available, and no reconciliation between what the certified payroll says and what the books say. That last gap matters more than most subs realize, because certified payroll that doesn't tie to your actual payroll records is a problem waiting for an audit.

This is also where certified payroll connects to the rest of your books.

The same labor data feeding the weekly reports should feed your job costing, so the compliance work and the margin visibility come from one pipeline instead of two parallel systems.

The foundations are covered in Bookkeeping for Contractors: What You Need to Know and How to Track Job Costs in QuickBooks Online, and on covered work the payroll layer sits directly on top of them.

Handling it in-house versus outsourcing

Plenty of subs handle certified payroll in-house successfully, typically when they have an experienced office manager, stable project types in one state, and enough volume to justify the learning curve. The in-house route makes sense when those hold.

The case for outsourcing is strongest when the office is thin, the projects span jurisdictions with different rules, prevailing wage work is new to the company, or the weekly production is consuming hours that the office needs for billing and collections.

The compliance risk also concentrates: a specialist producing these weekly across multiple clients sees the rejection patterns and the rule changes at a frequency no single sub's office can match.

The test is what certified payroll currently costs you: the office hours, the rejected-payroll delays, and the deadline stress. If that total is meaningful, the work is worth professional handling, and if it isn't, keep it in-house with a good process.

At Prophet Accounting, we produce certified payrolls weekly for construction subcontractors on active public projects, under real GC review, alongside the bookkeeping, job costing, and retainage tracking that contract work requires.

If prevailing wage compliance is eating your office's week or keeping you off public work entirely, schedule a consultation at prophetaccounting.com/construction or give us a call at (772) 380-2871.

Next
Next

How to Choose a Bookkeeper for Your Landscaping Business