Who is exempt from certified payroll requirements?

Bona fide owners, certain supervisory personnel, and genuinely independent contractors under the DOL's economic-reality standard may be exempt. The exemption is narrower than most contractors assume. Tax classification as 1099 does not automatically exempt a worker from certified payroll obligations. The economic-reality test looks at the working relationship, not the tax form. Contractors should resolve classification at onboarding rather than assuming exemption.

Does certified payroll need to be signed, and who can sign it?

Yes. The statement of compliance on WH-347 Part II requires a signature from an officer, owner, or authorized agent of the contractor. The signature is a legal attestation carrying weight under the False Claims Act on federal projects. Delegating preparation to a payroll processor does not transfer liability. The individual who signs remains personally responsible for the accuracy of every line item in the report.

What is the difference between Davis-Bacon wages and state prevailing wages?

Davis-Bacon applies to federally funded construction contracts over $2,000 and uses federal wage determinations. State prevailing-wage laws like California DIR apply to state-funded projects and often set higher rates with different overtime rules and fringe benefit treatment. On mixed-funding projects, the higher standard applies. Contractors must determine which law governs each project and tag time data accordingly.

What are the most common certified payroll mistakes?

The three most common mistakes are worker misclassification (logging hours under the wrong trade classification), overtime miscalculation (applying FLSA overtime rules instead of prevailing-wage overtime rules), and missing or incomplete fringe benefit documentation. All three trace back to gaps in time capture rather than errors in report formatting. Fixing the report without fixing the upstream data creates recurring audit exposure.

When is certified payroll required for construction projects?

Certified payroll is required on federally funded construction contracts over $2,000 under the Davis-Bacon Act. State thresholds vary. California DIR requires certified payroll on all public works contracts over $1,000. The definition of construction is broad and includes alteration, repair, painting, and decorating. Contractors should verify requirements at the project level based on funding source and jurisdiction.

Can payroll software alone solve certified payroll compliance?

Payroll software handles the reporting output, but compliance depends on the quality of upstream time-and-labor data. If time entries lack classification, project, or jurisdiction context, the payroll software will generate a clean-looking report built on incomplete data. Certified payroll compliance requires solving the time-capture layer first, then connecting it to a payroll engine that applies the correct wage and overtime rules.

Certified Payroll Is a Time-Capture Problem, Not a Forms Problem

Why Does Certified Payroll Fail Before the Report Is Even Generated?

A certified payroll report is a structured export of time-and-labor data. The WH-347 (or its state equivalent) requires, at minimum, worker name, classification, hours by day and trade, wage rate, fringe benefit treatment, and a signed statement of compliance. None of those fields can be accurately populated if the originating time entry lacked job and classification context.

The prevailing assumption among contractors is that certified payroll is a payroll-department problem solvable with the right form or the right software. That assumption is wrong. The form is downstream. The data is upstream. Every line item on a certified payroll report started as a punch at a time clock, a mobile check-in, or a manual entry on a timesheet. If that originating record did not carry the project code, trade classification, and wage determination attached to the work being performed, no amount of report formatting will fix it.

In working with public-works contractors, EasyClocking by WorkEasy Software consistently finds that the teams with the cleanest certified payroll records are the ones who solved time capture first, not reporting. The contractors who struggle are the ones who let field supervisors log hours without classification context and then ask payroll to reconstruct the missing data days or weeks later. By then, the accuracy of the data depends on memory, not record.

You can learn more about building a complete certified payroll workflow from time capture through reporting in the construction guide. The critical insight is that the chain of compliance starts at the moment a worker punches in, and every link after that is only as strong as the data captured at that first touch.

Are Davis-Bacon and State Prevailing Wage the Same Compliance Problem?

No. Davis-Bacon and state prevailing-wage laws are structurally different compliance obligations that many contractors must navigate simultaneously on the same project. Davis-Bacon applies to federally funded construction contracts over $2,000. State prevailing-wage laws, like California's DIR requirements, apply to state-funded projects and often set higher rates. On mixed-funding projects, the higher standard applies, and it is not always the federal one.

California's DIR prevailing-wage rates frequently exceed Davis-Bacon rates. A contractor who defaults to the federal wage determination on a state-funded project is non-compliant even if every number on the WH-347 is internally consistent. The report looks right. The rates are wrong. The fringe benefit calculation may differ. The overtime thresholds almost certainly differ.

The operational implication is that your time-capture system must carry a funding-source tag at the project level. Without it, the downstream certified payroll report cannot be correctly routed to the right wage determination, the right overtime rules, or the right reporting form. EasyClocking by WorkEasy Software addresses this with project-level wage-determination tagging built specifically to handle mixed-funding projects where both Davis-Bacon and DIR obligations apply to the same crew on the same day.

You can explore the structural differences between federal and state prevailing-wage frameworks in the construction solutions section. The takeaway for contractors operating across jurisdictions is that a single payroll configuration cannot serve both federal and state obligations unless the time data itself distinguishes which law governs each hour worked.

