ACA Year-End Reporting for Employers: How to Prepare Accurate 1094/1095 Filings

If you’re feeling like ACA year-end reporting is a January–March fire drill, you’re not imagining it. This is the part of ACA compliance where everything that happened all year, from hours and eligibility to offers, waivers, leaves, terminations, rehires, gets compressed into a set of reporting forms.

Of course, just submitting forms isn’t enough. The IRS also expects them to be clean, consistent, and defensible — something that it’s important to pay attention to all year long, because most ACA reporting problems aren’t caused by one big mistake. They’re caused by small data gaps that can pile up until you’re facing major compliance issues.

This guide is for Applicable Large Employers (ALEs) who need to get 1094/1095 done without panic, penalties, or last-minute spreadsheet archaeology. We’ll start with the basics (what ACA compliance reporting is, who has to do it, which forms matter), then move into how tracking and reporting connect over the year—because year-end reporting doesn’t start in January. It starts with how you track all year.

If you want the “checklist version” alongside this deeper guide, you can also bookmark our ACA compliance checklist. 

What is ACA compliance reporting and who has to do it?

ACA compliance reporting is how employers document to the IRS (and to employees) whether they offered health coverage that met ACA rules and whether employees were considered full-time for ACA purposes in each month of the year.

Think of it as the paper trail behind the employer mandate that shows what really happened.

ACA reporting requirements for large employers

In general, if you’re an Applicable Large Employer (ALE), you’re responsible for ACA employer reporting using Forms 1094-C and 1095-C. ALEs are employers with 50 or more full-time employees, including full-time equivalent employees, on average in the prior year.

“Full-time” for ACA purposes is generally based on the ACA definition (30 hours/week or 130 hours/month), which is exactly why the tracking side of the house matters so much. Your year-end forms are only as good as the monthly determinations behind them.

Two more important clarifiers that trip teams up:

• ACA reporting is not only for employers who offer coverage. If you’re an ALE, reporting is still required, even if you had gaps, even if you’re changing carriers, even if coverage eligibility is messy.
  
• Self-insured plans create additional reporting responsibilities (because you’re reporting who had coverage), even for employers that aren’t ALEs in certain scenarios. Most ALE-focused teams still run into this through subsidiaries, acquisitions, or plan structure changes.

Understanding ALE status and ACA ALE reporting requirements

ALE status is determined annually based on the prior year’s workforce size. That means you can drift into ALE territory faster than you expect, especially with growth, acquisitions, seasonal hiring, or variable-hour populations.

If you’re anywhere near the threshold (or you operate multiple EINs or controlled groups) this is where “we think we’re fine” becomes a risky assumption. Year-end reporting is often the moment organizations discover they should have been treating ACA as a year-round compliance motion.

Forms involved in ACA 1095 compliance reporting

Most year-end ACA reporting revolves around two forms:

Form 1095-C (Employee statement)
This is the form employees receive. It shows whether an offer of coverage was made (and what kind), month by month, and includes coding that reflects common ACA scenarios (waiting periods, offers, affordability safe harbors, etc.). The IRS is very specific about how this gets coded, because that’s how eligibility and mandate compliance is evaluated.

Form 1094-C (Employer transmittal)
This is the “cover sheet” that goes to the IRS along with your 1095-Cs. It summarizes ALE-level information and certifies the overall reporting package. It matters because it’s the IRS’s high-level frame for interpreting the employee-level data underneath.

The deadlines that drive all the pressure

For calendar year 2025 forms (the ones most employers file in early 2026), the IRS instructions note:

• The due date to furnish Form 1095-C to employees is automatically extended from January 31, 2026 to March 2, 2026.
  
• Forms 1094-C and 1095-C must be filed with the IRS by March 2, 2026 if filing on paper, or March 31, 2026 if filing electronically.

And if you file electronically through the ACA Information Returns (AIR) system, the IRS maintains the AIR program details here (we’ll come back to methods later):

None of this is meant to scare you. It’s meant to set expectations: year-end reporting has hard deadlines, and the data you need isn’t something you can reliably assemble at the last minute—especially if hours and employment status live in one system, benefits elections live in another, and payroll deductions tell a slightly different story.

