Prevailing Wage and Certified Payroll Explained

On covered federal or federally assisted construction, contractors and subcontractors generally must pay laborers and mechanics at least the applicable Davis-Bacon wage rates and fringe benefits and submit weekly payroll information. Form WH-347 is an optional federal format, but the required data and signed Statement of Compliance remain mandatory under the contract clauses. Each worker’s classification, daily and weekly hours, rates, gross pay, deductions, net wages, and fringe treatment must trace to paid payroll. State or local prevailing-wage laws can add classifications, rates, portals, deadlines, or record rules.

This guide is part of Steady’s Payroll, W-2 & 1099 library. It explains the federal workflow in practical terms, but the correct result still depends on the payment year, entity, worker relationship, filing method, and state rules.

The answer in context

Coverage comes from the project

Funding, contract clauses, location, agency, work, and jurisdiction determine whether prevailing-wage requirements apply.

The wage determination is specific

Use the applicable decision, construction type, county, modification, effective date, and incorporated contract terms.

Classification follows work performed

A job title alone does not control. Split hours when an employee performs duties in more than one covered classification.

Fringes are part of compensation

The obligation may be met with qualifying plan contributions, reasonably anticipated costs, cash in lieu, or a permitted combination.

Certified payroll is weekly

The report covers a stated workweek and project even when the company’s normal payroll cycle is biweekly or semimonthly.

Deductions need support

Payroll taxes, benefits, garnishments, and other deductions must be lawful, accurate, and traceable to the paid register.

Certification is a human responsibility

The authorized signer must know the facts represented. A legally valid electronic signature requires acceptance and identity verification.

Step-by-step workflow

1. Read the contract. Identify coverage, agency, project number, location, prime contractor, submission channel, and special clauses.
2. Lock the wage determination. Record the decision, modification, construction type, county, classifications, base rates, fringes, and effective dates.
3. Map the workforce. Document worker identity, duties, classification, apprenticeship status, project, and supervisor.
4. Capture daily time. Separate hours by date, project, classification, regular or overtime status, and noncovered work.
5. Configure pay and fringes. Set base rates, overtime, plan credits, cash in lieu, deductions, and effective dates.
6. Run and reconcile payroll. Tie time to gross wages, fringes, deductions, net pay, payment evidence, and the general ledger.
7. Prepare weekly reports. Populate the required worker, hour, rate, gross, deduction, net, project, and week-ending data.
8. Review and certify. Resolve exceptions and obtain the authorized signer’s valid signature on the compliance statement.
9. Submit and retain. Save the report, statement, portal receipt, wage determination, payroll, fringe support, and correction history.

Worked example

An electrician performs 30 hours of electrical work and 10 hours of lower-paid laborer work on a covered project. The contractor records the hours by day and classification, checks whether the wage determination and contract permit the classifications, calculates overtime under the applicable rule, and supports fringe credits with plan records. The weekly certified payroll ties to the paid payroll register. The signer reviews the split and submission evidence before certifying.

The example is intentionally a workflow illustration, not a conclusion for every taxpayer. A strong file connects each number on the return to a source report and records why an exception, exclusion, or classification was applied.

Records to keep

Keep the source form or worksheet, contracts or engagement records, payer and recipient identity support, the detailed payment or payroll ledger, bank and processor reconciliation, calculations, correspondence about corrections, filed copies, recipient-delivery evidence, and federal and state acceptance confirmations. Store the records by tax year and keep superseded versions when they explain a correction.

A reviewer should be able to begin with the final reported amount and trace it back to transactions without rebuilding the year. Add a short review memo for judgments such as worker status, corporate exemption, payment-method exclusion, state filing, or unusual timing. That memo is often more useful than another unlabeled spreadsheet.

Common mistakes

• Using the company job title. Match actual covered duties to the wage determination.
• Blending classifications. Separate hours and rates when workers perform different covered work.
• Treating base rate as the whole obligation. Include required fringe benefits or qualifying cash in lieu.
• Reporting the pay period instead of the workweek. Build the required weekly project report.
• Generating before payroll is paid. Tie the certification to completed wage payment.
• Using unsupported fringe credits. Retain plan eligibility, contributions, funding, and allocation support.
• Letting software certify. An authorized knowledgeable person must review and sign.
• Ignoring state overlays. Check state, local, agency, and project-specific requirements.

Final review before filing

Confirm the form and revision year, taxpayer identities, dollar fields, payment categories, withholding, filing channel, recipient statement, state obligations, due dates, and approval. Compare the final output with the source reconciliation rather than reviewing the form in isolation. If software recalculates an amount after an edit, rerun the tie-out.

Keep preparation, filing, and acceptance as three separate statuses. A draft can be complete but unfiled; a transmission can be sent but rejected; a federal return can be accepted while a state return is still missing. This status discipline prevents a polished PDF from being mistaken for finished compliance work.

How to handle a discrepancy

When a source form, ledger, payroll report, or software preview disagrees with another record, stop before filing and identify which amount represents the underlying transactions. Trace the difference by vendor or employee, date, invoice or payroll run, payment channel, and account. Common causes include a payment posted to the wrong year, a void recorded after a report was generated, a card payment included with checks, a duplicate import, an incorrect taxpayer name, or a late adjustment. Record the explanation and the correcting entry or form request.

Do not erase the trail by overwriting the original report. Save the first version, the reconciliation, the corrected version, and the approval. If a third party supplied an incorrect information return, request a formal correction and retain the correspondence. If a return was already transmitted, use the current correction procedure for that form and channel. A corrected recipient copy without a corresponding agency correction can leave the records inconsistent.

Federal filing is only one layer

Federal acceptance does not settle state or local obligations. A state may use a different threshold, worker test, filing portal, account number, transmittal, or due date. Some states receive eligible information through a combined program, while others require a direct submission. Verify the jurisdictions connected with the payer, recipient, employee, work location, withholding, and business activity. Save state confirmations separately so they are not hidden behind the federal acceptance.

Make next year easier

Turn the year-end work into a monthly control. Collect identity forms during onboarding, code payment methods consistently, reconcile payroll and vendor activity each month, and flag vendors or income streams that need special treatment. Schedule a fall review of missing forms, classification questions, state registrations, and electronic-filing access. By year-end, the team should be validating a maintained file instead of reconstructing twelve months of transactions under a deadline.

Assign one owner and one reviewer to the calendar. The owner prepares the source schedule and resolves open items; the reviewer tests identities, totals, rule references, filing status, and evidence. Record the date of the official guidance used because form pages and software menus can change during the filing season. If a rule is uncertain, document the question and escalate it before the deadline rather than placing an unsupported assumption in the final file. This short control list protects both accuracy and continuity when another bookkeeper, payroll specialist, or tax preparer takes over the work. Save the checklist with the return so next year’s team can see which controls were completed and which exceptions required follow-up.

Practical implementation notes

Project profile

Record coverage, contract, location, agency, determination, modifications, portal, contacts, and retention period.

Classification matrix

Map tasks, classifications, base rates, fringes, apprentices, overtime, and effective dates.

Weekly tie-out

Reconcile time, payroll, fringes, deductions, net wages, report, signature, and submission.

Exception log

Track missing time, rate shortages, fringe issues, deductions, rejects, corrections, and restitution.

For the next layer of context, see this related guide, the companion reporting article, and the connected workflow.

If the form, books, and filing status do not agree, Steady can help reconcile the source data and prepare a clean filing package through its specialist service.