Pay Schedules: A Small Business Guide

Before my first employee's first payday, I had to answer a question I had never thought about: how often was I going to pay people? I defaulted to whatever felt normal without realizing the choice affected my cash flow, my admin workload, my employees' finances, and, it turned out, whether I was even complying with my state's law. Picking a pay schedule seems trivial, but it is a real decision with real consequences, and this guide shows you how to make it deliberately rather than by accident.

A pay schedule is the recurring cadence on which you pay employees: weekly, biweekly, semi-monthly, or monthly. Most guides on this are generic glossary entries from payroll vendors. This one is written for the founder or owner setting up a pay schedule for the first time, and it walks through the actual decision from start to finish.

You will get the four options and their trade-offs, how many pay periods each has (including the 27-payday quirk), the confusing biweekly-versus-semi-monthly distinction, the state pay-frequency laws you must check first, how to choose, how to set one up step by step, how to handle pay dates and holidays, and how your HR data supports payroll.

FirstHR is an onboarding and HR platform, not a payroll provider, so the angle here is the choice and the employee data behind it, not running the payroll itself. I build the employee-data foundation for all of this into FirstHR. This article is general information, not legal advice, so confirm your state's current rules with counsel.

What Is a Pay Schedule?

A pay schedule, also called a payroll schedule, is the recurring cadence on which a business pays its employees. It answers a simple question, how often do people get paid, and it is one of the first operational decisions a business makes when it starts hiring.

It helps to separate three related terms that are easy to blur. The pay frequency is how often you pay, such as biweekly. The pay period is the span of time over which work is counted for a given paycheck, such as a two-week stretch. The pay date is the specific day the paycheck is actually issued, which usually falls a few days after the pay period ends to allow time for processing. A pay schedule ties these together into a predictable, repeating rhythm.

Getting this right matters more than it first appears. Every payday is a cash outflow for you, and every pay run is administrative work. How often your employees are paid shapes how they budget. And because some states dictate a minimum frequency, the choice is also a legal compliance question. A decision made casually on day one becomes a fixed rhythm you and your team live with, so make it thoughtfully.

The 4 Types of Pay Schedules

There are four standard pay schedules, defined by how often they pay: weekly, biweekly, semi-monthly, and monthly. Each has a different number of paychecks per year and a different balance of trade-offs, which is the heart of the choice.

Weekly pays 52 times a year and gives employees the steadiest cash flow, which hourly and lower-wage workers often value most. It is also the most administrative work, since you run payroll every week. Monthly, at 12 paychecks, is the least work for you but the hardest on employees, who must stretch a single check across the whole month. These are the two ends of the spectrum, trading your convenience against employee cash flow.

In the middle sit the two most practical options for most businesses. Biweekly, at 26 paychecks every two weeks, is the most common schedule in the US. It balances a reasonable administrative load with a pay frequency that employees are comfortable with, and it aligns cleanly with workweeks, which simplifies hourly and overtime calculations.

Semi-monthly, at 24 paychecks twice a month, aligns neatly with monthly benefit deductions and gives predictable calendar-date paydays, but it complicates overtime because its pay periods do not line up with workweeks.

Where Daily Pay Fits

Daily pay is not a fifth standard schedule, but it comes up often enough to answer. A few employers, mostly in day labor and staffing, settle up at the end of each shift. That is legal anywhere it clears the state minimum, because paying more often than the law requires is always allowed.

Most small businesses that want the same effect keep a normal biweekly run and add earned wage access, which lets an employee draw part of what they have already earned before payday. The schedule underneath does not change, so your compliance floor and your pay runs stay where they were.

Pay Periods per Year (and the 27-Payday Quirk)

Each schedule produces a set number of pay periods per year, which is worth knowing because it affects budgeting and, for salaried employees, how each paycheck is calculated. The counts are straightforward, with one quirk that catches employers off guard.

For salaried employees, the annual salary is divided across these periods, so the same salary produces smaller, more frequent checks on a weekly schedule and larger, less frequent ones on a monthly schedule. For hourly employees, the number of periods matters less than the hours worked in each, but the schedule still shapes how their pay arrives.

