ZenotiHelp

PTO payroll β€” Average pay, Fixed pay and Hourly pay compensation types

ZTZenoti Docs Team Updated November 9, 2026 9 min readGuide

Employees who take paid time off (PTO) expect to be paid for it. A leave policy now offers three ways to work out that pay: Fixed pay, Hourly pay and the new Average pay. Use Average pay for commission-based employees, who have no hourly rate on their profile and whom you don't want to pay the same fixed rate as everyone else. Zenoti pays PTO at the average rate the employee has actually been earning, taken over a Lookback period that you choose.

This article explains the three compensation types, how to set up Average pay, how Zenoti works out the average rate, and the primary work task hourly rate fallback that applies to Hourly pay.

Audience: Payroll administrators and center managers who manage leave policies and PTO payroll calculations.


On this page


Before you begin

  • Your organization must have PTO enabled. Contact your administrator to confirm that the Enable PTO setting is turned on at Configuration > Employee.
  • Work tasks must be enabled at your organization if you want the primary work task rate fallback to apply. The Enable work tasks setting is at Configuration > Employee > Employee attendance > Check in.
  • Employees must have leave entries created and approved before PTO pay is included in payroll calculations.
  • You need the following permissions to approve leave and run payroll:

Permission: Manage (under Leave Approvals) β€” Required to approve or reject leave requests submitted by other employees. Grant it on the Leave Approvals row in the Employee Manager section of the security role (Configuration > Security > Security roles > the role > Permissions).

Permission: Enable (under Auto Leave approval) β€” Required to approve your own leave requests without manager review. Grant it on the Auto Leave approval row in the Employee Manager section of the security role (Configuration > Security > Security roles > the role > Permissions).

Permission: Add (under Work Tasks) β€” Required to create work tasks used in the primary work task rate lookup. Grant it on the Work Tasks row in the Employee Manager section of the security role (Configuration > Security > Security roles > the role > Permissions).


How PTO compensation types work

When a leave group in a leave policy is paid time off, you choose a Compensation type. It tells Zenoti how to work out the dollar amount owed to the employee for those hours. The compensation type is part of the leave policy, not something you set on an individual leave entry. Payroll picks it up automatically when it processes PTO hours for the pay period.

Compensation type How Zenoti calculates PTO pay Best for
Fixed pay Uses one fixed hourly amount for everyone covered by the leave group, whatever their role or level. For example, if the fixed amount is $15, every employee is paid $15 for each PTO hour. A flat PTO rate for all employees
Hourly pay Uses the hourly rate defined on the employee's profile. Employees who are paid by the hour
Average pay (new) Uses the employee's average hourly rate over the Lookback period that you set in the leave policy. Commission-based employees, who have no hourly rate on their profile

Set up Average pay in a leave policy

You set Average pay on a leave group inside a leave policy.

  1. Navigate to Employee > Manage Leaves. Open the leave policy that you want to change, or create a new one. A new policy (Create new leave policy) has four steps: Policy details (Policy name and Description), Leave groups, Employees and Notifiers.
  2. On the Leave groups step, open an existing leave group, or add a new one to open the Add leave group panel. The panel has three steps: Allotment details, Tenure rules and Policy rules.
  3. On Allotment details, enter a Leave group name and select the Leave types that the group covers.
  4. For Is this paid time off?, select Yes.
  5. For Compensation type, select Average pay. The Lookback period (weeks) field appears.
  6. In Lookback period (weeks), enter how many weeks of past pay Zenoti should average, from 4 to 13 weeks. For example, enter 6 to average the last six weeks.
  7. Complete the rest of the leave group (Allocation, then the Tenure rules and Policy rules steps), and save the policy.

What you see after you choose a Compensation type:

  • Fixed pay β€” an Hourly compensation field, where you enter the one amount paid for every PTO hour.
  • Hourly pay β€” no extra field, because Zenoti uses the hourly rate on each employee's profile.
  • Average pay β€” the Lookback period (weeks) field.

The Lookback period (weeks) field answers one question: how far back should Zenoti look when it averages the employee's pay? A short lookback follows recent earnings closely. A long lookback smooths out busy and quiet weeks.

Note: Lookback period (weeks) is required when the Compensation type is Average pay. Zenoti doesn't save the leave group without a value from 4 to 13.


How Zenoti calculates the average rate

Zenoti works out the average rate from the employee's actual pay, so it needs no hourly rate on the employee's profile.

  1. Zenoti saves an average rate for each pay period. For every payroll that runs, Zenoti divides the employee's gross earnings by the hours in that pay period, and saves the result. Gross earnings for this purpose don't include PTO pay itself. The hours are the hours the employee checked in. When there are no checked-in hours, Zenoti uses the scheduled hours.
  2. Zenoti averages the saved rates over the lookback. When PTO is paid, Zenoti takes the saved pay-period rates that fall inside the Lookback period (weeks). The lookback ends the day before the current pay period starts. The average of those rates is the employee's average rate.
  3. Zenoti pays the PTO hours at that average rate. PTO pay is the average rate multiplied by the PTO hours.

The first time Average pay is used after this feature is released, Zenoti calculates the average rate over the lookback period that you configured. From then on, Zenoti saves the average rate for every payroll and uses the saved rates.

