Category: Payroll & Compliance

  • Sandwich Days, Explained: A Fair Way to Handle Attendance Edge Cases

    An employee takes leave on Friday and the following Monday. In between sits a weekend, or worse, a public holiday. Does that middle stretch count as leave too, or is it exempt? Most attendance policies never write down an explicit answer — they just quietly assume one, and HR finds out which assumption when someone disputes their payslip.

    Why “Just Pick One Rule” Doesn’t Work

    A blanket rule — always include, or always exclude — feels simple until it collides with a real case: a holiday deliberately used to extend a trip, versus a genuine coincidence of scheduling. Treating both identically is fair in the abstract and frustrating in practice.

    A sandwich day isn’t a rule to automate away. It’s a decision that deserves a human to actually look at it.

    The Better Default: Flag, Don’t Assume

    • Automatically detect when a weekend or holiday sits between two leave days
    • Flag it explicitly, rather than silently including or excluding it
    • Let HR make an include/exclude decision on that specific case
    • Never apply the same silent assumption to every employee regardless of context

    This keeps the system honest about the fact that some attendance edge cases genuinely need judgment — and makes sure that judgment is applied deliberately, not buried in a default nobody remembers configuring.

    Attendance windows, half-day cutoffs, and sandwich-day handling are all configurable per organization. See Attendance Tracking →

  • The Real Cost of Manual Payroll Reconciliation

    Somewhere in most companies, a spreadsheet gets rebuilt every single month: attendance pulled from one system, leaves from another, manual adjustments tracked in a third, all reconciled by hand into something payroll can actually run against. The cost of that process rarely shows up as a line item — it shows up as a person’s entire last week of the month.

    Where the Hours Actually Go

    • Re-entering attendance data that already exists somewhere else
    • Manually calculating paid days from present/absent/half-day/leave records
    • Cross-checking PF and professional tax by hand, employee by employee
    • Chasing down one-off adjustments that never made it into the main record

    None of this is hard, exactly — it’s just repetitive, error-prone, and entirely avoidable when attendance and payroll already live in the same system.

    The most expensive part of manual reconciliation isn’t the hours it takes. It’s the one mistake that makes it into someone’s actual paycheck.

    What Attendance-Linked Payroll Looks Like

    When payroll reads directly from the same attendance data used everywhere else, paid days, PF, and professional tax calculate themselves — automatically, and consistently, every single run. Adjustments still happen, but they layer on top of the record instead of requiring it to be rebuilt.

    See a projected payroll run before the month even closes, recalculated as attendance comes in. See Payroll Management →