Kellith

Leave policy, applied without argument.

Define your leave types once. Employees request from their phone, approvers decide with balances and team context in front of them, and the result lands in attendance and payroll by itself.

What it does

Your policy, encoded

Casual, sick, earned, unpaid — leave types are yours to define, each with its own rules and balances tracked per person.

Requests from the pocket

Employees raise leave requests from the Kellith app and watch their status change. No forms, no corridor conversations, no lost email threads.

Approvals with context

Approvers see the balance, the dates and the team picture before deciding. Every decision is recorded on the audit trail automatically.

One decision, three ledgers

An approved request updates the balance, resolves the attendance days and reaches payroll — from a single approval, with no retyping.

Part of one system

Leave Management doesn’t work alone.

04

Payroll

Payroll leave outcomes carry into the pay run.

Questions, answered

Can we define our own leave types?

Yes. Leave types are configuration, not code — you define the kinds of leave your policy recognises, and balances are tracked per person against each type.

How do employees request leave?

From the Kellith employee app, or through the console. Requests carry their dates and type to the approver, and the outcome is visible to the employee the moment it is decided.

Does approved leave show up in attendance automatically?

Yes. Attendance and leave share the same day record, so an approved request resolves those days as leave — they can never be counted as absence by mistake.

Begin the conversation

See Kellith with your organisation’s names in it.

A thirty-minute walkthrough with your org structure, your leave policies and your payroll calendar — not a canned demo.

Already run on Kellith? Sign in to your console.