Semi-Monthly vs Biweekly: Calculating Paydays

Payroll schedules look simple on paper until you try to answer one practical question: when is the next payday? The difference between semi-monthly and biweekly pay schedules is more than a label. It changes how pay periods line up with a calendar, how deductions behave over time, and how managers and employees experience “regularity” week to week.

Below is a practical way to think through both schedules, with enough concrete examples to actually calculate paydays and avoid the common traps that show up in real payroll systems.

A biweekly payroll runs on a repeating two-week cadence. That usually means 26 pay periods per year (because 52 weeks divided by 2 equals 26). If a payday is every other Friday, for instance, that pattern continues by calendar logic.

A semi-monthly payroll splits the month into two pay dates. Most organizations that use it pay on something like the 15th and the last day of each month, or the 1st and 15th, depending on their policy. Semi-monthly produces 24 pay periods per year (two per month times 12 months).

That difference matters Visit this website because it determines whether pay dates “walk” through the calendar.

With biweekly, every payday is anchored to a day-of-week pattern. With semi-monthly, pay dates are anchored to specific calendar dates within the month. Those anchors interact differently with weekends, holidays, and month length.

Semi-monthly is not “every half month.” It is “two fixed pay dates each month,” or “two fixed pay dates that are tied to month boundaries,” then adjusted when the date falls on a weekend or holiday.

Two common semi-monthly structures you will see in the wild:

The pay period itself (the work days that feed each check) may differ from those pay dates. A company might define the pay period as the 1st through 15th work window, then the 16th through end-of-month work window, with pay issued a few days later. Or it may use a different cut-off and pay date lag.

So when you calculate paydays, you need to separate: 1) Pay dates (when money lands), from

Payroll teams usually build the system around pay dates first, then define the pay period ranges that roll into those dates.

Biweekly usually means “every other pay date,” with pay periods spanning 14 days (or sometimes 13 days plus one day depending on how a system cuts and processes). In a well-behaved schedule, each pay period is consecutive, non-overlapping, and forms a repeating chain.

For example, if pay day is every other Friday, then once you have a known payday (a base date), the next payday is always 14 days later. In other words, you do not need to mentally stretch or compress months. The calendar provides the spacing for you.

The practical wrinkle is processing time. Some payrolls issue checks on Friday for work that ended the previous day. Others end the pay period on a Thursday and pay on the Friday. If you are computing paydays rather than pay period coverage, you still mostly care about the pay date rule and any adjustments for weekends and holidays.

When someone asks, “How do I calculate paydays?” there is a temptation to do a simplistic average. People might say:

The problem is that semi-monthly spacing in practice is not consistent. For instance, if the pay dates are the 15th and the last day, the distance between paydays varies because the “last day” changes by month length, and because the next month’s 15th is tied to the calendar.

Biweekly spacing stays consistent in day count, but it can appear irregular if you are tracking by month. A biweekly schedule may deliver three paychecks in one month more often than you expect, and then sometimes only two in another.

Those perceptions affect budgeting and payroll planning, but the math for pay dates is still straightforward once you know the anchor.

The method depends on schedule type, but the logic is consistent: determine the anchor, then apply the cadence, then adjust for non-working days.

1) Identify one confirmed payday date that is already on the biweekly schedule. 2) Add 14 days to get the next payday. 3) Repeat as needed until you reach your target. 4) Apply your company’s rule for weekends and holidays (for example, pay issued on the preceding business day).

The key is that biweekly is essentially arithmetic with occasional business-day adjustments.

Semi-monthly has a different anchor structure: 1) Identify whether you pay on the 1st and 15th, or 15th and last day, or another policy. 2) Determine the next pay date based on the calendar. 3) Apply the company’s adjustment rule when the scheduled date falls on a weekend or holiday.

Unlike biweekly, you generally do not “add 14 days” in semi-monthly schedules. You jump to the next calendar-defined date.

Suppose a company’s confirmed payday is Friday, January 12, 2024. With a biweekly schedule, the next paydays are straightforward:

That’s just 14-day steps.

If the company’s policy is “if payday falls on a holiday, pay on the prior business day,” then you might adjust one of those dates. For example, if February 23, 2024 were a scheduled payday but that day is a holiday, the system might move pay to February 22 (assuming it is a business day). The cadence stays biweekly; only the processing timing changes.