Does 1099 Classification Exempt Workers from Certified Payroll?

Not necessarily. The exemption test for certified payroll is not the tax classification but the economic-reality test applied by the DOL and state labor agencies. A worker who is 1099 for tax purposes but works exclusively for one contractor, uses that contractor's tools, and works under that contractor's supervision is likely an employee for prevailing-wage purposes. The contractor is liable for the wage differential, back pay, and potential debarment.

This misunderstanding surfaces most often in specialty subcontractor relationships. The general contractor assumes the sub's 1099 workers are the sub's compliance problem. On a prevailing-wage project, that assumption can be expensive. The DOL and state agencies look through the tax classification to the working relationship, and the GC can be held jointly responsible if the sub's workers were misclassified.

What EasyClocking by WorkEasy Software has seen repeatedly is that the 1099 exemption question is not a payroll question. It is a classification question that has to be answered before a single hour is logged. If you capture time for a worker without resolving their classification status for prevailing-wage purposes, you are building your certified payroll on an unverified assumption.

For definitions of independent contractor status under prevailing-wage law, see the resources hub. The practical guidance for contractors is to resolve classification at onboarding, tag it in your time-capture system, and never rely on tax classification alone to determine certified payroll obligations.

Why Does Prevailing-Wage Overtime Break Standard Payroll Assumptions?

Prevailing-wage overtime is calculated differently than FLSA overtime, and contractors who run prevailing-wage projects through a standard payroll engine without a prevailing-wage overtime module systematically underpay overtime. Under FLSA, overtime is calculated on the blended rate across all hours worked in a week. Under Davis-Bacon and most state prevailing-wage laws, overtime is calculated on the classification rate for the hours in which overtime is worked. Fringe benefits may or may not be credited toward the overtime premium depending on the jurisdiction.

California's DIR prevailing-wage rules add further complexity. California applies daily overtime (over 8 hours) and double-time (over 12 hours) thresholds that do not exist under federal Davis-Bacon. This makes California DIR certified payroll the most complex single-jurisdiction variant in the U.S. A contractor operating in California who applies only weekly FLSA overtime thresholds will underpay every worker who exceeds 8 hours in a single day.

EasyClocking by WorkEasy Software's overtime engine is built to apply the correct overtime logic by jurisdiction and classification, not by defaulting to FLSA rules that produce the wrong number on a prevailing-wage project. You can review how overtime compliance and visibility works within the platform to understand the structural difference between standard and prevailing-wage overtime handling.

The audit exposure compounds with every pay period. Each miscalculated overtime payment is a separate line item on a certified payroll report, and each line item is a separate basis for a finding of non-compliance.

What Makes the Statement of Compliance So Consequential?

The statement of compliance (WH-347 Part II or its state equivalent) is not a formality. It is a legal attestation that the signatory has reviewed the certified payroll report and that all information is accurate. Signing a statement of compliance on a report that contains misclassifications, overtime errors, or missing fringe benefit data exposes the individual signatory, not just the company, to False Claims Act liability on federally funded projects and to personal liability under state prevailing-wage statutes.

Contractors who automate time capture and classification upstream can sign the statement of compliance with confidence because the data chain is auditable from clock-in to report. Contractors who manually compile the report from spreadsheets are signing a document they cannot fully verify. A defensible certified payroll record is one where every line item traces to a timestamped, classification-tagged time entry with project and funding-source context attached.

EasyClocking by WorkEasy Software's position is that the statement of compliance should be the easiest part of certified payroll: a confirmation of a clean data chain, not a leap of faith. That is only possible when time capture is payroll-ready from the first punch. The platform's audit trail logs punches, edits, approvals, and classification assignments so the signatory can verify the report against source data before signing.

For step-by-step guidance on preparing and signing the statement of compliance, review the construction time tracking guide. The bottom line is that practitioners who want audit-ready certified payroll need to audit their time-capture workflow first, specifically whether every time entry carries job, classification, funding-source, and jurisdiction context before it reaches the payroll engine.

How EasyClocking by WorkEasy Software Addresses This

EasyClocking by WorkEasy Software combines biometric time clocks proven in industrial conditions with a cloud platform that tags every punch with project, classification, and jurisdiction context at the point of capture. The system applies the correct overtime logic by jurisdiction and classification, supports project-level wage-determination tagging for mixed-funding projects, and maintains an audit trail from clock-in through certified payroll export. With integrations into payroll systems, approved hours and classification data flow into payroll without manual re-entry or spreadsheet reconstruction. Most sites go live within days, and the platform requires no IT team to deploy.

Certified Payroll Is a Time-Capture Problem, Not a Forms Problem

What You Need to Know

Sources

Related on EasyClocking

Is your time tracking system fair to your team?

Frequently Asked Questions

Clocked

Not Ready for a Quote? Start Here.