Is Certified Payroll Always Prevailing Wage? (w/Examples) + FAQs

No, certified payroll and prevailing wage are not the same thing. Certified payroll is the weekly wage report a contractor files to document pay. Prevailing wage is the pay rate the law requires in the first place. The report only exists because a prevailing-wage law already covers the job.

The distinction matters for contractors on federal or federally assisted construction jobs. The $2,000 Davis-Bacon threshold triggers coverage of the entire prime contract. Miss that distinction, and two things can go wrong. You might pay workers correctly but still fail the paperwork, or file paperwork on a job that never needed it.

What Certified Payroll Reports

Certified payroll is a weekly wage report. A contractor or subcontractor files it to prove it paid workers the wages a government contract requires. This article reflects federal Davis-Bacon rules as of 2026, and wage determinations change by project and location. Always confirm the current wage determination before you submit a report.

The report is not the paycheck itself. It is the sworn record of what the paycheck should have been. It also shows what the worker was paid that week.

Contractors may use the Department of Labor's optional Form WH-347 or any other format with the same fields. Each report lists each covered worker's name, labor classification, and daily hours. It also shows the pay rate, gross wages, deductions, and net pay for that week. A signed Statement of Compliance goes with it, certifying under penalty of law that the numbers are accurate.

Federal rules require weekly filing, not monthly or biweekly. A contractor must deliver each week's report within seven days of the pay date. This holds even in a week with no covered work, since a no-work week still needs a report. Federal rules generally ask the contractor and its funding agency to keep the original certified payrolls for at least three years after the project ends.

The prime contractor carries the compliance load for the whole job site, not only its own crew. It must collect, review, and forward each sub's certified payroll to the funding agency. A sub's mistake can still land back on the prime's desk. That is why many general contractors review payroll during sub onboarding, before a problem can surface later.

Independent contractors on a covered job do not escape the rule. Federal guidance treats a 1099 worker on covered construction work the same as an employee for pay purposes. The certified payroll must still list that worker and note that no FICA or taxes were held back. Mislabeling a worker as a contractor to skip this step is one of the fastest ways to draw an investigation.

How Certified Payroll Connects to Prevailing Wage Law

The Davis-Bacon Act, enacted in 1931, set the original rule. Contractors on covered federal construction contracts must pay laborers and mechanics no less than the wage and fringe benefits that prevail locally for similar work. Certified payroll exists to prove that rule was followed, week by week, on every covered contract.

Where no prevailing-wage law covers a project, there is nothing for certified payroll to prove, so the filing rule never applies. Congress extended the Davis-Bacon rule through a group of laws often called the Davis-Bacon Related Acts, or DBRA. These generally cover projects funded by federal grants, loans, loan guarantees, or insurance. A state road and a HUD-insured apartment upgrade can both trigger the same duty, even though only one has a direct federal deal.

The prevailing wage itself is not one flat number. It combines a basic hourly rate with any required fringe benefits. Both pieces are set separately for each labor classification and each area by the Department of Labor. A contractor can pay the cash wage correctly and still owe money if it skips the fringe piece, because both pieces together make up the full prevailing wage.

Not every federal contract that mentions prevailing wage uses the construction-specific certified payroll form. The Wage and Hour Division also enforces other federal wage laws, such as the Service Contract Act for federal service contracts, a separate law with its own wage rules and its own paperwork. A janitorial or security contract at a federal building can carry prevailing-wage rules without ever generating a Davis-Bacon-style certified payroll.

Does My State Differ?

Federal Davis-Bacon rules only reach contracts tied to federal money. Many states run their own prevailing-wage laws, often called little Davis-Bacon statutes. These laws apply to state and local public works even with no federal funding involved. Where both laws apply to the same job, the contractor must satisfy whichever rule is stricter.

States that run their own program often require a separate, state-specific certified payroll form. A contractor may have to file it through the state's own portal, on top of the federal WH-347. Never assume that the absence of federal money means no certified payroll is required. Check with the awarding agency or the state labor department named in the contract.

