Electronic Certified Payroll Explained

Contractors and subcontractors on covered federal or federally assisted construction work generally submit weekly payroll information and a signed Statement of Compliance. Form WH-347 is an optional format, but the required data and certification still matter. An electronic process can collect worker identity, classification, hours, rates, gross pay, deductions, net pay, fringe-benefit treatment, project details, and week-ending date. The certifying official must have knowledge of the facts, and a legally valid electronic signature needs an identity-verification method. A scanned image of a signature alone does not satisfy the current DOL instruction.

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 contract

Determine the funding, wage determination, clauses, labor standards, state rules, and submitting agency before building the report.

Certified payroll is generally weekly

Each report identifies a specific project and week ending, even when the employer’s normal pay cycle differs.

Classification controls the rate

Hours and pay must be separated when a worker performs more than one covered labor classification.

Fringe benefits require detail

Distinguish cash paid in lieu of fringes from credit for qualifying plans and preserve plan support.

Deductions must be supportable

The report shows deductions and net wages, while the employer retains authorizations and legal support.

Certification carries consequences

The signer should review the payroll facts because the statement is made subject to federal penalties.

Electronic signatures need validation

Use a legally valid process that records acceptance and verifies signer identity.

Step-by-step workflow

1. Read the contract and wage determination. Identify project, location, classifications, rates, fringes, apprentices, and submission rules.
2. Set the workweek and project codes. Align time entry, job costing, payroll, and the required week-ending period.
3. Validate worker setup. Confirm identity, classification, apprenticeship status, rate, fringe treatment, and deductions.
4. Capture daily and weekly hours. Separate regular and overtime hours by project and classification.
5. Reconcile payroll. Tie hours, rates, gross pay, taxes, deductions, fringes, and net pay to the paid payroll register.
6. Generate the electronic report. Populate the required fields in WH-347 or the agency’s accepted equivalent.
7. Review the Statement of Compliance. Confirm wage and fringe compliance, apprentices, deductions, payroll completion, and remarks.
8. Apply a valid electronic signature. Use the authorized signer and preserve identity-verification and timestamp evidence.
9. Submit through the required portal. Use the contracting agency, prime contractor, state, or local workflow stated for the project.
10. Archive and correct. Retain the report, signature, acceptance, source payroll, wage determination, and correction trail.

Worked example

A subcontractor pays every two weeks but works on a covered federal project. Its time system records hours by worker, day, project, and classification. Payroll produces the paid register, while the compliance team creates two weekly certified-payroll reports within the biweekly pay cycle. A knowledgeable official reviews fringe credits and deductions, signs through the accepted identity-verified process, and saves portal receipts for each week.

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

• Treating a payroll export as certification. Include the required statement and authorized signature.
• Using the normal pay period only. Build the required weekly project report.
• Combining classifications. Separate hours and rates when duties differ.
• Assuming base cash rate equals prevailing wage. Review fringe-benefit obligations and cash-in-lieu amounts.
• Using a signature image. Follow the current legal electronic-signature requirements.
• Certifying before wages are paid. Tie the statement to completed payroll.
• Ignoring state prevailing-wage rules. A project can have additional jurisdictional requirements.
• Saving no submission receipt. Retain portal status and correction history.

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

Save contract number, location, funding, wage determination, classifications, rates, fringes, portal, and contacts.

Weekly tie-out

Reconcile time, classifications, rates, gross, fringes, deductions, net, payroll register, and report.

Signer control

Record authority, knowledge review, signature method, identity verification, timestamp, and submission.

Correction log

Preserve the original report, error, source fix, corrected report, certification, 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.