Loading page
All-in-one HR platform · v2.0
14-day free trial · No credit cardhello@HrMagix.com
All-in-one HR platform · v2.0
14-day free trial · No credit cardhello@HrMagix.com
Leave goes wrong in two directions at once, employees do not know their true balance, and managers do not know who else is away. HRMagix fixes both with one shared, accrual-accurate calendar.
Leave Management at a glance
Leave is the only part of HR that every single employee interacts with, which is why a bad leave process does far more damage. It is not the policy that irritates people. It is the uncertainty: not knowing the balance, not knowing whether the request was seen, not knowing whether a Friday and a Monday will cost two days or four.
The sandwich rule is the clearest example. It is a perfectly reasonable policy that becomes a source of resentment purely because it is applied inconsistently and explained after the fact.
The parts that decide entitlement, the parts that move an application, and the parts that let people plan around each other.
Leave goes wrong in two directions at once, employees do not know their true balance, and managers do not know who else is away. HRMagix fixes both with one shared, accrual-accurate calendar.
A leave balance is not a number somebody maintains. It is the outcome of an accrual rule applied month by month against a joining date, adjusted for unpaid days, capped by a carry-forward limit and reset on a policy year.
HRMagix computes it rather than storing it, which is why the balance an employee sees in their portal is the same balance the approving manager sees and the same one payroll uses. Categories are configurable, earned or privilege leave, casual, sick, maternity and paternity, each with its own accrual, encashment and carry-over behaviour.
Multi-level approval sounds bureaucratic until you consider what it replaces: an email to a manager who is themselves on leave. Requests route to the reporting manager, escalate on a configured hierarchy where policy requires HR counter-approval, and notify by email and push at each hop.
The employee sees the state of their request at all times, which removes most of the follow-up traffic that leave generates in a company of any size.
An Indian company with offices in more than one state does not have a holiday list. It has several. A shared calendar that shows Bengaluru's holidays to a Pune team is worse than no calendar at all.
Holiday calendars in HRMagix are defined per location, and the team calendar an employee sees combines their own location's holidays with their team's approved leave, so the question "who is around next Thursday" has a single, correct answer.
For eleven months a leave balance is an administrative figure. At the close of the leave year it becomes three different things: leave that carries forward, leave that lapses, and leave that is encashed, and the last of those is a payroll transaction.
The rules that decide the split are the employer's, and they are usually more specific than they first appear. A carry-forward cap. A separate cap on how much of the carried balance may later be encashed. A rule on whether encashment is computed on basic or on gross. A cut-off date that is not the same as the financial year end.
A leave management system earns its place by applying those rules identically to everyone on the same night, and by producing the encashment figures as a payroll input rather than as a spreadsheet somebody types up. The arithmetic is not hard; doing it consistently for four hundred people on one date is.
Loss of pay is where leave and payroll meet, and where the handover between them usually goes wrong. An absence without an approved application, or an approved application against an exhausted balance, becomes an unpaid day, and an unpaid day changes the salary, the PF wage, and in some cases the ESI contribution for that month.
The decision belongs to leave management, because that is where the balance and the approval live. The consequence belongs to payroll. When the two are separate systems, the connection is a monthly file, and the file is prepared under time pressure in the same week the run has to close.
Holding both in one platform makes the LOP day an outcome of the leave ledger rather than a line somebody adds to it. That also means an application approved after the run has closed is visible as an arrear against a specific date, instead of a quiet correction next month.
Maternity leave under the Maternity Benefit Act, and leave taken while on ESI benefit, are entitlements the employer does not set and cannot reduce by policy. They are earned differently, approved differently and treated differently in payroll from casual or earned leave.
Keeping them as separate leave types rather than deductions from a common pool matters for two reasons. The employee's ordinary entitlement continues to accrue rather than being consumed, and the statutory absence is identifiable in the record when it has to be evidenced later.
The same logic applies to compensatory off. A comp-off is earned by working a day that was not a working day, which makes it a consequence of the attendance ledger rather than an allowance granted at someone's discretion, and it usually carries an expiry that a manual tracker forgets.
Leave quotas in India sit under state Shops and Establishments Acts and, for covered factories, the Factories Act. HRMagix is configured against those rules rather than a single national default.
Accrued monthly against service, with configurable carry-forward and encashment.
Configured per state establishment rules and company policy, with their own accrual behaviour.
Configured as a leave category with its own entitlement and approval path, tracked against the employee record.
Credited on approved weekend or holiday work, with expiry and consumption rules of its own.
Unpaid days flow directly into the month's payable-days figure, no separate register.
Rarely on an ordinary application. Almost always at a boundary, a joiner mid-month, a festival week, a year end, an exit.
Somebody joins in August. How much earned leave do they have in October, and does the probation policy change the answer?
Accrual runs pro-rata from the date of joining on the record, under the rule the policy sets for probationers. The balance is calculated rather than estimated, so nobody has to remember the joining date to answer the question.
Half a department applies for the same four days, and the approvals arrive in the manager's inbox one at a time with no view of the whole.
The team calendar shows the overlap at the point of approval rather than afterwards. The manager is making a staffing decision with the roster in front of them, which is a different decision from approving four separate requests in sequence.
A Pune office and a Chennai office observe different regional holidays, and one company-wide holiday list is wrong for both.
Holiday calendars are defined per location and attach to the employee record, so an employee sees the list that applies to where they work. Optional or floating holidays are held as an entitlement rather than a fixed date.
An employee resigns with an unused balance, some of it carried forward from last year, and the final settlement has to account for it.
The balance at the last working day is computed from the same ledger the year-end encashment uses, under the same rules, and passes into the full and final settlement as an input rather than a negotiation.
Attendance, leave and the rules that govern them.
Almost all of these arrive at a boundary, a joiner, a festival week, a year end, an exit.
Yes. Leave schemes and holiday calendars are configured per location and grade, which is what allows a company operating across states to hold different quotas and different regional holiday lists under one policy engine.
As a policy setting rather than a manual adjustment. Where the rule applies, intervening weekly offs and holidays are counted according to the configured policy for every employee equally, and the outcome is visible to the employee at the point of applying rather than discovered on the payslip.
Historical leave balances are imported alongside employee master data through the structured Excel templates, so accrual continues from the position you are actually in rather than restarting from zero.
By the rules the employer configures: a carry-forward cap, an optional separate cap on how much of that may be encashed, and the wage base encashment is computed on. The platform applies them to everyone on the same cut-off date and produces the encashment figures as a payroll input.
It becomes a loss-of-pay day, which reduces the paid days for the month and therefore the salary, the PF wage and, where applicable, the ESI contribution. Because leave and payroll read the same ledger, the LOP day is an outcome of the leave record rather than a figure typed into the run.
Yes. Maternity leave is a statutory entitlement under the Maternity Benefit Act rather than a draw on the company pool, so it is a distinct leave type. Ordinary entitlement continues to accrue through it, and the absence stays identifiable in the record for evidence later.
As an entitlement earned from the attendance ledger, a day worked that was not a working day, rather than a discretionary grant. It carries the expiry the policy sets, and lapses on that date rather than when someone notices.
Yes. Routing follows the rule rather than the hierarchy alone, so a second approver can be required above a threshold of days, and a delegate can be named for a period. What does not happen is a request sitting with someone who has left, because routing reads the current record.
Looking for a custom walkthrough or have specific statutory policy requirements? Connect with our product specialists in Pune for a 1-on-1 consultation.
A walkthrough against your own policies, with a dry-run before the first live cutoff.
14-day free trial · Full access to all 12 modules · Zero implementation fee · Cancel anytime