Certified Payroll for Beginners:
What Every Contractor Must Know

What Certified Payroll Actually Is

Here's the simplest way to understand it: regular payroll answers one question — "did I pay my people?" Certified payroll answers a different question — "can I prove to the government that I paid my people the legally required wages?"

When you win a construction contract funded by federal money — anything from a USDA rural water project to a GSA office renovation to a DoD barracks upgrade — the government attaches a string to every dollar: you must submit a weekly report documenting exactly who worked, what they did, how many hours they put in, what rate you paid them, and what deductions you took out. That weekly report is your certified payroll. The standard federal form for this report is WH-347 (official DOL form page) — or your state's equivalent if the project falls under state prevailing wage law.

This isn't optional paperwork. It's a legal obligation embedded in the contract. You submit it every week, on time, for every worker — including subcontractors' crews. If a sub fails to submit, you are on the hook as the prime contractor (more on that later).

The core output is the WH-347 form, but the real requirement is the underlying system: your time records, wage rate documentation, worker classifications, and fringe benefit calculations all have to stand up to audit. Certified payroll isn't just a form you file — it's a record-keeping discipline you adopt.

Where It Comes From: The Davis-Bacon Act

Understanding why certified payroll exists makes the rest of this much easier to navigate. The requirement traces back to 1931 — the depths of the Great Depression — and a specific problem Congress wanted to solve.

At the time, federal construction contracts were being won by out-of-state firms that would import cheap labor, underbid local contractors who paid fair wages, complete the project (sometimes poorly), and leave. Local workers lost jobs. Local contractors couldn't compete. Communities that needed the economic boost from federal construction spending were instead watching their wages get driven down by itinerant low-ball bidders.

The Davis-Bacon Act (40 U.S.C. § 3141 et seq.) was Congress's answer. Its core mechanism: any contractor working on a federally funded construction contract over $2,000 must pay workers no less than the prevailing wage for that type of work in that geographic area. The prevailing wage isn't a fixed number like the federal minimum wage — it's the rate that the U.S. Department of Labor determines, through local surveys, to be standard for each construction trade (carpenter, electrician, laborer, operating engineer, etc.) in each county.

The law also spawned a network of supporting regulations:

• 29 CFR Part 5 — the labor standards enforcement rules that govern how Davis-Bacon is applied on the ground
• 29 CFR Part 1 — the procedures the DOL uses to survey and publish wage determinations
• 29 CFR Part 3 — implementing the Copeland "Anti-Kickback" Act (40 U.S.C. § 3145), which regulates what deductions you can take from a worker's paycheck and makes it illegal to require kickbacks
• Contract Work Hours and Safety Standards Act (CWHSSA) (40 U.S.C. § 3701 et seq.) — requires 1.5× overtime pay for hours worked beyond 40 in a week on covered contracts

Twenty-nine states have since enacted their own "Little Davis-Bacon" laws, extending prevailing wage requirements to state-funded public works. The thresholds vary widely — from $1,000 in some states to $100,000 in others. If you're bidding public work in California, New York, or Illinois, you're dealing with both federal and state prevailing wage frameworks, each with its own wage determinations and reporting forms.

A significant regulatory update arrived in 2023, when the DOL overhauled Davis-Bacon rules for the first time in decades — updating how prevailing wages are calculated and strengthening enforcement mechanisms. While the Associated General Contractors (AGC) challenged parts of the rule in court and obtained an injunction on certain provisions, most of the update is in effect and applies to contracts awarded after October 2023.

The WH-347 Form: What Goes In It

The WH-347 is the standard federal certified payroll report. Think of it not as a form you fill out once, but as a template you submit every single week for the duration of the project. Here's what each section covers — not a line-by-line tutorial, but the structural understanding you need to make sense of it.

The key information categories

Worker identity and classification. For each employee, you report their name, the last four digits of their SSN (not the full number), and — critically — their work classification. This classification isn't whatever job title you use internally. It must match the classifications listed in the wage determination attached to your contract. If your contract's wage determination says "Carpenter" at $34.50/hr and "General Laborer" at $22.75/hr, those are the exact classifications you must use. Classifying a carpenter as a laborer because it's easier is a violation — even if the worker agreed to it.

