Documentation

Payroll Schedules

Requires. Payroll with View and Payable+ enabled. Creating, editing, or deleting schedules requires the matching Payroll Create, Modify, or Delete grant.

A payroll schedule is a reusable configuration that counts a payee's activity — installs completed or customers funded — over a specific time window. The count is then matched against a Lookup Table to determine the payout amount.

Open Administration -> Payroll -> Schedules to see the active schedules. Select a schedule name to edit it, or choose New Schedule to create one.

Schedule fields

Field Required? Type Validation Notes
Name Yes Text Up to 255 characters Use a clear, descriptive name such as "Monthly Installs" or "Prior Week Funded".
Description No Text Up to 500 characters Optional explanation of when or how this schedule is used.
Metric Yes Select Installs or Funded customers What to count. Installs counts active, installed, non-cancelled customers whose install appointment falls within the window. Funded customers counts active, non-cancelled customers whose funding was paid in full within the window.
Time Window Yes Select See options below The date range over which to count.
Scope Yes Select Payee only, Team — direct reports, or Team — all reports Whose activity to count. Payee only counts only the payee's own records. Team options count the payee's reports as well (optionally including the payee).
Exclude payee's own records No Checkbox Visible only for team scopes When checked, the payee's own installs or funded customers are excluded from the count. Only the reports' activity counts.

Time window options

Option What it covers
Prior calendar month The full previous calendar month (1st through last day).
Prior calendar week Monday through Sunday of the previous week.
Prior day Yesterday (midnight to 11:59 PM).
Rolling 7 days The seven days ending now.
Rolling 30 days The thirty days ending now.
Rolling 60 days The sixty days ending now.
Rolling 3 days The three days ending now.
Year to date January 1 of the current year through now.

How schedules connect to payroll level rows

Schedules do not pay out on their own. A payroll level row must use the Scheduled count lookup amount source to activate a schedule.

When you set a level row's Amount Source to Scheduled count lookup, you choose two things:

  1. Schedule — the schedule that defines what to count and over which window.
  2. Lookup Table — a single-dimension table whose rows map count thresholds to payout amounts.

At payout time, SecurityTrax runs the schedule against the payee, gets a count, and uses that count to find the best-matching row in the lookup table. The matching row's amount becomes the payout.

Tip. Set up the lookup table first. Use a single dimension with the schedule variable (it appears in the Schedule group in the Variable picker once you have active schedules), Minimum of range (numeric) match type, and one row per count tier. Then create the level row and wire in the schedule and the table.

Scope and team counts

When scope is set to a team option, SecurityTrax counts activity across every user in the payee's reporting line — not just the payee. Use this for manager bonuses that depend on how many installs or funded customers the team produced.

  • Team — direct reports includes only the users who report directly to the payee. Add the payee's own records by leaving Exclude payee's own records unchecked.
  • Team — all reports includes the payee's entire reporting hierarchy, down to the deepest level.

If a payee has no reports, a team-scoped schedule with Exclude payee's own records checked returns 0 and produces no payout.

Deleting a schedule

Before deleting a schedule, remove any payroll level rows that reference it. A deleted schedule causes those rows to return a count of 0 and pay nothing.

Related

Ask about the docs
Ask about the docs
Answers from the SecurityTrax documentation

Ask about a feature, setting, or workflow.

Answers come from the documentation. Double-check anything important. AI features are subject to the AI Terms.