This matters most for contractors who work across state lines. A job that looks federal in one state might rely on purely private financing in another. Confirm the funding source and the applicable law before each new project, not only once per company.

When You Won't See a Certified Payroll Requirement

A private construction job with no government contract, grant, loan, or guarantee behind it usually sits outside Davis-Bacon. A homeowner remodel, a privately financed office build, or a retail buildout paid with private capital carries no certified payroll duty. No prevailing-wage law reaches down to trigger one. The paperwork follows the funding, not the size or complexity of the job.

A federal contract under the $2,000 threshold also falls outside coverage, though this is rare in practice. Once a prime contract crosses that line, each subcontract under it is covered too, even a small one. Contractors sometimes assume a modest change order is automatically exempt. That assumption is usually wrong once the prime contract itself is covered.

State-funded work with no matching state prevailing-wage law is the other common gap. Not every state has adopted a little Davis-Bacon statute. Some states that have one still carve out smaller public projects below their own dollar line. A contractor moving between states cannot reuse the same checklist from one job to the next.

Filing certified payroll on a job that never needed it is not dangerous, but it wastes staff time and can confuse a later audit. The simplest self-check is to trace each dollar back to its source. Ask whether it came from a federal agency, a federal loan or grant program, a state agency with its own law, or a private client. If each dollar traces to a private source, no certified payroll is required, and none should be filed.

This distinction also protects the reader from over-compliance. A contractor who files certified payroll on an uncovered project creates a paper trail that later reviewers may misread as an admission of coverage. Keep records of the funding source instead, so you can show clearly why the rule never applied. This matters most on mixed-use developments where only part of the money is public.

Which Situation Applies to You?

The certified payroll question comes down to where the project's money originates. It also depends on how the contract itself is structured. Match your project to the closest description below before you decide whether, and how, to file.

A Direct Federal Construction Contract

A federal agency awards the contract directly. Common examples are the General Services Administration and the Army Corps of Engineers. Once the total tops $2,000, Davis-Bacon applies in full. Weekly certified payroll is then mandatory for the prime contractor and each sub on the job.

This is the clearest case of all, and it is the one most contractors picture first. Errors still happen, though, when a prime contractor assumes a sub already knows the rule. Confirm each sub knows the weekly filing duty before work starts on site.

A short kickoff talk about certified payroll can prevent weeks of cleanup later. It costs little time and closes the most common gap on this type of job. Treat it as a normal part of every sub agreement.

A Federally Assisted Project

The project is privately or locally run. But a federal grant, loan, loan guarantee, or mortgage insurance program funds all or part of it. A Davis-Bacon Related Act then extends the prevailing-wage rule to the whole project, not only the federally funded slice. This surprises contractors who assume that if the developer is private, the rules must be too.

Contractors bidding on affordable housing, infrastructure, or broadband builds should confirm this status early. Ask the developer or lender whether any federal financing backs the project. Missing this step before pricing labor can turn a competitive bid into a losing one.

This rule applies whether the federal share is large or small. Even minority federal participation can pull the entire project under Davis-Bacon. When in doubt, request written confirmation from the funding agency.

A State- or Locally Funded Project Only

No federal money touches the project. But the state or municipality has its own prevailing-wage law covering public works of this type and size. Certified payroll is still required, only under state rules instead of federal ones. It often uses a state-specific form rather than the federal WH-347.

Contractors who check only for federal triggers can be caught off guard here. A state highway or school-construction job can carry the same weekly filing duty as a federal one. The penalty for missing it does not care that no federal money was involved.

Ask the awarding agency directly which prevailing-wage law applies before you bid. State labor departments often publish a checklist for exactly this situation. A five-minute call can save weeks of correction later.

A Purely Private Project

No government contract, grant, loan, or guarantee funds any part of the work. No state prevailing-wage law applies to private construction in the area either. No certified payroll duty exists, and none should be filed.

