HRMS · Leave Policies
Hub /admin/leave/global-policy-center Balances /admin/employee-leave-config Apply /people/leaves

Leave Policies User Guide

One place for supported leave policies, how to configure them in Global Policy Center, go-live scenarios, and how new CFA requirements map to shipped Tracopus features.

Screen setup checklist: Leave Configuration · Runtime apply/approve: Leave Management · Scenarios: Configure Global Leave

Policy catalog reading

What the engine can express, and how CFA maps in

The leave policies user guide is the reading room for supported policies, Global Policy Center configuration, go-live scenarios, and how new CFA requirements map to existing types — not a second policy editor.

Docs · Leave policies (opens from Leave admin Guide) Route /admin/leave/global-policy-center HR Admin · implementation partner

The job of this console

Match a business rule to a supported policy shape before you click Publish. Use go-live scenarios as rehearsal, then configure in Policy Center.

Seat at the table

People designing leave. Employees read balances on Leave management, not this guide.

The working rhythm

Find the policy family, read the mapping, configure in Global Policy Center, prove in Test lab or a sample apply.

Moments that bring you here

A statutory type you have not used. CFA / compliance mapping. Training a new HR admin. Before cloning a policy that is already the wrong shape.

ⓘ
Guide, then Policy Center
Nothing here publishes. The live policy list remains in Global Policy Center.

What this guide covers

Tracopus leave has two layers:

  1. Policy configuration — jurisdictions, country templates, versioned team policies, holidays, working days, publish (this guide + Leave Configuration).
  2. Day-to-day runtime — employees apply on People → Leave management; managers approve there or in Workspace → Approvals.
Shipped — India CFA packs Shipped — apply / approve / accrual / CF Partial — AE / SA / US stubs Planned — adoption days TBD
ℹ️
Publishing ≠ balances
Publishing a policy activates eligibility and accrual rules. Opening balances still come from Employee leave config (OB template → dry-run → live) or the accrual schedule — Tracopus does not invent balances.

Domain principles

  • Location-driven policy — entitlements differ by work location / jurisdiction (KA, MH, HR, TN-CBE, …).
  • Two leave years — earned leave uses fiscal Apr–Mar; floating holiday budget uses calendar Jan–Dec.
  • Leave always needs approval — even when attendance auto-approves for some bands.
  • Configurable, not hardcoded — rules live in Global Leave templates / published versions (not hard-coded Sat/Sun).
  • Canonical sources only — Employee, leave types, balance ledger, holidays, TaskActivity promotion; no shadow leave tables.

Quick path (first go-live)

  1. Flags — enable leaveManagementEnabled (+ Global Leave role modules) in Application Config.
  2. Publish policy — Global Policy Center: jurisdiction → apply CFA India template → simulate → publish (or use production prefill SQL for defaults).
  3. Holidays + working days — calendar keys + weekly-off rules.
  4. Balances — Employee leave config OB template / Adjust balance.
  5. Prove — apply spanning holiday → Approvals approve → check timesheet / attendance sync.