HAWKEYE SYSTEMS

Certified Payroll Reporting: Field Records Catch Contractor Errors

Learn who signs certified payroll reports, when federal and New York filings are due, and how field records support accurate submissions.

Plan a walkthrough

Certified payroll reporting means filing a project-level payroll record with a signed Statement of Compliance for work covered by prevailing wage law. The exact requirement depends on your contract and jurisdiction, so your first move is confirming which agency, portal, or form applies, then gathering the field and payroll records you will need to support it. Federal guidance like the Department of Labor’s WH-347 instructions and state portals in places like New York and California are the primary references.

TL;DR:

Federal filings are generally due within seven days of payday; New York requires submissions at least every 30 days with weekly wage details.
On federal prevailing wage projects, prime contractors must collect, review, and submit each subcontractor’s payroll, although subcontractors prepare their own records.
The federal template is optional, but covered projects still require weekly certified submissions and a Statement of Compliance signed by an authorized person.
New York submissions cannot be edited after filing, and late reports incur a $100 daily penalty after a grace period of 14 days.
Have someone other than the preparer verify classifications, rates, and totals against field records before an authorized signer certifies the report.

Hefieldops

Keep Field Records Ready for Review

Hefieldops connects field activity with office management, helping teams document site work and integrate records for efficient review and billing.

Visit Hefieldops

What makes certified payroll different from regular payroll
Who signs, who’s responsible, and how often you file
Forms, portals, and file formats you’ll actually encounter
How to prepare and submit a certified payroll without last-minute scrambling
Record retention, inspections, and what late filings cost you
Why accurate field records make certified payroll easier
What payroll teams should prioritize over reactive fixes
Another way to keep field evidence audit-ready
FAQ
Sources

What makes certified payroll different from regular payroll

Regular payroll tracks what you paid your crew. Certified payroll proves it, project by project, with a signed attestation that the figures match prevailing wage law. That attestation, the Statement of Compliance, is what turns a payroll export into a legal document: whoever signs it is certifying under penalty of perjury that classifications, hours, and rates are accurate for that specific contract.

The WH-347 guidance lays out what has to appear on the record for covered federal work. A compliant certified payroll includes:

Each worker’s name and an identifying number (not a full Social Security number on the public copy)
Work classification for every hour worked, since misclassification is one of the most common compliance failures
Daily and weekly hours, split between straight time and overtime
Base wage rate, fringe benefit rate or cash equivalent, and any deductions
Gross pay for the project and net pay after deductions

This structure exists because prevailing wage law only works if someone can check the math after the fact. A certified payroll is the paper trail that lets an agency confirm a worker was paid the determined rate for the classification actually performed, not just a lower one that happened to be cheaper.

Who signs, who’s responsible, and how often you file

Responsibility flows uphill. On Davis-Bacon Related Acts work, the prime contractor is responsible for collecting, reviewing, and submitting certified payrolls for every subcontractor on the job, even though each subcontractor fills out its own. That makes subcontractor oversight a prime contractor problem, not just a subcontractor one.

A few rules to keep straight:

The Statement of Compliance must be signed by someone with authority to attest to its accuracy, typically a payroll manager or principal, not a field supervisor filling in for convenience
Electronic signatures are generally accepted where the portal or contract allows them, but check the specific submission channel’s requirements first
Federal guidance under 29 CFR 3.4 points to a delivery window generally understood as within seven days of the regular payroll payment date
New York’s certified payroll portal runs on a different cadence: contractors report at least every 30 days, but each submission still has to contain weekly wage detail, according to the NYSDOL contractor user guide

These timing differences matter because missing a federal week-by-week expectation while assuming a state’s monthly cadence applies (or the reverse) is a common and avoidable error. Confirm the governing rule before you build your submission calendar.

Forms, portals, and file formats you’ll actually encounter

Your submission channel depends entirely on the funding source and jurisdiction. Three examples cover most of what contractors run into.

Federal WH-347: This form is the standard federal certified payroll template, pairing worker-level payroll data with the Statement of Compliance. The form itself is optional under DOL guidance: you can use another format, but the weekly certified submission and signed certification are mandatory whenever Davis-Bacon or a related act applies.

California DIR: Public works contractors submit through DIR’s Public Works Website Services using the structure referenced in Form A-1-131. The certification language carries the same weight as a federal one: a statement made under penalty of perjury, according to California DIR’s certified payroll guidance, and a public entity can require a stricter format than the state minimum.

New York State: New York’s portal requires electronic submission and upfront project setup, including your FEIN, Prevailing Rate Case (PRC) number, and contractor registration details. For firms running high volumes, the state provides XML bulk-upload templates with XSD guidance rather than requiring manual entry for every record, per the NYSDOL user guide.

A detail worth flagging: once a New York submission goes in, the portal does not allow edits, according to the same NYSDOL guidance, which means your internal review has to happen before you hit submit, not after.

A few shared practicalities across jurisdictions:

Confirm whether your contract requires the state’s own form or simply the same data in an alternative layout
If you use payroll software like QuickBooks to generate source data, verify the export maps to every required field before treating it as a finished certified payroll
Test bulk upload templates against the published XSD before your first real submission
Keep a copy of every confirmation receipt, since some portals do not resend them automatically

How to prepare and submit a certified payroll without last-minute scrambling

A certified payroll is only as good as the records behind it. This sequence works across most jurisdictions, with adjustments for the specific portal or form you use.

