Virginia's New Wage Liability Law: What HB 238 Means for General Contractors After July 1, 2026

Imagine this: you manage a mid-size general contracting firm in Virginia. You paid your subcontractors in full, on time, for every phase of a recent project. Months later, you open a letter and learn you are now responsible for $38,000 in unpaid overtime and minimum-wage shortfalls — for workers you never hired, never supervised, and never paid directly. Under Virginia law as of July 1, 2026, that scenario is not hypothetical. It is the new baseline.

House Bill 238, signed by Governor Abigail Spanberger, fundamentally shifts wage-payment risk in Virginia construction. For contracts entered on or after July 1, 2026, a general contractor is automatically on the hook for wages owed to a subcontractor's employees — even if you had no knowledge of the violation. If you build in Virginia, work with subs, or plan to bid projects that will start after mid-year, this law changes how you contract, document payroll, and manage your books.

What HB 238 Actually Does​

At its core, HB 238 amends Virginia Code § 11-4.6 and related wage statutes to make wage liability automatic and shared. Here are the changes that matter most to owners and operators.

1. Automatic Joint and Several Liability​

For any construction contract between a general contractor and a subcontractor entered on or after July 1, 2026, the law deems the contract to include a clause making both parties jointly and severally liable for all wages owed to the subcontractor's employees.

"Jointly and severally" means the employee can pursue either party — or both — for the full amount owed. A worker for your drywall sub does not have to chase the sub first. They can sue you directly for the entire unpaid balance, and you would then have to seek reimbursement from the sub separately.

This applies across the federal Fair Labor Standards Act (FLSA), the Virginia Wage Payment Act, and the Virginia Minimum Wage Act. In practice, that covers minimum wage, regular wages due under an employment agreement, and overtime.

2. General Contractors Are Now Deemed "Employers"​

HB 238 does more than add a contract term. It expressly classifies a general contractor as a statutory employer of a subcontractor's employees for wage-payment purposes.

Why that matters: Virginia's wage remedies are not limited to back pay. Once you are deemed an employer, you are exposed to the full range of civil and criminal penalties that apply to an employer who fails to pay wages — not just the contract value.

3. The Knowledge Defense Is Gone​

Since 2020, Virginia already had a wage-theft statute that made GCs jointly liable — but only if the GC knew or should have known of the subcontractor's wage violation. That knowledge requirement gave diligent contractors a real defense: maintain reasonable oversight, rely on sworn payroll certifications, and document compliance.

HB 238 eliminates that limitation. For covered contracts after July 1, 2026, knowledge is irrelevant. You can be liable even if the violation was hidden, the payroll records looked clean, and you acted in good faith.

4. Sworn Certifications No Longer Protect You​

Under the prior framework, many GCs required subcontractors to submit weekly sworn statements certifying that all wages had been paid. Those certifications, while not bulletproof, supported the "no knowledge" defense.

HB 238 expressly provides that a subcontractor's sworn wage-payment certification is not a defense to a wage claim against the general contractor. Even if a sub falsely certifies compliance, you can still be held directly liable. The certification may give you a contract claim against the sub later, but it will not stop the wage case against you.

5. Indemnification Is Allowed — But You Must Chase It Separately​

You can still include an indemnification clause requiring a subcontractor to reimburse you if you are forced to pay their wage liability. HB 238 does not prohibit indemnity.

The catch: if the subcontractor refuses to indemnify after a claim is asserted, your remedy is limited to a separate breach-of-contract action. You must defend (and potentially pay) the wage claim first, then sue the sub to get the money back. There is no automatic setoff or right to withhold unrelated payments unless your contract independently provides for it and Virginia law permits it.

6. Stronger Employee Presumption for Misclassification​

HB 238 also tightens worker-classification rules. It creates a presumption that a worker is an employee, not an independent contractor, unless the business satisfies the IRS independent contractor test — a strict, control-focused standard that looks at behavioral control, financial control, and the nature of the relationship.