This is why biweekly schedules often feel consistent to employees: it is always the “same day of week rhythm,” and the pattern repeats cleanly year to year.

Now consider a semi-monthly schedule where pay days are the 15th and the last day of each month.

In a month with 30 days, like April, the pay dates are:

In a month with 31 days, like May, the pay dates are:

In a month with 28 days, like February in a non-leap year:

Notice what changes: the gap from the 15th to the end of the month can be 13, 14, 15, or even 16 days depending on month length and leap year status.

If your company pays on the same calendar-defined dates but shifts when they hit weekends, then the “last day” payday can move earlier. A common example is when the last day is a Saturday. The payroll might move the payday to Friday, which affects how employees perceive timing around month-end.

Paydays are what employees care about most. Pay periods are what timekeeping cares about.

In many payroll systems, the pay period dates do not necessarily match the pay date. For example, an organization might use a cut-off window like:

Biweekly systems can be similar: a payday could occur 2 to 5 days after the pay period ends. That processing lag is internal timing, not a fundamental rule of the schedule.

So if you are calculating paydays only, you can ignore the internal lag. If you are trying to answer questions like “Which pay check will include hours worked on March 3?” then you must map work dates to pay period cutoffs, not just pay dates.

People often ask which schedule produces more or fewer paychecks in a given month. The honest answer is: it depends on the month and on where the anchors fall, but the general pattern is predictable.

That predictability is one reason some employers choose semi-monthly for salaried employees or where HR wants uniform employee expectations month to month. It also helps with forecasting expenses in accounting cycles.

Biweekly can still be perfectly workable, but budgeting requires more attention to monthly variability. Over a full year, biweekly paychecks total 26; semi-monthly totals 24. That 2-check difference per employee per year can matter when you are doing annual accruals and expense recognition.

A payroll calendar is not only a set of pay dates. It is also:

Biweekly schedules often require tighter operational rhythm because changes between pay periods happen every 14 days. Semi-monthly has more time between the “mid-month” cycle and the “end-of-month” cycle, but month boundaries still introduce complexity in cutoffs and handling of partial periods (like hires and terminations).

In lived payroll operations, most errors are not caused by the idea of biweekly or semi-monthly. They come from mismatched assumptions:

If you are building or using a payroll calendar, you want a calculation rule that explicitly accounts for those realities.

No matter which schedule you use, certain calendar facts force judgment calls.

If pay day lands on a weekend, most payroll policies move it earlier. Holidays vary by company, and sometimes by jurisdiction.

The main risk is double-adjusting. For example, if a holiday falls on a Sunday, and the policy says “observed holiday moves to Monday,” you must know whether the payroll adjustment happens on the observed holiday date or the originally scheduled date.

Your calculation logic needs to match the employer’s policy wording, not your guess.

Semi-monthly schedules care about:

Biweekly schedules care less about month length, but they still care about holidays. A biweekly calendar can cross a major holiday mid-period, and the system still has to assign hours and run approvals with consistent cutoffs.

Employees who start mid-cycle or end mid-cycle can create “proration” or “final pay” timing issues. Even if the pay schedule is consistent, the amount and sometimes the inclusion logic can change.

If you are trying to calculate “When will my final check be?” that might depend on whether your employer runs final payroll on the regular cycle or uses a separate legal requirement timeline. Those policies vary by location and company.

For the purposes of calculating paydays in a payroll system, the safest assumption is:

When people get paydate math wrong, it is usually because they are doing “mental arithmetic” instead of using the schedule anchor plus a consistent adjustment rule.

Here is a simple workflow that many payroll coordinators use internally.

That last point is the one that saves time. Cutoff rules often use different day boundaries than payday rules.

An employee might ask, “I worked the week of the 10th, why didn’t it show up on my check dated the 15th?” The answer is usually that the “15th” check has a pay period that ends on a cut-off date that might be the 14th or might be based on payroll system time zones.

If you only calculate payday dates, you miss the cutoff.

Semi-monthly is calendar-based, not workload-based. In a “15th semi monthly vs bi weekly and last day” schedule, the second half of the month can be longer than the first half, and it can also be shorter in February. That can be fine, but it means employees sometimes see unequal gross pay amounts per paycheck in the same month if hours worked are proportional to workdays rather than calendar days.

