The ACA employer mandate is not optional. If your company has 50 or more full-time employees and you fail to offer affordable minimum essential coverage — or you offer coverage that doesn't meet affordability standards — the IRS assesses penalties of $2,970 per affected employee in 2025, scaling upward annually. For a mid-market company with 300 employees, a configuration error that causes an ACA violation can mean six-figure penalty exposure. The uncomfortable truth: most Dayforce customers with penalty exposure don't have a compliance intent problem. They have a Dayforce configuration problem.
What ACA penalty exposure actually means for Dayforce customers
The ACA employer mandate requires applicable large employers (ALEs) — those with 50 or more full-time equivalent employees — to offer health coverage that meets two tests: minimum value and affordability. If you fail either test and an employee receives a premium tax credit through the marketplace, the IRS can assess a penalty back to the date of the failure.
The penalty is calculated on a per-employee basis: $2,970 per employee in 2025 (rising with inflation). But it is not applied to your entire headcount — it is applied to the subset of employees who received a marketplace premium tax credit. That number depends on whether you offered coverage at all, whether coverage was affordable, and whether it met minimum value.
The part that catches most Dayforce customers off guard: the failure is measured against your coverage offer, not your intent. If your Dayforce configuration generates incorrect 1095-C codes — codes that incorrectly flag an employee as not offered coverage when they were, or that misrepresent the coverage tier — the IRS interprets that as a failure to offer coverage. The penalty follows automatically.
How Dayforce generates and files your 1095-C codes
Need hands-on help with Dayforce?
Talk to our team →Dayforce is the system of record for your ACA reporting. Each year, it generates Form 1095-C for every employee who was enrolled in coverage (or was offered coverage but declined). The code combinations in Part II of the 1095-C tell the IRS whether you offered coverage, what type of coverage you offered, and whether the employee enrolled.
Dayforce generates these codes based on configuration you set up at implementation: offer periods, coverage tier assignments (Employee Only, Employee + Spouse, Employee + Children, Family), affordability safe harbors, and HR eligibility rules. If any of those configurations are wrong — or if they drift from your actual benefit plan design — the codes Dayforce generates will be wrong.
The complexity is that Dayforce is computing this across your entire employee population, every month, for the entire year. One configuration error in a benefits plan rule can corrupt thousands of codes. You will not find it by spot-checking a few employees. You need a systematic audit.
Three configuration failures that trigger ACA penalties in Dayforce
Struggling with Dayforce Consulting?
Harmon & Co specializes in Dayforce consulting for mid-market companies. We fix it the first time — no endless ticket queue, no generic advice.
