Pay Period Setup: How to Choose and Configure Yours

Setting up a pay period means making four decisions: how often you pay, which dates each period covers, how many days pass between the period's end and payday, and which rules apply in your state. Get those four right once and every payroll run after it is predictable. Get them wrong and you spend months fixing overtime splits, late checks and mismatched timesheets.

This guide walks through each decision in order, with a worked calendar, the rules that limit your choices, and the timekeeping details that make a schedule hold up in real life.

TL;DR

• A pay period is the span of time employees earn wages for. A payday is the date they get paid for it. Set both, and set the gap between them on purpose.
• The four standard frequencies are weekly (52 periods a year), bi-weekly (26), semi-monthly (24) and monthly (12). Bi-weekly is the most common in the U.S.
• Federal law does not set how often you must pay. Your state does, and some states vary the rule by industry or company size.
• Build in a buffer between period end and payday so hours are approved before payroll runs.
• Align your time clock and approval cutoffs with the pay period so payroll gets clean hours with no rekeying.

Table of Contents

• Pay period vs. payday: set both, not just one
• The four pay period frequencies
• Rules that limit your choices
• How to choose a frequency
• Step-by-step pay period setup
• Weekends, holidays and the timekeeping link
• Changing your pay period later
• Our perspective: the schedule is only as good as the hours behind it
• Get your hours ready before every pay run
• Common pay period setup mistakes
• FAQ
• Sources

Pay period vs. payday: set both, not just one

A pay period is the set span of time during which an employee earns wages. The payday is the date they actually receive payment for that work. People mix the two up, and the mix-up causes real setup errors.

Here is the distinction in practice:

• Pay period: Monday, October 5 through Sunday, October 18. This is the date range used to add up hours and earnings.
• Payday (check date): Friday, October 23. This is when money lands in accounts.
• Payroll run date: The day you actually submit payroll. Payroll runs commonly happen two to four days before the pay date, so direct deposits can arrive on time.

So you are really configuring three dates for every cycle, and a good setup defines the rule that links them, such as "period ends Sunday, hours approved Monday, payroll submitted Wednesday, payday Friday."

The four pay period frequencies

The number of periods per year is simple arithmetic: 52 weeks, 26 two-week blocks, 24 half-months and 12 months. The share of U.S. employers using each is less obvious. As of February 2023, the Bureau of Labor Statistics reported that bi-weekly was the most common length among private establishments at 43.0%, followed by weekly at 27.0%, semi-monthly at 19.8% and monthly at 10.3%.

Weekly

Weekly pay lines up neatly with the workweek, so overtime math is simple and employees see wages quickly. The cost is 52 payroll runs a year. Industry matters here: the BLS noted that 65.4% of construction establishments use weekly pay periods.

Bi-weekly

Bi-weekly pay covers two full workweeks and always ends on the same weekday. That makes it easy for hourly overtime, since no workweek is ever split between two periods. One quirk: a year has 52 weeks plus a day or two, so in some calendar years a bi-weekly schedule produces 27 paydays instead of 26. Check your payday calendar for the year ahead so you can budget for it.

Semi-monthly

Semi-monthly pay lands on set calendar dates, usually the 15th and the last day of the month. Employees like the predictability, and salaried pay stays constant. The downside for hourly teams is that periods are uneven in length (13 to 16 days), and a workweek can straddle two periods. That complicates overtime tracking and makes weekly-hours reports harder to read.

Monthly

Monthly means 12 runs a year and the lowest admin load. It also means the longest wait for employees and the largest cash outlay per run. Even if you pay monthly, you still have tax obligations on a shorter clock. Reconcile withholdings and deposits on the schedule your tax agency assigns, not on your pay schedule.

Rules that limit your choices

Before you pick, know what the law allows.

Federal law sets overtime, not pay frequency. The Fair Labor Standards Act defines a 168-hour fixed workweek for overtime purposes, but it leaves the question of how often to pay to the states.

State law sets minimums. The U.S. Department of Labor keeps a state payday requirements page noting that states such as California and Massachusetts have specific statutory rules on how often employees must be paid. Many states vary the requirement by company size, industry, or whether the worker is hourly or salaried. If you have employees in more than one state, you may need more than one schedule.