For construction companies that rely on 1099 labor, this matters because misclassification claims now tie directly into expanded wage-payment remedies: a three-year statute of limitations, automatic liquidated damages, attorneys' fees, and the right to proceed as a collective action. The cost of getting classification wrong has gone up sharply.

How This Differs From the Old Rule​

It helps to see HB 238 in context. Understanding what changed clarifies why your contracts and controls need to change too.

In short, the legislature took a narrow, fault-based rule and replaced it with a broad, strict-liability framework.

The Penalties Behind the Liability​

Liability is not just back wages. Virginia's wage statutes stack remedies that can quickly multiply exposure.

• Liquidated (double) damages: Under the Virginia Wage Payment Act, an employer who fails to pay wages can be liable for the unpaid wages plus an equal amount as liquidated damages — effectively doubling the claim — plus prejudgment interest, reasonable attorneys' fees, and costs.

• Triple damages for knowing violations: If a court finds the failure to pay was "knowing" — a standard that can include willful or reckless disregard — damages can rise to three times the wages due.

• Three-year statute of limitations: Employees have up to three years to bring a claim, longer than many contract claims. Payroll errors from a project completed two years ago can still generate a lawsuit today.

• Collective and representative actions: Claims can be brought individually or on behalf of a group of similarly situated workers, increasing the scale of exposure from a single subcontractor's practice.

When you combine joint and several liability with these remedies, a relatively small underpayment by one sub can become a six-figure exposure for the GC that hired them.

Which Contracts Are Covered?​

HB 238 applies to construction contracts entered into on or after July 1, 2026. That effective-date language creates a few practical points:

• New contracts only. A contract signed on June 30, 2026 is governed by the prior law; one signed on July 1, 2026 is governed by HB 238. Long-running master agreements with new work orders or task orders after July 1 will need careful review — each work order could be treated as a new contract.

• All tiers potentially affected. Summary guidance describes the deeming provision as applying between a general contractor and its subcontractor and, in related Code sections, to lower-tier subs as well. If you are a first-tier sub hiring second-tier subs, you should assume the same upstream risk applies to you.

• No commercial-value floor. The earlier $500,000 threshold for commercial projects is not restated in the HB 238 summaries. Prudent contractors are treating any Virginia construction subcontract after July 1 as covered until regulations or case law say otherwise.

If you bid work that will be contracted after July 1, price and manage it under the new rules even if the bid went out earlier.

Part of a National Trend — Not Just Virginia​

Virginia is not acting in isolation. The shift toward upstream wage accountability is spreading, which matters if you work across state lines or hire subs who do.

• Oregon SB 426, enacted June 2025, makes property owners and direct contractors jointly and severally liable for unpaid wages and fringe benefits owed to unrepresented employees of subcontractors at any tier, effective January 1, 2026.
• Connecticut HB 5275 would make a contractor jointly and severally liable for unpaid wages owed to a subcontractor's employee on certain construction contracts executed on or after October 1, 2026, with a required 30-day notice before suing the contractor.
• New York Labor Law § 198-e has imposed joint liability on contractors for wage theft by subcontractors at any tier since 2021.

The direction is clear: more states are moving wage enforcement from the employer who underpaid to every contractor above them in the chain. Virginia's HB 238 is among the broadest because it pairs strict liability with employer status and enhanced misclassification presumptions.

A Practical Compliance Playbook for General Contractors​

You cannot contract your way out of HB 238, but you can dramatically reduce your risk. The contractors who will navigate this best are the ones who treat wage compliance as an operational system, not a paragraph in a subcontract.

1. Audit Your Current Subcontract Form — Now​

Start with the agreement you use today. With counsel, revise:

• Joint-liability acknowledgment: Reflect that the contract is deemed to include joint and several liability; do not attempt to disclaim it.
• Indemnification: Require the sub to indemnify, defend, and hold harmless the GC for wage claims arising from the sub's workforce, including attorneys' fees and liquidated damages. Address survival beyond final payment.
• Cooperation and access: Require the sub to provide payroll records, timecards, and classification documentation within a set window (e.g., 5 business days) on request and during any wage claim.
• Remedies for non-cooperation: Include rights to withhold payment to the extent permitted by law, suspend work, or terminate for failure to provide records — drafted carefully to comply with Virginia prompt-payment statutes.
• Lower-tier flow-down: Require the sub to include equivalent wage-compliance and indemnity terms in every lower-tier subcontract and to provide copies on request.

2. Build a Prequalification System That Actually Tests Payroll Capability​

Price is not the only predictor of wage risk. Before awarding a sub:

• Verify contractor license, workers' compensation coverage, and unemployment insurance registration.
• Request recent payroll compliance history: have there been Virginia Wage Payment Act claims, DOL Wage and Hour Division investigations, or Davis-Bacon issues?
• For subs with significant labor forces, ask for a sample certified payroll or evidence of a payroll service provider, not just a one-line certification.
• Check independent-contractor usage: a sub whose crew is predominantly 1099 should trigger deeper review given the new presumption.

Document the prequalification decision. If a claim arises, your diligence record supports indemnity and shows a pattern of reasonable care, even though it is no longer a direct defense.

3. Move From Certifications to Verification​

Because sworn certifications are no longer a defense, treat them as a starting point, not proof.

• Require detailed payroll registers by project and pay period, showing employee name (or ID with last four of SSN as permitted), hours, rate, overtime, deductions, and net pay.
• For prevailing-wage or Davis-Bacon-related projects, collect WH-347-style certified payroll and statements of compliance even when not strictly required — the format forces completeness.
• Spot-check timecards against gate logs, daily reports, or foreman logs. A 40-hour certification for a worker who was on site 58 hours is a red flag you can catch before it becomes a claim.
• Retain records for at least four years (beyond the three-year statute) in a project-specific file.

4. Reassess Every Independent Contractor Relationship​

The presumption that workers are employees raises the stakes for misclassification. For each 1099 individual who works regularly on your projects or your subs' projects:

• Apply the IRS control test honestly: who sets the schedule, provides tools, directs the sequence of work, and bears opportunity for profit or loss?
• If the worker is functionally an employee, convert to W-2 or engage through a properly structured staffing entity that handles payroll taxes and wage compliance.
• Document the analysis. A file memo explaining why a worker meets the IRS independent-contractor standard is far more persuasive than a label in a contract.

5. Separate Wage Exposure in Your Job Cost and Cash-Flow Planning​

HB 238 creates a contingent liability that belongs in your financial planning, not just your legal file.

• Track labor by sub and by project in your job-cost system so you can quickly isolate which sub and which pay periods are implicated if a claim arises.
• Create a wage-compliance reserve for higher-risk projects or new subs, just as you would for warranty or retention. Even a 1–2% reserve on subcontracted labor can cushion a surprise claim.
• Model the worst case: unpaid wages × 2 (liquidated) + estimated attorneys' fees + interest. Knowing the multiplied exposure changes how you evaluate a low-bid sub.

6. Train Field Teams to Spot Flags​

Superintendents and foremen see problems before the office does. Train them to escalate:

• Workers who say they were paid cash, paid late, or shorted overtime.
• A sub whose crew size drops sharply after a wage complaint or who rotates workers to avoid hour thresholds.
• Timesheets that are uniformly 40.0 hours every week despite weather delays and overtime on the schedule — a sign of after-the-fact paperwork rather than real timekeeping.

Create a simple, non-retaliatory reporting channel and document follow-up.

7. Calendar the Effective Date Carefully​

Because HB 238 turns on the date the construction contract is entered into, set internal controls:

• Flag any subcontract that will be executed on or after July 1, 2026 for HB 238 review.
• For master service agreements, confirm whether a new work authorization counts as a new construction contract.
• If you opportunistically accelerated or delayed a signing around the effective date, document the business reason. Courts will look past form to substance.

