Certified Payroll is GO's prevailing-wage compliance reporting. When a project falls under Davis-Bacon or state prevailing-wage rules, you owe the Department of Labor a weekly certified payroll report — Form WH-347 — listing every worker on the project that week: their classification, hours by day, rates, gross pay, withholdings, net pay, and a signed Statement of Compliance. GO generates that form as a PDF straight from payroll data you've already posted, keeps a register of every report, and stamps each one when you've filed it.
Where to find it
From the left sidebar choose HR & Payroll → Payroll, double-click a payroll run to open its Control Center, and click the Certified Payroll tile (the last tile — "Prevailing-wage WH-347 reporting").
The tile stays gated with "Post payroll first" until the payroll is posted — certified reports are built from posted numbers, never drafts. Once posted, the tile shows how many prevailing-wage projects already have reports on this payroll.
Set up before your first WH-347
Generation pulls everything from data that must already be in place. Work down this list once per prevailing-wage job:
Flag the project as prevailing wage. Open the project → General tab → turn on the Prevailing Wage toggle. GO refuses to generate a WH-347 for any project without it.
Pick the project's Rate Schedule. When the toggle is on, a required Rate Schedule field appears next to it — this is the wage determination that governs the job.
Build the rate schedule with a line for every classification. Rate schedules live at HR & Payroll → Prevailing Wage & Union (see Prevailing Wage & Union). Each line carries a Pay Classification with its base rate, fringe, pension, training, and OT multiplier. Every classification that clocks time on the project needs a line — this is the number-one thing that blocks generation.
Clock time against the project with classifications assigned. The form's daily hours come from clock logs tied to the project and a pay classification.
Have SSNs on employee records — the form prints the last four digits only.
Set up fringe benefit plans if you pay fringes into bona-fide plans rather than cash; active plans drive the form's fringe disclosure section.
Generating a WH-347
In the Certified Payroll Reports workspace, click Generate WH-347 (top right).
| Field | Notes |
|---|---|
| Project | Required. Only prevailing-wage projects will generate — anything else is rejected with a clear error. |
| Week ending | Required. Pick the Saturday that ends the workweek — GO builds the report for Sunday through that Saturday. A mid-week date silently shifts the whole window. |
| Final payroll for this project | Tick on the last report for the job — it's flagged on the form. |
| Certifying person | Required. Who signs the Statement of Compliance. Search any active employee by name or email — including someone who worked on this payroll, so a working owner can sign for themselves. |
| Certifier title | Required. Pre-filled with "Owner" — change it to the signer's real title. |
| Exceptions | Optional free text that prints verbatim in the Statement of Compliance (e.g. an apprentice ratio). |
On success you'll see "WH-347 generated" and the report appears in the register. If a classification with time on the project has no rate-schedule line, generation fails with a message that names the exact classifications missing lines — add those lines to the project's rate schedule and generate again. Nothing partial is saved on a failure.
The report register
Each row is one project + week: the form type (WH-347), worker count, total hours, a Generated (amber) or Submitted (green) status, and when it was generated. Click a row's chevron to expand the per-worker breakdown — name, masked SSN (xxx-xx-1234), classification, and hours for each day split straight/overtime (e.g. 8.00 / 2.00), with weekly totals.
Right-click a row for the actions:
Download WH-347 PDF — the finished Letter-format form, named like
WH-347-1-2026-05-16.pdf.Mark Submitted to DOL — stamps the report as filed and flips the badge to green.
Good to know
"Mark Submitted to DOL" is a bookkeeping stamp, not a filing. GO does not transmit anything to the Department of Labor — you still file through the DOL's own channel, then stamp the report here so the register reflects reality. The stamp is one-way; there's no un-submit.
Regenerating doesn't replace — it adds. Generating again for the same project and week creates report #2, #3, and so on; the register shows the latest. There is no edit or delete on a generated report.
Week ending means Saturday. Worth repeating, because it's silent — and what lands in the week is decided by the local working day, not the clock at head office. Every punch is certified under the working day it happened on where the team was standing: the timezone reported by the device that clocked it, falling back to the business unit's timezone, then UTC. That's the same rule the payroll engine uses to decide which week a punch belongs to, so the WH-347 and the payroll agree. In practice it matters at the edges — an evening punch close to the week boundary certifies under the local day the team worked, not whatever date it was in UTC by then.
Permissions: anyone with payroll view access can open the register and download PDFs; generating and marking submitted require the payroll process permission.
The PDF holds wage data on identifiable people — downloads are authenticated and links are short-lived by design; don't expect a permanent shareable URL.
Rate schedules and classifications are covered in Prevailing Wage & Union and Pay Classifications; the posting flow that must come first is in Payroll.