Certified Payroll Sheet: Fields and Review Steps

The sheet should identify the contractor, project or contract, payroll number, week ending, worker, permitted identifying number, classification, daily and weekly hours, pay rate, fringe treatment, gross wages, deductions, and net wages. It should also support the Statement of Compliance that accompanies the certified payroll. Form WH-347 is optional, but covered contractors still provide the required information and certification. The sheet must map work actually performed to the applicable wage determination and preserve enough detail to calculate overtime, fringes, deductions, 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

One row can hide changing work

Use enough detail to separate project, date, and classification when a worker performs more than one type of covered work.

The wage determination is the rate source

Internal titles and standard payroll rates do not replace the applicable classification and fringe requirement.

Daily hours matter

Weekly totals alone can conceal overtime, project allocation, and classification changes.

Fringes need components

Show funded bona fide benefits and cash in lieu with supporting plan and payment records.

Deductions require authorization

Reconcile each deduction to payroll and applicable law before certification.

Worker identifiers must be protected

Use the allowed abbreviated identifier and secure access to the source identity records.

The sheet must tie to actual pay

Gross and net amounts should agree to the final payroll register and payment evidence.

Corrections need version control

Preserve the original submission, revised sheet, added wages or benefits, payment, reason, and recertification.

Step-by-step workflow

1. Record project setup. Capture contract number, wage determination and modifications, covered location, reporting recipient, deadline, and payroll week.
2. Import employee identity safely. Use legal name and permitted identifier without exposing full sensitive data in shared spreadsheets.
3. Load daily time. Record date, project, work performed, classification, straight hours, and overtime hours.
4. Apply wage rates. Compare regular and overtime pay with the wage determination, contract, state rule, and any higher company rate.
5. Calculate fringes. Tie benefit credits and cash in lieu to eligible hours, plan terms, funding, and worker eligibility.
6. Reconcile deductions. Match taxes and other deductions to the payroll register and authorized records.
7. Calculate gross and net wages. Tie the sheet to the employee’s full weekly payroll, including work on other projects when required.
8. Review exceptions. Flag missing time, unmatched classifications, rate changes, apprentices, negative amounts, and underpayments.
9. Prepare the certified submission. Transfer or export the reviewed data to WH-347 or the required equivalent and complete the Statement of Compliance.
10. Archive submission evidence. Keep the sheet, source time, payroll, benefits, corrections, signature, portal receipt, and acceptance.

Worked example

A worker spends 18 hours as a carpenter and 22 hours as a laborer on one covered project. A one-line weekly spreadsheet showing 40 laborer hours is not adequate. The reviewed sheet separates daily hours and classifications, applies each required base and fringe rate, calculates overtime using the full workweek, ties deductions and net pay to payroll, and feeds the certified submission. The signer receives the exception report and wage support before signing.

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 a generic template without the contract. Project number, wage determination, classifications, and recipient rules must be configured.
• Reporting only weekly totals. Daily and classification detail can be necessary.
• Treating Excel formulas as legal conclusions. Rates, fringes, deductions, and coverage require source review.
• Displaying full Social Security numbers. Protect identity data and use the permitted reporting format.
• Certifying estimated payroll. Use final wages paid and supported benefit information.
• Overwriting a prior submission. Maintain a traceable correction history.
• Ignoring nonproject hours. The full workweek can affect overtime and payroll reconciliation.

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

Locked inputs

Separate source inputs, protected rate tables, calculations, exception fields, review approval, and export tabs.

Control totals

Reconcile employee count, total hours, gross wages, deductions, net pay, fringes, and project totals to payroll.

Change log

Record who changed a rate, classification, time entry, formula, or submitted value and why.

Signer dashboard

Summarize missing support, rate exceptions, apprentice ratios, shortages, corrections, and tie-out status.

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.