The WH-347 is a standardized form. Fill it out correctly, sign the Statement of Compliance, submit on time, and you have satisfied a concrete federal reporting obligation under the Davis-Bacon and Related Acts. That sounds straightforward, but the form has twelve columns, a back-page statement that carries legal certification weight, and dependencies on your wage determination, your fringe benefit plan, and your employee classification records. Errors compound quietly, often for months, before a WHD investigator requests your payroll records and the scope of the problem becomes visible.
The five errors below are not edge cases. They appear in DOL Wage and Hour audit findings with enough regularity that they should be on your standing pre-submission checklist every pay period. Each one has a specific reason it triggers scrutiny beyond the surface-level description, and understanding the mechanism helps payroll teams build better checks rather than just adding more manual review steps.
Error 1: Fringe Benefit Column Does Not Break Out Plan Contributions vs. Cash in Lieu
Column 6 of the WH-347 captures fringe benefits. The form instructions require you to indicate, for each employee, how much of the fringe obligation is being satisfied by contributions to a qualifying benefit plan and how much is being paid as cash in lieu of fringe. Many payroll teams fill in a single combined number. That combined number may be mathematically correct, but it obscures whether the plan-cost component actually meets the H&W floor on its own or whether the cash-in-lieu component is properly calculated and included in gross wages.
When an auditor sees an undifferentiated fringe figure, they cannot verify compliance from the WH-347 alone. They will request your benefit plan cost documentation, your contribution schedules, and your per-employee H&W calculation worksheets. That document request is the beginning of a full compliance review, not a quick data pull. Breaking out Plan vs. Cash in column 6 is not extra work; it is the data auditors need to close a review without expanding it.
Error 2: Employee Classification Does Not Match the Wage Determination
The SCA Directory of Occupations (DOO) and Davis-Bacon wage determinations each define occupational categories with specific duties. The classification you assign to an employee on the WH-347 determines the minimum wage rate that applies. Using a classification that does not match the actual duties the employee performs, or using a generic classification because it is easier to maintain, is one of the most common underpayment mechanisms auditors find.
A concrete pattern: a federal IT support contractor classifies help desk analysts under a broad "Clerical/Administrative" category when the applicable wage determination has a specific "Computer Operator" or "IT Technician" classification at a higher wage rate. The employee receives the clerical rate. The WH-347 reports that rate. An auditor cross-referencing the classification against the WD finds the mismatch and triggers a back-wage calculation covering the full period of incorrect classification.
Classification errors are difficult to catch during a payroll run because the error is in the setup, not the calculation. The calculation is correct given the wrong input. This is why classification audits need to happen at contract start and at each wage determination revision, not just during a complaint investigation.
Error 3: Deductions Are Listed Incorrectly or Without Required Consent Documentation
Column 9 of the WH-347 records deductions. The Davis-Bacon Act and its implementing regulations at 29 CFR Part 3 (the Copeland Anti-Kickback Act regulations) impose strict requirements on what deductions are permissible. Permissible deductions include taxes, FICA, voluntary benefit contributions, and certain court-ordered deductions. Deductions for tools, uniforms, transportation, or other business expenses are generally not permissible unless specific conditions are met.
Errors appear in two forms. First, payroll teams sometimes include deductions that are not legally permissible under Copeland, either because the policy predates the contract or because the HR system applies standard deduction rules without a Davis-Bacon filter. Second, even for permissible voluntary deductions like health insurance premium contributions, the authorization must be documented in writing and the deduction must be genuinely voluntary. An auditor who requests deduction authorization records and finds unsigned or backdated forms will treat that as a potential Copeland violation, which carries consequences separate from the wage-rate findings.
Error 4: Contractor or Subcontractor Identification Is Incomplete
The header section of the WH-347 requires the full legal name of the contractor or subcontractor, the employer identification number (EIN), the contract number, and the project name and location. These seem like administrative fields, but incomplete header information is one of the first flags a DOL auditor looks for when assessing whether certified payroll records are reliable.
The problem is most acute in subcontractor situations. A prime contractor's payroll team may submit their own WH-347s correctly but not track whether each tier of subcontractors is submitting certified payroll with complete and accurate header information. Under Davis-Bacon, prime contractors are responsible for the compliance of their subcontractors. If a WHD investigation finds that sub-tier certified payrolls are missing EINs, using the wrong contract number, or omitting a tier of the subcontract chain, the prime's compliance exposure extends to those records.
We are not saying primes are responsible for auditing every subcontractor's internal payroll practices. But the prime is responsible for collecting certified payrolls from subs and reviewing them for completeness before incorporating them into the project's compliance record. That review is a contractual obligation under standard Davis-Bacon prime contract clauses, not just a best practice.
Error 5: Statement of Compliance Signed by Someone Without Actual Knowledge of Payroll Facts
The back page of the WH-347 contains the Statement of Compliance. The person signing it is certifying, under the penalties of 18 U.S.C. 1001 (false statements to the federal government), that the payroll information is correct and complete, that each employee has been paid at least the required wage rates, and that the required fringe benefits have been provided or a cash equivalent paid. This is a federal criminal certification, not an administrative sign-off.
A common operational practice that creates legal risk: the WH-347 is signed by an administrative assistant or payroll processor who does not independently verify the underlying data and has not been given the authority or training to make the statutory certification. If an audit finds errors in the payroll records and the signatory cannot explain how they verified the information before signing, the DOL investigator may conclude that the certification was false, which escalates from a civil back-wage finding to a potential criminal referral.
The person signing the WH-347 Statement of Compliance should have direct access to and responsibility for the wage rate calculations, the fringe benefit records, and the deduction documentation. That does not mean a senior executive needs to sign every form. It means the designated signer has the knowledge and the documentation to support the certification if questioned.
Building Checks That Actually Catch These Errors
Most of these errors are detectable before submission if you have a pre-submission checklist that is tied to the underlying data sources rather than to a visual inspection of the completed form. Visual inspection of a WH-347 catches formatting problems; it does not catch a wage rate that is $0.30 below the WD minimum if you are not cross-referencing the rate against the current WD while reviewing the form.
At CVRD Health, the checks we build into our workflow are specifically designed to flag these five categories before the payroll run closes. The fringe column breakdown is generated from plan contribution data vs. H&W floor comparison. The classification field is cross-referenced against the applicable WD occupation list. Deductions are flagged if they fall into categories requiring Copeland documentation. Header fields are auto-populated from contract records. And the Statement of Compliance routing goes to the designated signatory with the supporting data attached, not just the form.
That is not a comprehensive quality control framework on its own. Audits catch things that pre-submission checks miss. But catching these five error categories before submission is the baseline, and building the checks into the data workflow rather than relying on manual review is the only approach that holds up as contract volume grows.