Contractors sometimes file one anyway out of caution, but that habit can backfire. It creates a paper trail a later reviewer may read as an admission of coverage. Keep proof of the private funding source instead, in case the project is ever questioned.

This gap matters most for small contractors who also work public jobs. Mixing habits between a private job and a covered one is where mistakes start. Keep the two workflows apart in your office. A simple color-coded folder system works well for many small firms.

A Federal Service Contract, Not Construction

The federal government is paying for a service, not construction. Think janitorial work, security staffing, or equipment maintenance at a federal site. The Service Contract Act, not Davis-Bacon, sets the wage floor here. Its compliance paperwork looks different from a construction certified payroll.

Both laws are prevailing-wage laws enforced by the same Wage and Hour Division. But reading the phrase prevailing wage in a solicitation is not enough on its own. The type of work performed, service or construction, decides which paperwork applies.

A single company can face both rules on different contracts in the same year. Keep the two compliance tracks separate, since mixing the forms creates confusion during a review. When a contract blends services and construction, ask the contracting officer which rule governs each part.

A Worked Example: Checking a Wage Line for Compliance

Suppose a wage determination for the Laborer classification lists a basic hourly rate of $28.50. It also requires a fringe benefit of $9.10 an hour. Together, that is a total prevailing wage of $37.60 an hour. A subcontractor pays its laborer $28.50 in cash and provides no health plan or retirement contribution.

The worker's certified payroll entry looks compliant at a glance. The base rate matches the wage determination exactly. The gap is the fringe piece, and it is easy to miss because the cash rate on the pay stub looks right. The table below breaks down the shortfall using the same checks a reviewer would use.

At 40 hours in one workweek, the shortfall comes to $364.00 for that single worker. Multiply that by six weeks, and the total reaches $2,184.00 for one laborer alone. A crew of several workers in the same classification multiplies that figure fast. This is the exact pattern a Wage and Hour Division reviewer is trained to spot.

The fix does not require guesswork. The contractor can raise the cash wage to $37.60 an hour going forward. Or it can keep the $28.50 cash rate and add $9.10 an hour in a bona fide benefit like health coverage. Either route satisfies the same total obligation, but the correction should be documented clearly on the next report.

This example uses a single classification to keep the math clear, but real payrolls often mix several classifications in one week. The same shortfall math applies to each one separately. Treat the wage determination as the baseline for each line on the report, not only the cash column.

A contractor who understands this math can catch a shortfall before it compounds across a project. Waiting for a formal review to find it almost always costs more than catching it early. Build this check into each payroll cycle, not only the first one.

Where Contractors Trip Up on Certified Payroll

Three recurring situations account for most certified payroll problems that surface on inspection. Each one teaches a different lesson about where the paperwork and the wage rules can pull apart. None of them involves a contractor deliberately underpaying anyone. Each one starts as a documentation gap that becomes a wage problem later.

Marcus Misses the Funding Trail

Marcus runs a mid-size electrical subcontracting firm. He bid a renovation project believing it was purely private, since his contract ran through the building's private developer with no federal agency in sight. Midway through the job, he learned the developer's construction loan carried federal mortgage insurance. That single fact pulled the entire project under a Davis-Bacon Related Act, retroactively.

Marcus had to rebuild weeks of missing certified payrolls from timecards and bank records. The process cost far more staff time than filing correctly from week one would have. His lesson: confirm the full capital stack behind a project, not only the name on the contract.

Elena Applies the Wrong Wage Line

Elena processes payroll for a plumbing contractor. She logged her crew's hours correctly each week. But she paid one worker at an apprentice wage rate without confirming his registration was still current. Once that registration lapsed, the worker had to be paid the full journeyworker rate for every hour worked after that date.

The correction required back pay covering several pay periods. It also required amended certified payrolls for each affected week. All of it traced back to a single unchecked registration status. Elena now checks apprentice status each pay period, not only at hiring.

A lapsed registration is easy to miss, since nothing about the worker's daily routine changes. The wage rate is the only thing that shifts, and it shifts automatically under the rule. Building a simple registration-renewal calendar prevents the entire problem.

