Can a general contractor withhold payment for missing certified payroll?

On federally funded work, the agency may suspend further payment when required records are missing, and the prime is responsible for its subcontractors’ certified payrolls (29 CFR 5.5). That gives the GC a reason to make each week a condition of a sub’s pay app. What this subcontract allows the GC to hold, and what notice it owes, is a question for the shop’s construction attorney.

How often does certified payroll have to be submitted?

Weekly, for each week in which covered work is performed, under 29 CFR 5.5(a)(3)(ii)(A). The Copeland Act regulations set the delivery at within 7 days after the regular payment date of the payroll period (29 CFR 3.4). A GC can set an earlier internal date in the subcontract.

Is Form WH-347 required?

No. The Department of Labor describes WH-347 as optional: the payroll information can be submitted in any format, but it must be submitted weekly and carry the signed Statement of Compliance, which the back of WH-347 provides.

Do certified payrolls need workers’ full Social Security numbers?

Not on the weekly transmittal. 29 CFR 5.5(a)(3)(ii)(B) says full Social Security numbers and home addresses must not be included; an individually identifying number such as the last four digits is enough. A prime contractor may still ask a subcontractor for full details for its own records.

What if no covered work was done in a given week?

The federal clause ties the weekly submission to weeks in which covered work is performed. Some agencies and GCs ask for a “no work performed” report for idle weeks on an active job; the subcontract or the portal’s instructions say which, so ask the GC in writing at the start of the job.

Do these rules apply to state prevailing-wage jobs?

Not directly. The rules here are federal and apply to Davis-Bacon and Related Acts work. State prevailing-wage programs set their own reporting format, deadlines and penalties, so read the contract and the state labor agency’s requirements for each state job.

Answers · Electrical contractors

Certified Payroll Holding Up Payment: The Weekly Report That Can Stop a Pay App

When certified payroll is holding up payment on a prevailing-wage job, the cause is a week the GC or the agency does not have — missing, late or rejected — and the fix is a weekly routine with one owner and one due date per job rather than new software. On federally funded construction, the rules require a certified payroll for every week covered work is performed, make the prime contractor responsible for getting every subcontractor’s payrolls in, and let the agency suspend further payment when required records are missing. So a general contractor can stop an electrical subcontractor’s pay app over a single week, and the pay app that rolls costs the shop a month of cash on work already paid for in wages. This guide covers what the federal rules require, the four things that must land with every pay app on a covered job, where the week gets stuck, a weekly log that keeps no worker’s personal data, and when to call a construction attorney instead.

By Tamara Stepanyan, founder of Lumina Business Advisory · Updated October 27, 2026 · Sources checked October 17, 2026 · Editorial standards

Why certified payroll can hold up payment

On construction covered by the Davis-Bacon and Related Acts, the contract clauses in 29 CFR 5.5 apply to the prime contractor and flow down to every subcontractor. Three of them explain why a missing week stops money.

Weekly, for every covered week. The contractor or subcontractor must submit certified payrolls weekly, for each week in which covered work is performed (29 CFR 5.5(a)(3)(ii)(A)). Under the Copeland Act regulations, each one is due within 7 days after the regular payment date of the payroll period (29 CFR 3.4).
The prime answers for the subs. The same paragraph says the prime contractor is responsible for the submission of all certified payrolls by all subcontractors, and 29 CFR 5.5(a)(6) makes the prime responsible for every subcontractor’s compliance with the clauses.
Missing records can stop payment. If a contractor or subcontractor fails to submit the required records, the agency may, after written notice, act to suspend any further payment until the violation has ceased; the failure may also be grounds for debarment (29 CFR 5.5(a)(2) and (a)(3)(iv)(B)).

Put those together and the GC’s position is plain: an electrical subcontractor’s missing week can put the GC’s own payment at risk. That is why a subcontract can make each week’s certified payroll a condition of the sub’s pay app. Whether this subcontract does, and how much it lets the GC hold, is in its payment terms. The federal rules exempt contracts of $2,000 or less (29 CFR 3.3(c)), and state prevailing-wage programs set their own rules; on a state job, read the contract and the state agency’s requirements, not this summary.

