One ledger, no arguments
Leave policies run by rule — accrual, carry-forward, encashment and the sandwich question — against balances every employee can see for themselves. And the employee record behind it drafts itself from the joining documents instead of being typed.
The people side, kept straight
Leave Policies By Grade
Casual, sick, earned, comp-off and unpaid — with accrual, opening balances, carry-forward caps and encashment set per grade and entity.
Balances Everyone Trusts
One ledger. The employee sees the same number the approver sees, which ends most leave disputes before they start.
Onboarding That Drafts Itself
Forward the joining papers. Klok reads the Aadhaar, PAN and bank details, drafts the record, and waits for you to confirm.
Document Vault
Every document against the person it belongs to, with expiry tracking for the ones that lapse.
Employee Master
One record per person — grade, department, branch, reporting, salary history — with an assignment history you can trace back.
Exit, Handled Properly
Notice arithmetic, clearance and full-and-final flow through the same records, so the last salary is right the first time.
Almost every leave argument is about a number
The employee has one balance, from a message in March. HR has another, from a spreadsheet. The manager has a third, from memory. Nobody is lying and everybody is confident.
The fix is not a better policy. It is having one balance — computed by the engine from the policy for that person's grade and entity, and identical to the one payroll uses. When there is only one number, there is nothing to disagree about.
Policy layered, not duplicated
Company defaults, then grade, then entity. A rule stated once applies everywhere it is not deliberately overridden.
The alternative — six similar policies maintained separately — drifts. Not dramatically, and not all at once, but within two years nobody can say which one is authoritative, and the answer to a straightforward question depends on who you ask.
Cover is the actual decision
A manager approving leave is not really deciding whether the employee has the balance. They are deciding whether the team can spare them that week.
So who else is already away appears on the approval screen. Hiding it asks the manager to approve blind and discover the gap on the day, which is how a leave system becomes something operations works around rather than through.
Comp-off has to be real
Credited as a dated balance with its own expiry, by the supervisor who promised it, at the moment they promise it. Comp-off that lives in somebody's memory is the entitlement most likely to reappear as a claim at exit, with no way to settle it either way.
Apply, approve, done
They apply on the phone
The employee sees their real balance before applying, so the request that reaches you is already a sensible one.
You approve in a tap
The approver sees who else is out that day and what the balance becomes. WhatsApp or email tells them a request is waiting.
The register updates
Balance, attendance register and payroll input move together. No separate leave sheet to reconcile at month-end.
Leave questions we actually get
Our leave rules are unusual. Will they fit?
Policies are set per grade and entity — accrual rate, opening balance, carry-forward cap, encashment and whether holidays inside a leave count. Most Indian SMB rules are a combination of those settings rather than an exception.
Can we start mid-year with existing balances?
Yes. Opening balances import with the employee list, including negative ones, so you can go live in August without pretending the year began in April.
What about comp-off for people who worked a holiday?
Comp-off is credited as a real balance with an expiry, and spending it draws down the credit — not an informal promise someone has to remember.
Do we have to retype every employee record?
No. Import the Excel you already keep, or upload the joining documents and let the validator draft each record for you to confirm.
Who approves leave when the manager is away?
Approval chains carry cover and escalation, so an absent approver does not stall the request. Requests waiting on somebody on holiday is the most common complaint about leave workflow.
Can employees see their balance before applying?
Yes, and that single change removes most of the routine questions HR fields. Self-service fails when the balance shown is wrong, so the balance is derived rather than typed.
Do we have to use the same holiday list everywhere?
No. Holiday calendars are scoped by location and type, which matters the moment you have staff in more than one state.
Can we switch this module off if we do not need it?
Yes. Modules are switched on per company and what is off is not billed. There is no bundle you have to buy through to reach the part you actually want.
End the leave-balance argument
Import your people and last year’s balances, set the policy once, and let the ledger keep itself.