The quirk to know is the 27-payday year. A biweekly schedule pays every 14 days, which over 26 pay periods covers only 364 days, one day short of a full year. That extra day accumulates, so roughly every 11 years a calendar year ends up containing a 27th biweekly payday instead of the usual 26.

Salaried employees are where that extra payday shows up as money. Their annual pay is split across the year's paydays, so an unplanned 27th check can raise your payroll cost for that year if you do not account for it in advance. It is not a problem, just something to anticipate, which almost no one does until it surprises them.

Biweekly vs Semi-Monthly: The Confusing One

The single most confused comparison in pay schedules is biweekly versus semi-monthly, because they sound similar and land at similar frequencies but work differently. Getting the distinction clear saves real trouble, especially with overtime.

Biweekly means paying every two weeks, on the same day of the week, producing 26 paychecks a year. Because the paydays track a 14-day cycle rather than the calendar, they drift across the month, and two months each year end up with three paydays.

Semi-monthly means paying twice per calendar month on fixed dates, such as the 15th and the last day, producing exactly 24 paychecks a year that always land on the same calendar dates. In short, biweekly is 26 checks on a rolling cycle, and semi-monthly is 24 checks on fixed dates.

The practical difference that matters most is overtime. Biweekly pay periods align with workweeks: each workweek fits neatly inside one pay period, so calculating overtime is straightforward.

Semi-monthly pay periods do not align with workweeks. A period can start or end mid-week, splitting a workweek across two paychecks, which complicates overtime calculation for non-exempt employees. This is why businesses with many hourly workers often prefer biweekly, while semi-monthly can suit salaried teams where overtime is less of a factor.

State Pay-Frequency Laws to Check First

Before you choose any schedule, you must check one thing: your state's minimum pay-frequency law. This is the constraint that overrides preference, and getting it wrong exposes you to penalties, yet most guides mention it only in passing.

Most states set a minimum pay frequency, meaning you can pay more often than the law requires but never less. The rules vary widely. Some states have no pay-frequency law at all, so you have full choice. Others set specific minimums, and some tie the requirement to the type of employee.

The California and New York rows come straight from the agencies that enforce them. California's Labor Code 204 requires wages for most employees at least twice during each calendar month, on days designated in advance, and New York requires weekly pay for manual workers and at least twice a month for clerical and other workers.

No frequency rule is not the same as no rules. South Carolina sets no minimum frequency, but employers of five or more people must give written notice at hire of the time and place of payment, so the payday you pick still goes in writing.

Two practical points follow. First, the law that applies is the law of the state where the employee physically works, not where your company is headquartered, so a multi-state team may face different rules for different people. Second, these rules are minimums, so meeting the law is a floor, not a target.

How to Choose the Right Pay Schedule

With the state-law floor established, choosing among the compliant options comes down to balancing three practical factors against each other: cash flow, administrative load, and employee needs. There is no universally right answer, only the right fit for your business and team.

The first factor is cash flow. More frequent pay means more frequent outflows and more frequent processing, so a weekly schedule demands tighter cash management than a monthly one. The second is administrative load: each pay run takes work, so weekly is the most effort and monthly the least, which matters when you are the one running payroll.

The third factor is employee needs. More frequent pay helps hourly and lower-wage employees manage their finances and is often what they expect, so the schedule affects satisfaction and retention as much as it affects your calendar.

For most small businesses, biweekly is the sensible default because it balances all three: manageable administrative load, reasonable cash-flow rhythm, and a pay frequency employees are comfortable with, all while aligning cleanly with workweeks for overtime.

Your own situation can still point elsewhere. A business with many lower-wage hourly workers might choose weekly for their benefit; a small salaried team might find semi-monthly aligns well with benefits. Whatever you pick, apply it consistently, since erratic timing can create both legal exposure and employee distrust.

Can You Run More Than One Pay Schedule?