That’s why the most effective ACA reporting teams treat year-end as the final step in a year-round tracking process, not an annual paperwork project.

Next, we’ll connect those dots: how ACA tracking and reporting fit together over the year, who owns which parts of the data, and the common gaps that create filing problems when it’s time to generate 1095-C codes.

 How ACA tracking and reporting fit together over the year

Take heart! There is one thing that can help ACA year-end reporting feel less brutal: 1094/1095 filing is not a standalone task. It’s the output of a year-long tracking process—one that’s only as reliable as the data feeding it each month.

When teams get crushed at filing time, it’s rarely because they don’t know what a 1095-C is. It’s because the organization treated ACA as a “forms problem” instead of a measurement + documentation problem, and those cracks only show up once you try to code Line 14/16 across twelve months for hundreds or thousands of people.

How monthly tracking drives ACA year-end reporting

ACA reporting requires month-by-month answers to questions like:

• Was this employee considered full-time (for ACA purposes) this month?
• Were they offered coverage? If so, what kind of offer, and when?
• If they weren’t offered coverage, what was the reason (waiting period, not full-time, terminated, in a limited non-assessment period, etc.)?
• If they were offered coverage, does affordability safe harbor logic apply?

Those aren’t “year-end” questions. They’re monthly determinations. The year-end forms simply summarize the outcomes.

This is why ACA tracking tends to break down in the same predictable places:

Hours aren’t captured consistently. Variable-hour populations are the classic challenge, but even “mostly full-time” orgs can have pockets of messy data: unpaid leave, different timekeeping tools, late approvals, transfers between payroll groups, or situations where the HRIS says one thing and payroll says another.

Employment status changes don’t translate into ACA logic cleanly. Rehires, leaves, terminations and reinstatements, changes in location, changes in eligibility class—these are normal HR events. But for ACA, they can change the months that need an offer, the months that fall into waiting periods, and the codes that are defensible.

The offer of coverage gets treated like a checkbox. In reality, the “offer” needs to align with eligibility, effective dates, affordability logic, and what the employee was actually offered. When those elements drift apart, you get forms that look plausible, but don’t hold up. 

The role of HR, benefits, and payroll in ACA tracking and reporting

One reason ACA reporting gets messy is that it’s cross-functional by nature, and ownership is rarely as clean as people assume.

HR usually owns the employee profile truth: hire dates, termination dates, job status, location, and classification.

Payroll and timekeeping usually own the hours truth: hours worked, leave coding, pay periods, and what happened when someone’s status shifted mid-month.

Benefits teams (or brokers/enrollment partners) often own the coverage truth: plan eligibility rules, enrollment timing, effective dates, waivers, and whether someone actually had access to coverage.

ACA year-end reporting is where those truths have to line up.

If they don’t, the work turns into detective mode: reconciling timelines, rebuilding missing logic, and trying to make a 1095-C code pattern tell a coherent story after the fact. And if you’re running a small team, one person can be left holding the bag. That’s why strong teams treat ACA compliance as a shared operational process. 

Common data gaps that cause ACA reporting issues

You don’t need to be an ACA specialist to spot the problems that lead to filing headaches. They usually show up as one of these “quiet gaps”:

• Misaligned systems of record. The HRIS shows the current status, payroll shows pay history, benefits shows enrollment elections, and none of them perfectly capture the ACA logic you need month-by-month—especially across mid-month changes.
  
• Missing or inconsistent coding for leave and status changes. Leaves of absence, unpaid time, disability, and reduced schedules can change full-time determinations and introduce limited non-assessment periods. If leave codes aren’t consistent, your ACA logic gets shaky fast.
  
• ACA eligibility and coverage offer timing that are misaligned. For example: waiting periods that are applied inconsistently, eligibility classes that weren’t updated after an acquisition, or effective dates that drift because enrollment was delayed.
  
• Controlled group or multi-EIN complexity that isn’t reflected in reporting setup. If you’ve got multiple entities, the reporting package has to reflect that reality correctly. When it doesn’t, you can end up with filings that are incomplete, inaccurate, or hard to defend.

None of this is about perfection. It’s about building a process that catches issues early—when they’re still small, and not at the exact moment you’re trying to finalize codes and generate final forms.

Preparing for ACA year-end reporting: your step-by-step process