Public employers have their own rules. For example, Washington's municipal guidance says local government pay intervals can be monthly, bi-monthly, bi-weekly or weekly, but no less frequent than monthly.

Final pay is separate. Many states set their own deadline for paying a departing employee, and that deadline does not follow your regular pay period. Look up your state's rule before the first termination, not after it.

Tax timing matters too. The Small Business Administration advises scheduling pay periods to coordinate tax withholding with the IRS, so talk to your accountant before locking in a frequency.

This is general information, not legal advice. For a specific situation, such as a multi-state team or a schedule change, confirm the rule with your state labor department or a payroll professional.

How to choose a frequency

There is no universally best schedule. Work through these five questions.

1. Who are you paying? Hourly employees with variable hours are easiest to manage on weekly or bi-weekly cycles. Salaried employees fit semi-monthly or monthly. You can run different schedules for each group, as long as you apply each consistently during the calendar year.
2. What does your state require? Start here, because it removes options.
3. What does your team need? Restaurant and field crews often live paycheck to paycheck, and weekly or bi-weekly pay helps retention. Office teams usually care more about a predictable date.
4. What does your cash flow allow? Weekly pay means smaller, more frequent outflows. Monthly means one large one. Match the rhythm to when revenue arrives.
5. How heavy is your admin load? Each run takes time to review hours, approve changes and reconcile. Fewer runs mean less overhead, unless your hours data is messy, in which case every run is expensive.

For most shift-based businesses with hourly staff, bi-weekly is the practical default. It matches the most common choice in the BLS data, keeps workweeks intact for overtime, and cuts runs in half compared with weekly.

Step-by-step pay period setup

Whatever tool or process you use, the setup follows the same logic. Payroll tools generally ask for a frequency, the first check date and the start and end dates of the first period, and then project future cycles automatically.

1. Define the workweek. Pick the day and time your workweek starts, such as Monday 12:00 a.m. Use it for every overtime calculation.
2. Choose the frequency. Use the criteria above and confirm it against your state's rules.
3. Set the period start and end. For bi-weekly, pick a Monday start and a Sunday end two weeks later. For semi-monthly, use the 1st to the 15th and the 16th to month-end.
4. Set the lag between period end and payday. A gap of a few days to a week or two is common, because hours must be confirmed first. A delay of one or two weeks between the end of a pay period and payday is common. Shorter lags are possible when your time data is clean.
5. Set the first check date. Count forward from the first period's end date using your lag.
6. Set the payroll run date. Work backward from payday and leave time for processing. Many payroll tools quote a turnaround of about two business days.
7. Name the schedule clearly. If you use several, include the team name or payday in the name, such as "Field Crews, Friday Bi-weekly," so whoever runs payroll can pick the right one.
8. Tell your employees. Publish the calendar for the full year, with paydays and the cutoff for timesheets or approvals.

A worked bi-weekly example

Suppose you run a restaurant with hourly staff and choose bi-weekly pay with a five-day lag.

Every period has exactly two workweeks, so overtime never splits across cycles. Every payday is a Friday, and every cutoff is a Monday. Employees learn the rhythm in one cycle.

Weekends, holidays and the timekeeping link

A payday can land on a weekend or bank holiday. If a check date falls on a weekend, payroll tools typically pay on the next business day, but many employers choose to pay on the business day before so staff are not waiting. Decide the rule once, write it down, and apply it every time. Check your state's rules too, since some require payment no later than a set date.

Timekeeping is where most schedules break. Finance and HR teams can align pay period end dates with their timekeeping systems to cut manual adjustments and payroll errors. In practice that means:

• The time clock period matches the pay period exactly. No hours should fall in a gap.
• Managers approve timesheets by a fixed cutoff. Our guide to timesheet approvals covers how to run that step without chasing people.
• Hours export in a format payroll can import directly. See how to export time clock data for payroll step by step.
• Missed punches and edits are resolved before the payroll run, not after.

If you pay from paper or spreadsheet timesheets, compare that approach with a digital clock in this breakdown of timesheets vs. a time clock. For teams on multiple sites, multi-site time tracking keeps every location on the same period boundaries.

Field crews add one more wrinkle: software choice. Payroll tools differ in how they handle crews, job sites and overtime rules, and a look at payroll software for solar installers shows the kind of configuration questions installation teams weigh.

