PEO for government contractors

This page is general information, not legal advice. Federal and state contract labour rules turn on the contract clause, the wage determination and the facts of the arrangement. Consult government-contracts counsel before changing who employs the people who perform a covered contract.

What this page can and cannot tell you

A PEO sits on top of a co-employment arrangement: the PEO and the client share employer responsibilities, and the PEO typically runs payroll and benefits under its own tax identity (see what a PEO is). For a contractor on a Service Contract Act or Davis-Bacon contract, the question is what that does to obligations the contract already imposes. We read the Department of Labor, eCFR, FAR and IRS pages listed below. None of them addresses PEOs or co-employment. So this page sets out what those sources require of a “contractor”, and then names the questions the sources leave open.

Who the “employer” is for wage-determination purposes

The Service Contract Act regulations define their own terms. According to 29 CFR 4.1a, Definitions and use of terms (eCFR, retrieved 14 October 2026), a “contractor” includes a subcontractor whose subcontract is subject to the Act, a “contract” covers any contract subject wholly or in part to the Act and any subcontract of any tier, and “employer” is used interchangeably with “contractor” and “subcontractor”. The same section states that the U.S. Government and its agencies are not contractors, subcontractors, employers or joint employers for the Act’s purposes.

Two things follow from that text, and one thing does not. The obligations run through the contract chain, down to subcontractors of any tier. And the section expressly uses the phrase “joint employers”, which is the language of shared employment. What the section does not say, on the text we read, is whether a PEO that is a co-employer of the contractor’s service employees is itself a “subcontractor” or “employer” under the Act. We could not confirm that from a primary source and we do not state an answer.

Wage determinations and fringe benefits

The DOL Wage and Hour Division SCA page (U.S. Department of Labor, retrieved 14 October 2026) says the Act requires contractors and subcontractors performing services on prime contracts in excess of $2,500 to pay wage rates and fringe benefits found prevailing in the locality, and that the Department issues wage determinations on a contract-by-contract basis, which become part of the contract. FAR 52.222-41 (Acquisition.gov, retrieved 14 October 2026), paragraph (c), requires each service employee to be paid not less than the minimum monetary wages and furnished fringe benefits set by the Secretary of Labor. Paragraph (d) says the contractor may discharge the obligation to furnish fringe benefits through equivalent bona fide benefits or cash payments under subpart D of 29 CFR Part 4.

The subpart D rules on equivalent benefits are where a PEO’s bundled plan would be tested. In 29 CFR 4.177 (eCFR, retrieved 14 October 2026), the terms “equivalent fringe benefit” and “cash equivalent” are defined as equal in terms of monetary cost to the contractor. We did not read the rest of subpart D, so we cannot say how a pooled PEO plan is credited against a determination’s fringe rate, or what documentation DOL expects. That is the single most consequential open question on this page.

Davis-Bacon is separate. The DOL Davis-Bacon overview (U.S. Department of Labor, retrieved 14 October 2026) says contractors must pay laborers and mechanics no less than locally prevailing wages and fringe benefits for corresponding work on similar projects, and that the Department determines those rates. Under 29 CFR 5.5 (eCFR, retrieved 14 October 2026), paragraph (a)(1), contributions made or costs reasonably anticipated for bona fide fringe benefits are considered wages paid. The same paragraph addresses contractors that do not make payments to a trustee or other third person: anticipated costs may be counted only where the Secretary of Labor has made the required finding on the contractor’s written request. Whether payments to a PEO are payments to a “third person” within that provision is not something we could confirm. The DOL page also notes a federal court preliminary injunction affecting three provisions of the 2023 final rule, so check current status before relying on any Davis-Bacon rule text.

The wage determinations themselves are published in the SAM.gov wage determination database, which both DOL program pages link to. We did not open the database, so we do not describe any specific determination.

Payroll records, certified payroll and flowdown

