Certified Payroll: The Complete Guide

On federal Davis-Bacon and Related Acts work, covered contractors and subcontractors generally submit payroll information every week. Form WH-347 is optional, but the required data and a signed Statement of Compliance are not. The report should identify the project, contractor, payroll number, week, workers, classifications, daily and weekly hours, rates, fringe benefits, gross wages, deductions, and net wages. A reliable process begins with the contract and wage determination, follows actual time and paid payroll, and ends with review, certification, delivery, and retained acceptance evidence.

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 before the form

Confirm the funding, contract clauses, prime and subcontract scope, project location, and jurisdiction. Certified payroll may be required by a federal contract, a state prevailing-wage law, an awarding body, or more than one authority.

The wage determination is the rate source

Use the determination and revision incorporated into the contract, then map every worker’s actual duties to an available classification. A payroll system’s job title is not a wage classification.

Weekly reporting follows covered work

Federal certified payroll is organized by seven-day workweeks even when the employer pays biweekly. The reporting week, payroll pay date, and accounting period should remain distinguishable.

Fringe benefits need a calculation trail

Show cash paid instead of fringes and document credit claimed for qualifying benefit plans. Administrative cost, employee deductions, and unsupported benefits should not be treated as automatic fringe credit.

Deductions require support

Taxes, benefits, garnishments, repayments, and other deductions should tie to payroll and be permitted. An unexplained deduction can reduce the worker below the required wage.

WH-347 is optional, not the obligation

A contractor may use another report containing the required information, but the equivalent report and compliance statement must satisfy the governing requirements.

The signer certifies facts

The authorized signer should receive the final payroll tie-out, exception log, wage support, and correction status. A signature is not a routine software click.

Portal acceptance is not wage approval

A report can pass electronic validation while using a wrong classification, rate, fringe credit, or week. Preserve both the technical receipt and substantive review.

Step-by-step workflow

1. Read the contract package. Identify coverage, wage decisions, modifications, reporting instructions, portal, project identifiers, and any awarding-body additions before the first hour is worked.
2. Build the classification matrix. List every expected task, approved classification, base rate, fringe rate, overtime rule, apprentice requirement, and effective date.
3. Configure time collection. Capture worker, date, project, location, classification, regular hours, overtime hours, and supervisor approval at the source.
4. Configure payroll codes. Separate base wages, cash fringes, plan contributions, overtime premiums, deductions, reimbursements, and noncovered work so the report can be reconciled.
5. Close each workweek. Resolve missing time, mixed classifications, rate changes, apprentices, travel, shift differentials, and work outside the covered project.
6. Run and pay payroll. Calculate wages and deductions under the applicable pay schedule, then confirm workers actually received the reported amounts.
7. Prepare the certified record. Populate WH-347 or the required equivalent from approved time and paid payroll, not from estimates or a bid worksheet.
8. Perform a three-way tie-out. Reconcile the report to time records, the payroll register, and payment evidence by worker and week.
9. Review and certify. Provide the signer with the compliance statement, exception report, wage determination, fringe support, and any correction documentation.
10. Submit, monitor, and retain. Save the report, signed statement, portal or delivery receipt, rejection messages, corrected versions, and final acceptance.

Worked example

A carpenter works 24 hours as a carpenter and 16 hours performing laborer duties on a covered project. The contractor records each day’s hours by classification and checks both classifications against the contract wage determination. Payroll applies the correct base and fringe treatment, including overtime based on the full workweek. The certified report shows the split, ties to paid payroll and deductions, and is reviewed with benefit support before the authorized official signs. The team saves the submission receipt and its classification memo.

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 employee job titles. Certified classifications follow covered work and the applicable wage decision, not internal titles.
• Reporting one line for mixed duties. Separate hours by day and classification when workers perform more than one type of covered work.
• Using the bid rate forever. Contract modifications, effective dates, conformance decisions, and local requirements can change the required rate.
• Treating all benefits as fringe credit. Verify plan qualification, funding, allocation, and the portion attributable to covered work.
• Building the report before payroll closes. Certified wages should reflect actual paid payroll and supported corrections.
• Letting software certify. Software organizes data; an authorized person remains responsible for the representation.
• Discarding rejected versions. Keep the original, rejection, correction, resubmission, approval, and any worker repayment 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.