The four things that must land with every pay app on a covered job

Every pay app needs percent complete, new change-order lines and the waiver the GC asks for, each from a different person. On a prevailing-wage job it needs a fourth input, and the fourth runs on a weekly clock while the pay app runs on a monthly one.

Percent complete by line on the schedule of values, from the PM or the foreman.
New lines for every executed change order since the last pay app, from whoever keeps the change-order log.
The lien waiver the GC requires with the pay app, from the office.
A certified payroll for every week in the period in which covered work was performed — accepted, not just sent — from payroll.

When any one of the four is late, the pay app waits. The first three are visible to the PM, because they sit in the pay app itself. The fourth may not be: it goes to a GC portal or an agency, and a rejection on week three can surface only when the GC’s accountant holds the pay app at the end of the month.

Where the week gets stuck, from timesheet to signed statement

A certified payroll is the shop’s ordinary payroll for the week, cut to the covered job and certified. The steps are short; the delays live between them.

Hours coded to the job. Time entered as “shop” or against the wrong job number has to be found and moved before the week can be reported.
The right classification for the work actually performed. An electrician, a laborer and an apprentice carry different rates in the wage determination. Apprentices may be paid below the predetermined rate only under the registration rules in 29 CFR 5.5(a)(4), so the registration paperwork has to be on file.
Fringe benefits shown the way the wage determination and the shop’s plans require.
The Statement of Compliance, signed by the contractor or by the person who pays or supervises the payment of the workers — an original handwritten signature or a legally valid electronic one. Optional Form WH-347 carries it on its back, but any format with the same certification is accepted.
Submission where the contract says: the agency, the owner, or the GC’s portal, which may have its own login and its own format checks.
Corrections. A rejected week has to be fixed and resubmitted, and a wage correction can mean back pay before the corrected report goes in.

None of this should be rushed to make a cutoff. Under 29 CFR 5.5(a)(3)(ii)(F), falsifying the certification may expose the contractor or subcontractor to civil or criminal prosecution. The goal is a routine that starts early enough that nobody has to choose between a signature and a deadline.

A weekly certified payroll log: one owner, one date, no worker data

The fix is a log with one row per job per week, kept by one named person and looked at on the same day every week. It tracks weeks and dates, not people. Workers’ names, Social Security numbers and addresses stay in payroll, where they belong; the weekly transmittals themselves must not carry full Social Security numbers or home addresses, only an individually identifying number such as the last four digits (29 CFR 5.5(a)(3)(ii)(B)).

Job number, GC, and where the payroll goes: agency, owner or the GC’s portal.
Week ending date and the regular payment date for that week.
Due date: 7 days after the payment date, or the GC’s earlier date if the subcontract sets one.
Date submitted, and who signed the Statement of Compliance.
Status: accepted, rejected or no answer, with the date of that status.
For a rejection: the reason in a few words, the correction date and the resubmission date.
The pay app the week belongs to, and that pay app’s cutoff.

Two checks make the log work. Every Monday, any week past due or rejected gets a name and a date. And five working days before each GC’s pay-app cutoff, the log is matched against the pay-app period: every covered week in it must read “accepted.” If one does not, the PM hears it that day rather than from the GC’s accountant at month end. Illustrative example: a school job with a monthly pay app of about $80,000. Week three comes back rejected for a classification, nobody sees the rejection, and the GC holds the pay app. One rolled cycle is a month of carrying $80,000 of work whose wages already went out every Friday. The numbers are hypothetical; the mechanism is not.

What the GC may hold — and when to call a construction attorney

On a direct federal contract, the prompt-payment clause at FAR 52.232-27 requires the prime to pay a subcontractor for satisfactory performance within 7 days of receiving payment, and it lets the subcontract permit withholding when the sub’s request does not meet the subcontract’s terms, with written notice to the sub. On a federally assisted job — a school, a transit project, a water plant paid partly with federal grants — that FAR clause does not govern the payment; the owner’s contract, the subcontract and state law set the timing instead.