Yes. Nothing stops you from putting different sets of employees on different cadences, and plenty of businesses do it: hourly staff weekly, salaried staff semi-monthly. In payroll systems each of those sets is called a pay group, and every pay group carries its own pay periods and its own pay dates.

Two conditions make it work. Each pay group has to clear the minimum frequency for the state where its people work, and what puts someone in a group has to be their job, not who they are. Splitting the team also doubles your pay runs, so do it only when the workforce genuinely calls for it.

How to Set Up a Pay Schedule

Setting one up takes six steps, from the legal check to running payroll on the same rhythm every time. Doing it deliberately from the start prevents the confusion and compliance problems that come from an improvised approach.

The step small businesses most often skip is building a full-year payroll calendar and communicating it clearly. Employees plan their finances around paydays, so telling them exactly when they will be paid, ideally as part of new hire paperwork and their onboarding, prevents a stream of when-do-I-get-paid questions.

Documenting the schedule in your employee handbook gives everyone one place to check it and satisfies the policy expectation that a handbook should state your pay schedule.

Write the decision itself down once, separately from the calendar and the handbook policy. The record below captures what you checked, what you chose, and why, so that a year later, when someone asks whether the cadence can change or a hire in a new state raises the question again, the reasoning is on paper instead of in your memory.

Pay Dates, Deadlines, and Holidays

The pay period is the span of work you are paying for, and the pay date is the day the money reaches the employee. The gap between the two is your processing window, and every payroll deadline you actually have to hit lives inside it.

Pin the pay period to the workweek and the boundaries stop being a question. If your workweek runs Sunday through Saturday, a weekly pay period starts Sunday morning and ends the following Saturday night, with the pay date a few days later, commonly the Friday after the period closes. Biweekly works the same way across two workweeks.

Write those boundaries down, because federal recordkeeping already assumes you know them. For every non-exempt employee, the Fair Labor Standards Act (FLSA) requires you to keep the time and day of week the workweek begins, the pay period covered by each payment, and the date of payment (DOL Fact Sheet 21). Those payroll records have to be kept for at least three years.

Your real deadline is not payday. It is the cutoff for submitting the pay run, which sits a fixed number of banking days ahead of the pay date so the money has time to move. Find yours, put it on the calendar beside every payday, and treat it as the date that matters. A payroll calendar is where both belong.

Holidays are where that calendar bites. If payday falls on a holiday or a weekend, move the deposit earlier rather than later. Paying before the scheduled payday raises no issue; paying after it can, because state payday rules fix the date wages are due.

Direct deposits run over the ACH (Automated Clearing House) network, which does not process on days the Federal Reserve is closed. The Fed publishes its holiday schedule years ahead, weekend rules included: a holiday falling on Sunday closes every Federal Reserve office the following Monday, and one falling on Saturday leaves the Reserve Banks open the preceding Friday.

Write the rule once instead of deciding case by case: a payday that lands on a closed day moves to the last business day before it. Put that sentence in the handbook next to the schedule so nobody has to ask, and set a reminder on each submission cutoff, since that is the deadline people miss.

The HR Data Behind Every Payroll Run

A pay schedule is only as good as the employee data behind it, and this is where an HR system earns its place even if it does not run payroll itself. Every pay run depends on accurate underlying records, and keeping those clean is the foundation that makes payroll work.

Each paycheck draws on data that lives in your HR records: the employee's pay rate, their exempt or non-exempt classification, their direct-deposit details, their start date, and their hours worked. If any of that is wrong or scattered across spreadsheets and emails, payroll errors follow, whichever schedule you chose.

The connection runs deeper than data storage. Letting employees see their pay schedule and update their own banking details through employee self-service reduces the questions that land on your desk, and accurate hours from your timesheets feed the pay run correctly.

Storing your pay-schedule policy and direct-deposit forms alongside the employee record keeps everything consistent. Treat the pay schedule as part of your HR foundation rather than an isolated payroll setting. Before the first pay run on your new calendar, confirm that every employee's pay rate, classification, and deposit details are correct.

Frequently Asked Questions