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 it is one you should make 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 covers the actual decision: the four options and their trade-offs, the state laws you must check first, how to choose, and how to set one up. FirstHR is an HR platform, not a payroll processor, so the angle here is the choice and the employee data behind it, not running the payroll itself.

Below you will find what a pay schedule is, the four types compared, how many pay periods each has (including the 27-payday quirk), the confusing biweekly-versus-semi-monthly distinction, the state pay-frequency laws to check, how to choose, how to set one up step by step, and how your HR data supports payroll. 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. The pay schedule shapes your cash flow, since each payday is an outflow; your administrative burden, since each pay run takes work; your employees' financial lives, since how often they are paid affects how they budget; and your legal compliance, since some states dictate a minimum frequency. A decision made casually on day one becomes a fixed rhythm you and your team live with, so it is worth making 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, but it is 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, because it balances reasonable administrative load with pay frequency that employees are comfortable with, and because 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. Recognizing that biweekly is the default most US employees expect is a useful starting point.

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 eleven years a calendar year ends up containing a 27th biweekly payday instead of the usual 26. For salaried employees, whose annual pay is split across the year's paydays, 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 and plan for when it lands, 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. So biweekly is 26 checks on a rolling cycle; semi-monthly is 24 checks on fixed dates.

The practical difference that matters most is overtime. Biweekly pay periods align with workweeks, which makes calculating overtime straightforward, since a workweek fits neatly inside the pay period. 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. The exempt-versus-non-exempt distinction that drives this is covered in the exempt vs non-exempt guide.

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 critical practical points are two. 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 are minimums: you are always free to pay more frequently than required, so meeting the law is a floor, not a target. Because penalties for getting pay frequency wrong can be significant, and because the rules genuinely vary, checking your specific state before you commit is non-negotiable. The broader wage-and-hour framework these rules sit within is covered in the Fair Labor Standards Act guide.

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. 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 is employee needs: more frequent pay helps hourly and lower-wage employees manage their finances and is often what they expect and prefer, so the schedule affects satisfaction and retention.

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. That said, weigh your specific situation. 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, the most important thing is to apply it consistently, since erratic timing can create both legal exposure and employee distrust.

How to Set Up a Pay Schedule

Once you have chosen a cadence, setting it up is a clear sequence. 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 and builds trust. Documenting the schedule in your employee handbook gives everyone a reference and satisfies the policy expectation that a handbook should state your pay schedule.

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. Keeping this information accurate and in one place, as part of your broader HR for small business setup, is what lets payroll run smoothly regardless of which 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. Storing your pay-schedule policy and direct-deposit forms alongside the employee record keeps everything consistent. And accurate hours from your timesheets feed the pay run correctly. Treating the pay schedule as part of a connected HR foundation, rather than an isolated payroll setting, is what keeps the whole thing reliable, which is the broader theme of the HR automation guide.

Frequently Asked Questions