On Service Contract Act contracts, the clause in 29 CFR 4.6 (eCFR, retrieved 14 October 2026) requires the contractor and each subcontractor to make and maintain records for three years from completion of the work, listing items such as names, classifications, rates and hours, to make the contract available for inspection, and to allow Wage and Hour Division representatives to interview employees at the worksite. It also requires the clauses to be inserted into covered subcontracts. FAR 52.222-41 carries a matching record-keeping requirement and a requirement to notify each service employee of the minimum wage or post the wage determination.

On Davis-Bacon work, 29 CFR 5.5(a)(3) (eCFR, retrieved 14 October 2026) requires the contractor or subcontractor to submit weekly certified payrolls, each accompanied by a signed Statement of Compliance, and states that the prime contractor is responsible for submission of all certified payrolls by all subcontractors. Paragraph (a)(6) requires the clauses, with the applicable wage determinations, to be inserted into subcontracts and flowed down to lower tiers, and states that the prime contractor is responsible for subcontractor compliance and may be liable for unpaid wages and monetary relief. FAR 52.222-6 (Acquisition.gov, retrieved 14 October 2026) requires that wages including bona fide fringe benefits be paid at least weekly and that payroll records accurately set forth time spent in each classification; the clause text we read does not name certified payrolls, which is why the regulation is cited for them.

The practical point is that the signature and the records trail stay with the contractor under every version of this text. If a PEO produces the payroll, the contractor still needs those records, in the form the contract asks for, on the schedule the contract asks for, and needs the PEO bound to produce them. Whether the PEO’s system can do that is a capability question, separate from the legal one.

Successor and contract-transition issues

Contract transitions are where payroll continuity matters most. The SCA clause in 29 CFR 4.6 addresses contracts that succeed a contract subject to the Act, and requires an incumbent prime contractor, in the circumstances the clause describes, to furnish a certified list of service employees with their anniversary dates of employment. 29 CFR 4.163 (eCFR, retrieved 14 October 2026), on section 4(c) of the Act, states that a successor’s obligation is to ensure service employees are paid no less than the wages and fringe benefits in the predecessor’s collective bargaining agreement, and allows equivalent combinations of benefits or equivalent cash payments under 4.177.

For a contractor considering a PEO, the transition points run in both directions: entering a PEO arrangement mid-contract moves the payroll and benefit platform under people whose anniversary dates and accrued benefits are already tracked, and later exiting a PEO does the same in reverse. We did not read any DOL guidance on how those two events are treated, so treat both as items for counsel.

Who is liable for employment taxes

The IRS CPEO page (Internal Revenue Service, retrieved 14 October 2026) states that a CPEO is a person the IRS has certified under section 7705 of the Internal Revenue Code, and that the Tax Increase Prevention Act of 2014 requires the IRS to establish a voluntary certification program. The page we read did not discuss which party is liable for employment taxes, so we make no statement on that here. Certification is separate from anything in a government contract.

What the nonprofit engagement showed

One BRG engagement involved a nonprofit employing roughly seven hundred people, almost entirely through federal set-aside contracts, whose payroll provider could no longer meet the program’s real-time and mid-payroll reporting requirements. We wrote the reporting obligations into the selection criteria as a gate before anything was scored, then ran an RFP against that standard. The selected provider met the requirements. The full engagement reports $550,000 from administrative consolidation and $200,000 from the platform and shared compliance risk, with a further $250,000 projected and not yet realized. That is one organization’s result, driven by its own reorganisation, and it is not a forecast for another contractor.

What we could not confirm

We could not load DOL Fact Sheet #94 or the Davis-Bacon fact sheets, and did not open the SAM.gov wage determination database, so nothing on this page comes from them. None of the pages we read addresses PEOs, co-employment, leased employees or professional employer organizations. Specifically, we could not confirm: whether a PEO is itself a subcontractor or employer under the SCA or Davis-Bacon; how a PEO’s pooled benefits are credited as bona fide fringe benefits against a wage determination; whether payments to a PEO satisfy the Davis-Bacon third-person rules; which party must sign certified payrolls; how contract transitions are treated when a PEO is introduced or removed; state prevailing-wage and state contractor rules, which we did not read; and employment tax liability under a CPEO arrangement.