Guide

    Why leave and timesheets belong in the same system

    Two systems produce two answers to "was that person working on the 14th?" — and neither is trusted.

    The short answer

    Should leave management and time tracking be in one system?

    Leave and time tracking belong together because every workforce metric needs both. Utilisation requires available hours, which is scheduled hours minus approved leave. Payroll needs to know a thin week was planned absence, not underperformance. When the two live in separate systems they disagree, and reconciling them becomes somebody’s recurring job.

    The reconciliation tax

    Separate systems mean somebody exports both every month and matches them by hand. That work produces nothing, recurs forever, and introduces its own errors — a pure tax paid for a decision made once, usually by accident.

    One approval scope for both

    The person best placed to approve an absence is the person who approves the hours: the direct manager. In Flocci Timesheets leave listing and approval are manager-scoped exactly like time entries, so one reporting line governs both.

    Policies that carry real rules

    A leave policy here holds an allowance, an accrual period and an unlimited flag, so entitlement is computed rather than remembered. Requests move through a request-and-approve flow instead of an email thread.

    The solo case, handled honestly

    A one-person workspace has nobody to approve leave, so leave requests are created Approved and the interface frames it as recording rather than requesting. That is more honest than showing a pending queue that will never have a reviewer.

    Last reviewed 2026-10-20 by Flocci Technologies.

    Follow-up questions

    Does this replace an HRMS?
    No. It covers leave policies, requests and approval next to time. Statutory Indian payroll compliance, employee lifecycle and benefits administration belong in a full HRMS — Flocci Technologies builds one separately in its ERP work suite.
    Can a manager approve leave for anyone?
    Not since 2026-07-28. Leave listing and approval are now manager-scoped to direct reports, matching how time entries had always worked. Admins and Owners still see leave organisation-wide.
    What is the unlimited flag?
    It marks a policy as having no allowance ceiling, so requests against it are not measured against a remaining balance. The request and approval flow is otherwise unchanged.

    Put the workflow to work.

    Draft → Pending → Approved, free at every team size, with no per-seat licence in the way.