PunchOne Worker, Two of Your Companies: Joint Employment and Overtime in 2026
One Worker, Two of Your Companies: Joint Employment and Overtime in 2026
The short answer: If the same person works 30 hours for your landscaping LLC and 30 hours for your snow removal LLC in the same week, that is usually 60 hours in one workweek with 20 hours of overtime owed, not two tidy part-time weeks. Separate EINs do not create separate workweeks. Both entities can be held liable for the full amount. The only reliable defense is a single, honest record of every hour the person worked for you, across every business you run. Punch produces that record as a byproduct of punching in.
The Trap Is Common and It Is Expensive
Small operators end up with two entities for perfectly ordinary reasons. Different insurance. A seasonal line of work. A partner on one side and not the other. An accountant who suggested it.
Then a good worker gets shared. They run the mower crew Monday through Thursday and cover the shop on Friday and Saturday. Two schedules, two payroll runs, two checks, each one under 40 hours, no overtime paid.
That arrangement is the single most common way a small business accrues an unbudgeted overtime liability. The federal wage and hour rules do not count entities. They count the hours one human being worked in one week.
What the DOL Said in Its 2025 Opinion Letter
The Wage and Hour Division addressed this directly in opinion letter FLSA 2025-05, issued September 30, 2025.
A hostess worked at a restaurant for $28.00 per hour and was offered additional shifts at a members-only club on the second floor of the same hotel. The two operations were separately structured on paper and may have used different timekeeping and payroll systems. She was told there would be no overtime because they were different companies.
The Department disagreed. The two operations shared a kitchen, offered substantially the same food and beverages, used similar trade names, moved staff between them, had managers who supervised in both, and appeared to have the same owners. That made them joint employers. All of her hours in both places had to be combined for the workweek, and both entities were jointly and severally liable for compliance.
The letter includes the arithmetic in plain form. A cashier working 30 hours a week for each of two associated establishments has worked 60 hours. Twenty of those hours carry an overtime premium, and the worker may collect it from either employer.
Read that last part twice. Joint and several liability means an employee who is owed the money can pursue whichever entity has assets. The one that only got 30 hours of work can be made to pay for all 60.
What Makes Two Companies "Sufficiently Associated"
The relevant concept is horizontal joint employment. It applies when a worker puts in separate hours for two or more employers in the same week and those employers are sufficiently associated with respect to that person's employment.
Employers are generally sufficiently associated when any of the following is true:
- There is an arrangement between them to share the worker's services, such as interchanging employees.
- One employer is acting directly or indirectly in the interest of the other in relation to that worker.
- They share control of the worker because one controls the other, is controlled by the other, or both are under common control.
That third one is where owner-operated sister companies land almost automatically. Common ownership plus a shared worker is most of the test.
Some things are not enough on their own. Using the same vendor does not make two businesses joint employers. Being franchisees of the same franchisor does not either. The question is the specific employment relationship, not general business overlap.
The Rule Book Is Being Rewritten Right Now
The regulatory history matters because it explains why your accountant and your neighbor may remember different answers.
A 2020 rule at 29 CFR part 791 took effect March 16, 2020, and set out separate horizontal and vertical standards. The Department rescinded it in a final rule published July 30, 2021, effective September 28, 2021, which removed and reserved part 791 in its entirety. For roughly five years there has been no unified federal regulation on point, and courts in different circuits have applied different tests.
On April 22, 2026, the Department announced a new proposed rule to set one standard across the FLSA, FMLA, and MSPA. It was published in the Federal Register on April 23, 2026, and the comment period closed June 22, 2026. It distinguishes horizontal from vertical joint employment and carries forward the sufficiently-associated language above. It is a proposal. No final rule has issued.
None of that churn changes the underlying statute. The FLSA has always required overtime after 40 hours in a workweek for a covered nonexempt employee, and joint employers have always had to aggregate. The regulations argue about where the edges are. Two companies you own that share a worker are not near the edge.
The Math, Including the Part People Get Wrong
Start with the total. Hours worked for all joint employers in the workweek are added together to test minimum wage compliance and to determine overtime.
If the pay rate differs between the two businesses, the overtime premium is not based on whichever rate happened to apply when the 41st hour landed. It is based on the weighted average regular rate for the week: total straight-time earnings from both entities divided by total hours from both entities. Time and a half is then computed from that blended rate.
A worker at $22 in one company and $26 in the other has a different regular rate every week, because it moves with the mix of hours. There is no shortcut around the weekly calculation, which is exactly why the hours need to arrive in one place before payroll runs, not after.
Two Timekeeping Systems Is the Root Cause
Look back at the DOL letter. The two operations possibly used different timekeeping and payroll systems, and that is precisely how the hostess ended up being told no overtime was owed. Nobody added the week up. There was no place where the week existed as a single number.
That is the failure mode. Not malice, arithmetic that nobody was assigned to do.
What a defensible record has to show is small and specific:
- Which person worked, as one identity, not two employee IDs
- Which day, with real start and stop times to the minute
- Which business line or job site the hours belong to
- Whether the unpaid meal was taken, and when
- The rate that applied to those hours
- A weekly total that spans everything they did for you
If your two entities cannot produce that combined number on Monday morning, you are relying on nobody ever asking.
How Punch Handles It
Punch is built so the combined week exists by default.
Keep one Punch organization for the people you employ, and separate the businesses with job sites. Every punch in and punch out is timestamped to the minute and attached to a job site, so the landscaping hours and the shop hours stay distinguishable while still belonging to one person and one week. Lunch is tracked as its own event, so unpaid meal time never disappears into a paid block, and a split shift stays two clean segments instead of one invented long one.
Overtime is applied automatically against your fixed workweek, using Punch's overtime presets covering more than 50 countries and the daily rules that apply in states that have them. Because the workweek belongs to the employee rather than to a job site, hours from both business lines roll into one correct weekly total. The 60-hour week shows up as a 60-hour week.
Owners and managers review that week in one place and approve or reject in bulk instead of one shift at a time, and each decision is recorded against the shift. Pay periods run weekly or bi-weekly. When the week is approved, Reports export to Excel or a QuickBooks CSV, or push straight into QuickBooks Online, with the job-site detail intact so you can still allocate labor cost to the right entity after paying the correct overtime.
Punches work offline, so a truck yard with no signal still records a real punch that syncs later. For crews without company phones, a shared iPad becomes a punch station with a PIN. Verification stays private throughout. Punch confirms an on-site punch-in with a job-site geofence on iOS, never facial recognition and never a photo at the punch. Proving someone was on the job should not require a camera in their face.
Why Punch Beats the Per-Seat Alternatives
Running two businesses is exactly the situation per-seat and per-location billing punishes. ClockShark, Connecteam, Buddy Punch, QuickBooks Time, and Homebase all bill by the user, and some add cost as you add locations, which nudges owners toward the very thing that creates the liability: two cheap accounts instead of one complete record.
Punch charges a flat price per organization. Every plan includes every feature, from geofenced punch-in to kiosk mode to bulk approvals to QuickBooks Online export, and owners are always free. Add every job site both businesses run, add the crew that floats between them, and your software bill does not move.
The Bottom Line
Two entities, one worker, one workweek. The hours combine, the overtime is computed on the blended rate, and both companies can be made to pay it. The DOL restated this in September 2025 and proposed a unified rule in April 2026, but the arithmetic has not changed in decades. The only thing that reliably protects you is a single record of every hour that person worked for you, wherever they worked it.
Start with Punch and let both businesses share one honest week.
This article is general information, not legal advice. Joint employment turns on the specific facts of your arrangement, and state law may reach further than federal law. Confirm your obligations with the Wage and Hour Division, your state labor agency, or a qualified professional.