Changing your pay period later

Sometimes a schedule stops fitting: you grow, move to a new state, or switch from semi-monthly to bi-weekly. Before you change:

• Check state notice requirements. Some states require advance notice to employees.
• Plan the transition period. Switching can create a short or long period, or a gap, where employees are owed wages for days that fall between schedules. Map every day to exactly one period.
• Check your tax deposit schedule and accountant's guidance.
• Communicate the new calendar in writing with the first new payday highlighted.
• Do a reconciliation after the first cycle. Our payroll reconciliation workflow gives you an eight-step audit-ready process.

Our perspective: the schedule is only as good as the hours behind it

Most pay period problems we see are not frequency problems. Employers pick a sensible schedule, then lose days at the cutoff because hours are late, wrong or typed in by hand. A bi-weekly calendar cannot fix a timesheet that someone has to retype.

We built Heyhive around that gap. Shifts are scheduled, hours are clocked with GPS-verified punches, managers review and approve, and payroll-ready hours export without rekeying. When the clock, the approvals and the pay period all share the same boundaries, the lag between period end and payday can shrink, and the corrections shrink with it.

Our advice: choose the simplest frequency your state and team allow, keep the workweek fixed, publish the full-year calendar, and make approvals a hard cutoff. Then fix the data pipeline before you tweak the schedule. For the controls that help, see reducing payroll errors from hire to pay run and our guide to time tracking to payroll integration.

— Heyhive

Get your hours ready before every pay run

Once your pay period is set, Heyhive keeps the hours behind it clean. AI Scheduling builds the week of shifts and you approve it before it publishes. The GPS Time Clock verifies arrivals and departures, and Payroll-Ready Hours gives you totals for each period without retyping. Managers stay in control at every step.

Start free with Heyhive and see how scheduling, time tracking and payroll-ready hours fit around your pay period.

Common pay period setup mistakes

• Splitting the workweek. Starting a period midweek makes overtime messy. Start periods on the first day of the workweek unless you are semi-monthly.
• No buffer before payday. If approvals and payroll processing share the same day, one late timesheet delays everyone.
• Ignoring state rules. A schedule that works in one state may be unlawful in another. Check every state where you have employees.
• Unclear schedule names. With several schedules, generic names lead to the wrong group being paid on the wrong date.
• Forgetting the 27-payday year. Bi-weekly employers should budget for the extra payday in years that have one.
• Skipping reconciliation. Compare payroll totals against approved hours each cycle. Small gaps compound.

FAQ

What is the most common pay period?

Bi-weekly. The Bureau of Labor Statistics reported that 43.0% of U.S. private establishments used it as of February 2023, ahead of weekly at 27.0%, semi-monthly at 19.8% and monthly at 10.3%. Your best choice still depends on your state's rules and your workforce.

Can I use different pay periods for different employees?

Yes, in many cases. Employers commonly pay hourly and salaried employees on different schedules, as long as each schedule is applied consistently and meets your state's rules. Name each schedule clearly so the right group is paid on the right date.

How long after the pay period ends should payday be?

There is no single federal rule, but a gap of a few days to one or two weeks is common. The right lag depends on how quickly you can confirm hours and process payroll, and on any state deadlines. Cleaner time data lets you shorten it.

Does federal law say how often I must pay employees?

No. The FLSA defines the workweek for overtime but does not set pay intervals. States set those, and requirements can vary by industry or company size, so check your state labor department's rules.

What if payday falls on a weekend or holiday?

Choose a consistent rule: pay on the prior business day or the next one. Many employers pay early so staff are not left waiting. Confirm that your state does not require payment by a fixed date.

Sources

• Common payroll terminology
• Payroll Run Date vs. Paydays
• Length of pay periods in the Current Employment Statistics, U.S. Bureau of Labor Statistics
• State Payday Requirements, U.S. Department of Labor
• Payroll Administration, MRSC
• Manage your business, Small Business Administration
• Pay Schedules help article

Recommended

• How to Export Time Clock Data for Payroll, Step by Step
• Reduce Payroll Errors With 9 Checks From Hire to Pay Run
• For Managers: Stop Accrual Drift with Time Clock Hourly PTO Tracking
• Timesheet Approvals: A Manager's Complete Guide