Pull source data first. Collect time records, sign-ins, field tickets, and project assignments that tie each worker to a specific classification and project.
Reconcile hours against the payroll journal. Match straight time, overtime, and fringe credits between field records and what payroll actually processed.
Assemble supporting documentation. Gather fringe-benefit plan documents or invoices, apprentice program registration, and explanations for any deductions beyond standard withholding.
Run a pre-certification review. Someone other than the preparer should check classifications, rates, and totals before anyone signs.
Route for sign-off. The Statement of Compliance needs a signature from someone authorized to attest to its accuracy, not whoever happens to be available.
Submit through the designated channel. Use the correct portal, form, or upload template for the contract’s jurisdiction.
Save your confirmation and retain records. Keep the submission receipt and the underlying documentation in case of inspection.

Pro Tip: Build your pre-certification review into the payroll calendar as a fixed step, not an optional one; skipping it under deadline pressure is how classification errors make it into a signed document.

DOL training materials point to the same recurring failure points across many contractors: misclassification, unpaid overtime, missing apprentice documentation, and recordkeeping gaps, according to DOL’s certified payroll guidance for contractors. Reconciliation before signature catches most of these before they become a problem.

Record retention, inspections, and what late filings cost you

Federal rules require certified payrolls and supporting records be preserved, with agencies generally expected to retain them for three years after contract completion under 29 CFR 3.4. Inspectors typically ask for the certified payrolls themselves, fringe benefit documentation, apprentice program records, and daily field logs that corroborate the hours reported.

Penalties for errors or delays vary by jurisdiction, so check your specific contract’s terms:

New York’s certified payroll portal applies a $100 per day penalty after a 14-day grace period for late submissions, per the NYSDOL contractor user guide
Willful inaccuracies in a signed Statement of Compliance carry consequences beyond a late fee, since the certification is made under penalty of perjury in most jurisdictions

Treating retention as an ongoing habit rather than a year-end scramble makes an inspection request far less disruptive.

Why accurate field records make certified payroll easier

Most certified payroll errors start in the field, not in payroll. A worker logged under the wrong classification, hours recorded inconsistently between a paper sheet and a time clock, or a missing signature on a field ticket all surface later as reconciliation headaches.

Time-stamped field records close that gap before it opens. Daily work logs, digital crew assignments, and mobile site documentation give payroll teams a verifiable source to check against, instead of reconstructing a week from memory or a supervisor’s notes. The types of field evidence that matter most for reducing certified payroll risk include:

Time-stamped crew assignments tied to a specific project and classification
Daily task logs that corroborate hours and work type
Site photos or video documenting work performed on a given day
Digital signatures on field tickets confirming who was on site and when

Pro Tip: Treat field evidence as part of your payroll file, not a separate record; when the two live together, reconciliation takes minutes instead of days.

What payroll teams should prioritize over reactive fixes

The instinct after a failed audit is to tighten the paperwork. The better fix is earlier: build an internal approval step that reconciles field records to payroll before anyone signs the Statement of Compliance, so errors get caught before they become a signed, perjury-level claim.

Classification accuracy and fringe documentation deserve more attention than most payroll calendars give them, since they are the two areas DOL training materials flag most often as recurring failure points. And if you’re a prime contractor, put subcontractor payroll evidence requirements directly into your contracts. You carry the compliance exposure for their records, so you need the same visibility into their field data that you have into your own.

— Client

Another way to keep field evidence audit-ready

Certified payroll depends on field data matching payroll data, and that match is hardest to prove when crew assignments, hours, and site activity live in scattered logs and paper tickets. We built Hawkeye Field Ops to close that gap: time-stamped crew assignments, digital field tickets, and mobile site evidence that reconcile directly to payroll, so your certification step starts from a record you can already trust.

For teams managing remote or multi-site crews, we also offer Hawkeye Workforce Readiness to track training and classification records alongside field activity, and Hawkeye Security for site-level monitoring that adds another layer of documented evidence. Our approach centers on:

Capturing field activity at the moment it happens, not reconstructing it later
Keeping crew assignments, classifications, and site evidence in one connected record
Making the reconciliation step between field and payroll faster to complete and easier to defend

See how Hawkeye Field Ops fits your certified payroll workflow and request a walkthrough today.

This article is general information, not a substitute for advice from a qualified lawyer. Consult a qualified legal professional about your own circumstances before acting on anything here.

FAQ

What is a certified payroll report?

A certified payroll report is a project-level payroll record, usually filed weekly, that lists each worker’s classification, hours, wage rate, fringe benefits, and deductions for prevailing wage work. It includes a signed Statement of Compliance attesting the figures are accurate, as outlined in DOL’s WH-347 guidance.

Can QuickBooks do certified payroll?

QuickBooks and similar payroll platforms can supply the underlying wage and hour data used in a certified payroll, but they don’t automatically produce a compliant submission on their own. You still need to confirm the export matches every required field and pairs with a signed Statement of Compliance before it counts as certified.

How do I get certified payroll set up for my contracts?

Start by confirming which agency, form, and portal apply to your contract, since requirements differ by jurisdiction, from federal WH-347 submissions to state systems like California’s DIR portal or New York’s certified payroll system. From there, build a weekly process that reconciles field records to payroll data before anyone signs the required certification.

What is the difference between certified payroll and regular payroll reporting?

Regular payroll reporting tracks pay for internal and tax purposes without a legal attestation tied to a specific public contract. Certified payroll adds project-level classification detail and a signed Statement of Compliance confirming the figures meet prevailing wage requirements for that job.

Sources

See your operations in action.

Walk through the handoffs that slow your team down—and see where a connected record can help.