Payroll
Payroll runs and approvals are always on the trail.
Every consequential action in Kellith — a profile edit, a leave approval, a payroll run — lands on one activity trail, written automatically and readable by humans.
What it does
Directory changes, attendance corrections, leave decisions, payroll approvals — a single stream across the whole platform, not a log per feature.
Entries are enriched into plain language at the moment they are recorded — names, not IDs; actions, not table rows. The trail reads like a narrative, because for an auditor it is one.
Recording is part of how the platform executes actions, not a setting somebody can forget. If it happened in Kellith, it is on the trail.
The feed lives in the console and filters by person, module and time — so 'who approved this?' takes a minute, not a support ticket.
Part of one system
Payroll runs and approvals are always on the trail.
Leave Management every decision is recorded with its author.
Employee Directory profile changes tracked to the field.
Questions, answered
No. Recording is built into how the platform executes actions across every module — there is nothing to enable and nothing that can be quietly disabled.
Yes. Entries are enriched into plain language when they are recorded — an HR manager or an auditor can read the feed directly, without a developer translating identifiers.
Because HR records decide pay, leave and employment history. When a figure is questioned months later, the trail shows who changed what, when, and under which authority — evidence, not recollection.
Begin the conversation
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.