Certified Payroll Deadlines: The 7-Day Rule

29 CFR 5.5(a)(3)(ii)(A) is the paragraph that creates the submission obligation: "The contractor or subcontractor must submit weekly, for each week in which any DBA- or Related Acts-covered work is performed, certified payrolls to the [appropriate Federal agency]." The word doing the work is weekly. It establishes a cadence — one submission per covered week — but the paragraph does not state a number of days between paying your workers and getting the payroll in.

The other place a deadline would live is the Federal Acquisition Regulation clause that goes into federal construction contracts. FAR 52.222-8 covers payrolls and basic records, and its submission language is similarly cadence-based: the contractor "shall submit weekly for each week in which any contract work is performed a copy of all payrolls to the Contracting Officer." Again a weekly obligation, again no day count in the text we reviewed.

We do not know, and we are not going to invent a citation. Two explanations are plausible and both are common in this area. It may derive from an earlier revision of the FAR clause — regulations get reworded, and a number that was once explicit can persist in industry knowledge long after the text changes. Or it may be an agency convention that spread: agencies issue their own instructions, several do specify a day count, and a rule that binds many contractors gets repeated as though it binds all of them.

Here is the reassuring part. If you are meeting the weekly obligation in any normal sense — running payroll, then submitting that week's certified payroll in the ordinary course — you are almost certainly inside whatever deadline applies. The seven-day figure is not demanding. Contractors who run into trouble on timing are generally not a day or two late; they are weeks behind because a subcontractor stopped sending figures or because nobody owned the task. That is a different problem from a deadline.

As with most questions in this subject, the party you submit to decides. Check the labour standards section of your contract, the agency's contractor instructions, and the portal you submit through if there is one — portals frequently enforce a schedule directly, which settles the question without anyone having to interpret anything. Failing all that, ask the compliance administrator. It is a one-line email and the answer governs.

The useful discipline is weekly rhythm rather than a countdown. Certified payroll is one of those obligations that is trivial when it is a habit and miserable when it is a catch-up exercise, because the information gets harder to reconstruct as it ages. Fix the day of the week it happens, make one person accountable for it, and the deadline question stops being interesting. Contractors who file the same day every week are never the ones asking how many days they have.

If submissions are drifting, look down the chain before looking at your own office. A second-tier specialist working a few weeks on site has no routine for this, and their payroll is the one that arrives late or not at all. Under 29 CFR 5.5(a)(6) the prime "is responsible for the compliance by any subcontractor or lower tier subcontractor with all the contract clauses in this section", so their lateness is your problem in a way that is easy to underestimate until an agency asks where three weeks of payrolls are.

Less than people fear in isolation, and more than they expect in aggregate. A single late submission is an administrative matter. A pattern of them contributes to the impression the debarment standard at 29 CFR 5.12(a)(1) turns on — having "disregarded their obligations to workers or subcontractors" — which is about the shape of conduct over time rather than any single lapse. The practical risk arrives sooner than that, though: agencies can withhold payment where compliance is in question, and a stalled progress payment does not wait for a formal finding.