This is the part most teams wish someone had handed them the first time they owned ACA reporting. The goal isn’t to turn you into an ACA expert. It’s to make year-end predictable: clear ownership, clean data, fewer surprises, and filings you can stand behind.

Set your ACA year-end reporting calendar and ownership

Start by backing into the deadlines and then working forward with a realistic plan. Year-end reporting tends to go sideways when it’s owned by “everyone” and scheduled by “we’ll deal with it in January.”

At minimum, define:

• Who owns the filing outcome (the person accountable for deadlines and final sign-off)
• Who owns each data stream (HR status data, hours/payroll data, benefits enrollment data)
• Who resolves exceptions (because there will be exceptions)
• Who handles employee questions once forms go out

Even if you use a vendor or partner for ACA services, internal ownership still matters. Vendors can’t fix what they don’t see, and they can’t validate business decisions for you.

If you want an easy way to structure the calendar and roles, you can also point stakeholders to our Selerix blog to align on what “good” looks like across the year. 

Gather and validate your ACA reporting data

Before you even think about codes, you want a clean “source of truth” dataset for the calendar year: who was employed in each month, who was ACA full-time in each month (by your measurement method), and what coverage was offered (and when).

This is the step that keeps you out of correction purgatory later. A good validation pass catches the classic issues early: missing SSNs, inconsistent hire/termination dates across systems, employees who bounce between entities, and anyone whose hours or status changes don’t line up cleanly with benefits eligibility.

If you only do one thing here, do this: run a “weird list”—the populations most likely to create reporting problems—then make sure you can tell a coherent story for each of them before you generate forms. Think variable-hour employees, rehires, leaves, mid-month transfers, and anyone in a waiting period.

Reconcile payroll and benefits for ACA payroll reporting

Payroll is where the hours live. Benefits is where the coverage elections live. ACA reporting is where the IRS expects the story to make sense.

This is why “ACA payroll reporting” by itself is usually incomplete: payroll can tell you what someone worked and what deductions happened, but it often can’t tell you whether an ACA offer was made correctly, what affordability safe harbor applies, or how to handle limited non-assessment periods. Meanwhile, benefits systems may show elections and effective dates, but not the underlying hour-based eligibility logic that drives ACA full-time status.

Reconciliation is the bridge. The goal is to confirm that:

• The people marked full-time for ACA purposes align with hours/timekeeping reality.
• The offer of coverage (or reason no offer was required) aligns with employment status timing.
• Deductions and coverage effective dates line up enough that an employee dispute won’t turn into an investigation.

Prepare 1095-C codes and review edge cases

Coding is where a lot of teams get nervous—and for good reason. The codes on Form 1095-C are essentially the IRS’s shorthand for “what happened here, month by month.” If the codes don’t match the underlying reality, you can end up answering employee questions, issuing corrected forms, or defending filings later.

Two practical tips that make this less intimidating:

1. Don’t code from memory. Code from scenarios. Build a short list of your most common employee situations (new hire waiting period, variable-hour measurement, ongoing full-time, leave of absence, termination mid-month, rehire) and make sure you can code each one consistently.
   
2. Treat edge cases as a required workflow, not a side quest. The tricky cases are always the same: employees who change status mid-year, employees with leaves that affect measurement, and employees who move between entities or EINs. These are the people who break “default” logic.

If it helps, Selerix has an ACA codes resource that walks through common Line 14/16 logic in plain English. 

Choose your ACA reporting method and platform

At a high level, you have three common paths:

• In-house preparation + electronic filing (usually feasible only if you have the expertise, time, and tooling)
  
• Payroll/HRIS-supported reporting (works in simpler environments; often breaks down with variable-hour, multi-EIN, or frequent change)
  
• Specialist ACA software and/or services (best when you want defensibility, audit trails, and fewer surprises)

If you’re filing electronically, the IRS uses the ACA Information Returns (AIR) system. (IRS)

Also important: if you have 10 or more information returns, electronic filing is required (and that threshold applies broadly to information returns). (IRS)

Run test files and pre-filing quality checks

The best ACA teams treat filing like a launch: you don’t ship the first version.

Before you finalize:

