If you pay employees every other Friday, check your 2026 payroll calendar right now: this is one of those rare years with 27 biweekly paydays instead of 26. If you budgeted 26 equal paychecks for each salaried employee, you are about to either hand out an unplanned extra payday or scramble to re-amortize everyone's salary — and your benefits deductions, 401(k) limits, and tax withholding all need attention too.
Payroll schedules feel like a set-it-and-forget-it decision, but the choice ripples through your compliance obligations, your overtime math, your cash flow, and your books. And in several states, the choice is partly made for you: the law sets a minimum pay frequency, and picking a slower schedule than your state allows is a wage violation waiting to happen. Here is how to choose the right cadence — weekly, biweekly, semimonthly, or monthly — and run it without tripping over the rules.
There Is No Federal Pay Frequency Law — Your State Sets the Floor
The Fair Labor Standards Act (FLSA) sets minimum wage and overtime rules but says nothing about how often you must pay employees. Pay frequency is entirely a matter of state wage-payment law, and the U.S. Department of Labor maintains a state-by-state payday requirements chart summarizing each state's minimum.
The strictest states cluster in New England and the Mid-Atlantic:
- Connecticut requires weekly pay by default; employers need state approval to move to biweekly or semimonthly.
- Rhode Island requires weekly pay for hourly workers, with exemptions available on request.
- New Hampshire requires weekly or biweekly pay; slower schedules need Department of Labor approval.
- Massachusetts requires weekly or biweekly pay for most employees.
- Vermont defaults to weekly pay, but employers can switch to biweekly or semimonthly with written notice to employees.
- New York requires manual workers to be paid weekly; other employees must be paid at least semimonthly.
Most other states set the floor at semimonthly or monthly, and the details vary: some distinguish between hourly and salaried workers, between manual laborers and office staff, or between private-sector and public-sector employment. A few states also regulate when wages must arrive relative to the end of the pay period, not just how often periods occur.
Two practical consequences follow. First, look up the rule in every state where you have employees, not just where your business is registered — remote workers bring their state's payday law with them. Second, if you operate in multiple states, the strictest applicable rule effectively sets your company-wide schedule unless you want to run different frequencies for different employees, which most small businesses should avoid for sanity's sake.
The Four Schedules at a Glance
| Schedule | Paydays per year | Typical payday pattern | Best for |
|---|---|---|---|
| Weekly | 52 | Same weekday each week | Hourly-heavy teams, construction, hospitality |
| Biweekly | 26 (sometimes 27) | Every other Friday | Most common overall; mixed hourly/salaried staff |
| Semimonthly | 24 | 1st and 15th (or 15th and last day) | Salaried-only workforces |
| Monthly | 12 | Once a month | Very small salaried teams in permissive states |
Biweekly is the most common schedule in the country: Bureau of Labor Statistics data puts it at 36.5 percent of private businesses in 2014, with more recent Current Employment Statistics figures around 43 percent, followed by weekly at roughly 27 percent. But "most common" is not "right for you." Each option has a distinct cost, compliance, and complexity profile.
Weekly Pay: Simple, Employee-Friendly, Expensive to Run
Weekly payroll means 52 pay runs a year — double the processing of biweekly, with double the per-run fees if your payroll provider charges that way, and double the reconciliation work in your books. For a small business running payroll in-house, it also means the owner or bookkeeper touches payroll every single week.
Why do it anyway? Three reasons. First, some states and some worker categories effectively require it. Second, industries with high hourly turnover — construction, restaurants, staffing — find that weekly pay is a genuine recruiting advantage; BLS data shows roughly two-thirds of construction establishments pay weekly. Third, weekly periods align perfectly with the 7-day FLSA workweek, so overtime calculations are trivially simple: every pay period contains whole workweeks, never fractions.
Weekly makes the most sense when most of your staff is hourly, when your state leans that way, or when faster pay helps you hire. It makes the least sense for an all-salaried office team, where you would pay 52 processing fees to deliver paychecks nobody needed that urgently.
Biweekly Pay: The Default Choice — With Two Quirks to Manage
Biweekly (every two weeks, usually on Fridays) hits the sweet spot for most employers: half the runs of weekly, whole-workweek periods that keep overtime math clean, and a rhythm employees understand. Salaried exempt employees divide neatly too — an $80,000 salary is $3,076.92 every other Friday.
But biweekly has two quirks that generate most of the support tickets and accounting confusion:
Quirk 1: two three-paycheck months per year. Ten months have two paydays and two months have three. That third paycheck in a month wrecks any deduction taken as a flat monthly amount. The standard fix, used by university and government payrolls alike, is to take benefits and other fixed deductions from only the first two paychecks each month and skip them on the third. Whatever convention you choose, configure it deliberately in your payroll system — the wrong default silently over-withholds from employees twice a year.
Quirk 2: the 27-payday year. Twenty-six biweekly periods cover only 364 days, so roughly every 11 years the leftover days accumulate into a 27th payday. 2026 is one of those years for many employers on a biweekly schedule — employment-law advisories from firms like Fisher Phillips and Thompson Coburn flagged it specifically. If you pay salaried employees by dividing their annual salary by 26, a 27-payday year quietly gives everyone a ~3.8 percent raise. Your options: divide by 27 for that year (smaller checks, same annual total — communicate this early), absorb the extra payday as a bonus, or adjust. Either way, revisit 401(k) and HSA contribution pacing, benefits deductions, and withholding annualization before the year starts, not after the extra check clears.
Semimonthly Pay: Clean Books, Messy Overtime
Semimonthly means twice a month on fixed dates — typically the 1st and 15th, or the 15th and last day — for 24 runs a year. It is the cheapest of the three common options to administer, and it lines up beautifully with monthly accounting: each month's payroll cost is exactly two equal checks, month-end close is simple, and benefits deductions divide evenly with no three-paycheck months to handle.
The catch is that semimonthly periods are uneven (13 to 16 days depending on the month) and almost never align with 7-day workweeks. A pay period routinely contains one full workweek plus fractions of two others. For salaried exempt employees who never earn overtime, that does not matter. For hourly nonexempt employees, it matters a great deal — which brings us to the trap.
Semimonthly works best for salaried-only workforces. If you have hourly staff earning overtime, think twice: you will compute overtime on a workweek basis and then map it onto misaligned pay periods every single cycle, which is exactly the kind of fiddly manual step that produces errors.
Monthly Pay: Cheap, but Often Illegal and Always Unpopular
Twelve runs a year is the lowest possible processing cost, and holding wages for a full month flatters the employer's cash flow. But monthly pay is the worst option for nearly every small business. Many states prohibit it for hourly workers outright, employees living paycheck to paycheck cannot wait 30 days between checks, and any payroll error takes a full month to correct. Unless you run a tiny salaried team in a state that permits monthly pay — and your employees genuinely prefer it — cross this one off the list.
The Overtime Trap: Your Pay Period Is Not Your Workweek
This is the single most expensive misunderstanding in payroll scheduling. Under the FLSA, overtime is computed on the workweek — a fixed, recurring 7-day period — not on your pay period. The regular rate equals total compensation in the workweek (minus statutory exclusions) divided by total hours actually worked in that workweek, and every hour over 40 in that workweek earns time-and-a-half.
With weekly or biweekly schedules, pay periods always contain whole workweeks, so the mapping is automatic. With semimonthly or monthly schedules, it is not. Consider an employee on a semimonthly schedule who works 45 hours in the workweek that straddles the 15th: those 5 overtime hours belong to that workweek and must be paid at the overtime premium even though the hours fall across two different pay periods. You cannot average the hours across the pay period, and you cannot defer the overtime to whichever check is convenient — DOL Fact Sheet #23 is explicit that overtime is a workweek concept.
The compliance-safe approach for semimonthly hourly payroll is to compute overtime by workweek first, then attribute each workweek's wages to the pay period in which the workweek ends (or the payday covering it, per your state's timing rules). Document the method, configure it in your payroll software rather than in a spreadsheet, and audit it quarterly. Or sidestep the whole problem by putting hourly staff on weekly or biweekly pay even if salaried staff stays semimonthly — running two frequencies is extra work, but less work than defending a wage claim.
How to Switch Schedules Without Breaking Things
Changing frequency is allowed in every state as long as the new schedule still satisfies that state's minimum — but it touches everything downstream. Use this checklist:
- Confirm the new schedule is legal everywhere you employ people. The strictest state's floor governs.
- Check notice requirements. Some states, contracts, and collective bargaining agreements require advance written notice before a frequency change — timelines range from one pay period to 90 days. Even where no notice is legally required, announce the change at least a month ahead; employees budget around paydays.
- Recompute salaried pay correctly. Annual salary ÷ new number of periods (÷26 for biweekly, ÷24 for semimonthly). Never just copy the old per-check amount onto the new cadence.
- Rebuild every per-check deduction. Additional withholding amounts, flat-dollar benefits contributions, garnishments, and retirement contributions calibrated to the old frequency will over- or under-withhold on the new one. This is the step Bloomberg Law's payroll coverage flags most often — acquired employees kept on the wrong frequency code in the system get overtaxed on the very first check.
- Decide the three-paycheck-month policy now if moving to biweekly: which deductions skip the third check, and how you will explain it.
- Run a parallel test cycle. Process a full off-cycle run on the new frequency, verify every pay statement line — gross, withholding, each deduction — and reconcile totals to the old schedule before the change goes live.
- Reset timekeeping cutoffs. New period end dates mean new timesheet deadlines; hourly staff and their managers need the new calendar before the first short period catches someone off guard.
- Plan the cash-flow bridge. Moving from semimonthly to biweekly front-loads one extra payday into the transition quarter; moving the other way delays one. Forecast the quarter so the shift does not surprise your operating account.
Which Schedule Should You Choose?
For most small businesses, the decision tree is short:
- Mostly hourly staff, or in a strict New England / Mid-Atlantic state? Choose weekly or biweekly. Weekly if turnover is high and fast pay helps hiring; biweekly otherwise.
- All salaried, no overtime? Semimonthly gives you the cheapest processing and the cleanest monthly books.
- Mixed hourly and salaried across multiple states? Biweekly is the pragmatic default — legal in every state, clean overtime math, and familiar to every payroll provider.
- Tempted by monthly? Reconsider unless your state allows it and your team is small, salaried, and genuinely on board.
Whichever you pick, write it into your handbook or offer letters, calendarize the full year's paydays (including the three-paycheck months and any 27-payday year), and revisit the choice when your workforce mix changes — the schedule that fit five salaried founders rarely fits fifty hourly employees.
Keep Your Payroll Books Clean From Day One
Your payroll schedule shapes your bookkeeping more than most founders expect: biweekly means accruing split-period wages at almost every month-end, semimonthly means mapping workweek overtime onto calendar-half periods, and every schedule means reconciling dozens of payroll runs — plus per-run processing fees — against your bank feed each year. Tracking wages, employer taxes, benefits, and garnishments as separate accounts from the start is what makes that reconciliation a routine instead of a forensic exercise. If you like seeing where the money actually goes, Fava's dashboards can turn those payroll postings into burn-rate and labor-cost trends at a glance, and the Beancount documentation walks through the plain-text workflow step by step.
Simplify Your Financial Management
As you set up payroll for a growing team, maintaining clear financial records from the first payday is essential — payroll errors compound fast when the books are a black box. Beancount.io provides plain-text accounting that gives you complete transparency and control over your financial data — no black boxes, no vendor lock-in. Get started for free and see why developers and finance professionals are switching to plain-text accounting.