For hourly employees, that unevenness shows up immediately. For salaried employees, it’s usually smoothed, either by dividing salary across pay periods or by using a payroll calculation rule that still produces two checks per month.

If you are trying to decide which schedule is easier to manage or more predictable for employees, it helps to compare the operational impacts, not just the paycheck count.

Here is the simplest comparison that captures the day-to-day reality.

| Feature | Biweekly | Semi-monthly | |---|---|---| | Pay frequency | every 14 days | 2 times per month | | Pay dates pattern | consistent day-of-week cadence | fixed calendar dates (often 15th and last day, or 1st and 15th) | | Monthly paycheck count | 2 most months, sometimes 3 | always 2 | | Annual pay periods | 26 | 24 | | Calendar complexity | mainly weekends and holidays | month length, month-end rules, leap year | | Common errors | incorrect base date or double adjustment around holidays | assuming fixed day spacing between pay dates |

The table is a snapshot, but your actual experience will depend on your company’s payroll processing rules, especially the holiday policy and the time zone cutoffs used in the timekeeping system.

To make this more usable, consider these scenarios. These are not assumptions about any specific employer, they are examples of how the logic plays out once you set the anchor.

A biweekly payroll is anchored on Friday, March 8. The next payday is March 22. The one after is April 5, even though April has a different month structure. You only adjust if March 22 or April 5 is a weekend or holiday by policy.

If the schedule pays on the 15th and last day, then in a month with 30 days, the last-day payday is the 30th. In the following month with 31 days, the last-day payday becomes the 31st. If either date falls on a non-processing day, you move it according to the stated rule.

Suppose someone worked on March 14, and the biweekly payday is March 22. That does not automatically guarantee the March 22 check includes March 14. It depends on the pay period cutoff. Many systems assign work to a pay period based on time-entry date and cutoff timestamp, not simply on whether the workday occurs before the payday.

This is the area where payroll systems diverge, so you cannot safely compute it without the cutoff rule.

If your semi-monthly pay dates are the 15th and last day, and the last day is a Saturday, the payday is often moved to Friday. If someone started work on the last Friday, their pay could be included in the moved payday if the cutoff allows it, or it could roll into the next cycle depending on the system. Again, payday date and cutoff date are related but not identical.

People usually care about one of three things: 1) predictability for employees, 2) operational simplicity for HR and payroll, 3) accounting and accrual consistency.

Semi-monthly offers predictability for employees because every month has two paydays. It also simplifies monthly cash planning for many budgets, since the number of payroll runs is consistent by month.

Biweekly offers strong rhythm because it repeats every 14 days. That consistency can make timekeeping expectations more intuitive for some teams, especially when supervisors schedule shifts in weekly blocks. It also reduces the need to remember month-end variations for payday timing, though you still have to handle holidays and weekend adjustments.

From an operations standpoint, the schedule is only half the story. The other half is how cutoffs are defined, how approvals are timed, and whether your payroll system is configured with correct time zones and policy logic.

No. It is two fixed pay dates. If you pay on the 15th and last day, the interval between paydays changes every month because “last day” is not constant.

Not always. A biweekly schedule can generate three paychecks in a month when pay periods overlap month boundaries in a certain way. That does not mean anything is wrong, it is just calendar math.

There is no universal answer. Hourly employees care about when their hours are credited to a check. If cutoffs are clear and communicated, either schedule works. If cutoffs are confusing, biweekly and semi-monthly both produce complaints, just for different reasons.

When you calculate paydays for a specific year, the safest approach is to build from a known anchor date. If you don’t know the anchor date, find it from:

Then apply your schedule rules:

If your employer publishes a payroll calendar, use it. The work is not just about accuracy, it is about avoiding the policy mismatches that create “missing hours” disputes.

Even when you calculate correctly, it helps to sanity-check with expected annual totals.

This does not replace checking individual pay dates, but it catches mistakes like using the wrong base date or applying a step size incorrectly. It also catches cases where someone is mixing “pay schedule” with “pay frequency setting” in the payroll system, which sometimes looks correct until you review the yearly pattern.

If you want, tell me the pay frequency and the exact pay date rule your employer uses (for example, “biweekly Friday” or “semi-monthly 15th and last day,” plus how holidays are handled). I can walk through calculating the next 6 to 12 paydays and also show how to identify the correct pay period for a given work date.