Devon Pays Correctly But Files Late

Devon runs a small paving subcontractor. He paid each worker the exact prevailing wage the project required, with no shortfall in the numbers. His office ran payroll on a biweekly cycle to match his other private jobs. So certified payrolls for the public project arrived every two weeks instead of every week.

An awarding-agency review flagged the timing as a standalone violation. The finding had nothing to do with whether the wages themselves were correct. Devon's lesson is that the filing schedule is its own separate rule, not a formality attached to the wage rule.

He now runs a separate weekly cycle for each covered project, even when it duplicates work his office already does biweekly for private jobs. The extra step takes an afternoon each week and has never triggered another finding. He treats it as a fixed cost of doing public work.

Mistakes to Avoid

Certified payroll problems tend to repeat across contractors, and most of them are avoidable once you know where they hide.

• Filing on a cycle other than weekly. Biweekly or monthly filing violates the requirement even when every wage is calculated correctly, and it is one of the easiest violations for a reviewer to spot.
• Skipping no-work weeks. A week with no covered work still needs a certified payroll marked as such; silence reads as a missing report, not an empty one.
• Paying the cash rate and forgetting the fringe benefit. The prevailing wage is the basic rate plus the fringe together, and paying only the cash portion leaves a documented shortfall.
• Letting an apprentice's registration lapse without noticing. Once registration ends, the worker must be paid the full journeyworker rate, and the old apprentice rate on file becomes an underpayment.
• Averaging hours across two labor classifications. Without an accurate daily record of time in each classification, the contractor must pay the highest applicable rate for all hours worked that week.
• Leaving 1099 workers off the certified payroll. Independent contractor status does not exempt a worker performing covered work from the prevailing-wage requirement or the reporting duty.
• Assuming a small subcontract is automatically exempt. Once the prime contract clears the $2,000 threshold, every subcontract under it is covered, regardless of its own size.
• Missing a change in project funding mid-job. A refinancing or a new federal grant added partway through can pull a previously uncovered project under Davis-Bacon retroactively.
• Taking an unapproved payroll deduction. Deductions outside the standard list require a written approval request to the Wage and Hour Division before the contractor can make them.

Do's and Don'ts for Certified Payroll Compliance

A short set of habits separates contractors who stay clean from those who end up rebuilding weeks of records. The difference rarely comes down to knowledge. It comes down to which habits get built into the weekly routine from day one.

Do

• Confirm the wage determination before the first payroll runs, since using an outdated or mismatched determination sets every later report up wrong.
• Track hours by labor classification daily, so a worker moving between tasks in one week is paid the correct blended rate instead of an average.
• Verify apprentice registration status on every pay period, not only once at hiring, because registrations can lapse mid-project.
• File every week, including no-work weeks, using a report marked to show no covered work occurred.
• Keep original certified payrolls for at least three years after project completion, along with the timecards and bank records that support them.
• Ask the funding agency directly when project financing is unclear, especially on renovation, housing, and infrastructure work with layered funding sources.

Don't

• Don't assume private developer involvement means no federal rules apply, since federally insured financing can pull a private project under Davis-Bacon.
• Don't average hours across classifications without a documented daily record; pay the highest rate instead when records are incomplete.
• Don't wait for an audit notice to reconcile timecards against certified payrolls; catch the gap yourself first.
• Don't take a payroll deduction outside the standard list without written approval from the Wage and Hour Division.
• Don't treat a signed Statement of Compliance as a formality; it is a sworn certification, and a false one carries its own legal exposure.
• Don't assume every federal contract needs the same certified payroll form; a service contract under the Service Contract Act follows a different compliance path.

Pros and Cons of Handling Certified Payroll In-House

Contractors weigh whether to run certified payroll through their own office staff or hand it to a payroll provider. The right answer usually depends on how many covered projects the firm juggles at once. A firm with one small covered job has different needs than one running five at a time.

Pros

