Every December, the same call comes in. A payroll manager opens the new year's schedule, spots a pay date sitting on a bank holiday, and realizes the whole calendar was copied forward from last year without anyone checking it. Now direct deposits will land late in January, the first month of a new fiscal year, right when leadership is watching everything.
It is an avoidable problem, and it is one of the most common ones we fix. A payroll calendar looks simple from the outside: pick the dates, load them, done. But pay frequency rules, banking holidays, period-end alignment, and the occasional 27-pay-period year all hide inside that "simple" grid. Miss one detail and you spend the year making manual corrections instead of running payroll on autopilot.
Here is the good news. Building a clean calendar in ADP takes an afternoon of focused work if you do it in the right order, and October is exactly the right time to start. Walk through the steps below and you will head into January with a calendar you never have to think about again. Your people need to get paid. We make that happen.
Before you touch a single date, confirm the frequency for every pay group you run. Weekly, biweekly, semimonthly, monthly. Many companies run more than one: hourly staff on biweekly, executives on semimonthly, a small owner group on monthly. Each frequency needs its own calendar, and each one has its own quirks.
This is also the moment to ask whether your current frequency still fits the business. State rules set minimum pay frequencies for certain worker types, and some states require more frequent pay for hourly employees than for salaried ones. If you have expanded into new states this year, a frequency that was compliant in your home state may not be compliant everywhere you now have people. Changing frequency mid-year is painful, so if a change is coming, plan it for the start of the new year and build the new calendar around it from day one.
One more check: make sure every employee is actually assigned to the pay group you think they are in. We regularly find employees sitting in a legacy pay group nobody uses anymore, quietly inheriting the wrong schedule. A ten-minute audit now beats a missed paycheck in February.
The Federal Reserve does not move money on federal holidays, and neither does the ACH network. If a scheduled pay date lands on a holiday or a weekend, the deposit does not arrive that day. That is the single most common calendar error we see, and it is completely predictable a year in advance.
Pull the list of federal banking holidays for the new year and lay it next to your draft pay dates. Watch for the usual troublemakers: New Year's Day, Martin Luther King Jr. Day, Presidents Day, Memorial Day, Juneteenth, Independence Day, Labor Day, Columbus Day, Veterans Day, Thanksgiving, and Christmas. Some of these float, and a holiday that missed your pay dates last year can land squarely on one this year.
For each collision, decide your rule and apply it consistently: pay the business day before, or the business day after. Most employers pay early, because paying late creates real hardship for employees and, in some states, a compliance problem. Whatever you choose, write the rule down. When someone asks in July why the pay date moved, you want a documented policy, not a shrug.
Remember that moving the pay date also moves your processing deadline. If Friday's payroll now pays on Thursday, your submit-by date shifts a day earlier too, and so does the deadline for approvals, timecard sign-off, and any funding wires. Build the whole chain backward from the new pay date, not just the deposit day.
Pay date and period end are two different things, and the gap between them matters more than most people think. The number of days between the end of the work period and the day people get paid is your processing window. Too tight, and every payroll becomes a fire drill: chasing timecards, rushing approvals, no room for a single error. Too loose, and employees wait an uncomfortably long time for hours they already worked, which some states restrict.
A common healthy pattern for biweekly payroll is a period ending Saturday or Sunday with a pay date the following Friday. That gives you the early part of the week to collect and approve time, run previews, and fix problems before you commit. If your current setup gives you less than three business days between period end and pay date, treat the new calendar as your chance to widen the window.
Also check that period-end dates flow cleanly into the quarters. Payroll taxes report on a quarterly basis by pay date, so know which December-worked, January-paid payroll belongs to which year. Wages are generally taxed in the year they are paid, not the year they are earned, and your calendar should make that boundary obvious rather than ambiguous.
If you pay biweekly, most years hold 26 pay periods. But 26 periods of 14 days only covers 364 days, so roughly every 11 years the calendar serves up a 27th pay date. Weekly payrolls hit the same effect as a 53rd period. Whether the new year is one of those depends on your specific pay dates, so count them. Do not assume.
Why it matters: salaried employees paid a fixed annual amount divided by 26 would receive an extra period's pay if you simply run 27 periods unchanged. Benefits deductions calculated per pay period will collect one extra time. Annual deduction goals may hit their caps a period early. Employers handle this a few different ways, from absorbing the extra period as an extra payment, to dividing annual salary by 27 for that year, to adjusting deduction schedules so totals still land where they should.
There are pay-timing, employee-relations, and plan-document considerations in that choice, so decide deliberately and communicate early. What you do not want is to discover the 27th period in November, after 26 periods of deductions have already been taken. Count your pay dates in October, while every option is still open.
Once the dates are settled on paper, load them. In ADP Workforce Now, payroll schedules drive far more than the check date. They set your processing deadlines, feed accrual calculations, control when time and attendance periods close, and determine when general ledger entries post. A calendar entered correctly once pushes clean dates to every corner of the system.
Set up the full year, not just the first quarter. Verify each pay group separately, confirm the adjusted dates around every holiday, and check that the first payroll of the year picks up exactly where the last payroll of the old year ends, with no orphaned days between periods and no overlap. Then run your eyes over the quarter boundaries one more time: the last pay date of each quarter should be unmistakable.
Finally, preview the first payroll of the new year early. A dry run in December surfaces mismatched period dates, stale deduction schedules, and pay group errors while there is still time to fix them calmly.
A perfect calendar that nobody knows about still generates a flood of questions. Publish the full year's schedule to employees before January: pay dates, period ends, and any dates that moved for holidays, with a one-line reason. Post it where people actually look, and give managers their own version showing timecard approval deadlines.
Do not forget your internal partners. Finance needs the calendar for cash planning and accrual timing. Benefits needs it to schedule deduction changes. HR needs it for new-hire start date planning, since a start date two days before period end creates a tiny first check and a confused new employee. One shared calendar, distributed once, prevents a hundred one-off emails.
A client running biweekly payroll for about 220 employees came to us in early December, having copied the prior year's calendar forward in ADP without review. Three problems were hiding in it. Two pay dates in the new year landed on federal holidays, so those deposits would have arrived a day late. The new year was also a 27-pay-period year for their pay dates, which nobody had noticed. And their processing window was two business days, which explained why every payroll felt like a sprint.
We rebuilt the calendar in about a week. The two holiday collisions moved to the prior business day, with processing deadlines shifted to match. For the 27th period, leadership reviewed the options and chose to keep per-period salaries unchanged and treat the extra date as an additional pay period, while we adjusted the per-period benefits deduction schedule so annual totals still landed on target, roughly $18 per period lower for the typical medical election instead of a surprise double-take later. We also pushed the period end back one day, widening the processing window to three business days.
Total effort was about six hours of consulting time plus the client's internal reviews. Compare that to the alternative: two late payrolls, a benefits over-collection to refund across 220 people, and a year of rushed processing. The calendar is boring now. That is the goal.
No single federal rule forces a direction, but paying late can violate state pay-timing requirements and always frustrates employees. Most employers move the deposit to the prior business day. Pick one rule, document it, and apply it all year.
Yes, and the start of a year is the cleanest time to do it. Plan for state frequency rules, employee communication, and a transition period where deductions and accruals need remapping. Give yourself at least sixty days of runway.
Loaded and verified in ADP by early December, published to employees before the holidays. That leaves December's payrolls as live rehearsals with the old calendar while the new one sits ready.
Here is the standard worth aiming for. Every pay date for the year is loaded, holiday-checked, and visible to employees before January 1. Processing deadlines give your team at least three business days of breathing room. The 27-period question has been answered on paper, whether or not it applies this year. Finance, benefits, and HR are working from the same schedule you are. And the first payroll of the year previews clean in December, so January is just execution.
Put a recurring task on your own calendar for every October: pull next year's holidays, count the pay periods, rebuild, verify, publish. One afternoon a year buys you twelve months of quiet.
If your calendar is already tangled, or you would rather have an expert build it right the first time, that is what we do all day. Ignite HCM is staffed by former ADP service professionals, and we work with ADP exclusively. No tickets, no hold queues, just a dedicated consultant who has built hundreds of these calendars and knows exactly where the traps are. Hair on fire? Call us.
Ready to lock in next year's calendar before January sneaks up? REQUEST A CONSULTATION.
ADP and the ADP logo are registered trademarks of ADP, Inc. This article is general guidance, not tax or legal advice; confirm specifics with your licensed advisor.
