Pay Period Calculator Pay Period
Calculate pay dates that comply with Federal Reserve banking schedules — automatically adjusted for weekends and bank holidays.
Data Source
Based on Federal Reserve K.8 holiday schedule and FLSA fixed-workweek definitions.
Planning Use Only
Results are for payroll planning. Verify against your state's Department of Labor requirements and consult a certified payroll professional.
Pay Period Planning at a Glance
The gap between when work happens and when funds land is more complicated than it looks.
Every payroll cycle has two dates that look similar but work differently. The pay period calculator separates them clearly. The period end date is the last day your company tracks hours. The pay date is when those wages actually hit bank accounts. Between them sits the processing lag — the administrative window where HR verifies timesheets, calculates deductions, and transmits ACH files before the bank's cutoff.
Miss that cutoff by one day, and your employees wait an extra banking day for their money. Miss it on the eve of a Federal Reserve holiday, and they wait longer still.
Quick Answer: Enter your pay period start date, select your frequency (weekly, bi-weekly, semi-monthly, or monthly), and set your processing lag. The calculator outputs the period end date and the nearest preceding business day compliant with Federal Reserve banking schedules.
Most payroll mistakes trace back to conflating these two dates. They represent fundamentally different phases of the compensation cycle.
Pay Period
The fixed, recurring timeframe during which employee hours are tracked. The FLSA requires this to be exactly 168 hours (weekly) or its equivalent — it cannot vary from cycle to cycle.
Processing Lag
The administrative gap between the period end date and the pay date. HR uses this window to collect timesheets, verify overtime, calculate deductions, and submit ACH batch files to the bank.
Pay Date
The date funds are deposited into employee accounts. This is what must clear Federal Reserve banking windows and avoid weekend/holiday closures — it's the legally relevant date.
| Concept | Definition | Practical Example |
| Pay Period | Fixed block of time where hours are tracked | Mon Jun 1 to Sun Jun 14 |
| Pay Date | Day funds are deposited to the employee's account | Fri Jun 19 |
| Processing Lag | Administrative buffer required between the two | 5 days (Jun 14 → Jun 19) |
HR Manager rule of thumb: Always mandate a minimum 4-day processing lag. It provides the buffer to resolve timesheet disputes, calculate overtime, and transmit ACH files before the bank's afternoon cutoff. Many compliance violations trace back to a 1- or 2-day lag that worked fine until a team member disputed their hours.
To compute a compliant pay date, this calculator applies three sequential formulas. Each builds on the last.
End Date = Start Date + (N − 1) daysNominal Pay = End Date + Processing LagAdjusted Pay = Nominal Pay − Δ days (skipping weekends + Federal Reserve holidays)Why subtract, not add? The FLSA-standard rule is preceding business day. Employees must be paid before the obstacle, not after. Some union CBAs invert this to the succeeding business day — if your workforce has negotiated contracts, check before applying this default.
Semi-monthly variant: When frequency is semi-monthly, Formula 1 changes. If the period starts on the 1st–15th, the period ends on the 15th. If it starts on the 16th–31st, the period ends at the last day of that month (EOM). This guarantees exactly 24 pay periods per year regardless of month length.
This example from the research demonstrates how the preceding-business-day algorithm cascades through multiple obstacles — and why the chart exists.
Calculate the Period End Date
A bi-weekly payroll starts June 15, 2026. Add 13 days (14-day period minus 1 for inclusivity): period ends June 28, 2026 (Sunday).
Calculate the Nominal Pay Date
HR requires a 6-day processing lag. Add 6 days to June 28: nominal pay date = July 4, 2026.
Check the Day of Week
July 4, 2026 falls on a Saturday. Apply the preceding business day rule: shift back 1 day to Friday, July 3.
Check Federal Reserve Holidays
Independence Day (July 4) falls on a Saturday in 2026. The Federal Reserve observes it on the preceding Friday — making July 3 an official bank holiday.
Cascade the Adjustment
Friday July 3 is a bank holiday, so shift back one more day. Thursday, July 2 is a regular business day — the cascade stops here.
Final Pay Date: July 2
Two obstacles bypassed in one cascade: a Saturday AND an observed bank holiday. Without this logic, deposits would be trapped in the banking system over a 3-day weekend.
Why This Matters
Missed ACH transmission windows due to holiday cascades are a leading cause of delayed wage claims. Automating this lookup eliminates the human error of manually checking the Federal Reserve K.8 schedule.
Frequency selection has downstream consequences for HR administration, tax deposits, and — critically — cash flow. The right choice depends on your workforce composition.
| Frequency | Checks/Year | Best For | Key Trade-off |
| Weekly | 52 | Trades, manual labor | Highest employee satisfaction; highest ACH processing cost (~$150/employee/year) |
| Bi-weekly | 26 | Hourly employees | Aligns with FLSA 40-hour workweek; 2 months/year have 3 pay dates |
| Semi-monthly | 24 | Salaried employees | Aligns with monthly benefits deductions; complicates hourly overtime |
| Monthly | 12 | Executives, freelancers | Lowest processing overhead; lowest employee satisfaction |
The 3-paycheck month phenomenon: In any bi-weekly schedule, exactly two calendar months per year will contain three pay dates. This is mathematically inevitable — 26 × 14 = 364, leaving one or two extra pay dates that spill into different months. Budget for a 50% payroll spike in those months, and pre-adjust benefit deductions (health insurance premiums are typically calculated for 2-paycheck months).
For a first pay date of January 2, 2026: the 3-paycheck months are May and October. For a first pay date of January 9, 2026: they are July and December.
There is a rare but disruptive anomaly lurking inside any bi-weekly payroll schedule. A standard year has 365 days; 26 bi-weekly periods cover only 364. The leftover day accumulates annually.
Every 11 to 12 years, this accumulation forces a 27th pay date into the calendar year — the "payroll leap year." When it happens:
Identify Exempt Employees
Salaried employees whose compensation is expressed as an annual figure are affected. Hourly workers simply receive a 27th paycheck for their actual hours worked.
Recalculate the Per-Period Salary
Divide the annual salary by 27 instead of 26. Failing to do this results in overpaying exempt employees by roughly 3.8% for the year (1/26 extra paycheck).
Adjust Benefits Deductions
Many benefit elections (FSA contributions, 401k deferrals) are structured around 26 periods. Review these limits when a 27th period is imminent.
2026 is a standard 26-paycheck year. No payroll leap year adjustment required.
The result gives you two checkpoints:
Period End Date
Use this date to confirm when the tracked work window closes. If this is wrong, every downstream payroll step is wrong too.
Final Pay Date
This is the actionable date for employee communication, ACH planning, and cash-flow scheduling. If it differs from the nominal date, the shift was caused by a weekend or Federal Reserve holiday.
If your calculated pay date moves backward more than expected, double-check whether a bank holiday is stacked against a weekend. The Add/Subtract Business Days Calculator is useful for testing those edge cases independently.
The calculator strictly applies Federal Reserve banking schedules and FLSA fixed-period logic. Several real-world factors it cannot account for:
State-Specific Processing Lag Limits
California requires most employees to be paid within 7 days of the period close; New York's rules vary by worker category. A 10-day lag legal in one state may trigger penalties in another. Always verify your lag against your state's Department of Labor requirements.
Union Contract Overrides
Many Collective Bargaining Agreements (CBAs) require the succeeding business day when a scheduled payday falls on a holiday — not the preceding day used here. Applying the preceding day in unionized environments can technically constitute a contract breach.
ACH Cutoff Times
Even a mathematically correct pay date can result in a one-day delay if the employer misses the bank's ACH transmission window (typically 2–5 PM local time). The pay date alone is necessary but not sufficient for on-time deposit.
International Payroll
This calculator applies U.S. Federal Reserve holidays only. Canadian, UK, EU, and other jurisdictions have different banking calendars. Do not use these results for international payrolls without substituting the correct holiday calendar.
All outputs are for informational planning purposes. They do not constitute legal or tax advice. Consult a certified payroll professional (CPP) for compliance verification. For a deeper comparison of pay frequency regulations by state, see the U.S. Department of Labor's state payday requirements.
The Bottom Line
A reliable payroll schedule depends on three inputs staying aligned: the period start, the pay frequency, and the processing lag. Once those are correct, weekend and Federal Reserve holiday adjustments become predictable instead of last-minute surprises.