Role-Scoped Compensation Data. Pay Runs With An Audit Trail.

Access is scoped on the server from the org hierarchy. A manager sees their own reporting subtree, an employee sees only their own record, and visibility is never enforced by a client-side toggle alone.

Yes. A pay run moves through Draft, Submit, Approve and Pay, and incentives, salary revisions, claims and loans route through built-in approvals. Every step is written to an audit trail.

Access is defined by role. A permissions matrix sets what each role can view and do, enforced on the server, so configuration and approval can sit with different roles rather than one person. Custom approval workflows are part of Enterprise.

Role-Based Access Control is part of the Growth plan, alongside the full payroll suite and statutory compliance — Starter's org hierarchy tops out at three levels without the same access scoping.

Incentive plan rules are defined once. Each cycle, qualifying transactions are captured against them and routed for approval. Approved amounts are paid alongside fixed salary in the pay run, which moves from Draft to Submit to Approve to Pay, and payslips generate once it is paid.

Yes. While the run is still a draft, BizzField compares each employee's pay with the previous cycle and flags sharp movements, duplicate claims and timesheet conflicts. Reviewers work through those flags before the run is submitted and approved, so a heavy incentive month is checked before payment, not recovered after it.

Access scope derives from the person's position in the org hierarchy, so when their reporting line changes, their scope updates with it, without a separate access request. A new manager sees their own reporting subtree and nothing more.