Bookkeeping and Financial Controls That Reduce Risk​

Legal drafting helps, but your books are your first line of defense when a wage claim arrives. The general ledger and job-cost system are where compliance either lives or dies.

Chart of accounts: Keep subcontracted labor distinct from direct labor and from materials. Within subcontracted labor, create subaccounts by project and by subcontractor. When a claim letter arrives citing "unpaid overtime on the Riverside Apartments, June 2026," you should be able to pull the exact sub, the exact weeks, and the exact payments without reconstructing from bank statements.

Payables discipline: Pay only from an approved subcontractor file that includes a current W-9, certificate of insurance, contractor license verification, and a signed subcontract with the updated HB 238 terms. Collect lien waivers in exchange for payment and reconcile them to the payroll periods they cover.

Payroll reconciliation: If you self-perform any work, reconcile payroll to the general ledger every pay period and to job costs every month. Track certified or prevailing-wage payroll separately where required. Require subs to submit payroll registers that you can tie to your payment applications — if you paid the sub $120,000 for labor in June and their certified register shows$88,000 in gross wages for that period, the gap is explainable (burden, overtime, unworked hours) or it is a flag.

Documentation retention: Store payroll registers, timecards, subcontract agreements, change orders, and lien waivers together by project in a single digital file. Virginia's three-year limitations period means a project closed in summer 2026 can generate a claim in summer 2029. A complete, searchable file turns a disruptive records chase into a same-day response.

Month-end close habit: At month-end, review subcontractor payables aging, retention balances, and any wage-related correspondence. A small bookkeeping routine — 30 minutes per project — surfaces issues while memories and records are fresh. The cost of that routine is a fraction of liquidated damages on a single claim.

For small firms that have run on cash-basis, year-end cleanup, this law is a reason to adopt a more disciplined monthly close. Auditors, lenders, and sureties are already asking how contractors are accounting for contingent wage liability; clean books answer the question before it is asked.

Common Mistakes That Increase Exposure​

• Assuming a low price means savings. A bid that is 15% below the next competitor may reflect thinner payroll compliance rather than efficiency. Under HB 238, that discount can flow back to you as liability.

• Relying on a one-sentence indemnity. "Subcontractor shall indemnify GC for wage claims" is better than nothing, but without defense, cooperation, and flow-down language, it is hard to enforce quickly.

• Treating certifications as proof. A signed certification that "all wages have been paid" no longer stops a claim. Without underlying payroll data, it is just paper.

• Misclassifying to save on taxes and benefits. The new presumption makes 1099 crews a liability magnet. The payroll tax savings rarely outweigh double or triple damages plus fees.

• Co-mingling labor and materials in the books. When you cannot separate what you paid for labor versus materials by sub and by project, you cannot quickly verify or contest a wage allegation.

What to Do in the Next 30 Days​

1. Have counsel review and update your subcontract template for HB 238.
2. Inventory every subcontract that will be signed on or after July 1, 2026 and flag it for the new workflow.
3. Implement a prequalification checklist that includes payroll compliance history.
4. Require detailed payroll registers, not just certifications, from every sub.
5. Reclassify any doubtful 1099 relationships under the IRS test.
6. Set up project-level labor cost tracking and a document retention protocol that outlasts the three-year statute.

HB 238 does not make Virginia construction riskier because contractors are doing something new — it makes a long-standing risk newly visible at the top of the chain. A wage shortfall that once stayed with one subcontractor can now travel directly to your balance sheet, with interest and attorneys' fees attached. The firms that adapt early — tighter contracts, verified payroll, clean project accounting — will bid with confidence while others are learning the statute in litigation.

Simplify Your Financial Management​

As you tighten wage compliance and payroll verification, maintaining clear, auditable financial records is essential. Beancount.io provides plain-text accounting that gives you complete transparency and control over your construction financial data — version-controlled, scriptable, and ready for audits. Get started for free and see why contractors and finance professionals are switching to plain-text accounting for job costing and compliance tracking.