Why Leave and Attendance Have to Be One System

Companies usually solve attendance first and leave second, which is how the two end up in different tools. The consequence appears every month-end: attendance says an employee was absent on the 14th, the leave register says it was approved casual leave, and someone has to reconcile the two before salary can be processed.

When leave and attendance share one record, that reconciliation disappears. An approved leave day is not an absence — it is a paid day with a leave type attached, and the balance is deducted at approval rather than at month-end. An absence with no approved leave behind it becomes loss of pay automatically, with no one deciding case by case under time pressure.

This is also what makes rosters reliable. If the scheduling module can see approved leave, it can warn you the moment you assign someone to a shift they are already on leave for. Two systems cannot do this, which is why companies running separate tools discover the clash on the morning of the shift.

• Approved leave should mark the day as paid leave, not as an absence to reconcile
• Balances should be deducted at approval, not reconstructed at month-end
• Unapproved absence should become loss of pay without a manual decision
• The roster should warn about approved leave before you publish the week

Define Leave Types Before You Define Anything Else

Almost every messy leave setup traces back to leave types that were created casually. Indian companies typically run casual leave, sick leave, earned or privileged leave, and unpaid leave, with variations for maternity, paternity, compensatory off, and bereavement. Each of these behaves differently and the differences are what your configuration has to capture.

For each type, decide four things. Is it paid or unpaid. Does the balance accrue through the year or is it credited as a block at the start. Does an unused balance carry forward, and if so up to what cap. Can it be taken in half-day units. Getting these four right for each type removes most of the ambiguity that later becomes a dispute.

In Attend Mitra you configure leave types and then group them into leave policy templates, which is the part that saves real time. A factory-floor policy, a head-office policy, and a probation policy can each hold a different set of types with different entitlements. Templates are assigned to individual employees, to entire departments, to custom groups, or set as the company default, so a new joiner inherits the right policy without anyone remembering to configure them.

• Define paid versus unpaid, accrual versus block credit, carry-forward cap, and half-day rules per type
• Build policy templates rather than configuring entitlements employee by employee
• Assign templates by department, group, individual, or company default
• Set a company default so new joiners are never left without a policy

Accrual, Carry-Forward, and the Ledger That Settles Arguments

Accrual is where leave systems earn their keep. Manually crediting monthly leave for two hundred employees is both tedious and error-prone, and errors here surface months later as a disputed balance nobody can reconstruct. An accrual engine credits entitlement on the schedule you define and records each credit as a ledger entry.

Carry-forward needs an explicit cap and an explicit expiry, decided before year-end rather than during it. Attend Mitra applies carry-forward rules through the policy and processes accrual as recorded runs, so the year-end rollover is a repeatable operation rather than a spreadsheet exercise.

The ledger is the piece most teams underestimate. Every credit, every deduction, every manual adjustment, and every carry-forward entry is a line with a date and a reason. When an employee disputes a balance, you open the ledger and show the history instead of arguing from a single current number. Opening balances can be imported when you migrate from a previous system, so the ledger starts from your real position rather than from zero.

• Automate accrual so monthly credits are not applied by hand
• Set carry-forward caps and expiry rules in the policy before year-end
• Keep a ledger of every credit, deduction, adjustment, and carry-forward line
• Import opening balances at migration so history starts from reality
• Use adjustments with reasons rather than editing balances silently

Approvals That Match Your Actual Hierarchy

Single-step approval is fine until it is not. A shift supervisor can approve a day off; extended leave often needs a department head as well. Attend Mitra supports multi-level approval with permission checks at each level, so the routing reflects how decisions are actually made rather than flattening everything to one approver.

Speed matters as much as structure. A request that sits unseen for four days becomes an unplanned absence regardless of what the policy says. Managers receive push notifications and can approve or reject from the manager app, which is what turns a two-day turnaround into a two-minute one. Employees see status in their own app without having to ask.

Delegated administrators are the other half of this. Attend Mitra lets you create admin users with per-feature and per-department restrictions, so a branch manager can handle leave for their own department without seeing payroll or other branches. That is what makes approvals scale across locations without concentrating everything on one person at head office.

• Configure multi-level approval where extended leave needs a second approver
• Push notifications to managers so requests are actioned in minutes, not days
• Employees track request status in-app instead of following up manually
• Delegated admins scoped by department and feature keep approvals local

The Handoff to Payroll

The point of connecting leave and attendance is what happens at payroll. Paid days come from a single record set: days present with verified attendance, days on approved paid leave, holidays and declared closures from the company calendar, and week-offs from the roster. Anything left over is unapproved absence.

That remainder becomes a loss of pay adjustment in the payroll run rather than a manual deduction someone calculates. Because LOP is derived from records that supervisors already approved during the month, the conversation on payday is about the approval, not about the arithmetic — and the approval has a timestamp and an approver attached to it.

Public holidays and office closures belong in the company calendar rather than in each policy, so a declared closure is a paid non-working day everywhere at once. Setting the calendar for the year in January is a ten-minute task that removes a recurring monthly question.

• Paid days assembled from attendance, approved leave, holidays, and week-offs
• Unapproved absence flows into payroll as a loss of pay adjustment automatically
• Every LOP line traces back to a dated approval decision
• Maintain holidays and closures in the company calendar, not per policy
• Set the full-year calendar once instead of answering the question monthly