Published June 8, 2026 · Variant B · Not legal, tax, or compliance advice
Does each Friday feel like a fresh hit of WH-347 paperwork? You are not alone. Covered construction contracts often require weekly payroll reporting to show that workers received the required Davis-Bacon or prevailing wage.
For many small contractors, that means taking QuickBooks, payroll provider, or timecard data and forcing it into a spreadsheet that looks enough like WH-347 to submit. It works for a while. Then one changed rate, one split classification, or one rejected payroll turns the spreadsheet into the bottleneck.
Certified payroll 101
WH-347 is a standard certified payroll report format used for covered federal or federally assisted construction projects under the Davis-Bacon Act and its related acts. Each week, the report lists employees, classifications, hours, wage rates, gross wages, deductions, fringe information, and net pay.
The specific rates workers must be paid are set in the wage determination for your project — look for it attached to your contract, or look it up on SAM.gov. Rates vary by trade and location, and they can change when a contract is modified.
The report is not only a data table. It is tied to a Statement of Compliance, where an authorized signer — typically an owner, officer, or someone expressly authorized in writing — certifies under penalty of law that the payroll is accurate and workers were paid at least the required rates. That is why a "close enough" spreadsheet is not a great long-term system.
Filing responsibility: prime contractors must submit their own certified payroll and collect certified payroll from every subcontractor. Subs submit to the prime; the prime forwards records to the contracting agency. Certified payroll must be submitted within 7 days of the close of the payroll period, and records must be kept for 3 years after contract completion.
When Excel templates are good enough
Excel is familiar, cheap, and flexible. A WH-347 spreadsheet template can be good enough when your payroll is routine.
- Single job, small crew: one covered project and a handful of workers.
- One pay rate per worker: no classification changes in the same week.
- No overtime or simple overtime: no unusual split across projects or classifications.
- Stable fringes: fringe benefits are consistent and easy to calculate.
- One responsible person: one payroll admin owns the workbook and knows how it works.
In that situation, a spreadsheet may be faster than typing into a PDF. But the moment the process depends on remembering exceptions, Excel starts costing you attention every week.
When spreadsheets fail
Real payroll breaks the clean template. These are the failure modes that create the weekly headache.
Multiple roles and classifications
Picture a worker who spends part of the week in one classification and part in another. A basic template may show the total hours correctly but fail to split the hours into the right rows. That can create wage-rate errors and correction requests.
Overtime confusion
Overtime is not just a total-hours column. If a worker splits time across projects, classifications, or covered and non-covered work, the spreadsheet needs enough structure to explain where overtime belongs.
Fringe benefit math
If you pay fringes through a plan, in cash, or through a combination of both, the workbook needs to keep those values separate. Old formulas and copied tabs are where fringe mistakes often hide.
Human error accumulates
Every copy-paste step creates a chance to overwrite a formula, reuse an old rate, miss a new hire, or paste a deduction into the wrong row. A spreadsheet will not warn you unless you built the warning yourself.
Corrections and versioning
Once a payroll is rejected, the admin has to find the file, identify the mistake, update the row, and resubmit. If the process runs through email attachments and renamed Excel files, nobody has a clean audit trail.
Can Excel be fixed?
Sometimes. Before replacing Excel entirely, contractors usually try one of three fixes.
- Multiple sheets: one tab per week or project. This keeps headers reusable but makes cross-project review harder.
- Pivot tables and exports: useful if someone technical owns the setup, fragile if nobody understands it later.
- Pre-submit checks: a checklist helps catch obvious mistakes before upload or email submission.
These fixes buy time. They do not remove the underlying weekly review burden.
WH-347 pre-submit checklist
Before submitting from Excel, run through these checks.
- All employees accounted for: no covered worker from payroll is missing.
- Classifications matched: split-classification work is shown in the right rows.
- Wage rates updated: rates match the applicable wage determination (find yours on SAM.gov or in your contract) and have not been superseded by a contract modification.
- Hours totals correct: daily hours, weekly totals, and payroll-system totals agree.
- Overtime split: overtime is reported in the right place and paid at the right rate.
- Fringes match payroll: cash fringe and benefit contributions are not mixed together accidentally.
- Deductions and net pay reconcile: deductions plus net pay line up with gross pay.
- Project and week are correct: repeat files often fail because the header was not updated.
Signs it is time to upgrade
If any of these sound familiar, the spreadsheet is probably no longer the right system.
- Your payroll report has been rejected for correction.
- You added extra columns and formulas to handle edge cases.
- Certified payroll consumes a half day every week.
- You are starting more public projects or adding more workers.
- QuickBooks handles payroll but not the prevailing wage reporting details cleanly.
FAQ
Where can I get a WH-347 Excel template?
Many contractors build one internally. There is no official Excel version — the DOL publishes WH-347 as a fillable PDF. If you use a spreadsheet, confirm it captures all required fields and matches the current wage determination for your specific project before filing.
Can Excel handle DIR or LCPtracker filings?
Excel can prepare data, but portals may require separate entry, uploads, or additional project-specific fields. Treat Excel as preparation, not automatic filing.
What if we use QuickBooks?
QuickBooks handles standard payroll but does not know about wage determinations, Davis-Bacon trade classifications, or fringe benefit calculations. Most contractors who use QuickBooks still need a separate step to map each worker to the correct classification, verify the required prevailing wage rate, and produce WH-347-formatted output. That gap — between what QuickBooks exports and what the contract requires — is where classification and fringe errors accumulate.