Certified Payroll for Construction Projects

For federal Davis-Bacon and Related Acts work, covered contractors and subcontractors generally submit weekly payroll information. Use of Form WH-347 itself is optional, but the required payroll data and signed Statement of Compliance are not. The statement confirms the record is complete and accurate and that covered laborers and mechanics received at least the applicable prevailing wage and fringe benefits. State and local public-works systems can impose different portals, formats, identifiers, deadlines, and stricter requirements. A construction company therefore needs a project-specific control file linking the contract, wage determination and modifications, worker classification, apprenticeship facts, daily time, full workweek overtime, fringe plan, deductions, payroll register, payment evidence, submission, and corrections.

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

The contract defines coverage

Identify funding, agency clauses, project, prime and subcontract scope, and reporting recipient.

Classification follows duties

Map work actually performed, including split classifications within a week.

Daily time supports weekly totals

Preserve project, date, task, straight time, overtime, and noncovered work.

The full workweek affects overtime

Do not calculate overtime only within one project.

Fringe credit needs plan evidence

Tie cash in lieu and bona fide plan credits to eligibility, hours, cost, and funding.

Deductions require support

Maintain authorization and legal basis for every amount reducing gross pay.

WH-347 is a useful format

Alternative records must still contain required data and identical compliance language where applicable.

Submission does not cure underpayment

Correct wages, payroll, records, certification, and portal data formally.

Step-by-step workflow

1. Read the contract. Identify coverage, wage determinations, modifications, agency contacts, format, and deadline.
2. Create the project roster. List legal employer, workers, classifications, apprentices, identifiers, and work locations.
3. Capture daily time. Allocate hours by date, project, classification, shift, straight time, and overtime.
4. Apply current rates. Use the correct determination, effective modification, base rate, fringe, and overtime rule.
5. Calculate payroll. Reconcile gross wages, fringe treatment, deductions, taxes, net pay, and payment date.
6. Prepare certified data. Complete WH-347 or the required equivalent and identify final or no-work weeks correctly.
7. Review the Statement of Compliance. Confirm signer authority, full payment, permissible deductions, apprenticeship, and fringe statements.
8. Submit to the right recipient. Follow federal agency, awarding body, prime contractor, state portal, or local instructions.
9. Resolve discrepancies. Calculate shortages, pay workers, preserve the original, revise records, and resubmit.
10. Archive by project and week. Keep time, payroll, determinations, fringes, statements, transmission, acceptance, and corrections.

Worked example

A subcontractor has an electrician who also performs lower-paid laborer work during a covered week. The timecard separates daily duties and projects. Payroll applies each applicable classification and evaluates overtime using the full workweek. The fringe workpaper distinguishes funded benefits and cash in lieu. The certifying official reviews the final paid payroll, signs the compliance statement, and submits the required weekly record. When a wage modification was missed, the company calculates and pays the shortage before filing a corrected record.

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 an internal job title. Apply the contract classification for work performed.
• Reporting only total weekly hours. Maintain required daily and classification detail.
• Calculating overtime by project. Review the full workweek.
• Claiming unsupported fringe credit. Tie each credit to a bona fide plan and eligible cost.
• Certifying before workers are paid. Use actual final payroll.
• Using a scanned signature when not permitted. Follow current legal electronic-signature requirements.
• Treating WH-347 as universally mandatory. The data and statement may be mandatory even when the form is optional.
• Overwriting corrections. Preserve original and corrected evidence.

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 setup sheet

Record contract, funding, agency, determination, modifications, contacts, format, and due dates.

Classification matrix

Link actual duties to rates, fringes, apprentices, shifts, zones, and effective dates.

Weekly tie-out

Reconcile time, gross, fringes, deductions, net, payments, certified totals, and submission.

Correction log

Track worker, week, cause, shortage, payment, revised statement, transmission, and acceptance.

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.