• Run a test generation of your 1095-Cs and review a sample across your “weird list” populations.
• Confirm your totals and counts make sense at the employer level (what 1094-C will summarize).
• Spot-check for missing data fields that will cause rejections or employee confusion.
• Make sure you have a plan for employee delivery (especially if you’re using electronic distribution options).

If you’re filing through AIR, the IRS provides an Assurance Testing System (AATS) for test scenarios, which is helpful if you’re close to the mechanics. (IRS)

Key ACA year-end reporting deadlines and penalties

For calendar year 2025 reporting (filed in 2026), the IRS instructions list these key due dates:

• File Forms 1094-C and 1095-C with the IRS by March 2, 2026 (paper) or March 31, 2026 (electronic). (IRS)

Penalties are where putting off problems gets expensive. The IRS can assess penalties per return for failures to file correctly/on time and failures to furnish correct statements to employees. For returns due in 2026, the IRS penalty table shows (per return/statement): $60 (up to 30 days late), $130 (31 days late through August 1), $340 (after August 1 or not filed), and $680 (intentional disregard). (IRS)

Avoiding common ACA reporting pitfalls

Most ACA reporting pain comes from a short list of predictable issues:

• Assuming your HRIS “ACA module” is doing continuous measurement. Storing data isn’t the same as evaluating ACA outcomes monthly.
  
• Treating variable-hour employees like a year-end cleanup exercise. Measurement period logic has to run all year, or you end up guessing.
  
• Letting “edge cases” pile up until January. Rehires, leaves, and mid-year status changes need a consistent rule set.
  
• Relying on payroll deductions as proof of an ACA offer. Deductions can help validate the story, but they don’t tell you what offer was made (or what should have been made).

When payroll is not enough for ACA compliance reporting

Payroll is essential, but it’s not built to be your ACA compliance engine.

If your workforce is stable, mostly full-time, and cleanly integrated, payroll-supported reporting might be “good enough.” But payroll alone tends to struggle when:

• You have variable-hour, seasonal, or high-turnover populations
• You use measurement and stability periods
• You have multiple EINs or controlled group complexity
• Employees shift locations, eligibility classes, or status mid-year
• You’ve ever had to issue corrected 1095-Cs (or suspect you should have)

In those environments, ACA is less about producing forms and more about proving month-by-month determinations with an audit trail.

How Selerix supports ACA reporting compliance for employers

Selerix ACA solutions are built for the part that’s hardest to do with spreadsheets and best intentions: year-round tracking, defensible logic, and clean year-end outputs.

In practical terms, that means:

• Ongoing eligibility measurement that doesn’t wait for January
• Controls to catch data gaps early (before they become code problems)
• Audit-ready reporting and documentation
• Year round support from a team of tenured experts

FAQs on ACA year-end reporting and 1094/1095 filings

Do small employers ever have to worry about ACA year-end reporting?
Usually, ACA employer reporting is an ALE requirement. But smaller organizations can still run into reporting obligations depending on plan structure (for example, certain self-insured arrangements) or if they’re part of a controlled group. When in doubt, confirm your ALE determination annually and document it.

If I use a PEO or fully insured plan, do I still have ACA reporting responsibilities?
Often, yes. Using a PEO or being fully insured doesn’t automatically remove employer reporting responsibilities. The specifics depend on who is treated as the ALE and how offers and coverage are administered. This is a good place to get clarity early—before forms are generated.

How long do I need to keep ACA reporting records?
Keep documentation that supports your month-by-month determinations and what was furnished/filed, in case questions come up later. (Your legal/tax advisors can give retention guidance aligned to your risk posture.)

How does ACA year-end reporting interact with state individual mandate reporting?
State reporting requirements can differ by state and may involve different forms, timelines, and data needs. If you have employees in states with individual mandates, plan for those requirements as a parallel workstream—not an afterthought.

Can ACA payroll reports replace a dedicated ACA reporting solution?
Payroll reports are helpful inputs, but they typically don’t handle the full ACA measurement and coding logic, especially for variable-hour employees, safe harbors, limited non-assessment periods, and audit defensibility. If the cost of being wrong is high for you, relying on payroll alone is usually where teams get surprised. 

You don’t have to white-knuckle the ACA season. The Selerix ACA team can help you with any level of support, before deadlines force your hand. Reach out to connect with our ACA specialists.