Hours and rate. Two columns track straight-time hours (up to 40 per week) and overtime hours (beyond 40). The rate of pay — including both the base hourly rate and the fringe benefit rate — must meet or exceed the prevailing wage determination. CWHSSA requires 1.5× for overtime.

Gross wages, deductions, net wages. The Copeland Act tightly restricts what you can deduct from a worker's paycheck on a covered project. Standard withholdings (taxes, FICA) are fine. Deductions for tools, safety equipment, or transportation typically are not — unless the worker gave written consent and the deduction benefits the worker, not the employer.

Fringe benefits. The prevailing wage has two components: the base hourly rate and the fringe benefit rate. You have a choice: pay the fringe amount as additional cash wages on top of the base rate, or apply it toward bona fide benefit plans (health insurance, pension, vacation funds). If you contribute $5/hr to a worker's health plan and the fringe rate is $5.38/hr, you need to pay the $0.38 difference in cash. If your benefits exceed the fringe rate, you can't recover the excess — it just stays as a benefit to the worker. This calculation, more than any other single item on the WH-347, is where contractors make costly errors.

Statement of Compliance. The bottom of every WH-347 includes the Statement of Compliance — a block of text you sign every single week. The language says, in substance: "I certify that the information on this payroll is correct and complete, that each worker has been paid the applicable prevailing wage, and that I am aware that willful falsification may subject me to civil or criminal prosecution." This isn't legalese you can skim. By signing — which you must do every week — you're making a legally binding representation.

Form version note. In December 2025, the DOL updated the WH-347 with a new OMB control number. Starting September 30, 2026, the old version of the form will no longer be accepted. If you have active contracts spanning that date, make sure your payroll provider or manual template is using the current version.

Regular Payroll vs. Certified Payroll: The Mental Shift

This is the section most guides skip — and it's the one that makes everything else click. When you run payroll for a private project, your mental model is straightforward: calculate hours × rate, subtract deductions, issue checks or direct deposits, done. The payment is the output.

Certified payroll flips that model entirely. The payment still happens, but the output is now the auditable record. You're not just paying workers — you're building a chain of evidence, every week, that you paid the right amount to the right person doing the right classification.

Here's how that changes five specific things about your payroll workflow:

1. Classification becomes a compliance decision, not a convenience. On a private job, if you need John to do some cleanup after his framing work, you pay him his framing rate for all hours and move on. On a Davis-Bacon job, John's hours must be split between classifications if he performs work that falls under different categories. A framing carpenter who spends three hours clearing debris for truck access needs those hours reported as laborer work at the laborer prevailing rate — not the carpenter rate. Getting this wrong, week after week, compounds into back-wage liability.

2. Fringe benefits are part of the wage, not an afterthought. In most private payroll, benefits are a separate line in the budget. In certified payroll, the fringe benefit rate is part of the prevailing wage — and you have to account for it per employee, per week, on the form itself. If you're paying fringe as cash, it's a straightforward addition to gross wages. If you're crediting toward benefits, you need documentation that the plan meets DOL criteria for a bona fide benefit. The calculation is simple in concept but operationally messy — especially for smaller contractors who may not have a standing benefits plan for every trade.

3. The weekly filing deadline is non-negotiable. General contractors who've worked on federal projects learn this fast: the contracting officer expects the certified payroll packet every week, on time. Late submissions don't just annoy the contracting officer — they violate the contract terms and can trigger a cure notice. This isn't like sending an invoice a few days late. The weekly cadence is baked into the regulatory framework, and there's no "close enough" grace period.

4. Your signature carries criminal exposure. When you sign a regular payroll, you're authorizing payments. When you sign a WH-347 Statement of Compliance, you're making a sworn statement under 18 U.S.C. § 1001 — and knowingly submitting false information is a federal crime. This sounds alarming, and it should. It's also why the DOL recommends (and many contractors insist) that the person preparing the payroll and the person signing it both understand exactly what every column contains. "I didn't know fringe had to be reported separately" isn't a defense — it's evidence of a compliance failure.