We give no legal advice. Whether a GC may hold an entire pay app over one week of certified payroll, whether it owes interest, and what notice it owed the shop are questions about this subcontract and this state’s law, and they belong with the shop’s construction attorney. What an operations fix can do is make sure the question rarely comes up: every covered week accepted before the cutoff, and a written record of when each one went in.

What to automate, and when not to buy anything

Payroll and certified-payroll software can produce the weekly report from coded hours and push it to some portals, and that removes retyping. It does not code the hours to the right job, choose the right classification, chase a signature or notice a rejection. Those are habits with an owner, and the log above carries them whatever software sits underneath.

When not to buy anything: a shop with one covered job a year can run this log on a single sheet, and a payroll provider that already prepares the reports may be all it needs. If held pay apps happen once and the cause is obvious, fix the cause and move on.

If pay apps on prevailing-wage jobs keep slipping, and nobody can say whether the cause is certified payroll, change orders missing from the schedule of values or waivers, the Revenue Review is two weeks of read-only access to pay apps, the schedule of values, the change-order log, the lien waiver log and submission dates, ending in a written report that prices each delay and a 90-day plan. Certified-payroll worker identifiers stay out of it. Implementation is scoped and priced separately. The free 20-minute call settles whether it fits.

Before any next step

What should you do next?

Fix it yourselves.: If the cause is clear, it lives inside one process, and one person can own it — take the play from this page and run it. That outcome is fine with us; it is why the play is published in full.
Order one bounded build.: If the fix is known but needs configuration or integration inside your stack — a cadence wired into your own system, an alert, a handoff — scope that one build, with us or with anyone you trust. The six systems we build show what bounded looks like.
Start with the Review.: If the causes are debatable, the problem crosses departments or systems, or the economics are unclear — diagnose before anyone builds. The Revenue Review: $4,500 fixed, two weeks, computed from your own records. Read a sample finding before you decide — free, no email.

Asked right after

Can a general contractor withhold payment for missing certified payroll?: On federally funded work, the agency may suspend further payment when required records are missing, and the prime is responsible for its subcontractors’ certified payrolls (29 CFR 5.5). That gives the GC a reason to make each week a condition of a sub’s pay app. What this subcontract allows the GC to hold, and what notice it owes, is a question for the shop’s construction attorney.
How often does certified payroll have to be submitted?: Weekly, for each week in which covered work is performed, under 29 CFR 5.5(a)(3)(ii)(A). The Copeland Act regulations set the delivery at within 7 days after the regular payment date of the payroll period (29 CFR 3.4). A GC can set an earlier internal date in the subcontract.
Is Form WH-347 required?: No. The Department of Labor describes WH-347 as optional: the payroll information can be submitted in any format, but it must be submitted weekly and carry the signed Statement of Compliance, which the back of WH-347 provides.
Do certified payrolls need workers’ full Social Security numbers?: Not on the weekly transmittal. 29 CFR 5.5(a)(3)(ii)(B) says full Social Security numbers and home addresses must not be included; an individually identifying number such as the last four digits is enough. A prime contractor may still ask a subcontractor for full details for its own records.
What if no covered work was done in a given week?: The federal clause ties the weekly submission to weeks in which covered work is performed. Some agencies and GCs ask for a “no work performed” report for idle weeks on an active job; the subcontract or the portal’s instructions say which, so ask the GC in writing at the start of the job.
Do these rules apply to state prevailing-wage jobs?: Not directly. The rules here are federal and apply to Davis-Bacon and Related Acts work. State prevailing-wage programs set their own reporting format, deadlines and penalties, so read the contract and the state labor agency’s requirements for each state job.

Keep reading

Bring us the process that keeps getting stuck.

A 20-minute conversation about the workflow, the teams and the systems involved — and a straight answer on whether The Revenue Review is the right next step. If it is not, we say that on the call.

Book the 20-minute call +1 (202) 600-6027

A real person answers or calls you back the same business day.