Leave tracking fails quietly. A spreadsheet drifts by a day here and half a day there, and nobody notices until someone resigns and the encashment figure is disputed. A system that owns the balance — allocating, deducting and carrying it forward automatically — does not drift.
No credit card at signup. No trial clock. Your organisation gets its own isolated database.
Real leave policies have more edge cases than a simple request form can handle.
Casual, sick, earned, maternity, paternity, bereavement or anything specific to your organisation, each with its own rules.
Annual entitlement is allocated per employee, deducted on approval and visible to everyone — no parallel spreadsheet.
Requests route to the right approver automatically, with the decision and timestamp recorded.
Public and company holidays are declared centrally so they are never deducted as leave by mistake.
Time worked on a holiday or week-off converts into compensatory leave and enters the same balance.
Unused balance converts to a payable amount and flows into payroll rather than being calculated by hand at exit.
WFH is its own request type, so a remote day is recorded as worked instead of showing as an unexplained absence.
Applicants and approvers are notified by email and in-app, so requests do not sit unseen in a queue.
They pick a leave type, the dates and a reason, and see their remaining balance before submitting.
The request reaches the right approver with the employee's balance and team calendar as context.
On approval the balance is deducted and the attendance register is marked, both in the same action.
Paid and unpaid leave carry into payroll automatically, and the balance is already correct at exit.
A leave spreadsheet is accurate on the day it is written and slightly wrong every day after. Half-days get rounded. A cancelled request is approved but never subtracted back. Someone is added mid-year and their pro-rated entitlement is estimated. A carry-forward cap is applied inconsistently across departments. None of these are dramatic on their own, and together they produce a balance nobody trusts.
The cost surfaces at two moments: when an employee disputes a deduction on their payslip, and when someone leaves and the encashment figure has to be defended. Both are arguments you cannot win without a record of every allocation and deduction.
In ADMINFACE the balance is derived, not maintained. It is allocation minus approved deductions plus comp-off earned, and every movement has a record attached showing what caused it and who approved it. There is no second copy to reconcile, because approving a request is what updates the balance.
An approver seeing a request also sees the employee's remaining balance and what else is already approved around those dates. Approving three people onto the same week is a decision worth making deliberately. Notifications go out by email and in-app on both application and decision, so requests do not stall in a queue nobody is watching.
Every employee sees their own balance, their full leave history and the status of anything pending, without asking anyone. A large share of routine HR queries is simply "how many days do I have left", and self-service removes that traffic entirely.
Leave has direct payroll consequences, and keeping them in one system removes the month-end reconciliation. Unpaid leave becomes loss of pay in the payroll run. Encashed balance becomes a payable component. At exit, the final settlement already knows the correct balance rather than depending on a spreadsheet that has been drifting for three years. If you want to see how leave encashment and gratuity interact at exit, the free gratuity calculator covers the statutory side.
| ADMINFACE | Typical HR platform | |
|---|---|---|
| Cost | Free for unlimited employees | Per employee, per month |
| Leave types | Unlimited and fully configurable | Often capped on lower tiers |
| Attendance link | Same register — updated on approval | Frequently a separate sync |
| Comp-off and encashment | Included | Commonly missing or manual |
| Payroll link | LOP and encashment carry through | Usually a manual hand-off |
| Holiday calendar | Central, excluded from deductions | Often maintained per team |
"Typical HR platform" describes the pricing and packaging patterns common across the category — per-employee monthly billing, feature tiers and time-limited trials. Individual products vary; check current terms with any vendor you are comparing.
Yes. Leave types are configurable — casual, sick, earned, maternity, paternity, bereavement or anything specific to your organisation — each with its own annual allocation. There is no cap on how many you create.
The balance is derived from the annual allocation, minus approved leave, plus any comp-off earned. It updates the moment a request is approved rather than being maintained separately, so there is no second copy to reconcile.
Yes. Approving leave marks the attendance register for those days in the same action, so an approved leave day can never also appear as an unexplained absence. This prevents the most common cause of incorrect loss-of-pay deductions.
Yes, and half-days are held as half rather than rounded to a full day in either direction, so the balance stays accurate over a year of them.
Both the applicant and the relevant approvers receive email and in-app notifications on application and again on the decision. Exactly who is notified follows your organisation's configured policy.
Yes. WFH is its own request type with its own approval flow, so a remote working day is recorded as worked rather than consuming leave balance or appearing as an absence.
Unused leave balance can be encashed and converted into a payable amount that flows into payroll. Because the system has owned the balance all along, the encashment figure is derived from a record of every allocation and deduction rather than reconstructed at exit.
The whole platform at no cost, for unlimited employees — funded by ads in the app rather than per-seat fees.
HR built for teams of 5 to 200, without the per-seat maths or the enterprise implementation project.
Clock in/out, shifts, overtime, GPS and biometric sync feeding one attendance register.
Salary structures, PF, ESI, professional tax, approval workflow, PDF payslips and EPFO ECR files.
Sync eSSL, ZKTeco and Hikvision devices straight into attendance — pull or ADMS push.
Reusable onboarding templates, task checklists and a self-serve joiner portal.
Set up your leave types and holiday calendar, allocate balances and let employees apply for themselves. Free for unlimited employees.