A franchisee in the Southeast operates eleven quick-service locations under six LLCs, each with its own federal employer identification number, because that is how the lender and the franchisor wanted it structured. The payroll runs cleanly. The problem showed up when a shift lead started covering Saturdays at a second location two miles away, under a different LLC. Each entity recorded 32 hours. Nobody paid overtime. Eighteen months later a Department of Labor investigation treated the two entities as joint employers, aggregated the hours, and the back wages plus liquidated damages ran well past what the Saturday coverage had been worth.

Multi-entity structures exist for good reasons, including liability separation, financing requirements, and partner arrangements that differ by location. The trouble is that the reasons are legal and financial, while the hours are human, and employees do not stay neatly inside the entity on their offer letter. Multi-EIN time tracking is the discipline of recording hours in a way that respects the legal boundaries for tax and reporting while refusing to pretend those boundaries exist for wage and hour purposes. This covers where that distinction bites, how to partition data without buying six systems, and what a regulator looks at first.

Can Employees Work Across Two EINs in the Same Week?

Yes, and that is exactly where the risk concentrates. Separate EINs are separate taxpayers. They are not automatically separate employers under the Fair Labor Standards Act, and the FLSA defines an employer broadly enough that related entities sharing control over the same worker can both be on the hook for the same hours.

Under the joint employment analysis, when two entities are sufficiently associated with respect to an employee, the hours worked for both are added together for the workweek, and overtime is owed on the combined total above 40. Who writes the check and how the liability is split is a separate question, and it is one that generally ends in joint and several liability. The practical rule for a group with common ownership and shared staff is to assume aggregation applies unless counsel has looked at your specific facts and said otherwise.

What this means operationally:

• Hours must roll up by person across every entity, not just within each one, before overtime is calculated
• The workweek has to be defined identically across entities, since a Sunday-to-Saturday week in one LLC and a Monday-to-Sunday week in another makes aggregation arithmetic impossible to do correctly
• Cross-entity shifts need to be visible to whoever approves time, before the week closes rather than at payroll
• Pay rates can legitimately differ by entity, which means the regular rate for overtime becomes a weighted average of the rates actually worked

That last point catches a lot of groups. When an employee works at two rates in one week, the overtime premium is calculated on the weighted average regular rate, not on whichever rate they happened to be earning in hour 41. Some employers can use the rate in effect during the overtime hours instead, but that generally requires a prior agreement with the employee, so confirm the approach with a wage and hour attorney before relying on it.

What Multi-Entity Structures Actually Look Like

Three arrangements dominate, and each one changes what the time system needs to do.

The first is the franchise group with one LLC per location or per small cluster, usually driven by financing. Ownership is common, management is shared, and staff move between sites. This is the highest aggregation risk and the structure where unified time tracking matters most.

The second is the group with distinct operating lines under one umbrella, say a restaurant entity and a catering entity, where staff genuinely overlap during events. Different work, same people, two sets of books.

The third is a group using a professional employer organization or a certified PEO, where the PEO becomes the employer of record for payroll tax purposes. The hours still originate in your locations, and the PEO needs them separated by its own client sub-codes, which do not always match your entity structure.

What must stay separate by EIN	What should be unified across EINs
Form 941 quarterly filings	Employee master record and identity
State unemployment accounts and rates	Workweek definition and pay period calendar
W-2 issuance, absent a valid common paymaster	Overtime calculation across combined hours
General ledger and labor cost allocation	Time-off balance, where the group treats it as portable
Workers’ compensation policies and class codes	Break and meal period compliance rules by state
Entity-level labor reporting to lenders or franchisor	Audit trail of edits and approvals

The left column is why the entities exist. The right column is why one system beats six.

The Overtime and Benefits Aggregation You Cannot Structure Around

Two separate aggregation rules apply to multi-entity groups and they do not work the same way, which is a common source of confusion.

The wage and hour side is the joint employment analysis described above, and it turns on the facts of control, not on the paperwork. Separate EINs do not help. Separate management, separate hiring authority, separate scheduling, and no interchange of employees might, but a group where the same district manager schedules across entities has very little room to argue separation.

The benefits side runs on the controlled group rules in sections 414(b), 414(c), and 414(m) of the Internal Revenue Code. For determining whether you are an applicable large employer under the Affordable Care Act, entities under common control are aggregated, so six LLCs with 15 full-time equivalents each are treated as a single employer with 90 and sit well past the 50-FTE threshold. The employer mandate penalties under section 4980H are then assessed at the individual entity level, which is an uncomfortable combination: aggregate to determine the obligation, separate to assess the penalty.