5. Records are the product, not the byproduct. If an auditor arrives three years after contract completion and you can't produce the certified payroll reports, you have a problem — even if everyone was paid correctly. The federal retention requirement is three years from the date of contract completion (29 CFR 5.5(a)(3)), but many states go longer: California requires five years, New York requires six. You're not just filing these forms to satisfy a weekly requirement — you're building an archive that must survive scrutiny years later.

If you internalize one thing from this section, make it this: certified payroll is not a harder version of regular payroll. It's a fundamentally different exercise — one where the evidence trail is the deliverable.

What Happens When It Goes Wrong

Davis-Bacon enforcement is real, and the penalty structure escalates quickly. Between 2009 and 2016, the DOL's Wage and Hour Division recovered over $1.2 billion in back wages from Davis-Bacon and related Act violations. Those aren't abstract numbers — they represent real contractors who got the classification wrong, miscalculated fringe, or assumed nobody was checking.

The penalty ladder works like this:

Level 1 — Back wages with interest. This is the most common outcome. If the DOL determines workers were underpaid, you owe the difference — plus interest and, in some cases, liquidated damages. The amounts can compound fast. Underpay one carpenter by $3.15/hr for six months on a 40-hour week, and you're looking at roughly $3,276 in back wages before interest — for one worker on one project.

Level 2 — Contract funds withheld. The contracting agency can withhold funds from your progress payments to cover back-wage liability. For a contractor operating on thin margins, this withholding can trigger cash flow problems that cascade through the entire project.

Level 3 — Contract termination. If violations are knowing or repeated, the government can terminate the contract for default. A default termination is a career-altering event — it goes on your record and follows you into future bids.

Level 4 — Debarment. This is the nuclear option. The DOL can bar a contractor or subcontractor from bidding on or working on federal contracts for up to three years. For a construction company whose business model depends on public works, debarment is effectively a death sentence for that segment of the business. It's published in the Federal Register and on SAM.gov, visible to every agency and prime contractor evaluating bids.

Reddit threads on r/GovernmentContracting and r/ConstructionManagers paint the on-the-ground reality. One small subcontractor with a 12-person crew described spending two to three hours every week manually filling out WH-347s: "Anyone have a good system for Davis-Bacon certified payroll? Drowning in WH-347s." Another commenter captured the pressure around classifications: "Union construction payroll... manual submissions... hard to tell things like whether breaks were actually taken, which job or classification hours should be coded to."

And here's a point that catches many first-time prime contractors off guard: as the prime contractor, you are strictly liable for your subcontractors' certified payroll compliance. If the electrical sub falsifies classifications or skips reports, the DOL comes after you — not just them. The standard construction contract language (FAR 52.222-8 and 52.222-11) makes this explicit. The practical implication: you need a system for collecting, reviewing, and archiving your subs' weekly certified payroll reports — and you need to do it from day one of the project.

How Technology Changes the Game

Given everything above — weekly filings, classification tracking, fringe calculations, audit-ready archives — you're probably wondering whether you need specialized software. The short answer is: you need a system, and for most contractors, that system involves technology.

The software landscape

The market has evolved significantly beyond the era of filling out WH-347 in triplicate by hand. Roughly three categories of tools exist:

Compliance submission platforms like LCPtracker, eMars, and Elations are specialized portals that many government agencies require contractors to use for submitting certified payroll electronically. These platforms validate form completeness and flag errors before submission, but they don't prepare the data — you still need to get the numbers in.

Construction-specific payroll services — including Payroll4Construction, eBacon, Miter, Points North, and MyConstructionPayroll — are built from the ground up to handle prevailing wage calculations, fringe benefit tracking, multi-classification reporting, and WH-347 generation. They understand Davis-Bacon in a way that general payroll providers often don't.