• Direct control over accuracy, since the person entering hours also knows the crew and the work performed each day.
• No added monthly software or service fee beyond whatever general payroll system the office already runs.
• Faster corrections, because an in-house team can amend a certified payroll the same day an error is caught internally.
• Institutional knowledge builds over time, so the office gets faster and more accurate on each new covered project.
• Direct relationship with the funding agency, without a third party relaying questions back and forth during a review.

Cons

• Staff time adds up fast across multiple concurrent covered projects, especially with several wage determinations to track at once.
• A single point of failure exists if the one employee who understands the requirements leaves or is unavailable during a filing week.
• General payroll software may not flag classification or fringe errors as reliably as a construction-specific certified payroll tool.
• Multi-state work multiplies the burden, since each state's own prevailing-wage program may need separate tracking and separate forms.
• Mistakes are more likely without a dedicated compliance review step, since general office staff rarely specialize in Davis-Bacon rules alone.

What to Do Next

Work through these steps in order any time a new project might be covered by prevailing-wage rules.

1. Confirm the project's funding source in writing: direct federal contract, federally assisted, state-funded, or purely private.
2. If federal or federally assisted, request the applicable wage determination from the contracting agency before pricing labor.
3. Check whether a separate state prevailing-wage law also applies, and identify any state-specific certified payroll form it requires.
4. Set up weekly payroll filing on the project from week one, including a marked report for any no-work week.
5. Verify every worker's classification and any apprentice registration status before the first paycheck goes out.
6. Reconcile timecards, daily reports, and certified payrolls against each other monthly instead of waiting for an external review.
7. Bring in an employment attorney or a certified payroll specialist when a discrepancy, a funding change, or a formal notice appears, since this article is educational and not a substitute for advice on your specific contract.

Frequently Asked Questions

Is certified payroll the same as prevailing wage?

No. Certified payroll is the weekly report proving compliance; prevailing wage is the pay rate the law requires. The report exists only because a prevailing-wage law already covers the project.

Does every federal contract require certified payroll?

No. Only federal or federally assisted construction contracts covered by the Davis-Bacon Act or a Related Act require it, and the prime contract generally has to exceed the $2,000 threshold. A federal service contract follows different rules under the Service Contract Act instead.

What form is used for certified payroll?

Form WH-347 is the Department of Labor's optional standard form, though any format capturing the same required fields and a signed Statement of Compliance is acceptable.

How often must certified payroll be filed?

Weekly. Reports are due within seven days of the regular pay date, and a week with no covered work still needs a report marked as such.

Does a state-funded project ever need certified payroll?

Yes, if the state runs its own prevailing-wage law, often called a "little Davis-Bacon" statute, that covers the project even without any federal money involved. Confirm this with the state department of labor named in the contract.

Are independent contractors exempt from certified payroll?

No. A 1099 worker performing covered construction work must still be paid the prevailing wage and listed on the certified payroll, with a note that no FICA or taxes were withheld.

What happens if certified payroll is filed late?

It can trigger a violation separate from any wage issue, and repeated late filing may lead to withheld contract payments or closer agency scrutiny of the whole project.

Can a contractor be penalized even if wages were paid correctly?

Yes. Filing timing, missing no-work-week reports, and other paperwork failures can be cited on their own, independent of whether each worker was paid the full prevailing wage.

How long must certified payroll records be kept?

Generally at least three years after the project is completed, covering the original certified payrolls along with the timecards and payroll records that support them.

Who is responsible for a subcontractor's certified payroll mistakes?

The prime contractor carries responsibility for collecting and forwarding each sub's certified payroll, and a sub's error can still surface as a problem on the prime's project.

What is the penalty for a certified payroll violation?

It varies by severity, ranging from withheld contract funds and required back pay to contract termination, contractor liability for government costs, and debarment from future federal contracts for up to three years.

Can fringe benefits be paid as cash instead of health insurance?

Yes. Contractors may satisfy the fringe-benefit portion of the prevailing wage entirely in cash, entirely through bona fide benefits like health insurance or retirement contributions, or through a combination of both.