Organizing ACA Reporting Across Multiple Legal Entities

Related employers can be combined when determining ALE status. That review and the allocation of reporting work are separate decisions. The IRS ALE determination guidance explains that aggregation can bring a smaller employer into an ALE group.

For 2025, each ALE member files under its own EIN, and an aggregated group does not submit a combined authoritative transmittal. See the IRS authoritative-transmittal instructions. Preserve that distinction in your project structure: maintain a central group register, then create employer-specific work packets.

Ask the scope reviewer to record which entities were considered, the applicable periods, and unresolved facts. A company logo, trade name, cost center, or payroll department is not a substitute for the employer identity that the reviewer approves.

Add a status for each field: confirmed, awaiting evidence, or requiring review. Do not treat a missing EIN as a cosmetic issue to resolve after file preparation. Identify the source of the legal name as well, because payroll abbreviations may be operational labels.

A division and a separate employer are different structures. Two operating units under one employer can create duplicate records if each unit independently prepares an annual form. Employees who move between actual employers create a different review question. Put both scenarios in the intake instructions.

For every transfer, preserve the internal person key, originating employer, receiving employer, dates, and supporting employment history. Ask the reviewer to resolve overlapping work periods rather than assigning the entire calendar year to whichever company appears in the current HR profile. The IRS employer reporting Q&A addresses reporting when an employee works for multiple employers.

A central transfer log lets both employer teams use the same confirmed timeline. It also reveals a missing receiving record, an old payroll code that remained active, or a division record accidentally treated as a new legal employer.

Fictional Harbor Cedar Group has three employers: Harbor Cedar Operations, Harbor Cedar Design, and Harbor Cedar Logistics. A qualified internal reviewer has already confirmed their ALE-member status for the example. They share a benefits administrator, while operations and logistics use the same payroll platform.

The project register creates three employer packets. Operations expects 168 person-employer records, design expects 44, and logistics expects 72, for 284 records across the packets. Six people appear in two packets because they transferred between employers during the year. The central reconciliation therefore identifies 278 unique people: 284 minus six additional employer relationships.

Those counts are fictional control totals, not a determination that every listed person requires a form. The reviewers still confirm the reporting population. The key lesson is that a group-wide distinct-person count and the sum of employer-specific records can legitimately differ without an accidental duplicate.

Require finance or legal to notify the reporting coordinator of acquisitions, disposals, mergers, new EINs, and payroll-company changes. Capture the effective date and the documents supporting the change. Avoid assuming a payroll conversion is a legal employer change, or that an acquisition always preserves the same reporting arrangement.

Freeze an approved register version before the main preparation run. If the register changes, identify every downstream item that may need regeneration: employee assignments, employer summaries, vendor accounts, employee contact information, and approvals. Have each affected employer owner acknowledge the revision.

Maintain a monthly change column even when most entities are stable all year. That structure encourages the team to notice midyear facts instead of forcing them into one annual yes-or-no entry.

Before release, compare the legal employer on the draft forms with the approved register and the vendor's account mapping. Check the expected population, unresolved transfer questions, and the employer-level summary owner. Record which version of the entity register supports the approval.

The 2025 Form 1094-C includes employer information and aggregated-group fields. Have the responsible reviewer confirm those entries against the entity review, rather than copying them from another company's draft.

Use the downloadable entity worksheet to keep evidence references together. Close the program only after each employer has a documented outcome. A central dashboard should show the status of every employer packet, so one completed submission cannot mask an unprepared entity.