Certified Payroll Reporting: Software That Keeps You Compliant
Certified payroll reporting is one of the highest-stakes compliance areas for contractors performing public works. The requirements are specific, the deadlines are weekly, and the penalties for non-compliance are substantial. Contractors who get certified payroll right produce clean reports on time and avoid the audit findings that can produce withheld payments, back wages, debarment from future federal contracts, and significant financial penalties. Contractors who get it wrong typically don't realize they're getting it wrong until an audit reveals compliance gaps that have accumulated for months or years.
The framework comes from federal law. The Davis-Bacon Act and its Related Acts (DBRA) require contractors performing federal or federally-assisted construction work over $2,000 to pay prevailing wages and submit weekly certified payroll reports to the contracting agency. The federal framework applies directly to federal construction projects and indirectly through "Related Acts" to most federally-assisted construction (HUD projects, federal-aid highways, federal water projects, and many others). Most states have parallel prevailing wage laws applying to state public works projects, often with similar but state-specific reporting requirements.
This article covers what certified payroll is, how Davis-Bacon compliance works, what the WH-347 form requires, the consequences of non-compliance, and how software automates the workflow. The deeper coverage of construction payroll more broadly lives in our guide to construction payroll software. The deeper coverage of multi-state payroll complications can be found in our multi-state payroll section.
What Certified Payroll Is and When It Applies
Understanding the scope clarifies who needs to comply.
The Davis-Bacon Act
The Davis-Bacon Act (1931) applies to federal contracts in excess of $2,000 for the construction, alteration, or repair of public buildings or public works. The Act requires contractors and subcontractors to pay laborers and mechanics on the site of the work at least the locally prevailing wages, including fringe benefits, as determined by the Department of Labor.
The "site of the work" definition matters: prevailing wages apply to work performed at the construction site itself plus any adjacent or virtually adjacent secondary sites where significant portions of the building are constructed exclusively for the project. Work performed at general manufacturing facilities or material supply points typically isn't covered.
Davis-Bacon Related Acts (DBRA)
Beyond direct federal contracts, the "Related Acts" extend Davis-Bacon labor standards to most federally-assisted construction. The Related Acts cover:
HUD projects (housing development, community development, etc.)
Federal-aid highway projects
Federal water pollution control projects
Many infrastructure projects under the Infrastructure Investment and Jobs Act
Numerous other federally-funded construction programs
Contractors working on any project receiving federal financial assistance for construction need to verify whether Davis-Bacon Related Acts apply, because the requirements apply even when the contractor's contract is with a state, local, or private entity rather than directly with the federal government.
The Copeland Act
The Copeland "Anti-Kickback" Act (1934) requires contractors and subcontractors performing work on federal or federally-financed construction contracts to submit weekly statements of wages paid. The Copeland Act is what creates the certified payroll reporting requirement specifically; the Davis-Bacon Act creates the prevailing wage requirement, and Copeland creates the documentation requirement.
State Prevailing Wage Laws
Most states have their own prevailing wage laws applying to state-funded public works projects. State requirements typically parallel the federal framework but with state-specific:
Wage determinations
Reporting forms
Submission procedures
Compliance enforcement
Penalty structures
Some states (Georgia, Florida, Indiana, and a few others) don't have state prevailing wage laws applicable to state-funded projects. Contractors in these states still face federal Davis-Bacon requirements on federal or federally-assisted projects but don't have parallel state requirements on state-only projects.
Project Coverage Determination
The contractor determines coverage based on:
Whether the project is federally funded or assisted (and if so, which Related Acts apply)
Whether state prevailing wage laws apply
The contract value relative to coverage thresholds
The type of work being performed
The site location relative to coverage definitions
Strong contractors verify coverage at project start rather than discovering compliance requirements partway through the work.
Pro Tip: When evaluating any new project for prevailing wage applicability, get explicit written confirmation from the contracting authority about which Davis-Bacon (or state) requirements apply, which wage determination governs, and what reporting is required. Don't rely on assumption or word-of-mouth guidance. Specifications and contracts should explicitly reference the applicable wage determination by number and date. Operations that proceed on assumed coverage sometimes discover audit findings later because the actual coverage was different from assumed coverage. The 30 minutes upfront to confirm coverage prevents months of compliance issues later.
What Certified Payroll Reports Actually Contain
The federal WH-347 form is the standard for federal projects. State forms vary but typically capture similar information.
WH-347 Form Structure
The WH-347 captures information for each worker on the project for each work week:
Worker Information:
Name
Last 4 digits of social security number (full SSN no longer required as of 2008 regulation update)
Number of withholding exemptions
Work classification(s) performed during the week
Hours and Wages:
Daily and weekly hours worked in each classification
Total hours worked
Hourly rate paid for straight time and overtime
Total fringe benefit credit (cash and non-cash)
Gross amount earned
Deductions and Net Pay:
FICA deduction
Federal tax withholding
State tax withholding
Other deductions (specified)
Net pay
Statement of Compliance: The signed certification on page 2 of the WH-347 (or equivalent document) certifies:
Payroll information is accurate
Each laborer and mechanic was paid not less than the required Davis-Bacon prevailing wage
Fringe benefits were paid in cash or to bona fide benefit plans
No rebates or unauthorized deductions were taken
The contractor or signatory has authority to certify
The Statement of Compliance is the legal certification that creates personal liability for false statements. Section 1001 of Title 18 (federal false statement statute) applies to willful falsification.
Updated WH-347 Form
The DOL released an updated WH-347 form in January 2025, valid through January 2028. Key changes include:
Enhanced fringe benefit reporting distinguishing funded vs unfunded benefits
Clearer apprenticeship documentation requirements
Both gross and net pay required (previously some operations reported only one)
Updated overtime calculation fields
Consolidated format incorporating elements of the previous WH-348 supplemental form
The previous WH-347 form remains valid until September 30, 2026, after which only the new form will be accepted. Operations using the old form should plan transitions before the deadline.
Submission Requirements
Certified payroll reports submit weekly to the contracting agency within 7 days of each pay date. Operations need to submit reports for every week the project is active, including:
Weeks when no work was performed (a "no-work" report is required)
Weeks at the end of the project when work has wound down
Weeks during temporary shutdowns or weather delays
Late submissions can produce withheld payments and audit findings. Strong operations build the submission cadence into routine payroll workflow rather than treating it as periodic catch-up work.
State-Specific Variations
State requirements typically parallel federal but with specific differences:
California: DIR (Department of Industrial Relations) electronic submission, specific California-only fringe benefit rules
New York: NY State Department of Labor Bureau of Public Work, additional state-specific requirements
Illinois: IDOL submission, state-specific apprenticeship documentation
Massachusetts: Department of Labor Standards, state-specific procedures
Other states: Each has its own specific requirements
Operations working in multiple states need to track state-specific requirements rather than assuming federal compliance covers state requirements.
Required Recordkeeping Beyond Reports
Beyond the weekly reports, contractors must maintain payroll records for at least 3 years following project completion, including:
Worker names, addresses, social security numbers
Correct work classifications for each worker
Daily and weekly hours worked, including overtime
Hourly rates paid
Deductions taken
Wages and fringe benefits paid
Audits typically request these records, sometimes years after project completion. Operations without proper records face audit findings even if the certified payrolls submitted at the time were accurate.
Case Study: A 30-person commercial subcontractor performed approximately 25% of their annual work on prevailing wage projects through 2022. They handled certified payroll through a $2,400/year specialized service that imported data from QuickBooks Payroll, generated WH-347 forms, and submitted to the appropriate agencies. The system worked but produced occasional reconciliation issues between QuickBooks data and certified payroll outputs. In late 2022, a DOL audit covering 2020-2022 work identified compliance findings totaling approximately $63,000 in back wages owed plus $18,000 in penalties. The findings traced to several issues: workers performing multiple trades within single days where the payroll system had assigned hours to single classifications, fringe benefit calculations that didn't match plan documentation requirements, and apprentice classification documentation that was incomplete for the audit period. They migrated to Foundation Software with integrated certified payroll in 2023 at approximately $24,000 implementation plus $1,800/month subscription. The integrated platform handled multi-classification time correctly, maintained fringe benefit documentation with appropriate audit support, and tracked apprentice registration with required detail. The 2024 audit cycle produced clean findings. The lesson was that certified payroll compliance involves nuances that generic tools handle weakly. The audit findings cost more than years of integrated platform investment would have cost.
Penalties for Non-Compliance
The consequences of certified payroll failures are real and substantial.
Back Wages Owed
The most direct penalty: workers who weren't paid prevailing wages must be paid the difference. For projects with significant violations, back wage findings can run hundreds of thousands of dollars or more. The contractor pays the back wages regardless of whether the underpayment was intentional.
Civil Penalties
Civil penalties for Davis-Bacon violations have increased substantially. Current penalties (effective 2025) can run up to $13,508 per violation, with violations counted broadly (each worker, each pay period, each violation type can count separately).
Withheld Payments
Contracting agencies can withhold project payments to cover potential back wages and penalties. Operations facing audit findings often see project payments held until the issues are resolved, creating immediate cash flow pressure beyond the eventual financial penalty.
Debarment
The most severe penalty: debarment from future federal contracts for up to 3 years. Debarred contractors cannot bid on federal projects or projects receiving federal assistance during the debarment period. For contractors with significant federal business, debarment can be operationally devastating.
Personal Liability
The Statement of Compliance signature creates personal liability for false statements. Officers signing falsely can face civil and criminal prosecution under federal false statement laws.
Subcontractor Liability
Prime contractors are responsible for subcontractor compliance. If a subcontractor underpays workers, the prime contractor can face the consequences. This liability creates strong incentive for primes to verify sub compliance rather than relying on subs to self-police.
State-Specific Penalties
State penalty structures vary but often parallel federal:
California can issue stop-work orders for prevailing wage violations
Some states have additional civil penalties beyond back wages
Some states have permanent or long-term debarment provisions
Multi-state operations face cumulative exposure across jurisdictions
Audit Triggers
Certified payroll audits get triggered by:
Worker complaints to DOL or state labor agencies
Routine audits selected by contracting agencies
Whistleblower complaints from competitors or subcontractors
Cross-references between certified payroll reports and other records (tax filings, workers' comp filings)
High-profile projects with public attention
Operations doing meaningful prevailing wage work should expect periodic audits as part of normal operations rather than as exceptional events.
Pro Tip: Build certified payroll review into the weekly payroll workflow rather than handling it as separate periodic catch-up. The workflow: payroll runs, certified payroll reports generate from the payroll data, the controller or designated person reviews each report for accuracy and consistency, reports get submitted to contracting agencies, copies get archived for audit defense. The integrated workflow takes 30-60 minutes per pay period for typical operations. The catch-up approach (compiling reports periodically across multiple weeks) takes much longer because details fade and reconciliation is harder retrospectively. The integrated workflow also catches errors faster because they surface during current-week review rather than emerging in batches weeks later.
Certified Payroll Compliance Is Operational Necessity
Certified payroll compliance is one of the operational areas where the cost of getting it wrong far exceeds the cost of getting it right. Operations performing meaningful public works construction need systematic compliance: proper time tracking with classification accuracy, prevailing wage application, fringe benefit calculations matching plan documentation, weekly report generation and submission, comprehensive recordkeeping for audit defense.
The capability to handle certified payroll well typically requires construction-specific payroll software (integrated with construction accounting or specialized certified payroll services). Generic payroll plus manual workarounds produces compliance gaps that often surface during audits. The investment in proper tools earns out through compliance risk reduction alone, separate from administrative time savings.
Frequently Asked Questions
What is the WH-347 form?
The WH-347 is the U.S. Department of Labor's standard certified payroll form for federal and federally-assisted construction projects. It documents weekly payroll information for each worker on the project: hours worked, classifications performed, wages paid, fringe benefits, and deductions, along with a signed Statement of Compliance certifying the information is accurate and that workers received required prevailing wages. While use of the WH-347 specifically is optional (other forms with identical wording are acceptable), some form of weekly certified payroll reporting is required for Davis-Bacon covered work. DOL released an updated WH-347 effective January 2025, with the previous version remaining valid through September 2026.
How often do I need to submit certified payroll reports?
Weekly. The Copeland Act requires contractors to submit certified payroll reports weekly for each week the project is active, including weeks when no work was performed (a "no-work" report is required). Reports submit to the contracting agency within 7 days of each pay date. Late or missing reports can produce withheld payments and audit findings. Strong operations build the submission cadence into routine payroll workflow rather than treating it as periodic catch-up.
What happens if I make a mistake on a certified payroll report?
Mistakes happen and can typically be corrected through amended reports submitted to the contracting agency. The correction process varies by agency but generally involves submitting a corrected WH-347 with notation that it amends a prior submission. The key is correcting mistakes proactively rather than waiting for audits to discover them. Mistakes that get corrected promptly typically don't produce significant findings; mistakes that surface during audits years later often produce larger findings because the issues have compounded.
Do I need separate software for certified payroll or can my regular payroll handle it?
Generic payroll services (ADP, Gusto, QuickBooks Payroll, Paychex) typically don't generate certified payroll reports natively. Operations have three approaches: use construction-specific accounting and payroll platforms that generate certified payroll automatically (Foundation Software, Sage 100 Contractor, Viewpoint, others), use specialized certified payroll services (LCPtracker, Points North) alongside generic payroll, or generate reports manually from payroll data using available templates. The integrated approach is typically most efficient for operations doing meaningful prevailing wage work; specialized services work for operations not ready to migrate from generic accounting; manual generation works only for very low volumes of public works.