Payroll Admin Overview

Requires. Payroll with View to open Payroll admin. Creating, editing, or deleting payroll records requires the matching Create, Modify, or Delete grant for Payroll.

The Payroll admin area defines how SecurityTrax calculates what your company owes to employees and partners when specific events happen — a customer is sold, an install completes, funding posts, a referral converts. With Payable+, supported customer events can also attempt payable generation automatically. The entries these rules generate show up on each user's My Payroll and on the company-wide Payable Entries report.

Users with Payroll access can manage roles, functions, levels, and examples from the Payroll admin area. Payable+ adds lookup tables, automatic generation events, row conditions, and other advanced calculation controls.

Some older payroll functions are managed by the SecurityTrax Team. When you open one of those functions or levels, SecurityTrax shows the name and a warning callout instead of editable fields. Those functions cannot be created, edited, or converted from Payroll Admin.

The three-level hierarchy

SecurityTrax payroll rules are nested three levels deep. Understanding this shape is the key to reading entries on My Payroll or filing a support request that gets resolved quickly.

Payroll Role
  └─ Function (one rule per event type)
       └─ Level (tier / adjustment on the function's output)

Role — a named bundle of functions. Example roles: "Install Tech", "Sales Rep", "Lead Rep", "Manager Override". A user can hold multiple roles at once.
Function — a single calculation within a role. Example: "Install Tech — Per Install", "Install Tech — Equipment Add-On Bonus", "Install Tech — Same-Day Bonus". A role can have many functions; each fires on a different event or under different conditions.
Level — a tier applied to a function's output. Example: a tech at level 1 earns the base amount; level 2 earns 110%; level 3 earns 120%. Levels are how SecurityTrax handles seniority-based progression without duplicating functions.

A single sale might fire several payroll entries — one for the sales rep's commission function, one for the install tech's per-install function, and one for the manager's override on the rep's sale. Each runs through its own role → function → level chain.

How automatic generation works

Payable+ automatic generation uses event subscriptions on payroll functions. For example, a customer-based function can be configured to attempt a payable when a customer becomes installed, when the customer becomes funded, when a selected customer tag is applied or removed, or when a selected customer custom field is saved.

An event only starts the attempt. SecurityTrax skips duplicate active payables for the same customer, function, and payee. Payee resolution, amount setup, and Payable+ row filters can still cause individual rows or the whole attempted payable to produce nothing.

What you can edit

Payroll Admin is for payroll rules that SecurityTrax can manage directly:

Role functions define the event or reason someone can be paid, the list method that finds possible payees, whether the function is active, and any Payable+ automatic-generation events.
Levels define the tier that users or entities are assigned to under the function.
Payable rows define who receives money and how the amount is calculated. Without Payable+, rows use fixed amounts. With Payable+, rows can use variables, lookup tables, expressions, notes templates, and row-specific filters.

Payroll Admin does not expose legacy calculation-method fields or shared function-column controls. If a function is managed by the SecurityTrax Team, the page intentionally hides levels, rows, automation events, and save/delete actions so the rule cannot be accidentally changed.

Plan a payroll change

Before changing a payroll rule, gather these details:

Which event is involved. "When a sale closes," "when an install completes," "when funding posts," etc.
Whether automatic generation should be tied to install, funding, tag changes, custom field changes, or more than one event. If tags or custom fields are involved, include the exact tag names or custom field names and any required custom field value. Automatic generation currently runs for customer-based payroll functions.
Who should be paid. Sales rep? Install tech? Lead rep? Manager? More than one?
The math. A flat dollar amount, a percentage of contract value, a lookup against a rate sheet, or something more complex.
Eligibility rules. Only deals with a specific account type? Only customers in certain states? Only when a referral was attached?
Effective date. When the new rule should start firing.

Existing payable entries don't change retroactively when a rule is updated. New rules only affect events that happen after the change takes effect.

If your team asks SecurityTrax support to help configure the rule, include the same details so the request can be handled quickly.

How payroll data surfaces in SecurityTrax

You see the output of payroll rules in three places:

My Payroll — your own generated entries, period by period.
Payable Entries — the cross-user, cross-customer report.
Customer record → Payables — every payable tied to a specific customer.

If an entry's amount looks wrong or you expected one that didn't appear, check the troubleshooting tips on My Payroll first, then contact SecurityTrax support if it isn't resolved.