Payroll · readiness
Route /admin/payroll-config Flag payrollConfigEnabled

Payroll Readiness

Validate mandatory gates, then jump into groups, structures, and publishing config.

Scroll to Flowcharts. Scenario: Configure org payroll settings.

Payroll gates

Prove the org is allowed to run payroll

Payroll readiness validates mandatory gates, then jumps into groups, structures, and publishing config. It is the door to payroll, not the run itself.

Payroll → Payroll readiness Route /admin/payroll-config Org flag payrollConfigEnabled Payroll Manager · Finance Manager · HR Admin

The job of this console

See which gates are red, open the owning console, fix people, attendance, or structure data, then return until readiness is green. Do not start a payroll run from this page.

Seat at the table

Payroll and HR administrators. Employees view paychecks elsewhere. Project managers have no role here.

The working rhythm

Read the gate list, follow each fail into groups, salary structures, or people data, correct, refresh readiness, then continue to payroll runs when green.

Moments that bring you here

First payroll in a tenant. A new legal entity. After a bad attendance month that should block pay. Before publishing structures.

ⓘ
Readiness is a checklist on live HR data
Gates read Employee, attendance, and structure — they do not store a parallel payroll employee list.

Flowcharts

1 — Clear readiness gates

Fix missing config, then open payroll groups / structures.

flowchart TD
  A[Open Payroll readiness] --> B[Read checklist]
  B --> C[Fix missing gates]
  C --> D[Save]
  D --> E[Open groups / structures]
  E --> F[Preview a run]
            
  1. 1
    Open readinessAdmin → Payroll readiness (also under Payroll).
  2. 2
    Resolve gatesMandatory org fields and lists.
  3. 3
    Continue in PayrollGroups, structures, and runs stay on payroll routes.

Overview

Readiness is a gate over Application Config payroll nodes and valid employee bridge rows. It is not a payroll run engine.

How to use

1. Do not skip statutory IDs
Runs will block later.
2. Source of truth
Application Config + employee records — not this page’s KPIs.
3. Masking
Salary fields remain persona-masked.