Certified payroll is a federally required weekly wage report that contractors must submit when performing work on prevailing wage projects covered by the Davis-Bacon Act, documenting every worker’s classification, hours, wages, and fringe benefits — certified accurate under penalty of law via Form WH-347.
Certified payroll is not a one-time setup. It repeats every week a project is active. The U.S. Department of Labor mandates this weekly cadence for the full duration of each prevailing wage contract — which is exactly why contractors describe it as one of the most persistent administrative burdens in the construction business.
Unlike a standard payroll report, the WH-347 is a legal declaration. The reverse side contains the Statement of Compliance, a signed certification that carries real consequences. Errors — even clerical ones — can constitute a false certification under 18 U.S.C. § 1001.
Certified payroll is a federally mandated weekly submission — not a one-time task — that repeats every week a prevailing wage project is active.
Form WH-347 requires contractors to report every worker's classification, hours, wages, and fringe benefits, signed under penalty of law via the Statement of Compliance.
Worker misclassification, late submissions, and missing fringe documentation represent the three highest-liability errors contractors make in the weekly cycle.
Classification-based time tracking, assigned ownership, and a submission calendar are the three process changes that eliminate the Friday crunch before it starts.
Certified payroll software automates WH-347 generation, prevailing wage rate lookups, and direct portal submission — cutting weekly prep time from hours to under thirty minutes.
Certified payroll compliance requires contractors to collect, verify, calculate, and submit Form WH-347 each week for every active prevailing wage project — a cycle the DOL mandates for the full duration of each contract, with no breaks between payroll periods.
Most teams don’t struggle with certified payroll once. They struggle with it fifty-two times a year. When you have multiple active prevailing wage projects, the weekly cadence compounds. Three projects means three submission deadlines — potentially to three different agencies through three different portals, all due within the same window.
Manual certified payroll preparation typically takes three to five hours per project per week. For a contractor running four prevailing wage jobs, that’s a part-time position dedicated entirely to a compliance report.
The Friday pattern is predictable: hours trickle in from field crews Monday through Wednesday, Thursday is for chasing classifications and verifying fringe calculations, and Friday is for completing the WH-347, getting the signature, and submitting before the deadline.
Certified Payroll Requirements: What the WH-347 Form Demands
The WH-347 form requires contractors to report each worker’s name, work classification, daily and weekly hours, gross and net wages, all deductions, and fringe benefit contributions — plus a signed Statement of Compliance certifying accuracy under federal law.
Every field on the form is load-bearing. Here is what each weekly WH-347 submission must include:
• Worker name and identifying information
• Work classification (must match the applicable prevailing wage determination)
• Hours worked each day of the week and total weekly hours
• Hourly rate of pay and overtime rate
• Gross wages earned and all deductions (taxes, FICA, fringe contributions)
• Net wages paid
• Fringe benefit payment details (cash, plan contributions, or combination)
• Signed Statement of Compliance
Subcontractors have their own obligation. Each sub on a Davis-Bacon covered project must submit certified payroll independently. The prime contractor is responsible for collecting and reviewing those subcontractor submissions — which means the prime’s weekly workload scales with the number of subs on each job.
Davis-Bacon Act prevailing wage compliance applies to contractors and subcontractors on federally funded or federally assisted construction contracts over $2,000 — and more than thirty states extend similar requirements to state-funded projects through their own prevailing wage laws.
Key triggers for certified payroll requirements:
• Federal construction contracts exceeding $2,000
• Federally assisted construction projects (HUD, FHWA, EPA-funded work)
• State-funded projects in states with prevailing wage laws
• Renovation, repair, or alteration work on covered public facilities
• Projects where a wage determination number appears in the contract documents
State coverage: Is certified payroll required for state projects? Yes, in most states. California uses DIR’s eCPR system. New York has its own portal. Texas limits prevailing wage to highway construction. Verify the applicable law and submission portal before work starts — it defines your entire compliance framework for the project.
Most certified payroll errors trace back to five problems: misclassified workers, missed fringe benefit credits, incorrect overtime calculations, incomplete fringe documentation, and late or missing submissions — each of which creates direct liability exposure for the contractor.
Prevailing wage determinations assign specific pay rates to specific job classifications. A laborer is not always a laborer — the rate can differ between a “laborer,” a “carpenter’s helper,” and an “equipment operator.” When field supervisors track time without standardized classification codes, every Friday becomes a debate about what each worker was doing each day.
Contractors can offset a portion of the prevailing wage obligation using legitimate fringe benefit contributions — health insurance, pension plans, vacation pay, training fund payments. These credits must be documented, calculated per hour worked, and reported correctly. Underclaiming costs money. Overclaiming creates audit liability.
Davis-Bacon overtime rules interact with FLSA requirements in ways that are easy to get wrong. Prevailing wage rates apply to the first eight hours per day. Federal overtime kicks in after forty hours per week. Many state prevailing wage laws add daily overtime thresholds on top. Getting all three right simultaneously requires a clear, documented calculation process.
If you are claiming fringe credits, the DOL requires plan documentation on file and available for inspection. Many contractors submit the fringe credit consistently but never organize the underlying plan documents — creating audit exposure that surfaces months or years later.
Repeated late submissions are a primary trigger for DOL Wage and Hour Division investigations. One missed week creates a compliance gap. A pattern of missed weeks signals systemic wage payment control problems — which tends to expand the scope of any investigation.
Audit risk: Agencies notice submission gaps in their logs. When they come looking, the investigation scope tends to expand beyond the timing issue into actual wage payment practices.
A reliable certified payroll process depends on three things happening before Friday: time tracking tied to job classifications, fringe benefit data organized by worker, and one person accountable for each project’s weekly submission deadline.
The goal is not to make certified payroll faster on Fridays. The goal is to make Friday a ten-minute final check — not a three-hour data recovery sprint.
Every hour tracked must carry a job classification code. Create a project-specific classification code sheet at kickoff that references the applicable wage determination directly. Share it with every foreman. This single document eliminates most Friday classification debates.
Know exactly what you are contributing per hour worked — health insurance premiums, pension contributions, vacation accruals, training fund payments — and verify those amounts meet or offset the fringe portion of the prevailing wage determination. Document each plan in a project folder from day one.
Certified payroll submissions follow the project, not just the payroll cycle. A shared calendar with project name, awarding agency, portal link, and submission deadline prevents the “which project is due where?” conversation every Thursday. If you are using LCPtracker, eMars, or a state-specific portal, log the credentials with the calendar entry.
Shared responsibility means no one is responsible. One admin team member should own the process for each project — collecting classifications, running the WH-347, securing the signature, and submitting on time.
Certified payroll software automates WH-347 form generation, prevailing wage rate lookups, fringe benefit calculations, and direct agency submission — cutting weekly preparation time from several hours to under thirty minutes for contractors running multiple projects.
Purpose-built certified payroll software pulls current wage determinations directly from SAM.gov, calculates fringe benefit credits automatically, generates completed WH-347 forms from payroll data, and submits directly to LCPtracker, eMars, or agency-specific portals without manual re-entry.
Key features to evaluate:
• Payroll system integration — eliminates re-entry errors
• Prevailing wage rate database with automatic updates
• Multi-project management with per-project submission tracking
• Direct portal submission to LCPtracker, eMars, and state systems
• Fringe benefit credit calculation support
• Audit trail documentation with timestamps and version history
• Subcontractor compliance tracking
Before you buy: Confirm integration with your existing payroll system. Manual data re-entry between systems recreates the same error exposure you are trying to eliminate.
Contractors preparing for a prevailing wage compliance audit need organized records for every project: all WH-347 forms, the applicable wage determination, daily time records with classifications, fringe benefit plan documents, and payroll registers — all retained for at least three years after project completion.
Build your audit-ready file structure at project kickoff:
• Wage determination (the version incorporated into your contract)
• Worker classifications and rates for each trade on the project
• Weekly WH-347 submissions organized by date
• Payroll registers or reports by pay period
• Fringe benefit plan documents with per-hour contribution amounts
• Proof of fringe benefit payments (plan statements, canceled checks, or remittance records)
• Subcontractor certified payroll submissions and your review records
State prevailing wage laws follow the same core structure as the federal Davis-Bacon Act — weekly submissions, classification-based reporting, and signed certifications — but differ in wage determination sources, submission portals, overtime rules, and covered project thresholds.
What typically stays the same across federal and state requirements:
• Weekly submission cadence
• Classification-based hourly wage reporting
• Fringe benefit documentation requirements
• Signed Statement of Compliance
• Three-year minimum record retention
What varies by state:
• Wage determination source (state labor department vs. SAM.gov)
• Submission portal (eCPR in California, state-specific systems elsewhere)
• Covered project thresholds (some states use lower dollar thresholds than the federal $2,000)
• Daily overtime rules (California imposes daily overtime at eight hours; federal law does not)
• Coverage for maintenance and service work vs. construction only
Certified payroll gets easier when you stop treating it as a Friday task and start treating it as a Monday-through-Friday process.
The contractors who make certified payroll easy are the ones who built the process once and then run it — not the ones who improvise it every week. Certified payroll software helps significantly when you are managing multiple prevailing wage projects simultaneously. Clear ownership, classification-based time tracking, and organized fringe documentation help at any scale.
If your team is currently stuck in the Friday crunch cycle, the fastest fix is the simplest one: build the classification code sheet this week, assign one owner per project, and put every submission deadline on a shared calendar. That is not a technology purchase. It is a process decision — and it is the foundation on which everything else builds.
Submitting an incorrect worker classification can result in underpayment liability, back-wage obligations, civil penalties, and — for willful misclassification — potential debarment from federally funded projects for up to three years. If you discover a classification error after submission, file a corrected WH-347 immediately. Average back-wage liability per DOL prevailing wage investigation exceeds $50,000.
Certified payroll must be submitted weekly — the DOL’s guidance establishes a weekly cadence, and most awarding agencies require submission within seven days of each payroll period’s end. Some agencies impose tighter deadlines. The safest practice is to treat Friday of each work week as your submission deadline. Late submissions — even by a few days — can trigger payment withholding and flag your project for enhanced monitoring.
Late or missing certified payroll submissions can result in withheld contract payments, DOL investigations, and — for repeated violations — debarment from federally funded projects for up to three years. Agencies have discretion in how they respond to a single late filing vs. a pattern. A pattern of late submissions typically expands the investigation scope beyond timing into actual wage payment practices.
Yes — in most states, certified payroll is required for state-funded construction projects under state prevailing wage laws, which mirror the federal Davis-Bacon Act but apply their own wage determinations, submission portals, and project thresholds. More than thirty states maintain prevailing wage laws. Verify the applicable state law and submission process before work begins on any publicly funded project.
Yes — subcontractors on Davis-Bacon covered projects must submit their own certified payroll reports independently, and the prime contractor is responsible for collecting, reviewing, and retaining those subcontractor submissions. Primes who fail to monitor subcontractor submissions can face liability for wage violations they did not directly cause.