The reason this belongs in a conversation about multi EIN time tracking is that FTE determination is a calculation on hours. If your hours live in six systems that cannot be summed by person and by month, you cannot run the measurement period calculation at all, and the ACA calculation needs hours of service including paid leave, not just worked hours.

Tax and benefits aggregation rules are fact-specific and change. Have your CPA and benefits counsel confirm the analysis for your ownership structure rather than applying a general rule.

Partitioning One System Without Blurring the Entities

A single time system serving multiple EINs needs a partition at the entity level and a bridge at the person level. The partition handles reporting, cost allocation, and payroll export. The bridge handles the employee who works in two places.

What good partitioning looks like in a system:

• Entity is a first-class field on the location, the position, and every time entry, not a label on the department
• An employee record can carry multiple active assignments, each tied to an entity, a location, a job code, and a rate
• Every punch inherits its entity from the assignment or location where it happened, so the labor cost lands in the right set of books automatically
• Reporting runs at entity level by default, with a group-level roll-up available to whoever is permitted to see it
• Payroll export generates one file per EIN, with its own pay group, pay period, and tax jurisdiction mapping

The bridge is the harder part. Overtime calculation has to run on the person across all assignments, then allocate the premium back to entities. Most groups allocate the overtime premium proportionally to hours worked in each entity, which is defensible and simple. Some allocate it entirely to the entity where the hours crossed 40. Pick one method, document it in writing, and apply it consistently, because inconsistency is what makes an audit expand.

Payroll Export, Tax IDs, and the W-2 Question

Each EIN files its own Form 941 and its own state returns, so the export has to be clean per entity. The complication is Social Security and FUTA wage bases, which reset per employer. An employee who earns wages under two EINs in the same year generally has the taxable wage base applied separately by each, which means the employer pays more FICA and FUTA than it would for the same wages under one EIN, and the employee may over-withhold Social Security and need to claim the excess on their return.

Two mechanisms address this and both have conditions. The common paymaster rules under section 3121(s) of the Code allow related corporations to designate one entity to pay employees who work concurrently for more than one of them, with the wage base applied once. The relief is specific about who qualifies, and partnerships and LLCs taxed as partnerships generally cannot use it. The successor employer rules allow the wage base to carry over when an employee transfers in connection with an acquisition of a trade or business. Neither applies to a franchisee who simply moves staff around between affiliated LLCs mid-year.

The practical consequence is a cost, not a compliance failure. But you should know about it before you structure the group, and your time system should at least be able to tell you how many employees crossed entities during the year and what the duplicated wage base cost you. Most groups have never run that number.

Also build the export so that an employee working two entities produces two sets of wages that reconcile to one set of hours. When total hours in the time system do not equal total hours on the payroll registers across entities, you have found a mapping error, and that reconciliation should be a monthly habit rather than a year-end discovery.

Access Control for Managers Who Run Two Locations

Permissions in multi-entity groups fail in both directions. Managers get too much access, seeing labor costs for entities with partners who have not agreed to share that, or too little, unable to see the second-location hours of the employee whose overtime they are about to cause.

The workable model has three separate questions behind every permission. Which entities can this person see financial data for? Which locations can this person schedule and approve time for? And can this person see the cross-entity total for an employee they share? The third one should almost always be yes, at least to the extent of seeing that an employee has already worked 36 hours elsewhere this week, even when the manager cannot see where or at what rate. Blocking that visibility to protect entity confidentiality is how unintended overtime happens.

Partner-owned entities need particular care. If one LLC has an outside investor, that investor’s reporting rights usually cover their entity only, and a group-level dashboard that exposes other entities’ margins creates a problem that has nothing to do with labor law.

The Audit Trail a DOL Investigator Asks For First

In a wage and hour investigation, the first request is records, and the FLSA recordkeeping regulations at 29 CFR Part 516 set what you are expected to have: hours worked each workday and total each workweek, the basis of pay, regular hourly rate, overtime earnings, and additions or deductions. Payroll records are generally kept three years and the underlying time records two, though several states require longer and many employment attorneys recommend keeping everything longer than the federal minimum.

For a multi-entity group, the request becomes harder because the investigator wants it by person across entities, not by entity. Three things make that request answerable in an afternoon rather than a month:

• A single employee identifier that persists across every entity and assignment, so one person is one record
• An immutable edit log showing who changed a punch, when, what the prior value was, and why, since manual edits are the first thing scrutinized
• Employee attestation at the end of each pair period or week, confirming the hours recorded are complete, which is weak evidence on its own but valuable alongside a clean edit log

Groups that run multi-EIN time tracking in one system with these three elements in place generally come out of an audit with a narrow scope. Groups running six disconnected systems spend the investigation reconstructing what happened, and a reconstruction is an invitation to expand the review to other locations and other years.