For Tribal governments that own or operate casinos, hotels, retail businesses, and other enterprises, understanding how the Affordable Care Act’s aggregation rules apply to your structure is critical. The concept of ‘control’ — as defined by IRS rules, not everyday usage — can determine whether your Tribal government and its related entities are treated as a single employer under the ACA. For CFOs, HR directors, and controllers across Tribal operations, getting this analysis right affects ALE status, penalty exposure, and reporting obligations.
When ACA questions come up for Tribal employers, the conversation often lands on one word that sounds simple but gets complicated fast: control.
This is not “control” in the everyday sense of who runs meetings, supervises staff, or manages the casino floor. In the ACA world, control is a legal and tax concept that can determine whether a Tribe and its related enterprises are treated as one employer. That matters because it can change whether the organization is considered “large” under the ACA—and it can also shape what needs to be filed and by whom.
When Does the ACA Employer Mandate Apply?
The ACA’s employer mandate applies when an employer is an Applicable Large Employer (ALE). The familiar threshold is 50 or more full-time employees, including full-time equivalents, based on the prior year’s average.
For Tribes, the key question often is not, “Does the Tribe have 50 employees?” It’s more like: “Do we have 50 employees when we count everyone across the Tribal government and the enterprises the Tribe owns or controls?” That’s where the idea of aggregation comes in.
Key Question:
Do we have 50 employees when we count everyone across the Tribal government and the enterprises the Tribe owns or controls?
What Does “Aggregation” Mean?
Aggregation is essentially the IRS saying: if several entities are closely related, they may have to be treated like one employer for counting employees to determine whether the employer mandate applies. The ACA leans on long-standing IRS concepts—often discussed under Internal Revenue Code §414(b), (c) for control groups, and (m) for affiliated service groups—to decide when different entities must be counted together.
In practical terms, it means a Tribal government and its casino, hotel, retail operation, utility authority, or other enterprises might not be allowed to look at employee counts separately. The IRS may require the Tribe to add them together to see if the overall employer group meets the 50-employee ALE threshold.
Why is ACA ‘Control’ More Complex for Tribal Employers?
In the private sector, this analysis is sometimes easier because ownership is usually obvious: a parent company owns subsidiaries, stock percentages are clear, and the legal structure is familiar.
Tribal structures can look very different. Enterprises might be formed under Tribal law, under Section 17, under state law (LLCs or corporations), or through authorities and instrumentalities created for specific functions like housing, utilities, or economic development. Sometimes there are joint ventures with non-Tribal partners. Because of that variety, you can’t always answer “Who owns this?” by looking for stock certificates or a typical shareholder chart. That’s why “control” becomes the center of the conversation—because the real question is whether the Tribe effectively owns or controls the enterprise in a way that triggers ACA aggregation.
What’s the Difference Between Ownership Control and Governance Control?
One of the most helpful ways to make this topic understandable is to separate “control” into two categories: ownership control and governance control. They often point in the same direction, but they are not the same thing.
Ownership Control
Ownership control is the concept that usually drives aggregation. It’s about whether the Tribe (or a Tribal instrumentality) has ownership-style rights that function like owning the business. In a typical corporate structure, that might be measured by stock ownership and voting power. In Tribal enterprises, the structure may not look like that, but the idea is similar: does the Tribe have the right to the profits or net revenues, the ability to replace the entity, the authority to dissolve it, or other rights that amount to ownership in substance?
Governance Control
Governance control is about who directs the entity—who appoints the board, who has to approve budgets, who signs off on major borrowing or contracts, and who ultimately oversees the operation. In many Tribal structures, governance control is very strong: the Tribal council may appoint and remove board members, require approval of budgets and major decisions, and centralize HR or benefits functions across enterprises.
Here’s the important nuance: governance control often supports the conclusion that entities are related, but aggregation for ACA purposes usually turns on ownership-style control as defined under IRS rules. In other words, being able to oversee an enterprise does not always equal “control” under the technical controlled group standards—although in many Tribal structures the two are closely aligned.
A simple way to explain the difference is this: ownership control answers, “Who ultimately owns the economic benefits of the business?” Governance control answers, “Who has the authority to direct the business at the board or oversight level?” For many Tribes, the answer to both questions is “the Tribe,” but joint ventures and some authority structures can make the answer less obvious.
How Does ACA Aggregation Work in Tribal Enterprise Structures?
One of the most common situations is a Tribe that owns multiple enterprises—say a casino, a hotel, and a convenience store—each with its own EIN and payroll. It’s easy to assume each operation can stand alone for ACA purposes. But if the Tribe owns and controls them, the ACA often treats them as related entities under common control, which means the employees may need to be counted together to determine ALE status. Controlled group rules are designed to prevent employers from avoiding ACA obligations by splitting employees among separate entities.
Another common setup is government employees on one payroll and enterprise employees on separate payrolls. Even then, if the Tribe’s ownership/control ties the entities together, they may still be treated as part of the same aggregated employer group for ALE determination. That’s where coordination becomes essential—because someone has to track hours, determine full-time status, manage offers of coverage, and ensure the right entity files the right forms.
Authorities and instrumentalities add another layer. Some operate like an extension of Tribal government, while others are structured with more separation. Whether they’re treated as part of the same controlled group can depend heavily on how they are formed and governed.
Does Aggregation Mean One Combined ACA Filing?
This is another point that causes confusion. Even if a Tribe and its enterprises are aggregated for purposes of determining whether they meet the 50-employee threshold, that does not automatically mean everything is filed as one combined ACA report.
In many cases, each separate employing entity—often each EIN—still files its own ACA reporting forms (Forms 1094‑C and 1095‑C, if applicable). What changes is that the entities may need to identify that they are part of an aggregated ALE group and coordinate reporting so the overall picture is accurate and consistent.
A good way to say it is: you may be treated as “one employer” for counting employees, but still have multiple reporting entities.
What Are the Risks of Getting ACA Aggregation Wrong?
This isn’t just a filing exercise. If aggregation pushes the overall group above the ALE threshold, the employer mandate rules can apply, and mistakes in offers of coverage, eligibility tracking, or reporting can lead to penalty exposure. It can also create operational issues when employees move between enterprises, work variable-hour schedules, or are measured differently by different HR teams.
Penalty Exposure
Mistakes in offers of coverage, eligibility tracking, or reporting can lead to significant penalties
Operational Issues
Problems arise when employees move between enterprises, work variable-hour schedules, or are measured differently by different HR teams
Compliance Gaps
Failing to recognize aggregation requirements can create gaps in coverage offers and reporting obligations
How Should Tribal Employers Start Their ACA Aggregation Analysis?
When Tribes begin working through these questions, the most useful first step is simply mapping the structure: what entities exist, which ones have employees, how payroll is handled, how benefits are offered, and what the governance and ownership documents say. Once that picture is clear, it becomes much easier to evaluate whether aggregation likely applies and what reporting responsibilities follow.
Mapping your controlled group structure is the critical first step — and you don’t have to figure it out alone. REDW’s HR Consulting team has deep experience helping Tribal governments and their enterprises navigate ACA aggregation, reporting coordination, and compliance. Connect with our team to start your analysis.