Practical implementation notes

Project control sheet

Track contract number, location, prime, awarding body, wage decision and revision, project registration, reporting portal, workweek, first and last covered dates, and responsible users.

Weekly exception report

Flag missing time, unmatched classifications, below-rate pay, incomplete fringe support, unusual deductions, negative checks, manual checks, and prior-period corrections.

Worker-level evidence

Retain identity support, classification basis, time, payroll detail, payment proof, apprentice records, benefit allocation, and communications about corrections.

Closeout

Confirm final payroll designation, unresolved underpayments, rejected reports, portal acceptance, record retention, and access after the project team disbands.

Deeper planning points

Prime and subcontractor responsibilities

Map who collects, reviews, transmits, and follows up on each tier. A prime contractor may need visibility into subcontractor compliance, but access to a portal does not replace a documented review. Define escalation for missing weeks, rejected files, wage concerns, and late corrections before work begins.

Apprentices

Verify program, registration, ratio, classification, and rate before using apprentice treatment. An employee called an apprentice in the field may not qualify for the reduced rate. Preserve enrollment and ratio support for the specific week and project.

Multiple wage decisions

A project can involve more than one decision or schedule. Tie each scope and location to the incorporated decision, revision, and classification. Record the reasoning so a later reviewer can reproduce the choice.

Overtime

Certified payroll and overtime calculations must use the correct workweek and governing laws. Combine covered and noncovered hours when required, identify cash fringes and base rates correctly, and test whether another federal, state, or contract rule is more protective.

Corrections

Correct payroll and the certified record as a coordinated package. Document the cause, recalculation, employee payment, revised payroll register, tax or deduction effects, resubmission, acceptance, and preventive control.

Security

Certified payroll contains sensitive worker and compensation data. Limit full identifiers, use approved transfer channels, assign individual accounts, review access, and retain redacted public versions separately from complete source records.

Conformance requests

Do not invent a classification when the incorporated wage decision lacks the work. Follow the contracting agency’s conformance process, document the proposed classification and wage relationship, and retain the determination. A temporary payroll code should not become unsupported permanent treatment.

Owner-operators and working owners

Review whether each person performing covered labor must appear and how the governing rules treat that person. Entity ownership or a management title does not automatically remove worker-level reporting, prevailing-wage, time, or classification obligations.

Travel and subsistence

Separate reimbursements from wages and fringe credits. Document policy, receipts, accountable-plan treatment, project requirements, and any state rule. A per diem or vehicle payment should not be used to disguise a shortage in required base wages or fringes.

Union and plan data

Reconcile payroll deductions and employer benefit contributions to the certified fringe treatment. Use contribution reports, eligibility, rates, covered hours, payment evidence, and any annualization calculation so the claimed credit can be reproduced.

Subcontractor monitoring

Use a weekly completeness schedule across every lower tier. Track expected reports, no-work weeks, rejections, underpayment questions, corrected payrolls, and closeout. Escalate late or incomplete reports under the contract process.

Audit response

Assemble a project file before an agency request arrives. Index the contract, wage decisions, time, payroll, payments, fringe support, deductions, certifications, submissions, corrections, and worker communications by week and employee.

New wage revisions

Record when each modification was issued, incorporated, and effective for the contract. Test workers and classifications affected by the change, update configuration prospectively, calculate any correction, and preserve the former rate for earlier weeks.

No-work weeks

Follow the contract or portal rule for weeks without covered labor. Where a nonperformance report is required, label it accurately and keep it in the weekly sequence so a missing report is not mistaken for an unexplained compliance gap.

Project closeout

Do not close after the last normal payroll alone. Resolve late time, retention payments, corrections, fringe contributions, rejected submissions, final-report indicators, access, and record custody before releasing the compliance team.

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.