The practical answer
Build the annual 1095-C population using the reporting year, ALE member and employee identity. Combine records from divisions of the same ALE member into the appropriate single employee return. Separate ALE members report under their own EINs, with employee-month attribution reviewed under the employer instructions.
This guide is for employers consolidating payroll and benefits records before creating Forms 1095-C. Duplicate employee profiles can become duplicate agency returns when each source system independently creates its own annual form. The control belongs before filing, while the organization can still resolve identity and month ownership.
The 2025 employer instructions distinguish divisions within one ALE member from employees working for different ALE members. Use that distinction to design the reconciliation, rather than applying one blanket deduplication rule to every shared name.
Define the employee-return identity before importing records
Create an internal key for reporting year, legal employer EIN and employee identity. Retain each contributing payroll identifier as a source reference. A rehire or payroll-system migration can create a new internal ID without creating a new person or a new ALE member.
Use controlled identity matching rather than names alone. Two employees can share a name, and one employee can change a name during the year. Compare the authoritative personnel record and the full required filing identity within the approved system, while keeping general reconciliation worksheets free of unnecessary SSNs. Document ambiguous matches before a reviewer combines records.
Consolidate same-ALE-member divisions
The IRS instructions require one Form 1095-C for a full-time employee's employment with an ALE member. If separate divisions report under the same ALE member, combine the employee's monthly offer and coverage information into one annual return. A division label is useful for source ownership but is not a new employer identity.
Review overlapping months when the employee changes divisions. Decide which source supplies the authoritative rate, offer and enrollment facts. Do not concatenate two partial records and silently let the last imported row overwrite the first. Preserve the source priority rule and any manual resolution with the approved combined record.
Keep separate ALE members distinct
Each ALE member files under its own EIN, including members that have fewer than 50 employees themselves when the aggregated group meets the ALE rules. A common payroll vendor, shared benefits plan or parent company does not turn their employee returns into a single group return.
An employee who works for multiple members can require separate Forms 1095-C. For a month involving more than one member, apply the employer attribution rules in the instructions, generally considering where the employee worked the greatest number of hours of service. Retain the monthly determination and any applicable tie resolution instead of deleting one member's record merely because the SSN appears elsewhere.
Fictional example: two divisions share ten employees
Fictional Summit Services has one EIN and two payroll divisions. Division North exports 60 employee records and Division South exports 50. Ten employees transferred between divisions during 2025 and appear in both files. Identity review confirms there are no other overlaps and that all 100 unique employees belong in the employer's filing population.
| Measure | Count | Meaning |
|---|---|---|
| North export | 60 | Source records before consolidation |
| South export | 50 | Source records before consolidation |
| Confirmed duplicate people | 10 | Same employer and reporting year |
| Expected annual returns | 100 | 60 + 50 - 10 unique employee returns |
The ten merged records need twelve-month review, not just removal from a count. If one person's April offer differs between systems, resolve the conflict before releasing the combined annual record. A separate subsidiary EIN would require a separate analysis rather than being folded into this arithmetic.
Distinguish duplicate originals from valid corrections
A repeated employee key can also represent a draft, a corrected record or a reprint. Track the version and filing status separately from identity. Do not deduplicate a legitimate correction out of the workflow, and do not transmit an original again because an employee asks for another copy.
Record the original return reference and the reason a later record exists. If duplicate reporting has already reached the IRS, investigate the accepted submissions and follow the applicable correction or support process. Deleting a duplicate from your local database does not remove a previously filed agency record.
Approve count and month ownership together
Before release, compare unique employee keys with the final filing population, record excluded source duplicates and reconcile the related transmittal counts. Ask a second reviewer to sample transfers, rehires and shared-plan employees because these are where a simple row-count check can miss an incorrect annual story.
The sign-off should identify the exact input extracts, matching rules and resolved exceptions. Retain the final employee-to-return crosswalk with transmission evidence. This lets the business answer a later employee inquiry or correction request without reassembling several payroll exports from memory.
Employee return consolidation
Read the workflow as text
- Identify the employer. Match year, ALE member EIN and employee.
- Combine same-member records. Resolve division and payroll-system overlaps.
- Review separate members. Apply the employee-month attribution rules.
- Release unique returns. Preserve the source-to-return crosswalk.
Put this guide to work
1095-C employee-to-return consolidation worksheet
Save the editable text worksheet and use it with your own records. Keep completed copies in your secure working files.
Download the worksheet TXTCommon questions
Can each division file its own 1095-C for the same employee?
Not simply because it operates a separate payroll. For employment with the same ALE member, consolidate the information into the appropriate single annual employee return. Separate ALE members require their own analysis and report under their own EINs.
Should the parent company combine all subsidiary returns?
The parent can coordinate preparation, but each ALE member reports under its own EIN. Do not replace separate member returns with one parent-company employee statement merely because the group uses one benefits plan or filing vendor.
Does a second payroll ID justify another form?
No. A payroll ID is a source-system reference. Determine whether it represents the same employee and legal employer, then combine the relevant months and resolve conflicts before producing the annual return.
Can the same employee appear under two employer EINs?
Yes, when the separate ALE-member reporting rules call for it. Review employee-month attribution under the instructions. A cross-EIN match should create a review item rather than an automatic deletion.
What if we already transmitted duplicate originals?
Identify exactly which submissions and employee records were accepted, then follow the applicable correction or IRS support procedure. Preserve the original references; a local record deletion or an unmarked replacement PDF does not reverse an agency filing.
Official sources and scope
Sources checked September 5, 2026. Use the edition for the tax year and filing method you are working with; later instructions may change thresholds, fields, or procedures.
- IRS 2025 Instructions for Forms 1094-C and 1095-C
Employer filing populations, form fields, monthly offer/enrollment distinctions, employer identification, corrections and furnishing for 2025 reporting.
- IRS employer reporting questions and answers
Employer reporting responsibility and the relationship between ALE-member and employee returns.