General payroll and ERP systems — ADP (which offers a construction module), Paychex, and QuickBooks — can handle some certified payroll workflows but weren't designed for them. QuickBooks, notably, has no native certified payroll support; you'd be relying on third-party add-ons or manual exports. Construction ERP platforms like Procore, Viewpoint (Trimble), Sage, and CMiC integrate certified payroll into broader project management, but they represent a significant investment most suitable for mid-size and larger contractors.

The bottleneck nobody talks about: source documents

Regardless of which software you choose — or even if you're still filling out forms manually — there's a step that happens before any data enters any system. A worker somewhere fills out a paper time card, a foreman signs a daily log, and someone in the office has to transcribe those handwritten hours, cross-reference the correct classification, and enter the numbers into the payroll system.

This is the silent bottleneck in certified payroll — and it's where the most common errors originate. A digit transposed, a classification misread from a smudged card, an overtime hour entered as straight time. These aren't software failures; they're human transcription failures at the first link in the chain.

This is where AI-powered document extraction changes the workflow. When you scan or photograph a paper time card or pay stub, the AI reads the structured fields — hours worked, dates, worker names, pay rates — and populates them into a table ready for verification. It doesn't replace your payroll system or your compliance platform; it eliminates the step where someone sits at a keyboard manually typing numbers from paper.

For a small contractor whose office manager spends Wednesday afternoons transcribing time cards, the time savings are material. More importantly, the error rate drops. A properly scanned time card doesn't generate a transcription mistake — you're verifying data, not creating it.

This isn't about replacing your payroll provider or your compliance platform. It's about fixing the one step in the certified payroll chain that software has largely ignored: getting raw data off paper and into a digital format, accurately, without manual keying.

Frequently Asked Questions

Does certified payroll apply to every construction project?

No. It applies only to federally funded construction contracts over $2,000, plus state-funded public works in the 29 states with "Little Davis-Bacon" laws. Private construction projects — a commercial office build-out, a residential development, a retail renovation — are not subject to certified payroll requirements unless there's a specific federal funding component (such as HUD financing or a federal grant).

Can I do certified payroll manually, or do I need software?

You can do it manually — the WH-347 is a publicly available PDF, and many small contractors handle it this way. But the operational burden scales quickly. A contractor with five employees on one project can manage manually. A contractor with 25 employees across three projects, each with different wage determinations, will find manual preparation consumes hours per week and introduces significant error risk. Software doesn't remove your compliance responsibility, but it reduces the mechanical workload and catches classification mismatches before submission.

What's the difference between prevailing wage and minimum wage?

Minimum wage is a floor — the lowest legal rate you can pay any worker. Prevailing wage is a local market standard for a specific trade. On a Davis-Bacon project in Cook County, Illinois, the prevailing wage for a carpenter might be $48.25/hr (base + fringe), while the federal minimum wage is $7.25/hr and the Illinois minimum is $15.00/hr. You pay the higher of the applicable rates — and on a Davis-Bacon project, the prevailing wage is almost always higher.

What if my subcontractor doesn't submit certified payroll?

As the prime contractor, you are responsible. FAR 52.222-8 and 52.222-11 explicitly state that the prime must collect, review, and submit subcontractor certified payroll reports. If you submit your own WH-347 on time but your sub's is late or missing, the noncompliance is yours. Most experienced prime contractors build certified payroll submission deadlines into their subcontracts (e.g., "subcontractor shall submit certified payroll to prime by Wednesday 5pm for the preceding week") with contractual penalties for late delivery.

How long do I need to keep certified payroll records?

Federal requirement: three years from the date of contract completion. But state requirements often exceed this — California mandates five years, New York requires six. If you're working in multiple states, default to the longest applicable retention period. Records should include the certified payroll reports themselves, plus supporting documentation: original time cards, wage determination documents, fringe benefit plan statements, and any correspondence with the contracting agency about payroll matters.

What happens if I discover an error in a previously submitted WH-347?

File a corrected report immediately. The DOL views self-identified and self-corrected errors far more favorably than errors discovered during an audit. Document what was wrong, why it happened, what you've corrected, and any back wages paid as a result. The Statement of Compliance on the corrected form should reference the original submission and explain the correction.