Nobody thinks about holiday pay in October. Then Thanksgiving week arrives, half the warehouse works the holiday and the other half doesn't, three supervisors interpret the policy three different ways, and payroll gets a timecard file that raises more questions than it answers. Who gets the paid holiday? Does the crew that worked get time-and-a-half, double time, or holiday pay plus their hours? And why does the overtime calculation look strange on every check that week?
December is worse. Two holidays in one month, compressed processing calendars, year-end bonuses in the mix, and employees watching their checks more closely than at any other time of year. Holiday pay mistakes are rarely large in dollars, but they are always large in noise, because they land on the paychecks people were counting on for the holidays.
Here's the thing: holiday pay problems in December are almost never December problems. They're policy ambiguities and setup gaps that sat quietly all year until the holiday-dense season stress-tested them. Fix the policy language and the ADP Workforce Now earnings setup now, in the calm, and the season runs itself. Here's what to look at.
Most confusion starts because "holiday pay" means two different things, and companies often have both. The first is the paid holiday: the office is closed, the employee doesn't work, and they're paid anyway, typically eight hours at their regular rate. It's a benefit for not working.
The second is holiday premium pay: the business operates on the holiday, the employee works, and they earn extra for it, commonly time-and-a-half or double time, or their regular rate plus a separate holiday benefit payment. It's compensation for working a day most people have off.
A single company can owe one employee the first, another the second, and a third both, on the same day. Your policy needs to state, in plain language, what happens in each case: employee off on the holiday, employee working the holiday, and employee scheduled off anyway (does someone who never works Thursdays get anything for a Thursday holiday?). If the policy answers those three situations clearly for every employee group, most December disputes never happen.
Worth saying plainly: for private employers, federal law generally doesn't require paid holidays or premium pay for holiday work; a holiday is legally just another workday unless your policy, a contract, or a collective bargaining agreement says otherwise. That means your policy is the law of your company, which is exactly why it needs to be written well. A few states and localities have their own quirks for certain industries, so confirm the rules where you operate.
Eligibility is where identical-sounding policies diverge in practice. Common dividing lines: full-time versus part-time (and if part-timers get holiday pay, is it prorated by scheduled hours?), a waiting period for new hires (hired December 20, paid for December 25?), and the classic attendance condition, requiring employees to work their scheduled day before and after the holiday to earn the paid holiday, a rule designed to prevent the four-day-weekend engineered around a sick day.
If you use the scheduled-day-before-and-after rule, define its edges: does an approved vacation day count as "worked"? A doctor's note? And decide who verifies it, because a rule payroll can't verify is a rule that gets applied unevenly. Also decide how holidays interact with leave: employees on FMLA or other leave during a holiday, employees on light duty, and employees who quit or are terminated the day before a paid holiday. None of these are hard decisions, but every one of them will come up eventually, and December is the worst time to decide.
Write the answers down, publish them where employees can see them, and make sure timekeeping supervisors apply one rulebook. Half the "payroll errors" we investigate in December turn out to be three supervisors applying three private interpretations of the same sentence.
This is the technical piece that produces the most quiet errors. Two principles cover most of it.
First: paid time off for a holiday is generally not "hours worked" for federal overtime purposes. An employee who takes Monday as a paid holiday and then works four ten-hour days has 40 hours worked plus 8 hours of holiday benefit; under the federal weekly standard, the overtime threshold looks at the hours worked. Whether your company chooses to count holiday hours toward overtime anyway is a policy decision, a more generous one, and some companies make it deliberately. The mistake is not knowing which one your setup is doing.
Second: when employees work the holiday for a premium, the premium interacts with the regular rate of pay, the basis for overtime calculations. As general guidance, certain true premium payments, like time-and-a-half or better for holiday work, may be treated differently in the overtime math than flat extra amounts, and the details matter. The practical takeaway isn't to memorize the regulations; it's to know that holiday premiums and overtime in the same week is exactly the scenario where miscalculations hide, and to have someone qualified confirm your setup handles it the way your policy and the rules intend. State rules can differ from federal, and a few states add daily overtime on top. When holiday weeks also include weekly overtime, check those checks by hand at least once.
Once the policy is clear, the ADP setup should mirror it exactly. The clean pattern is separate earnings codes for separate concepts: one code for the paid holiday benefit (holiday pay, not worked), one for holiday premium (worked the holiday), and your normal codes for regular and overtime hours. Resist the shortcut of paying holiday benefit hours through the regular-hours code; it saves a minute of setup and costs you all visibility, because you can never again report on what holidays cost, and the overtime treatment can't be controlled per code.
For each code, confirm four settings against your policy: the pay rate it uses (regular rate, a multiplier, or a flat amount), whether its hours count toward overtime calculations, how it's taxed (holiday earnings are ordinary wages), and how it maps to the general ledger. That second setting, the overtime flag, is the single most common mismatch we find: policies that say holiday hours don't count toward overtime, sitting on top of codes configured to count them, or vice versa. The checks look plausible and nobody notices until someone runs the math.
Then test before the season. Take last year's Thanksgiving week timecards, or build a sample: one employee off for the holiday, one who worked it, one with both holiday pay and 44 hours worked. Run them through a preview and verify each check against a hand calculation. Twenty minutes of testing in early November beats an audit of hundreds of checks in December.
Floating holidays, the "pick your own" days many companies offer alongside fixed holidays, deserve their own paragraph in the policy and their own handling in the system. Decide: how many float days per year, whether they're granted upfront or accrued, whether new hires get a prorated number, whether unused days carry over or expire, and, importantly, whether they're paid out at termination. That last one isn't purely a policy choice; some states treat floating holidays like vacation, which can make them earned wages that must be paid out, so check the rules in your states.
In the system, floating holidays work best as a tracked balance, like a small PTO bank, with requests and approvals flowing through time off tracking rather than free-typed hours on a timecard. A floating holiday paid through a generic code with no balance behind it is how employees end up taking five float days in a two-day program, and how terminations end up in disputes about what was owed. Give the float its own earnings code, its own balance, and its own line in the policy, and it becomes the easiest benefit you administer.
A client running a distribution operation, about 220 employees, came to us in January after a rough December. Their policy said employees who worked a holiday received time-and-a-half for hours worked, and holiday benefit hours did not count toward overtime. Simple enough on paper.
The setup told a different story. Their holiday benefit code was configured to count toward overtime, and holiday premium hours had been entered by supervisors as regular hours plus a manual "adjustment" line because nobody had built a premium code. In Thanksgiving week, an employee who took the paid holiday Monday and worked 40 hours Tuesday through Saturday showed 48 hours toward overtime, generating 8 hours of overtime pay the policy didn't intend. Roughly 60 employees were in that situation across the two holiday weeks in November and December. Meanwhile, the manual premium entries were inconsistent: some supervisors entered 1.5 times the hours, some entered the hours expecting the system to apply a multiplier that didn't exist, so two employees who worked the same holiday shift earned visibly different pay, and both of them compared stubs in the break room.
The dollar total, once we reconstructed it, was about $9,800 in unintended overtime and a set of underpayments to correct in the other direction. The fix took an afternoon: a true holiday-premium earnings code at 1.5x, the overtime flag on the benefit code corrected to match policy, and a one-page supervisor guide for holiday-week timecards. The next December produced zero holiday pay corrections. Not fewer. Zero.
For most private employers, no; federal law generally treats holidays as ordinary workdays, and paid holidays or premiums are company policy or contract terms, not federal mandates. A few states and industries have specific rules, so check where you operate. Legally optional doesn't mean operationally optional, though: once your policy promises it, you owe it, consistently.
Often yes, and this is exactly the week to check by hand. Overtime is computed on hours worked against the applicable threshold, and holiday premiums may factor into that math in ways that depend on how they're structured. Pull one or two such checks each holiday week and verify them manually; if the numbers don't match your expectation, confirm the setup with someone qualified before the next run.
It depends on your policy language and your state. Some states treat floating holidays like earned vacation, which can make payout mandatory; policy wording about whether days are "earned" versus "granted" matters too. Decide the answer deliberately, write it into the policy, and confirm it with employment counsel for each state where you have employees.
The companies that sail through December did the work in October. Their holiday policy answers the three situations, off, worked, and not scheduled, for every employee group, in language a supervisor can apply without calling HR. Their earnings codes match the policy one-to-one, with overtime flags verified, and they re-test with a sample timecard each fall because policies and setups drift. Floating holidays live in a tracked balance. Supervisors get a one-page holiday-week timecard guide before Thanksgiving. And payroll hand-checks a couple of holiday-plus-overtime checks each season, not because they expect errors, but because that's how you keep expecting none.
If your policy and your setup have never been checked against each other, or last December left scar tissue, we can help before this one arrives. Ignite HCM consultants are former ADP service professionals working with ADP clients exclusively; we've configured and repaired holiday pay setups across every industry that works weekends and holidays. No tickets, no hold queues — a dedicated consultant who reads your policy, tests your codes, and gets it right before the season starts. Your people need to get paid. We make that happen.
Want December's payroll to be the quiet kind? REQUEST A CONSULTATION.
ADP and the ADP logo are registered trademarks of ADP, Inc. This article is general guidance, not legal or tax advice; overtime and wage rules vary by state and change over time, so confirm specifics with your licensed advisor and official federal and state sources.
