Overview
A payroll schedule determines the length of your pay period and how often you pay your employees. The most common payroll schedules are weekly, biweekly, semimonthly, and monthly. Your payroll schedule is dependent upon a few factors, including provincial laws and regulations. Many provinces have pay schedule frequency requirements that you’ll need to meet. On top of provincial laws, your pay schedule should also fit the needs of your employees and your business. If you employ mostly hourly workers, your pay schedule may look different from a business with mostly salaried employees. Your province, your industry, and the types of workers you employ all impact your payroll schedule. Typical pay frequencies include:- Weekly
- Bi-weekly
- Semi-monthly
- Monthly
Pay Schedule Parameters
Pay Day Movement Options
inherit(default): Use the Business Entity setting.previous_business_day: Move to the previous working day.next_business_day: Move to the next working day.
Non-Standard Period Counts
Weekly and bi-weekly schedules carry an extra pay period in some years, a 53rd or 27th payroll, which lowers the per-period amount of an annual salary. Some employers prefer to divide the salary over the standard 52 or 26 periods regardless, so an employee’s per-period pay stays the same from year to year.custom_pay_periods_per_year may be used to override the count that salaries are divided by. See Years With an Extra Pay Period.
Custom Pay Schedules
For more information on Custom Pay Schedules, please see theCustom Pay Schedules guide.
Creating a Pay Schedule
Endpoint
POST /services/payroll/pay_schedules
Request Example
Success Response
Error Response Example
Behavior by Pay Frequency
Weekly
- Projects payrolls weekly based on the weekday value of
anchor_pay_dateandanchor_end_of_pay_period.
Bi-Weekly
- Projects payrolls every two weeks based on the weekday value of
anchor_pay_dateandanchor_end_of_pay_period.
Semi-Monthly
- Two pay periods per month, paid on fixed pay dates set by
day_1andday_2. day_1andday_2are any two different days of the month, from1to31, or-1for the last day of the month. The two days can be in either order.day_1andday_2can’t both be28or later (-1counts as31), because those days land on the same date in February.- If
day_1orday_2doesn’t exist in a shorter month, the payroll’soriginal_pay_dateis that month’s last day. For example, a pay day of30gives anoriginal_pay_dateof February 28 in a non-leap year. anchor_pay_datemust fall onday_1orday_2. In a month where the pay day doesn’t exist, the month’s last day counts as the pay day.- The anchor dates set which pay period each pay date pays, so a schedule can pay after a pay period closes or before it closes. For example, a schedule with pay days
7and22and ananchor_end_of_pay_periodof January 15 pays the January 1 to 15 pay period on January 22 whenanchor_pay_dateis January 22, or on January 7 whenanchor_pay_dateis January 7.
Monthly
- One payroll per month.
day_1defines the pay date. Use-1to indicate “last day of the month”.- If
day_1would fall on an invalid date (e.g., September 31st), the payroll’soriginal_pay_datewill be adjusted to the prior valid date.
Notes
- Date Validations: Invalid dates automatically roll back to the nearest valid day.
- Pay Date adjustment: If the payrolls
original_pay_datefalls on a weekend or holiday, the payrollspay_datewill be adjusted to a valid date based on thepay_day_movement_setting. - Defaults: If
pay_day_movement_settingis not provided, the Business Entity default is used.