Worked example

Your leave policy has a leave group with Compensation type set to Average pay and Lookback period (weeks) set to 6. Jordan is a commission-based stylist with no hourly rate on their profile. Over the last six weeks, the rates that Zenoti saved for Jordan's pay periods average out to $17.00 an hour.

Jordan takes 8 hours of approved PTO. Zenoti pays the PTO at the average rate: 8 hours Γ— $17.00 = $136.00.


Primary work task hourly rate fallback

The primary work task rate fallback is a separate, smaller rule. It applies to leave entries that use an actual hourly rate, such as Hourly pay, when work tasks are enabled for your organization. If an employee has no hourly rate for the period, for example because they are fully off, there is nothing to look back at, so Zenoti picks the rate from the employee's work task configuration instead. It doesn't change how Average pay works.

When the fallback applies

The primary work task rate fallback applies when all of the following are true:

  • Work tasks are enabled at Configuration > Employee > Employee attendance > Check in (the Enable work tasks setting is on).
  • The employee's actual hourly rate for the relevant period is null or zero.

How Zenoti resolves the rate

When the actual hourly rate is null or zero, Zenoti looks up the rate in this order:

  1. Primary work task rate β€” Zenoti identifies the organization's primary work task using the organization-level primary work task setting. It then looks up the employee's hourly rate for that specific work task.
  2. Employee profile hourly rate β€” If no primary work task rate is found for the employee, Zenoti falls back to the hourly rate recorded on the employee's profile.

Note: The primary work task is set at the organization level by your Zenoti administrator. Employees do not configure this themselves. To see which work task is designated as primary, navigate to Employee > Jobs and review the work task assignments, or contact your administrator.

Worked example

Your organization has work tasks enabled. The primary work task is "Stylist β€” Floor." An employee named Alex has:

  • Actual hourly rate: null (not set for this period)
  • Rate for "Stylist β€” Floor" work task: $18.00/hour
  • Profile hourly rate: $15.00/hour

When payroll processes Alex's PTO hours, it finds the actual hourly rate is null. It looks up Alex's rate for the primary work task ("Stylist β€” Floor") and finds $18.00. Zenoti uses $18.00 as the PTO hourly rate.

If Alex had no rate configured for "Stylist β€” Floor," Zenoti would use the profile hourly rate of $15.00 instead.


Null value handling

For leave entries with a compensation type of Fixed pay or Hourly pay, Zenoti applies a consistent null-coercion rule to prevent calculation errors.

Rule

If the hourly compensation value or effective rate for a Fixed pay or Hourly pay leave entry is null, Zenoti treats it as zero rather than producing a null PTO pay amount.

This means:

  • Payroll completes without errors even when rate values are missing.
  • The PTO pay amount for that entry is $0.00.
  • The employee's payroll record reflects zero PTO earnings for that entry rather than an undefined or missing value.

Important: A PTO pay amount of $0.00 resulting from a null rate is not the same as no PTO entry. The entry still appears in payroll records. If an employee's PTO pay appears as $0.00 unexpectedly, check whether their hourly rate or fixed compensation is configured correctly. See Troubleshooting below.


Tips

  • Choose the compensation type by how the employee is paid. Use Hourly pay for employees with an hourly rate, Fixed pay when everyone gets the same PTO rate, and Average pay for commission-based employees.
  • Pick a lookback that matches your pay pattern. A short lookback follows recent earnings closely. A long lookback, up to 13 weeks, evens out seasonal busy and quiet periods.
  • Verify the primary work task assignment before running payroll. If work tasks are enabled and your organization relies on the primary work task fallback, confirm that each employee who might have a null actual hourly rate has a rate configured for the primary work task. Navigate to Employee > Employees, open the employee profile, and review the work task rate assignments.
  • Check leave entry compensation types before the pay period closes. Once a pay period is locked, you cannot edit attendance details or recalculate commissions for past payroll. Review leave entries and their compensation types while the period is still open.
  • Confirm the Enable work tasks setting is on if the fallback is expected. If work tasks are disabled, the primary work task rate lookup does not run β€” Zenoti goes directly to the employee profile hourly rate for any null actual hourly rate situation.

Troubleshooting

An employee's PTO pay is $0.00 for a Fixed pay or Hourly pay leave entry.

The most common cause is a null hourly rate. Zenoti coerces null values to zero, so no error is raised but no pay is generated. To resolve this:

  1. Navigate to Employee > Employees and open the employee's profile.
  2. Select the Payrates tab and confirm that a valid hourly or fixed rate is entered.
  3. If the rate is missing, add it and then recalculate payroll for the period before the payroll lock date passes.

The primary work task rate fallback did not apply β€” Zenoti used the profile hourly rate instead.

This occurs when the employee has no rate configured for the organization's primary work task. To resolve this:

  1. Confirm which work task is designated as the primary work task by contacting your administrator or reviewing the organization-level work task settings.
  2. Navigate to Employee > Employees, open the employee's profile, and check the work task rate assignments to ensure the primary work task has a rate entered for that employee.
  3. If work tasks are disabled at Configuration > Employee > Employee attendance > Check in, the fallback lookup does not run at all β€” only the employee profile rate is used.

Was this article helpful?
Your feedback helps us improve our documentation.