Punch27 Pay Periods in a Year: What an Extra Biweekly Paycheck Actually Changes (2027)
27 Pay Periods in a Year: What an Extra Biweekly Paycheck Actually Changes (2027)
The short answer: A biweekly payroll normally cuts 26 checks a year. Every eleven or twelve years, the calendar hands a given pay cycle a 27th. It is not a glitch and it is not extra money you can take back. For hourly crews it changes nothing, because hourly people are paid for the hours they worked no matter how many checks those hours are spread across. For salaried staff it is a budgeting decision you should make before January, not in March. And for overtime it changes nothing at all, because the FLSA counts overtime by the workweek, not by the pay period. Punch tracks hours by the workweek and runs weekly or biweekly pay periods on your own anchor date, so a 27-payday year is just one more period to approve and export.
Most owners find out the hard way. Payroll runs in late December, the software cuts one more check than the budget planned for, and somebody spends a weekend deciding whether it was a mistake. It was not. Here is the math behind it and the short list of decisions it forces.
Why a Biweekly Year Sometimes Has 27 Paydays
Biweekly means every 14 days. Twenty-six pay periods times 14 days is 364 days. A calendar year is 365 days, or 366 in a leap year.
So a biweekly cycle comes up a day short every year, two in a leap year. Those leftover days pile up until a 27th payday slides onto the calendar before December 31 closes. For any given weekday cycle that lands roughly once every eleven to twelve years.
Two other schedules behave differently. Semi-monthly is always 24. Paying on the 15th and the last day of the month produces exactly 24 checks every year, forever, and the calendar cannot create a 25th. Weekly drifts for the same reason biweekly does, since 52 times seven is also 364, and produces a 53rd payday about twice as often.
How to Tell If Your 2027 Is a 27-Paycheck Year
This is not a property of the year. It is a property of your anchor date, which means two businesses down the same street can have different answers for the same calendar year.
Take your first payday of the year and add 14 days, over and over. If the 26th step past that first payday still lands inside the year, you have 27.
January 1, 2027 falls on a Friday. A biweekly Friday cycle whose first 2027 payday is January 1 pays on January 1, January 15, January 29, and so on, and the 26th step past January 1 lands on December 31, 2027. That is 27 paydays. The same Friday cycle anchored one week later, with a first payday of January 8, gets 26 and nothing unusual happens.
The same thing caught some employers in 2026, where a cycle anchored to January 1 produced 27, and it will catch a different set in 2028, where anchors on January 1 and January 2 both do.
A 27-payday year also adds a three-paycheck month. On that Friday cycle anchored to January 1, 2027, employees see three checks in January, July, and December. Expect questions from the crew in the month it happens rather than in advance.
Hourly Employees: Nothing Changes
This is the part that gets over-thought.
An hourly employee is paid for hours worked. If they work 2,080 hours in a year, they get paid for 2,080 hours whether those hours are spread across 26 checks or 27. The annual cost of an hourly crew does not move because of an extra payday. The 27th period is a real 14-day window with real hours in it.
There is no true-up to run and no rate to adjust. If your crew is entirely hourly, the 27-payday year is a cash-flow note for the month it lands in and nothing more.
Salaried Employees: The Real Decision
Salaried pay is where the extra period costs money, because salary is usually set as an annual figure divided by the number of checks.
If you pay a $65,000 salary as $2,500 per check by dividing by 26, a 27-payday year pays that person $67,500. That is one extra check, roughly 3.8 percent over the budgeted annual figure, per salaried person. Across a handful of salaried staff it is real money, and it hits whichever month the 27th payday lands in.
You have two honest options, and one thing that is not an option at all.
Absorb it. Leave the per-check amount alone and accept the higher annual cost that year. Simplest, cleanest, and nobody is unhappy. Many small employers choose this because the alternative costs goodwill.
Recalculate the per-check amount prospectively. Divide the annual salary by 27 instead of 26, so $65,000 becomes about $2,407 per check and annual pay lands where you budgeted. The cost is that every check is smaller, employees notice immediately, and you have to explain it before the first one goes out. Some states require written notice before an employee's pay rate changes, so check your state's rule first.
What you cannot do is skip or claw back a check. Federal law defines salary basis as a predetermined amount the employee receives each pay period that is not subject to reduction because of variations in the quality or quantity of work, and an exempt employee must receive the full salary for any workweek in which they perform any work. Withholding the 27th check, or docking later checks to recover it, puts the exemption itself at risk. Lose the exemption and the employee is owed overtime for every hour past 40, retroactively.
One guardrail if you recalculate. The adjustment has to keep the weekly salary at or above the federal exempt threshold of $684 a week, which is $35,568 a year. Several states set a higher floor, including California, New York, Washington, Colorado, Connecticut, and Alaska, and the higher number governs there. Dividing by 27 lowers the weekly figure. On a salary near the threshold, that is the difference between an exempt employee and one you now owe overtime to.
Benefit Deductions on the Extra Check
Decide this in advance, in writing, before the 27th period runs.
Many employers already spread benefit deductions across 24 of 26 checks and skip the three-paycheck months. If that is your setup, the extra period folds in without drama. If you deduct a flat amount every period instead, a 27th period takes one more deduction than the annual premium calls for.
The same applies to anything deducted as a fixed dollar amount per check rather than a percentage, including retirement contributions and pretax account elections. A fixed per-check amount multiplied by 27 is not the number the employee elected. Confirm with your payroll provider and benefits administrator how the extra period is handled, and tell employees which checks carry deductions before the first surprise lands.
What Does Not Change: Overtime
Overtime is owed by the workweek. Federal regulation is explicit that the Act takes a single workweek as its standard and does not permit averaging hours over two or more weeks, regardless of whether the employee is paid on a daily, weekly, biweekly, monthly, or any other basis. An employee who works 30 hours one week and 50 the next is owed 10 hours of overtime for the second week, even though the two weeks average 40.
So the number of pay periods in your year has no bearing on overtime. Twenty-six periods, 27 periods, 24 semi-monthly periods, it does not matter. Each seven-day workweek is measured on its own, and the pay period is only the envelope the result arrives in.
The failure mode is a payroll process that totals a whole 14-day period and asks whether it exceeded 80 hours. That process underpays every time a crew works 46 hours one week and 33 the next. It reads as 79 hours and no overtime. It is actually six hours of overtime owed. An extra period does not cause that bug, but it is the kind of year where people rebuild the payroll spreadsheet from scratch, and rebuilding is when that bug gets introduced.
How Punch Handles the Extra Pay Period
Punch is built on the workweek, which is the unit the pay calendar keeps trying to obscure.
Your crew punches in and punches out from their phones, with lunch tracked separately. Every punch lands inside a fixed seven-day workweek you set once for the whole organization. Overtime is calculated against that workweek, using the 40-hour federal threshold or the daily and weekly thresholds for your state or country, drawn from overtime presets covering more than 50 countries. A 27th pay period does not change any of it, because the workweek never moved.
Punch runs weekly and biweekly pay periods natively, on your own anchor date. A biweekly period in Punch is two whole workweeks, each totaled and evaluated for overtime on its own before anything is marked paid. That is the FLSA-correct order of operations, and it is the order that survives an unusual year.
The extra period runs like every other one. Managers review hours with per-shift approvals or bulk approve and reject. Owners and managers pull Reports and export to Excel, send a QuickBooks-ready CSV, or push time straight into QuickBooks Online.
Verification stays honest. Punch confirms a punch with a job-site geofence on iOS, never a camera in your crew's face. No facial recognition, no photo at a punch. Punches also work offline, so a shift in a basement or a dead zone records cleanly and syncs when signal returns.
Pricing is flat per organization. Every plan includes every feature, and nothing is billed per seat. An unusual payroll year is a reason to check your math, not a reason to pay a bigger invoice.
The Bottom Line
Count forward from your first payday of the year in 14-day steps. If a 27th lands before December 31, decide now whether you absorb the extra salaried check or recalculate prospectively, settle how benefit deductions run on it, and tell your team before the three-paycheck month arrives. Then leave overtime alone, because it was never counted by the pay period in the first place.
Start with Punch and keep hours on the workweek, so the number of paydays in a year is a budgeting question and never a wage-and-hour one.
This article is general information, not legal advice. Wage, overtime, and pay-notice rules vary by state and country. Confirm your obligations with a qualified professional for your jurisdiction.